RFC 8100: Diffserv-Interconnection Classes and Practice
In plain English — editorial summary, not part of the RFC
This document defines a limited common set of Diffserv Per-Hop Behaviors (PHBs) and Diffserv Codepoints (DSCPs) to be applied at (inter)connections of two separately administered and operated networks, and it explains how this approach can simplify network configuration and operation. Many network providers operate Multiprotocol Label Switching (MPLS) using Treatment Aggregates for traffic marked with different Diffserv Per-Hop Behaviors and use MPLS for interconnection with other networks. This document offers a simple interconnection approach that may simplify operation of Diffserv for network interconnection among providers that use MPLS and apply the Short Pipe Model. While motivated by the requirements of MPLS network operators that use Short Pipe Model tunnels, this document is applicable to other networks, both MPLS and non-MPLS.
Document record
- Document ID
- RFC8100
- Published
- March 2017
- Authors
- R. Geib; D. Black
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- wit
- Pages
- 21
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3308Layer Two Tunneling Protocol (L2TP) Differentiated Services ExtensionCurrent
November 2002
- RFC 7937Content Distribution Network Interconnection (CDNI) Logging InterfaceCurrent
August 2016
- RFC 8325Mapping Diffserv to IEEE 802.11Updated
February 2018
- RFC 8436Update to IANA Registration Procedures for Pool 3 Values in the Differentiated Services Field Codepoints (DSCP) RegistryCurrent
August 2018
- RFC 8837Differentiated Services Code Point (DSCP) Packet Markings for WebRTC QoSCurrent
January 2021
- RFC 5129Explicit Congestion Marking in MPLSUpdated
January 2008
- RFC 5127Aggregation of Diffserv Service ClassesCurrent
February 2008
- RFC 4860Generic Aggregate Resource ReSerVation Protocol (RSVP) ReservationsCurrent
May 2007
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?