RFC 5151: Inter-Domain MPLS and GMPLS Traffic Engineering -- Resource Reservation Protocol-Traffic Engineering (RSVP-TE) Extensions
In plain English — editorial summary, not part of the RFC
This document describes procedures and protocol extensions for the use of Resource Reservation Protocol-Traffic Engineering (RSVP-TE) signaling in Multiprotocol Label Switching-Traffic Engineering (MPLS-TE) packet networks and Generalized MPLS (GMPLS) packet and non-packet networks to support the establishment and maintenance of Label Switched Paths that cross domain boundaries. For the purpose of this document, a domain is considered to be any collection of network elements within a common realm of address space or path computation responsibility. Examples of such domains include Autonomous Systems, Interior Gateway Protocol (IGP) routing areas, and GMPLS overlay networks. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5151
- Published
- February 2008
- Authors
- A. Farrel; A. Ayyangar; JP. Vasseur
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 25
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5316ISIS Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic EngineeringObsoleted
December 2008
- RFC 5392OSPF Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic EngineeringCurrent
January 2009
- RFC 5712MPLS Traffic Engineering Soft PreemptionCurrent
January 2010
- RFC 3480Signalling Unnumbered Links in CR-LDP (Constraint-Routing Label Distribution Protocol)Current
February 2003
- RFC 4105Requirements for Inter-Area MPLS Traffic EngineeringCurrent
June 2005
- RFC 5038The Label Distribution Protocol (LDP) Implementation Survey ResultsCurrent
October 2007
- RFC 4972Routing Extensions for Discovery of Multiprotocol (MPLS) Label Switch Router (LSR) Traffic Engineering (TE) Mesh MembershipCurrent
July 2007
- RFC 4920Crankback Signaling Extensions for MPLS and GMPLS RSVP-TECurrent
July 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?