RFC 4126: Max Allocation with Reservation Bandwidth Constraints Model for Diffserv-aware MPLS Traffic Engineering & Performance Comparisons
In plain English — editorial summary, not part of the RFC
This document complements the Diffserv-aware MPLS Traffic Engineering (DS-TE) requirements document by giving a functional specification for the Maximum Allocation with Reservation (MAR) Bandwidth Constraints Model. Assumptions, applicability, and examples of the operation of the MAR Bandwidth Constraints Model are presented. MAR performance is analyzed relative to the criteria for selecting a Bandwidth Constraints Model, in order to provide guidance to user implementation of the model in their networks. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC4126
- Published
- June 2005
- Authors
- J. Ash
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- sub
- Pages
- 22
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4125Maximum Allocation Bandwidth Constraints Model for Diffserv-aware MPLS Traffic EngineeringCurrent
June 2005
- RFC 4127Russian Dolls Bandwidth Constraints Model for Diffserv-aware MPLS Traffic EngineeringCurrent
June 2005
- RFC 4124Protocol Extensions for Support of Diffserv-aware MPLS Traffic EngineeringCurrent
June 2005
- RFC 4542Implementing an Emergency Telecommunications Service (ETS) for Real-Time Services in the Internet Protocol SuiteUpdated
May 2006
- RFC 5455Diffserv-Aware Class-Type Object for the Path Computation Element Communication ProtocolCurrent
March 2009
- RFC 6777Label Switched Path (LSP) Data Path Delay Metrics in Generalized MPLS and MPLS Traffic Engineering (MPLS-TE) NetworksCurrent
November 2012
- RFC 9291A YANG Network Data Model for Layer 2 VPNsCurrent
September 2022
- RFC 4128Bandwidth Constraints Models for Differentiated Services (Diffserv)-aware MPLS Traffic Engineering: Performance EvaluationCurrent
June 2005
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?