Protocol Extensions for Support of Diffserv-aware MPLS Traffic Engineering
RFC 4124, “Protocol Extensions for Support of Diffserv-aware MPLS Traffic Engineering”, is a Proposed Standard document published in June 2005 by F. Le Faucheur. The canonical text is published by the RFC Editor.
Abstract
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]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 4124 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 4123 Session Initiation Protocol -H.323 Interworking Requirements
- RFC 4125 Maximum Allocation Bandwidth Constraints Model for Diffserv-aware MPLS Traffic Engineering
- RFC 4122 A Universally Unique IDentifier URN Namespace
- RFC 4126 Max Allocation with Reservation Bandwidth Constraints Model for Diffserv-aware MPLS Traffic Engineering & Performance Comparisons
- RFC 4121 The Kerberos Version 5 Generic Security Service Application Program Interface Mechanism: Version 2
- RFC 4127 Russian Dolls Bandwidth Constraints Model for Diffserv-aware MPLS Traffic Engineering
- RFC 4120 The Kerberos Network Authentication Service
- RFC 4128 Bandwidth Constraints Models for Differentiated Services -aware MPLS Traffic Engineering: Performance Evaluation