rfc9894.original.xml		rfc9894.xml
	<?xml version='1.0' encoding='utf-8'?>		<?xml version='1.0' encoding='UTF-8'?>
	<!DOCTYPE rfc [		<!DOCTYPE rfc [
	<!ENTITY filename "draft-ietf-manet-dlep-da-credit-extension-21">		<!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' ?>
	<?rfc toc="yes" ?>		<rfc xmlns:xi="http://www.w3.org/2001/XInclude" category="std" ipr="trust200902"
	<?rfc symrefs="yes" ?>		docName="draft-ietf-manet-dlep-da-credit-extension-21" number="9894" consensus=
	<?rfc sortrefs="yes"?>		"true" obsoletes="" updates="" submissionType="IETF" xml:lang="en" tocInclude="t
	<?rfc iprnotified="no" ?>		rue" 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">
	<!-- xml2rfc v2v3 conversion 3.19.4 -->
	<front>		<front>
	<title abbrev="DLEP DA Credit Extension">DLEP DiffServ Aware Credit		<title abbrev="DLEP DA Credit Extension">Dynamic Link Exchange Protocol (DLE P) Diffserv Aware Credit
	Window Extension</title>		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 DiffServ Aware Credit Window Extension
			Currently:
			Dynamic Link Exchange Protocol (DLEP) Diffserv Aware Credit Window
			Extension
			-->
			<seriesInfo name="RFC" value="9894"/>
	<author initials="B." surname="Cheng" fullname="Bow-Nan Cheng">		<author initials="B." surname="Cheng" fullname="Bow-Nan Cheng">
	<organization>MIT Lincoln Laboratory</organization>		<organization>MIT Lincoln Laboratory</organization>
	<address>		<address>
	<postal>		<postal>
	<street>Massachusetts Institute of Technology</street>		<street>Massachusetts Institute of Technology</street>
	<street>244 Wood Street</street>		<street>244 Wood Street</street>
	<city>Lexington</city>		<city>Lexington</city>
	<region>MA</region>		<region>MA</region>
	<code>02421-6426</code>		<code>02421-6426</code>
			<country>United States of America</country>
	</postal>		</postal>
	<email>bcheng@ll.mit.edu</email>		<email>bcheng@ll.mit.edu</email>
	</address>		</address>
	</author>		</author>
	<author initials="D." surname="Wiggins" fullname="David Wiggins">		<author initials="D." surname="Wiggins" fullname="David Wiggins">
	<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" role="editor">		surname="Eastlake 3rd" 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>. -->
			<!-- [rfced] For ease of the reader, we expanded "CLI" where first
			used, per Section 3.6 of RFC 7322 ("RFC Style Guide" -
			<https://www.rfc-editor.org/info/rfc7322>). Please review, and
			let us know any objections.
			CLI: Command-Line Interface -->
	<abstract>		<abstract>
	<t>		<t>
	This document defines an extension to the Dynamic Link Exchange		This document defines an extension to the Dynamic Link Exchange
	Protocol (DLEP) that enables a DiffServ aware credit-window scheme		Protocol (DLEP) that enables a Diffserv aware credit-window scheme
	for destination-specific and shared flow control.		for destination-specific and shared flow control.
	</t>		</t>
	</abstract>		</abstract>
	</front>		</front>
	<middle>		<middle>
	<section anchor="sec-1" numbered="true" toc="default">		<section anchor="sec-1" numbered="true" toc="default">
	<name>Introduction</name>		<name>Introduction</name>
	<t>		<t>
	The Dynamic Link Exchange Protocol (DLEP) is defined in <xref		The Dynamic Link Exchange Protocol (DLEP) is defined in <xref
	target="RFC8175"/>. The protocol provides the exchange of link		target="RFC8175"/>. The protocol provides the exchange of link-related contro
	related control information between DLEP peers. DLEP peers consist of		l information between DLEP peers. DLEP peers consist of
	a modem and a router. DLEP defines a base set of mechanisms as well		a modem and a router. DLEP defines a base set of mechanisms as well
	as support for possible extensions. This document defines one such		as support for possible extensions. This document defines one such
	extension.		extension.
	</t>		</t>
	<t>		<t>
	The DLEP specification does not include any flow control capability.		The DLEP specification does not include any flow control capability.
	There are various flow control techniques theoretically possible with		Various flow control techniques are theoretically possible with
	DLEP. This document defines a DLEP extension which provides a		DLEP. This document defines a DLEP extension that provides a
	DiffServ-based flow control mechanism for traffic sent from a router		Diffserv-based flow control mechanism for traffic sent from a router
	to a modem. Flow control is provided using one or more logical "Credit		to a modem. Flow control is provided using one or more logical "Credit
	Windows", each of which will typically be supported by an associated		Windows", each of which will typically be supported by an associated
	virtual or physical queue. A router will use traffic flow		virtual or physical queue. A router will use traffic flow
	classification information provided by the modem to identify which		classification information provided by the modem to identify which
	traffic is associated with each credit window. Credit windows may be		traffic is associated with each credit window. Credit windows may be
	shared or dedicated on a per-flow basis. See <xref		shared or dedicated on a per-flow basis. See <xref
	target="I-D.ietf-manet-dlep-ether-credit-extension"/> for an		target="RFC9895"/> for an
	Ethernet-based version of credit window flow control. As specified in		Ethernet-based version of credit window flow control. As specified in
	Section 2.3.1 of <xref		<xref section="2.3.1"
	target="I-D.ietf-manet-dlep-traffic-classification"/>, when both		target="RFC9892"/>, when both
	DiffServ and Ethernet traffic classification are specified for a flow,		Diffserv and Ethernet traffic classification are specified for a flow,
	the Ethernet information takes precedence.		the Ethernet information takes precedence.
	</t>		</t>
	<t>		<t>
	This document uses the traffic classification and credit window		This document uses the traffic classification and credit window
	control mechanisms defined in <xref		control 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"/> to provide credit		target="RFC9893"/> to provide credit-window-based flow control based on DLEP d
	window based flow control based on DLEP destinations and DiffServ		estinations and Differentiated Services Code Points (DSCPs) <xref target="RFC247
	<xref target="RFC2475"/> DSCPs (differentiated services codepoints).		5"/>.
	The defined mechanism allows for credit windows to be shared across		The defined mechanism allows for credit windows to be shared across
	traffic sent to multiple DLEP destinations and DSCPs, or used		traffic sent to multiple DLEP destinations and DSCPs, or used
	exclusively for traffic sent to a particular destination and/or DSCP.		exclusively for traffic sent to a particular destination and/or DSCP.
	The extension also supports the "wildcard" matching of any DSCP.		The extension also supports the "wildcard" matching of any DSCP.
	</t>		</t>
	<t>		<t>
	The extension defined in this document is referred to as "DiffServ		The extension defined in this document is referred to as the "Diffserv
	Aware Credit Window" or, more simply, the "DA Credit" extension. The		Aware Credit Window" or, more simply, the "DA Credit" extension. The
	reader should be familiar with both the traffic classification and		reader should be familiar with both the traffic classification and
	credit window control mechanisms defined in <xref		credit window control 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"/>.		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
	target="sec-ext-type"/> which is used to indicate support for the		that is used to indicate support for the
	extension.		extension. See <xref target="sec-ext-type"/>.
	</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 NOT",		"<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and		"<bcp14>SHALL NOT</bcp14>", "<bcp14>SHOULD</bcp14>",
	"OPTIONAL" in this document are to be interpreted as described in BCP		"<bcp14>SHOULD NOT</bcp14>",
	14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only		"<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
	when, they appear in all capitals, as shown here.		"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document
	</t>		are to be interpreted as described in BCP&nbsp;14
			<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 mechanisms		The extension defined in this document is composed of the mechanisms
	and processing defined in <xref		and processing 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"/>. To indicate that		target="RFC9893"/>. To indicate that
	the DiffServ Aware Credit Window Extension is to be used, an		the Diffserv Aware Credit Window Extension is to be used, an
	implementation MUST include the DiffServ Aware Credit Window Type		implementation <bcp14>MUST</bcp14> include the Diffserv Aware Credit Window T
	Value in the Extensions Supported Data Item (see Section 13.6 of		ype
	<xref target="RFC8175"/>). The Extensions Supported Data Item is		Value in the Extensions Supported Data Item (see
			<xref target="RFC8175" section="13.6"/>). The Extensions Supported Data Item
			is
	sent and processed according to <xref target="RFC8175"/>. Any		sent and processed according to <xref target="RFC8175"/>. Any
	implementation that indicates use of the DiffServ Aware Credit Window		implementation that indicates the use of the Diffserv Aware Credit Window
	Extension MUST support all Messages, Data Items, the DiffServ Traffic		Extension <bcp14>MUST</bcp14> support all message types, Data Items, the Diff
			serv Traffic
	Classification Sub-Data Item, and all related processing defined in		Classification Sub-Data Item, and all related processing defined in
	<xref target="I-D.ietf-manet-dlep-traffic-classification"/> and <xref		<xref target="RFC9892"/> and <xref
	target="I-D.ietf-manet-dlep-credit-flow-control"/>.		target="RFC9893"/>.
	</t>		</t>
	<t>		<t>
	The DiffServ Aware Credit Window Extension Type Value is TBA1, see		The Diffserv Aware Credit Window Extension Type Value is 6. See
	<xref target="sec-iana"/>.		<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		This section provides several network management guidelines
	to implementations supporting the DiffServ Aware Credit Window		for implementations supporting the Diffserv 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 declared
	using the Extensions Supported Data Item (see Section 13.6 of		using the Extensions Supported Data Item (see
	<xref target="RFC8175"/>). DiffServ Aware Credit Window Extension		<xref target="RFC8175" section="13.6"/>). Diffserv Aware Credit Window Exten
	Data Items MUST NOT be emitted by a DLEP participant unless such		sion
			Data Items <bcp14>MUST NOT</bcp14> be emitted by a DLEP participant unless s
			uch
	support was specified in the initialization message received from		support was specified in the initialization message received from
	its peer. The use of the extension defined in this document		its peer. The use of the extension defined in this document
	SHOULD be configurable on both modems and routers. That		<bcp14>SHOULD</bcp14> be configurable on both modems and routers. That
	configuration can be implemented using a proprietary CLI or by		configuration can be implemented using a proprietary Command-Line Interface
			(CLI) or by
	implementing a YANG module. The definition of the YANG module is		implementing a YANG module. The definition of the YANG module is
	out of the scope of this document.		out of scope for this document.
	</t>		</t>
	<t>		<t>
	Modems SHOULD support the configuration of DSCP to credit		Modems <bcp14>SHOULD</bcp14> support the configuration of mapping a DSCP to
	window (queue) mapping.		a credit window (queue).
	</t>		</t>
	<t>		<t>
	Modems MAY support the configuration of the number of credit		Modems <bcp14>MAY</bcp14> support the configuration of the number of credit
	windows (queues) to advertise to a router.		windows (queues) to advertise to a router.
	</t>		</t>
	<t>		<t>
	Routers may have limits on the number of queues that they can		Routers may have limits on the number of queues that they can
	support and limits on supported credit window combinations. Per		support and limits on supported credit window combinations.
	destination queues might not be supported at all. When		Per-destination queues might not be supported at all. When
	modem-provided credit window information exceeds the capabilities of		credit window information provided by a modem exceeds the capabilities of
	a router, the router SHOULD use a subset of the provided credit		a router, the router <bcp14>SHOULD</bcp14> use a subset of the provided cred
	windows. Alternatively, a router MAY reset the session and indicate		it
	that the extension is not supported. In either case, the mismatch		windows. Alternatively, a router <bcp14>MAY</bcp14> reset the session and i
	of capabilities SHOULD be reported to the user via normal network		ndicate
	management mechanisms such as user interface messages or error		that the extension is not supported. In either case, any mismatch
			in capabilities <bcp14>SHOULD</bcp14> be reported to the user via normal net
			work
			management mechanisms, such as user interface messages or error
	logging.		logging.
			<!-- [rfced] Section 3: We changed "the mismatch of capabilities" to
			"any mismatch in capabilities" per
			draft-ietf-manet-dlep-ether-credit-extension. Please let us know any
			objections.
			Original:
			In either case, the mismatch of capabilities SHOULD be
			reported to the user via normal network management mechanisms such as
			user interface messages or error logging.
			Currently:
			In either case, any mismatch in capabilities SHOULD be
			reported to the user via normal network management mechanisms, such
			as user interface messages or error logging. -->
	</t>		</t>
	<t>		<t>
	In all cases, if credit windows are in use, traffic for which		In all cases, if credit windows are in use, traffic for which
	credits are not available MUST NOT be sent to the modem by the		credits are not available <bcp14>MUST NOT</bcp14> be sent to the modem by th e
	router.		router.
	</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 and		This document defines a DLEP extension that uses DLEP mechanisms and
	the credit window control and flow mechanisms defined in <xref		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		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 Considerations		existing DLEP messages and discussed in the Security Considerations
	section of <xref target="RFC8175"/> such as an injected message		section of <xref target="RFC8175"/>, such as an injected message
	resizing a credit window to a value that results in a denial of		resizing a credit window to a value that results in a denial of
	service. The security mechanisms documented in <xref		service. The security mechanisms documented in <xref
	target="RFC8175"/> can be applied equally to the mechanism defined		target="RFC8175"/> can be applied equally to the mechanism defined
	in this document.		in this document.
	</t>		</t>
	<t>		<t>
	Wildcards for matching Priority Code point (PCP) and VLAN ID (VID)		Wildcards for matching Priority Code Point (PCP) and VLAN Identifier (VID)
	fields (see <xref		fields (see <xref
	target="I-D.ietf-manet-dlep-ether-credit-extension"/>) are provided		target="RFC9895"/>) are provided. Note that wildcards
	which may be convenient to match a number of packet flows but could		may be convenient for matching a number of packet flows but could
	inadvertently match unexpected flows or new flows that appear after		inadvertently match unexpected flows or new flows that appear after
	the wildcard matching has been set up. It is therefore RECOMMENDED		the wildcard matching has been set up. It is therefore <bcp14>RECOMMENDED</b cp14>
	that wildcards not be used unless needed.		that wildcards not be used unless needed.
	</t>		</t>
	</section>		</section>
	<section anchor="sec-iana" numbered="true" toc="default">		<section anchor="sec-iana" numbered="true" toc="default">
	<name>IANA Considerations</name>		<name>IANA Considerations</name>
	<t>		<t>
	IANA is requested to assign one code point in the "Extension Type Values"		IANA has assigned the following code point in the "Extension Type Values"
	registry in the "Dynamic Link Exchange Protocol (DLEP) Parameters"		registry in the "Dynamic Link Exchange Protocol (DLEP) Parameters"
	registry group as follows:		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">6</td>
	<td align="left">DiffServ Aware Credit Window</td>		<td align="left">Diffserv Aware Credit Window</td>
	</tr>		</tr>
	</tbody>		</tbody>
	</table>		</table>
	<t keepWithPrevious="true"/>		<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>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2 119.xml"/>		<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2 119.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8 174.xml"/>		<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8 174.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8 175.xml"/>		<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8 175.xml"/>
	<reference anchor="I-D.ietf-manet-dlep-credit-flow-control"		<!-- draft-ietf-manet-dlep-credit-flow-control-19 (RFC 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"		<!-- draft-ietf-manet-dlep-traffic-classification-17 (RFC 9892) -->
	target="https://datatracker.ietf.org/doc/draft-ietf-manet-dlep-t		<reference anchor="RFC9892" target="https://www.rfc-editor.org/info/rfc9
	raffic-classification">		892">
	<front>		<front>
	<title>Dynamic Link Exchange Protocol (DLEP) Traffic		<title>Dynamic Link Exchange Protocol (DLEP) Traffic Classification
	Classification Data Item</title>		Data Item</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." surname="Berger">		<organization>LabN Consulting, L.L.C.</organization>
	<organization>LabN Consulting, L.L.C.</organization>		</author>
	</author>		<author initials="D." surname="Fedyk" fullname="Don Fedyk" role="edi
	<author fullname="Don Fedyk" initials="D." surname="Fedyk">		tor">
	<organization>LabN Consulting, L.L.C.</organization>		<organization>LabN Consulting, L.L.C.</organization>
	</author>		</author>
	<date day="19" month="November" year="2024"/>		<date month='November' year='2025'/>
	</front>		</front>
	<seriesInfo name="Internet-Draft"		<seriesInfo name="RFC" value="9892"/>
	value="draft-ietf-manet-dlep-traffic-classification"/>		<seriesInfo name="DOI" value="10.17487/RFC9892"/>
	</reference>		</reference>
	</references>		</references>
	<references>		<references>
	<name>Informative References</name>		<name>Informative References</name>
	<xi:include		<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2
	href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2475.xml"/		475.xml"/>
	>
	<reference anchor="I-D.ietf-manet-dlep-ether-credit-extension"
	target="https://datatracker.ietf.org/doc/draft-ietf-manet-dlep
	-ether-credit-extension/">
	<front>
	<title>DLEP IEEE 802.1Q Aware Credit Window
	Extension</title>
	<author fullname="David Wiggins" initials="D."
	surname="Wiggins"/>
	<author fullname="Lou Berger" initials="L."
	surname="Berger">
	<organization>LabN Consulting, L.L.C.</organization>
	</author>		<!-- draft-ietf-manet-dlep-ether-credit-extension-09 (RFC 9895) -->
	<author fullname="Donald E. Eastlake 3rd" initials="D. E."		<reference anchor="RFC9895" target="https://www.rfc-editor.org/info/rfc9895">
	surname="Eastlake">		<front>
	<organization>Independent</organization>		<title>Dynamic Link Exchange Protocol (DLEP) IEEE 802.1Q Aware Credit Wind
	</author>		ow Extension</title>
	<date day="15" month="December" year="2024"/>		<author initials="D." surname="Wiggins" fullname="David Wiggins">
	</front>		</author>
	<seriesInfo name="Internet-Draft"		<author initials="L." surname="Berger" fullname="Lou Berger">
	value="draft-ietf-manet-dlep-ether-credit-extension"/>		<organization>LabN Consulting, L.L.C.</organization>
	</reference>		</author>
			<author initials="D." surname="Eastlake 3rd" fullname="Donald E. Eastlake
			3rd" role="editor">
			<organization>Independent</organization>
			</author>
			<date month="November" year="2025" />
			</front>
			<seriesInfo name="RFC" value="9895"/>
			<seriesInfo name="DOI" value="10.17487/RFC9895"/>
			</reference>
	</references>		</references>
	</references>		</references>
	<section numbered="true">		<section numbered="false">
	<name>Acknowledgments</name>		<name>Acknowledgments</name>
	<t>		<t>
	The Sub-Data item format was inspired by Rick Taylor's "Data Item		The Sub-Data Item format was inspired by <contact fullname="Rick Taylor"/>' s "Data Item
	Containers". He also proposed the separation of credit windows from		Containers". He also proposed the separation of credit windows from
	traffic classification at IETF 98. Many useful comments were		traffic classification at IETF 98. Many useful comments were
	received from contributors to the MANET working group, notably		received from contributors to the MANET Working Group, notably
	Ronald in't Velt.		<contact fullname="Ronald in 't Velt"/>.
	</t>		</t>
	<t>		<t>
	We had the honor of working too briefly with David Wiggins on this		We had the honor of working too briefly with <contact fullname="David Wiggi ns"/> on this
	and related DLEP work. His contribution to the IETF and publication		and related DLEP work. His contribution to the IETF and publication
	of the first and definitive open source DLEP implementation have		of the first and definitive open-source DLEP implementation have
	been critical to the acceptance of DLEP. We mourn his passing on		been critical to the acceptance of DLEP. We mourn his passing on
	November 23, 2023. We wish to recognize his guidance, leadership		November 26, 2023. We wish to recognize his guidance, leadership,
	and professional excellence. We were fortunate to benefit from his		and professional excellence. We were fortunate to benefit from his
	leadership and friendship. He shall be missed.		leadership and friendship. He 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] Please let us know if any changes are needed for the
			following:
			a) The following term was used inconsistently in this document.
			We chose to use the latter form. Please let us know any objections.
			Sub-Data item / Sub-Data Item (as used elsewhere in this document
			and per the other documents in this group (Cluster 541 /
			https://www.rfc-editor.org/cluster_info.php?cid=C541) of documents)
			b) The following term appears to be used inconsistently in this document.
			Please let us know which form is preferred. (Note that we updated "Diffserv"
			to "DiffServ".)
			DiffServ Aware Credit Window Type Value /
			DiffServ Aware Credit Window Extension Type Value -->
	</rfc>		</rfc>
End of changes. 56 change blocks.
	182 lines changed or deleted		246 lines changed or added
This html diff was produced by rfcdiff 1.48.