RFC 4124: Protocol Extensions for Support of Diffserv-aware MPLS Traffic Engineering
In plain English — editorial summary, not part of the RFC
This document specifies the protocol extensions for support of Diffserv-aware MPLS Traffic Engineering (DS-TE). This includes generalization of the semantics of a number of Interior Gateway Protocol (IGP) extensions already defined for existing MPLS Traffic Engineering in RFC 3630, RFC 3784, and additional IGP extensions beyond those. This also includes extensions to RSVP-TE signaling beyond those already specified in RFC 3209 for existing MPLS Traffic Engineering. These extensions address the requirements for DS-TE spelled out in RFC 3564. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4124
- Published
- June 2005
- Authors
- F. Le Faucheur
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sub
- Pages
- 37
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3785Use of Interior Gateway Protocol (IGP) Metric as a second MPLS Traffic Engineering (TE) MetricCurrent
May 2004
- RFC 3936Procedures for Modifying the Resource reSerVation Protocol (RSVP)Current
October 2004
- RFC 3726Requirements for Signaling ProtocolsCurrent
April 2004
- RFC 3719Recommendations for Interoperable Networks using Intermediate System to Intermediate System (IS-IS)Current
February 2004
- RFC 4561Definition of a Record Route Object (RRO) Node-Id Sub-ObjectCurrent
June 2006
- RFC 3477Signalling Unnumbered Links in Resource ReSerVation Protocol - Traffic Engineering (RSVP-TE)Updated
February 2003
- RFC 3209RSVP-TE: Extensions to RSVP for LSP TunnelsUpdated
December 2001
- RFC 3182Identity Representation for RSVPCurrent
October 2001
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?