RFC 4202: Routing Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)
In plain English — editorial summary, not part of the RFC
This document specifies routing extensions in support of carrying link state information for Generalized Multi-Protocol Label Switching (GMPLS). This document enhances the routing extensions required to support MPLS Traffic Engineering (TE). [STANDARDS-TRACK]
Document record
- Document ID
- RFC4202
- Published
- October 2005
- Authors
- K. Kompella; Y. Rekhter
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 27
- Also known as
- —
Topics
Referenced by
3 later RFCs formally update or obsolete part of this document.
- RFC 6001Generalized MPLS (GMPLS) Protocol Extensions for Multi-Layer and Multi-Region Networks (MLN/MRN)Current
October 2010
- RFC 6002Generalized MPLS (GMPLS) Data Channel Switching Capable (DCSC) and Channel Set Label ExtensionsCurrent
October 2010
- RFC 7074Revised Definition of the GMPLS Switching Capability and Type FieldsCurrent
November 2013
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4203OSPF Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)Updated
October 2005
- RFC 4222Prioritized Treatment of Specific OSPF Version 2 Packets and Congestion AvoidanceUpdated
October 2005
- RFC 4167Graceful OSPF Restart Implementation ReportCurrent
October 2005
- RFC 4136OSPF Refresh and Flooding Reduction in Stable TopologiesCurrent
July 2005
- RFC 3883Detecting Inactive Neighbors over OSPF Demand Circuits (DC)Current
October 2004
- RFC 4552Authentication/Confidentiality for OSPFv3Current
June 2006
- RFC 4577OSPF as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs)Current
June 2006
- RFC 4750OSPF Version 2 Management Information BaseCurrent
December 2006
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?