RFC 9892: Dynamic Link Exchange Protocol (DLEP) Traffic Classification Data Item
In plain English — editorial summary, not part of the RFC
This document defines a new Data Item for the Dynamic Link Exchange Protocol (DLEP) to support traffic classification. Traffic classification information identifies traffic flows based on frame/packet content such as a destination address. The Data Item is defined in an extensible and reusable fashion. Its use will be mandated in other documents defining specific DLEP extensions. This document also introduces DLEP Sub-Data Items and defines two new Sub-Data Items to support Diffserv and Ethernet traffic classification.
Document record
- Document ID
- RFC9892
- Published
- January 2026
- Authors
- B. Cheng; D. Wiggins; L. Berger; D. Fedyk
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9893Dynamic Link Exchange Protocol (DLEP) Credit-Based Flow Control Messages and Data ItemsCurrent
January 2026
- RFC 9894Dynamic Link Exchange Protocol (DLEP) Diffserv Aware Credit Window ExtensionCurrent
January 2026
- RFC 9889A Realization of Network Slices for 5G Networks Using Current IP/MPLS TechnologiesCurrent
November 2025
- RFC 9895Dynamic Link Exchange Protocol (DLEP) IEEE 802.1Q Aware Credit Window ExtensionCurrent
January 2026
- RFC 9885Multi-Part TLVs in IS-ISCurrent
October 2025
- RFC 9884Label Switched Path Ping for Segment Routing Path Segment Identifier with MPLS Data PlaneCurrent
October 2025
- RFC 9902A YANG Data Model for IS-IS Segment Routing over the MPLS Data PlaneCurrent
December 2025
- RFC 9903A YANG Data Model for OSPF Segment Routing over the MPLS Data PlaneCurrent
December 2025
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?