RFC 3473: Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions
In plain English — editorial summary, not part of the RFC
This document describes extensions to Multi-Protocol Label Switching (MPLS) Resource ReserVation Protocol - Traffic Engineering (RSVP-TE) signaling required to support Generalized MPLS. Generalized MPLS extends the MPLS control plane to encompass time-division (e.g., Synchronous Optical Network and Synchronous Digital Hierarchy, SONET/SDH), wavelength (optical lambdas) and spatial switching (e.g., incoming port or fiber to outgoing port or fiber). This document presents a RSVP-TE specific description of the extensions. A generic functional description can be found in separate documents. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3473
- Published
- February 2003
- Authors
- L. Berger
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 42
- Also known as
- —
Topics
Referenced by
14 later RFCs formally update or obsolete part of this document.
- RFC 4003GMPLS Signaling Procedure for Egress ControlCurrent
February 2005
- RFC 4201Link Bundling in MPLS Traffic Engineering (TE)Current
October 2005
- RFC 4420Encoding of Attributes for Multiprotocol Label Switching (MPLS) Label Switched Path (LSP) Establishment Using Resource ReserVation Protocol-Traffic Engineering (RSVP-TE)Obsoleted
February 2006
- RFC 4783GMPLS - Communication of Alarm InformationCurrent
December 2006
- RFC 4873GMPLS Segment RecoveryUpdated
May 2007
- RFC 4874Exclude Routes - Extension to Resource ReserVation Protocol-Traffic Engineering (RSVP-TE)Updated
April 2007
- RFC 4974Generalized MPLS (GMPLS) RSVP-TE Signaling Extensions in Support of CallsUpdated
August 2007
- RFC 5063Extensions to GMPLS Resource Reservation Protocol (RSVP) Graceful RestartCurrent
October 2007
- RFC 5151Inter-Domain MPLS and GMPLS Traffic Engineering -- Resource Reservation Protocol-Traffic Engineering (RSVP-TE) ExtensionsCurrent
February 2008
- RFC 5420Encoding of Attributes for MPLS LSP Establishment Using Resource Reservation Protocol Traffic Engineering (RSVP-TE)Updated
February 2009
- RFC 6002Generalized MPLS (GMPLS) Data Channel Switching Capable (DCSC) and Channel Set Label ExtensionsCurrent
October 2010
- RFC 6003Ethernet Traffic ParametersCurrent
October 2010
- RFC 6780RSVP ASSOCIATION Object ExtensionsCurrent
October 2012
- RFC 8359Network-Assigned Upstream LabelCurrent
March 2018
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3472Generalized Multi-Protocol Label Switching (GMPLS) Signaling Constraint-based Routed Label Distribution Protocol (CR-LDP) ExtensionsUpdated
February 2003
- RFC 3471Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional DescriptionUpdated
February 2003
- RFC 4558Node-ID Based Resource Reservation Protocol (RSVP) Hello: A Clarification StatementCurrent
June 2006
- RFC 4652Evaluation of Existing Routing Protocols against Automatic Switched Optical Network (ASON) Routing RequirementsCurrent
October 2006
- RFC 2615PPP over SONET/SDHCurrent
June 1999
- RFC 3477Signalling Unnumbered Links in Resource ReSerVation Protocol - Traffic Engineering (RSVP-TE)Updated
February 2003
- RFC 3480Signalling Unnumbered Links in CR-LDP (Constraint-Routing Label Distribution Protocol)Current
February 2003
- RFC 3945Generalized Multi-Protocol Label Switching (GMPLS) ArchitectureUpdated
November 2004
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?