rfc9895.original.xml   rfc9895.xml 
<?xml version='1.0' encoding='utf-8'?> <?xml version='1.0' encoding='UTF-8'?>
<?xml-model href="rfc7991bis.rnc"?> <!-- Required for schema
validation and schema-aware editing -->
<!DOCTYPE rfc [ <!DOCTYPE rfc [
<!ENTITY filename "draft-ietf-manet-dlep-ether-credit-extension-09">
<!ENTITY nbsp "&#160;"> <!ENTITY nbsp "&#160;">
<!ENTITY zwsp "&#8203;"> <!ENTITY zwsp "&#8203;">
<!ENTITY nbhy "&#8209;"> <!ENTITY nbhy "&#8209;">
<!ENTITY wj "&#8288;"> <!ENTITY wj "&#8288;">
]> ]>
<!-- <?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?> -->
<!-- This third-party XSLT can be enabled for direct transformations
in XML processors, including most browsers -->
<!-- If further character entities are required then they should be
added to the DOCTYPE above. Use of an external entity file is not
recommended. -->
<?rfc toc="yes" ?> <rfc xmlns:xi="http://www.w3.org/2001/XInclude" category="std" ipr="trust200902"
<?rfc symrefs="yes" ?> docName="draft-ietf-manet-dlep-ether-credit-extension-09" number="9895" consens
<?rfc sortrefs="yes"?> us="true" obsoletes="" updates="" submissionType="IETF" xml:lang="en" tocInclude
<?rfc iprnotified="no" ?> ="true" symRefs="true" sortRefs="true" version="3">
<?rfc strict="yes" ?>
<rfc
xmlns:xi="http://www.w3.org/2001/XInclude"
category="std" ipr="trust200902"
docName="&filename;"
obsoletes="" updates=""
submissionType="IETF" xml:lang="en"
tocInclude="true" symRefs="true" sortRefs="true" version="3">
<front> <front>
<title abbrev="DLEP Ethernet Credit Extension">DLEP IEEE 802.1Q <title abbrev="DLEP Ethernet Credit Extension">Dynamic Link Exchange
Protocol (DLEP) IEEE 802.1Q
Aware Credit Window Extension</title> Aware Credit Window Extension</title>
<seriesInfo name="Internet-Draft"
value="&filename;"/> <!-- [rfced] Document title: FYI, for ease of the reader and per our process,
we expanded "DLEP" in the title. Please review.
Original:
DLEP IEEE 802.1Q Aware Credit Window Extension
Currently:
Dynamic Link Exchange Protocol (DLEP) IEEE 802.1Q Aware Credit Window
Extension -->
<seriesInfo name="RFC" value="9895"/>
<author initials="D." surname="Wiggins" fullname="David Wiggins"> <author initials="D." surname="Wiggins" fullname="David Wiggins">
<organization/> <organization/>
<address>
<email>david@none.org</email>
</address>
</author> </author>
<author initials="L." surname="Berger" fullname="Lou Berger"> <author initials="L." surname="Berger" fullname="Lou Berger">
<organization>LabN Consulting, L.L.C.</organization> <organization>LabN Consulting, L.L.C.</organization>
<address> <address>
<email>lberger@labn.net</email> <email>lberger@labn.net</email>
</address> </address>
</author> </author>
<author fullname="Donald E. Eastlake 3rd" initials="D." <author fullname="Donald E. Eastlake 3rd" initials="D." surname="Eastlake 3rd
surname="Eastlake" role="editor"> " role="editor">
<organization>Independent</organization> <organization>Independent</organization>
<address> <address>
<postal> <postal>
<street>2386 Panoramic Circle</street> <street>2386 Panoramic Circle</street>
<city>Apopka</city> <city>Apopka</city>
<region>Florida</region> <region>FL</region>
<code>32703</code> <code>32703</code>
<country>USA</country> <country>United States of America</country>
</postal> </postal>
<phone>+1-508-333-2270</phone> <phone>+1-508-333-2270</phone>
<email>d3e3e3@gmail.com</email> <email>d3e3e3@gmail.com</email>
</address> </address>
</author> </author>
<date/> <date month="November" year="2025"/>
<area>Routing</area> <area>RTG</area>
<workgroup>MANET</workgroup> <workgroup>manet</workgroup>
<!-- [rfced] Please insert any keywords (beyond those that appear in the
title) for use on <https://www.rfc-editor.org/search>. -->
<abstract> <abstract>
<t> <t>
This document defines an extension to the Dynamic Link Exchange Protocol (DLEP) that This document defines an extension to the Dynamic Link Exchange Protocol (DLEP) that
enables an Ethernet IEEE 802.1Q aware credit-window scheme for enables an Ethernet IEEE 802.1Q aware credit-window scheme for
destination-specific and shared flow control. destination-specific and shared flow control.
</t> </t>
</abstract> </abstract>
</front> </front>
<middle> <middle>
<section anchor="sec-1" numbered="true"> <section anchor="sec-1" numbered="true">
<name>Introduction</name> <name>Introduction</name>
<t> <t>
The Dynamic Link Exchange Protocol (DLEP) is defined in The Dynamic Link Exchange Protocol (DLEP) is defined in
<xref target="RFC8175"/>. The protocol provides the exchange of link rel ated <xref target="RFC8175"/>. The protocol provides the exchange of link-rel ated
control information between DLEP peers. DLEP peers control information between DLEP peers. DLEP peers
consist of a modem and a router. DLEP defines a base set of consist of a modem and a router. DLEP defines a base set of
mechanisms as well as support for possible extensions. This mechanisms as well as support for possible extensions. This
document defines one such extension. document defines one such extension.
</t> </t>
<t> <t>
The DLEP specification does not define any flow control The DLEP specification does not define any flow control
mechanisms. While various flow control techniques could be mechanisms. While in theory various flow control techniques could be
theoretically implemented with DLEP, this document specifies a implemented with DLEP, this document specifies a
DLEP extension that introduces an Ethernet-based flow control DLEP extension that introduces an Ethernet-based flow control
mechanism for traffic transmitted from a router to a modem. This mechanism for traffic transmitted from a router to a modem. This
mechanism utilizes one or more logical "Credit Windows", each of mechanism utilizes one or more logical "Credit Windows", each of
which is typically associated with a virtual or physical which is typically associated with a virtual or physical
queue. The router leverages traffic flow classification queue. The router leverages traffic flow classification
information provided by the modem to determine the appropriate information provided by the modem to determine the appropriate
credit window for a given traffic flow. Credit windows may be credit window for a given traffic flow. Credit windows may be
allocated on either a shared or a per-flow basis. For a allocated on either a shared or a per-flow basis. For a
DiffServ-based approach to credit window flow control, refer to Diffserv-based approach to credit window flow control, refer to
<xref target="I-D.ietf-manet-dlep-da-credit-extension"/>. As <xref target="RFC9894"/>. As
specified in Section 2.3.1 of <xref specified in <xref section="2.3.1" target="RFC9892"/>, when both
target="I-D.ietf-manet-dlep-traffic-classification"/>, when both Diffserv and Ethernet traffic classification are applied to a
DiffServ and Ethernet traffic classification are applied to a
flow, Ethernet-based classification takes precedence. flow, Ethernet-based classification takes precedence.
<!-- [rfced] Section 1: Are one or more words missing from this
sentence? If neither suggestion below is correct, please clarify
what is shared.
Original:
Credit windows
may be allocated on either a shared or a per-flow basis.
Suggestion #1 (flows are shared):
Credit windows
may be allocated on either a shared-flow or per-flow basis.
Suggestion #2 (windows are shared):
Credit windows
may be allocated on either a shared-window or per-flow basis. -->
</t> </t>
<t> <t>
This document leverages the traffic classification and credit This document leverages the traffic classification and credit
window control mechanisms defined in <xref window control mechanisms defined in <xref target="RFC9892"/> and <xref
target="I-D.ietf-manet-dlep-traffic-classification"/> and <xref target="RFC9893"/> to enable
target="I-D.ietf-manet-dlep-credit-flow-control"/> to enable credit-window-based flow control based on DLEP destinations,
credit window-based flow control based on DLEP destinations, Ethernet Virtual Local Area Networks (VLANs), and Priority Code Points (
Ethernet VLANs, and Priority Code Points (PCPs). Ethernet PCP PCPs). Ethernet PCP
support is specified as part of the IEEE 802.1Q <xref support is specified as part of the IEEE 802.1Q tag format <xref target=
target="IEEE8021Q"/> tag format, which includes a 3-bit "PCP" "IEEE8021Q"/>, which includes a 3-bit "PCP"
field. The tag format also incorporates a 12-bit "VLAN field. The tag format also incorporates a 12-bit "VLAN
Identifier (VID)" field. Identifier (VID)" field.
</t> </t>
<t> <t>
The defined mechanism allows credit windows to be shared across The defined mechanism allows credit windows to be shared across
traffic destined for multiple DLEP destinations, Virtual Local traffic destined for multiple DLEP destinations, VLANs, and PCPs, or to
Area Networks (VLANs), and PCPs, or to be dedicated exclusively be dedicated exclusively
to traffic associated with a specific destination, VLAN, and/or to traffic associated with a specific destination, VLAN, and/or
PCP. Additionally, this extension supports "wildcard" matching PCP. Additionally, this extension supports "wildcard" matching
for any PCP or VID. for any PCP or VID.
</t> </t>
<t> <t>
The extension defined in this document is referred to as "IEEE The extension defined in this document is referred to as the "IEEE
802.1Q Aware Credit Window" or, more simply, the "Ethernet 802.1Q Aware Credit Window" or, more simply, the "Ethernet
Credit" extension. The reader should be familiar with both the Credit" extension. The reader should be familiar with both the
traffic classification and credit window control mechanisms traffic classification and credit window control mechanisms
defined in <xref target="I-D.ietf-manet-dlep-traffic-classification"/> defined in <xref target="RFC9892"/>
and <xref target="I-D.ietf-manet-dlep-credit-flow-control"/>. and <xref target="RFC9893"/>.
</t> </t>
<t> <t>
This document defines a new DLEP Extension Type Value in <xref This document defines a new DLEP Extension Type Value that is used to in
target="sec-ext-type"/> which is used to indicate support for dicate support for the extension. See <xref target="sec-ext-type"/>.
the extension.
</t> </t>
<section anchor="sec-1.1" numbered="true"> <section anchor="sec-1.1" numbered="true">
<name>Key Words</name> <name>Key Words</name>
<t> <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>",
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>",
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT "<bcp14>SHALL NOT</bcp14>", "<bcp14>SHOULD</bcp14>",
RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be "<bcp14>SHOULD NOT</bcp14>",
interpreted as described in BCP 14 <xref target="RFC2119"/> "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
<xref target="RFC8174"/> when, and only when, they appear in "<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document
all capitals, as shown here. are to be interpreted as described in BCP&nbsp;14
</t> <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only
when, they appear in all capitals, as shown here.</t>
</section> </section>
</section> </section>
<section anchor="sec-ext-type" numbered="true"> <section anchor="sec-ext-type" numbered="true">
<name>Extension Usage and Identification</name> <name>Extension Usage and Identification</name>
<t> <t>
The extension defined in this document is composed of the The extension defined in this document is composed of the
mechanisms and processing defined in <xref mechanisms and processing defined in <xref target="RFC9892"/> and <xref
target="I-D.ietf-manet-dlep-traffic-classification"/> and <xref target="RFC9893"/>. To indicate
target="I-D.ietf-manet-dlep-credit-flow-control"/>. To indicate
that the IEEE 802.1Q Aware Credit Window Extension is to be that the IEEE 802.1Q Aware Credit Window Extension is to be
used, an implementation MUST include the IEEE 802.1Q Aware used, an implementation <bcp14>MUST</bcp14> include the IEEE 802.1Q Awar
Credit Window Type Value in the Extensions Supported Data Item. e
Credit Window Type Value in the Extensions Supported Data Item (see
<xref target="RFC8175" section="13.6"/>).
The Extensions Supported Data Item is sent and processed The Extensions Supported Data Item is sent and processed
according to <xref target="RFC8175"/>. Any implementation that according to <xref target="RFC8175"/>. Any implementation that
indicates use of the IEEE 802.1Q Aware Credit Window Extension indicates the use of the IEEE 802.1Q Aware Credit Window Extension
MUST support all Messages, Data Items, the Ethernet Traffic <bcp14>MUST</bcp14> support all message types, Data Items, the Ethernet
Traffic
Classification Sub-Data Item, and all related processing defined Classification Sub-Data Item, and all related processing defined
in <xref target="I-D.ietf-manet-dlep-traffic-classification"/> in <xref target="RFC9892"/>
and <xref target="I-D.ietf-manet-dlep-credit-flow-control"/>. and <xref target="RFC9893"/>.
</t> </t>
<t> <t>
The IEEE 802.1Q Aware Credit Window Extension Type Value is The IEEE 802.1Q Aware Credit Window Extension Type Value is
TBA1, see <xref target="sec-iana"/>. 5. See <xref target="sec-iana"/>.
</t> </t>
</section> </section>
<section anchor="sec-mgmnt" numbered="true"> <section anchor="sec-mgmnt" numbered="true">
<name>Management Considerations</name> <name>Management Considerations</name>
<t> <t>
This section provides several network management guidelines to This section provides several network management guidelines for
implementations supporting the IEEE 802.1Q Aware Credit Window implementations supporting the IEEE 802.1Q Aware Credit Window
Extension. Extension.
</t> </t>
<t> <t>
If this extension is supported, that support MUST be declared If this extension is supported, that support <bcp14>MUST</bcp14> be decl
using the Extensions Supported Data Item (see Section 13.6 of ared
<xref target="RFC8175"/>) which is configurable on both modems using the Extensions Supported Data Item (see
and routers. DiffServ Aware Credit Window Extension Data Items <xref target="RFC8175" section="13.6"/>), which is configurable on both
MUST NOT be emitted by a DLEP participant unless such support modems
and routers. Diffserv Aware Credit Window Extension Data Items
<bcp14>MUST NOT</bcp14> be emitted by a DLEP participant unless such sup
port
was specified in the initialization message received from its was specified in the initialization message received from its
peer. The use of the extension defined in this document SHOULD peer. The use of the extension defined in this document <bcp14>SHOULD</ bcp14>
be configurable on both modems and routers. be configurable on both modems and routers.
</t> </t>
<t> <t>
Modems SHOULD support the configuration of PCP to credit window Modems <bcp14>SHOULD</bcp14> support the configuration of mapping a PCP
(queue) mapping. to a credit window (queue).
</t> </t>
<t> <t>
Modems MAY support the configuration of PCP to credit window Modems <bcp14>MAY</bcp14> support the configuration of mapping a PCP to
(queue) mapping on a per VLAN basis. VID value zero (0) is used a credit window (queue) on a per-VLAN basis. VID value zero (0) is used
by <xref target="I-D.ietf-manet-dlep-traffic-classification"/> by <xref target="RFC9892"/>
to indicate that VID is ignored and any VID value is used in to indicate that the VID is ignored and any VID value is used in
traffic classification. traffic classification.
</t> </t>
<t> <t>
When VLANs are supported by a modem without support from PCPs, When VLANs are supported by a modem without support from PCPs,
the modem SHOULD support the configuration of VLAN to credit window the modem <bcp14>SHOULD</bcp14> support the configuration of mapping a VL
(queue) mapping. AN to a credit window (queue).
</t> </t>
<t> <t>
Modems MAY support configuration of the number of credit windows Modems <bcp14>MAY</bcp14> support the configuration of the number of cre dit windows
(queues) that they advertise to a router. (queues) that they advertise to a router.
</t> </t>
<t> <t>
Routers may impose limitations on the number of queues they can Routers may impose limitations on the number of queues they can
support and on the allowable credit window configurations. In support and on the allowable credit window configurations. In
some cases, per-destination queues may not be supported. If the some cases, per-destination queues may not be supported. If the
credit window information provided by the modem exceeds the credit window information provided by the modem exceeds the
router's capabilities, the router SHOULD utilize a subset of the router's capabilities, the router <bcp14>SHOULD</bcp14> utilize a subset
advertised credit windows. Alternatively, the router MAY reset of the
advertised credit windows. Alternatively, the router <bcp14>MAY</bcp14>
reset
the session and indicate that the extension is not supported. In the session and indicate that the extension is not supported. In
either case, any mismatch in capabilities SHOULD be reported to either case, any mismatch in capabilities <bcp14>SHOULD</bcp14> be repor ted to
the user through standard network management mechanisms, such as the user through standard network management mechanisms, such as
user interface notifications or error logging. user interface notifications or error logging.
</t> </t>
<t> <t>
Regardless of implementation, if credit windows are in use, the Regardless of implementation, if credit windows are in use, the
router MUST NOT send traffic to the modem unless sufficient router <bcp14>MUST NOT</bcp14> send traffic to the modem unless sufficie nt
credits are available. credits are available.
</t> </t>
</section> </section>
<section anchor="sec-sec" numbered="true"> <section anchor="sec-sec" numbered="true">
<name>Security Considerations</name> <name>Security Considerations</name>
<t> <t>
This document defines a DLEP extension that uses DLEP mechanisms This document defines a DLEP extension that uses DLEP mechanisms
and the credit window control and flow mechanisms defined in and the credit window control and flow mechanisms defined in
<xref target="I-D.ietf-manet-dlep-traffic-classification"/> and <xref target="RFC9892"/> and
<xref target="I-D.ietf-manet-dlep-credit-flow-control"/>. See <xref target="RFC9893"/>. See
also the Security Considerations sections of those documents. also the Security Considerations sections of those documents.
</t> </t>
<t> <t>
The defined extension is exposed to vulnerabilities similar to The defined extension is exposed to vulnerabilities similar to
existing DLEP messages and discussed in the Security existing DLEP messages and discussed in the Security
Considerations section of <xref target="RFC8175"/> such as an Considerations section of <xref target="RFC8175"/>, such as an
injected message resizing a credit window to a value that injected message resizing a credit window to a value that
results in a denial of service. The security mechanisms results in a denial of service. The security mechanisms
documented in <xref target="RFC8175"/> can be applied equally to documented in <xref target="RFC8175"/> can be applied equally to
the mechanism defined in this document. the mechanism defined in this document.
</t> </t>
<t> <t>
Wildcards for matching PCP and VID fields are provided which may Wildcards for matching PCP and VID fields are provided. Note that wildcar
be convenient to match a number of packet flows but could ds may
be convenient for matching a number of packet flows but could
inadvertently match unexpected flows or new flows that appear inadvertently match unexpected flows or new flows that appear
after the wildcard matching has been set up. It is therefore after the wildcard matching has been set up. It is therefore
RECOMMENDED that wildcards not be used unless clearly needed. <bcp14>RECOMMENDED</bcp14> that wildcards not be used unless clearly need ed.
</t> </t>
</section> </section>
<section anchor="sec-iana" numbered="true"> <section anchor="sec-iana" numbered="true">
<name>IANA Considerations</name> <name>IANA Considerations</name>
<t> <t>
IANA is requested to assign one code point in the "Extension Type IANA has assigned the following code point in the "Extension Type
Values" registry in the "Dynamic Link Exchange Protocol (DLEP) Values" registry in the "Dynamic Link Exchange Protocol (DLEP)
Parameters" registry group as follows: Parameters" registry group:
</t> </t>
<t keepWithNext="true"/>
<table anchor="table_et" align="center"> <table anchor="table_et" align="center">
<name>Requested Extension Type Value</name> <name>Extension Type Value</name>
<thead> <thead>
<tr> <tr>
<th align="left">Code</th> <th align="left">Code</th>
<th align="left">Description</th> <th align="left">Description</th>
</tr> </tr>
</thead> </thead>
<tbody> <tbody>
<tr> <tr>
<td align="left">TBA1</td> <td align="left">5</td>
<td align="left">IEEE 802.1Q Aware Credit Window</td> <td align="left">IEEE 802.1Q Aware Credit Window</td>
</tr> </tr>
</tbody> </tbody>
</table> </table>
<t keepWithPrevious="true"/>
</section> </section>
</middle> </middle>
<back> <back>
<references> <references>
<name>References</name> <name>References</name>
<references> <references>
<name>Normative References</name> <name>Normative References</name>
<reference anchor="IEEE8021Q" target="https://ieeexplore.ieee.org/document /8403927" quoteTitle="true"> <reference anchor="IEEE8021Q" target="https://ieeexplore.ieee.org/document /10004498" quoteTitle="true">
<front> <front>
<title>IEEE Standard for Local and Metropolitan Area <title>IEEE Standard for Local and Metropolitan Area
Networks--Bridges and Bridged Networks</title> Networks--Bridges and Bridged Networks</title>
<author> <author>
<organization showOnFrontPage="true">IEEE</organization> <organization>IEEE</organization>
</author> </author>
<date month="July" year="2022"/> <date month="December" year="2022"/>
</front> </front>
<seriesInfo name="DOI" value="10.1109/IEEESTD.2022.10004498"/> <seriesInfo name="DOI" value="10.1109/IEEESTD.2022.10004498"/>
<seriesInfo name="IEEE" value="802.1Q-2022"/> <seriesInfo name="IEEE Std" value="802.1Q-2022"/>
</reference> </reference>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.211 9.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.211 9.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.817 4.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.817 4.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.817 5.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.817 5.xml"/>
<reference anchor="I-D.ietf-manet-dlep-credit-flow-control" <!-- draft-ietf-manet-dlep-credit-flow-control-19 (9893) -->
target="https://datatracker.ietf.org/doc/draft-ietf-manet-dlep-c <reference anchor="RFC9893" target="https://www.rfc-editor.org/info/rfc9
redit-flow-control"> 893">
<front> <front>
<title>Dynamic Link Exchange Protocol (DLEP) Credit-Based Flow <title>Dynamic Link Exchange Protocol (DLEP) Credit-Based Flow Contr
Control Messages and Data Items</title> ol Messages and Data Items</title>
<author fullname="Bow-Nan Cheng" initials="B." <author initials="B." surname="Cheng" fullname="Bow-Nan Cheng">
surname="Cheng"> <organization>MIT Lincoln Laboratory</organization>
<organization>MIT Lincoln Laboratory</organization> </author>
</author> <author initials="D." surname="Wiggins" fullname="David Wiggins">
<author fullname="David Wiggins" initials="D." </author>
surname="Wiggins"/> <author initials="S." surname="Ratliff" fullname="Stan Ratliff">
<author fullname="Lou Berger" initials="L." surname="Berger"> </author>
<organization>LabN Consulting, L.L.C.</organization> <author initials="L." surname="Berger" fullname="Lou Berger">
</author> <organization>LabN Consulting, L.L.C.</organization>
<author fullname="Stan Ratliff" initials="S." </author>
surname="Ratliff"/> <author initials="E." surname="Kinzie" fullname="Eric Kinzie" role="
<author fullname="Eric Kinzie" initials="E." surname="Kinzie"> editor">
<organization>LabN Consulting, L.L.C.</organization> <organization>LabN Consulting, L.L.C.</organization>
</author> </author>
<date day="3" month="January" year="2025"/> <date month="November" year="2025" />
</front> </front>
<seriesInfo name="Internet-Draft" <seriesInfo name="RFC" value="9893"/>
value="draft-ietf-manet-dlep-credit-flow-control"/> <seriesInfo name="DOI" value="10.17487/RFC9893"/>
</reference> </reference>
<reference anchor="I-D.ietf-manet-dlep-traffic-classification"
target="https://datatracker.ietf.org/doc/draft-ietf-manet-dlep-t
raffic-classification">
<front>
<title>Dynamic Link Exchange Protocol (DLEP) Traffic
Classification Data Item</title>
<author fullname="Bow-Nan Cheng" initials="B."
surname="Cheng">
<organization>MIT Lincoln Laboratory</organization>
</author>
<author fullname="David Wiggins" initials="D."
surname="Wiggins"/>
<author fullname="Lou Berger" initials="L." surname="Berger">
<organization>LabN Consulting, L.L.C.</organization>
</author>
<author fullname="Don Fedyk" initials="D." surname="Fedyk">
<organization>LabN Consulting, L.L.C.</organization>
</author>
<date day="19" month="November" year="2024"/>
</front>
<seriesInfo name="Internet-Draft"
value="draft-ietf-manet-dlep-traffic-classification"/>
</reference>
<!-- draft-ietf-manet-dlep-traffic-classification-17 (9892) -->
<reference anchor="RFC9892" target="https://www.rfc-editor.org/info/rfc9
892">
<front>
<title>Dynamic Link Exchange Protocol (DLEP) Traffic Classification
Data Item</title>
<author initials="B." surname="Cheng" fullname="Bow-Nan Cheng">
<organization>MIT Lincoln Laboratory</organization>
</author>
<author initials="D." surname="Wiggins" fullname="David Wiggins">
</author>
<author initials="L." surname="Berger" fullname="Lou Berger">
<organization>LabN Consulting, L.L.C.</organization>
</author>
<author initials="D." surname="Fedyk" fullname="Don Fedyk" role="edi
tor">
<organization>LabN Consulting, L.L.C.</organization>
</author>
<date month='November' year='2025'/>
</front>
<seriesInfo name="RFC" value="9892"/>
<seriesInfo name="DOI" value="10.17487/RFC9892"/>
</reference>
</references> </references>
<references> <references>
<name>Informative References</name> <name>Informative References</name>
<reference anchor="I-D.ietf-manet-dlep-da-credit-extension" <!-- draft-ietf-manet-dlep-da-credit-extension-21 (RFC 9894) -->
target="https://datatracker.ietf.org/doc/draft-ietf-manet-dlep <reference anchor="RFC9894" target="https://www.rfc-editor.org/info/rfc9894">
-da-credit-extension/"> <front>
<front> <title>Dynamic Link Exchange Protocol (DLEP) Diffserv Aware Credit Window
<title>DLEP DiffServ Aware Credit Window Extension</title> Extension</title>
<author fullname="Bow-Nan Cheng" initials="B." <author initials="B." surname="Cheng" fullname="Bow-Nan Cheng">
surname="Cheng"> <organization>MIT Lincoln Laboratory</organization>
<organization>MIT Lincoln Laboratory</organization> </author>
</author> <author initials="D." surname="Wiggins" fullname="David Wiggins">
<author fullname="David Wiggins" initials="D." </author>
surname="Wiggins"/> <author initials="L." surname="Berger" fullname="Lou Berger">
<author fullname="Lou Berger" initials="L." <organization>LabN Consulting, L.L.C.</organization>
surname="Berger"> </author>
<organization>LabN Consulting, L.L.C.</organization> <author initials="D." surname="Eastlake 3rd" fullname="Donald E. Eastlake
</author> 3rd" role="editor">
<author fullname="Donald E. Eastlake 3rd" initials="D. E." <organization>Independent</organization>
surname="Eastlake"> </author>
<organization>Independent</organization> <date month="November" year="2025" />
</author> </front>
<date day="15" month="December" year="2024"/> <seriesInfo name="RFC" value="9894"/>
</front> <seriesInfo name="DOI" value="10.17487/RFC9894"/>
<seriesInfo name="Internet-Draft" </reference>
value="draft-ietf-manet-dlep-da-credit-extension"/>
</reference>
</references> </references>
</references> </references>
<section numbered="true"> <section numbered="false">
<name>Acknowledgments</name> <name>Acknowledgments</name>
<t> <t>
The document was motivated by discussions in the MANET working This document was motivated by discussions in the MANET Working
group. Many useful comments were received from contributors to Group. Many useful comments were received from contributors to
the MANET working group, notably Ronald in't Velt. the MANET Working Group, notably <contact fullname="Ronald in 't Velt"/>
.
</t> </t>
<t> <t>
We had the honor of working too briefly with David Wiggins on We had the honor of working too briefly with <contact fullname="David Wi ggins"/> on
this and related DLEP work. His contribution to the IETF and this and related DLEP work. His contribution to the IETF and
publication of the first and definitive open source DLEP publication of the first and definitive open-source DLEP
implementation have been critical to the acceptance of DLEP. We implementation have been critical to the acceptance of DLEP. We
mourn his passing on November 23, 2023. We wish to recognize his mourn his passing on November 26, 2023. We wish to recognize his
guidance, leadership and professional excellence. We were guidance, leadership, and professional excellence. We were
fortunate to benefit from his leadership and friendship. He fortunate to benefit from his leadership and friendship. He
shall be missed. shall be missed.
</t> </t>
</section> </section>
</back> </back>
<!-- [rfced] Please review the "Inclusive Language" portion of the
online Style Guide at
<https://www.rfc-editor.org/styleguide/part2/#inclusive_language>,
and let us know if any changes are needed. Updates of this nature
typically result in more precise language, which is helpful for readers.
Note that our script did not flag any words in particular, but this
should still be reviewed as a best practice. -->
<!-- [rfced] The following term appears to be used inconsistently in
this document. Please let us know which form is preferred.
IEEE 802.1Q Aware Credit Window Type Value /
IEEE 802.1Q Aware Credit Window Extension Type Value -->
</rfc> </rfc>
 End of changes. 60 change blocks. 
194 lines changed or deleted 227 lines changed or added

This html diff was produced by rfcdiff 1.48.