RFC 7074: Revised Definition of the GMPLS Switching Capability and Type Fields
In plain English — editorial summary, not part of the RFC
GMPLS provides control for multiple switching technologies and for hierarchical switching within a technology. GMPLS routing and signaling use common values to indicate the type of switching technology. These values are carried in routing protocols via the Switching Capability field, and in signaling protocols via the Switching Type field. While the values used in these fields are the primary indicators of the technology and hierarchy level being controlled, the values are not consistently defined and used across the different technologies supported by GMPLS. This document is intended to resolve the inconsistent definition and use of the Switching Capability and Type fields by narrowly scoping the meaning and use of the fields. This document updates all documents that use the GMPLS Switching Capability and Types fields, in particular RFCs 3471, 4202, 4203, and 5307.
Document record
- Document ID
- RFC7074
- Published
- November 2013
- Authors
- L. Berger; J. Meuric
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 9
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7079The Pseudowire (PW) and Virtual Circuit Connectivity Verification (VCCV) Implementation Survey ResultsCurrent
November 2013
- RFC 7080Virtual Private LAN Service (VPLS) Interoperability with Provider Backbone BridgesCurrent
December 2013
- RFC 7067Directory Assistance Problem and High-Level Design ProposalCurrent
November 2013
- RFC 7063Survey Report on Protocol Independent Multicast - Sparse Mode (PIM-SM) Implementations and DeploymentsCurrent
December 2013
- RFC 7062Framework for GMPLS and PCE Control of G.709 Optical Transport NetworksCurrent
November 2013
- RFC 7087A Thesaurus for the Interpretation of Terminology Used in MPLS Transport Profile (MPLS-TP) Internet-Drafts and RFCs in the Context of the ITU-T's Transport Network RecommendationsCurrent
December 2013
- RFC 7060Using LDP Multipoint Extensions on Targeted LDP SessionsCurrent
November 2013
- RFC 7054Addressing Requirements and Design Considerations for Per-Interface Maintenance Entity Group Intermediate Points (MIPs)Current
November 2013
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?