RFC 6344: Operating Virtual Concatenation (VCAT) and the Link Capacity Adjustment Scheme (LCAS) with Generalized Multi-Protocol Label Switching (GMPLS)
In plain English — editorial summary, not part of the RFC
This document describes requirements for, and the use of, the Generalized Multi-Protocol Label Switching (GMPLS) control plane in support of the Virtual Concatenation (VCAT) layer 1 inverse multiplexing data plane mechanism and its companion Link Capacity Adjustment Scheme (LCAS). LCAS can be used for hitless dynamic resizing of the inverse multiplex group. These techniques apply to Optical Transport Network (OTN), Synchronous Optical Network (SONET), Synchronous Digital Hierarchy (SDH), and Plesiochronous Digital Hierarchy (PDH) signals. This document updates RFC 4606 by making modifications to the procedures for supporting virtual concatenation. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6344
- Published
- August 2011
- Authors
- G. Bernstein; D. Caviglia; R. Rabbat; H. van Helvoort
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 21
- Also known as
- —
- Updates:
- RFC 4606
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6348Requirements for Point-to-Multipoint Extensions to the Label Distribution ProtocolCurrent
September 2011
- RFC 6329IS-IS Extensions Supporting IEEE 802.1aq Shortest Path BridgingCurrent
April 2012
- RFC 6361PPP Transparent Interconnection of Lots of Links (TRILL) Protocol Control ProtocolCurrent
August 2011
- RFC 6327Routing Bridges (RBridges): AdjacencyObsoleted
July 2011
- RFC 6326Transparent Interconnection of Lots of Links (TRILL) Use of IS-ISObsoleted
July 2011
- RFC 6325Routing Bridges (RBridges): Base Protocol SpecificationUpdated
July 2011
- RFC 6368Internal BGP as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs)Updated
September 2011
- RFC 6370MPLS Transport Profile (MPLS-TP) IdentifiersCurrent
September 2011
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?