RFC 5718: An In-Band Data Communication Network For the MPLS Transport Profile
In plain English — editorial summary, not part of the RFC
The Generic Associated Channel (G-ACh) has been defined as a generalization of the pseudowire (PW) associated control channel to enable the realization of a control/communication channel that is associated with Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs), MPLS PWs, MPLS LSP segments, and MPLS sections between adjacent MPLS-capable devices. The MPLS Transport Profile (MPLS-TP) is a profile of the MPLS architecture that identifies elements of the MPLS toolkit that may be combined to build a carrier-grade packet transport network based on MPLS packet switching technology. This document describes how the G-ACh may be used to provide the infrastructure that forms part of the Management Communication Network (MCN) and a Signaling Communication Network (SCN). Collectively, the MCN and SCN may be referred to as the Data Communication Network (DCN). This document explains how MCN and SCN messages are encapsulated, carried on the G-ACh, and demultiplexed for delivery to the management or signaling/routing control plane components on an MPLS-TP node. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5718
- Published
- January 2010
- Authors
- D. Beller; A. Farrel
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 8
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5586MPLS Generic Associated ChannelUpdated
June 2009
- RFC 5960MPLS Transport Profile Data Plane ArchitectureUpdated
August 2010
- RFC 7026Retiring TLVs from the Associated Channel Header of the MPLS Generic Associated ChannelCurrent
September 2013
- RFC 5654Requirements of an MPLS Transport ProfileCurrent
September 2009
- RFC 5860Requirements for Operations, Administration, and Maintenance (OAM) in MPLS Transport NetworksCurrent
May 2010
- RFC 5921A Framework for MPLS in Transport NetworksUpdated
July 2010
- RFC 5950Network Management Framework for MPLS-based Transport NetworksCurrent
September 2010
- RFC 5951Network Management Requirements for MPLS-based Transport NetworksCurrent
September 2010
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?