rfc9892v6.txt   rfc9892.txt 
Internet Engineering Task Force (IETF) B. Cheng Internet Engineering Task Force (IETF) B. Cheng
Request for Comments: 9892 MIT Lincoln Laboratory Request for Comments: 9892 MIT Lincoln Laboratory
Category: Standards Track D. Wiggins Category: Standards Track D. Wiggins
ISSN: 2070-1721 ISSN: 2070-1721
L. Berger L. Berger
D. Fedyk, Ed. D. Fedyk, Ed.
LabN Consulting, L.L.C. LabN Consulting, L.L.C.
December 2025 January 2026
Dynamic Link Exchange Protocol (DLEP) Traffic Classification Data Item Dynamic Link Exchange Protocol (DLEP) Traffic Classification Data Item
Abstract Abstract
This document defines a new Data Item for the Dynamic Link Exchange This document defines a new Data Item for the Dynamic Link Exchange
Protocol (DLEP) to support traffic classification. Traffic Protocol (DLEP) to support traffic classification. Traffic
classification information identifies traffic flows based on frame/ classification information identifies traffic flows based on frame/
packet content such as a destination address. The Data Item is packet content such as a destination address. The Data Item is
defined in an extensible and reusable fashion. Its use will be defined in an extensible and reusable fashion. Its use will be
skipping to change at line 40 skipping to change at line 40
received public review and has been approved for publication by the received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841. Internet Standards is available in Section 2 of RFC 7841.
Information about the current status of this document, any errata, Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc9892. https://www.rfc-editor.org/info/rfc9892.
Copyright Notice Copyright Notice
Copyright (c) 2025 IETF Trust and the persons identified as the Copyright (c) 2026 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Revised BSD License text as described in Section 4.e of the include Revised BSD License text as described in Section 4.e of the
Trust Legal Provisions and are provided without warranty as described Trust Legal Provisions and are provided without warranty as described
skipping to change at line 357 skipping to change at line 357
A router receiving the Traffic Classification Sub-Data Item MUST A router receiving the Traffic Classification Sub-Data Item MUST
validate the information on receipt, prior to using the carried validate the information on receipt, prior to using the carried
information, including potentially updating the data behavior as information, including potentially updating the data behavior as
determined by the extension requiring the use of the Sub-Data Item. determined by the extension requiring the use of the Sub-Data Item.
Validation failures MUST be treated as an error as described in Validation failures MUST be treated as an error as described in
Section 2.1.1. Section 2.1.1.
Once validated, the receiver MUST ensure that each DS Field value is Once validated, the receiver MUST ensure that each DS Field value is
listed only once across the whole Traffic Classification Data Item. listed only once across the whole Traffic Classification Data Item.
Note that this check is across the Data Item and not the individual Note that this check is across the Data Item and not the individual
Sub-Data Item. If the same DS Field value is listed more than once Sub-Data Items. If the same DS Field value is listed more than once
within the same Traffic Classification Data Item, the Data Item MUST within the same Traffic Classification Data Item, the Data Item MUST
be treated as an error as described in Section 2.1.1. be treated as an error as described in Section 2.1.1.
2.3. Ethernet Traffic Classification Sub-Data Item 2.3. Ethernet Traffic Classification Sub-Data Item
The Ethernet Traffic Classification Sub-Data Item identifies the VLAN The Ethernet Traffic Classification Sub-Data Item identifies the VLAN
and PCPs that should be treated as a single flow, i.e., receive the and PCPs that should be treated as a single flow, i.e., receive the
same traffic treatment. Ethernet PCP support is defined as part of same traffic treatment. Ethernet PCP support is defined as part of
the IEEE 802.1Q tag format [IEEE8021Q] and includes a 3-bit "PCP" the IEEE 802.1Q tag format [IEEE8021Q] and includes a 3-bit "PCP"
field. The tag format also includes a 12-bit "VLAN Identifier (VID)" field. The tag format also includes a 12-bit "VLAN Identifier (VID)"
skipping to change at line 684 skipping to change at line 684
<https://www.rfc-editor.org/info/rfc8126>. <https://www.rfc-editor.org/info/rfc8126>.
[RFC8651] Cheng, B., Wiggins, D., and L. Berger, Ed., "Dynamic Link [RFC8651] Cheng, B., Wiggins, D., and L. Berger, Ed., "Dynamic Link
Exchange Protocol (DLEP) Control-Plane-Based Pause Exchange Protocol (DLEP) Control-Plane-Based Pause
Extension", RFC 8651, DOI 10.17487/RFC8651, October 2019, Extension", RFC 8651, DOI 10.17487/RFC8651, October 2019,
<https://www.rfc-editor.org/info/rfc8651>. <https://www.rfc-editor.org/info/rfc8651>.
[RFC9893] Cheng, B., Wiggins, D., Ratliff, S., Berger, L., and E. [RFC9893] Cheng, B., Wiggins, D., Ratliff, S., Berger, L., and E.
Kinzie, Ed., "Dynamic Link Exchange Protocol (DLEP) Kinzie, Ed., "Dynamic Link Exchange Protocol (DLEP)
Credit-Based Flow Control Messages and Data Items", Credit-Based Flow Control Messages and Data Items",
RFC 9893, DOI 10.17487/RFC9893, December 2025, RFC 9893, DOI 10.17487/RFC9893, January 2026,
<https://www.rfc-editor.org/info/rfc9893>. <https://www.rfc-editor.org/info/rfc9893>.
[RFC9894] Cheng, B., Wiggins, D., Berger, L., and D. Eastlake 3rd, [RFC9894] Cheng, B., Wiggins, D., Berger, L., and D. Eastlake 3rd,
Ed., "Dynamic Link Exchange Protocol (DLEP) Diffserv Aware Ed., "Dynamic Link Exchange Protocol (DLEP) Diffserv Aware
Credit Window Extension", RFC 9894, DOI 10.17487/RFC9894, Credit Window Extension", RFC 9894, DOI 10.17487/RFC9894,
December 2025, <https://www.rfc-editor.org/info/rfc9894>. January 2026, <https://www.rfc-editor.org/info/rfc9894>.
Acknowledgments Acknowledgments
The Sub-Data Item format was inspired by Rick Taylor's "Data Item The Sub-Data Item format was inspired by 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. This document was derived from traffic classification at IETF 98. This document was derived from
[RFC9894] as a result of discussions at IETF 101. Many useful [RFC9894] as a result of discussions at IETF 101. Many useful
comments were received from contributors to the MANET Working Group, comments were received from contributors to the MANET Working Group,
notably Ronald in 't Velt and David Black. notably Ronald in 't Velt and David Black.
 End of changes. 5 change blocks. 
5 lines changed or deleted 5 lines changed or added

This html diff was produced by rfcdiff 1.48.