RFC 5586: MPLS Generic Associated Channel
In plain English — editorial summary, not part of the RFC
This document generalizes the applicability of the pseudowire (PW) Associated Channel Header (ACH), enabling the realization of a control channel associated to MPLS Label Switched Paths (LSPs) and MPLS Sections in addition to MPLS pseudowires. In order to identify the presence of this Associated Channel Header in the label stack, this document also assigns one of the reserved MPLS label values to the Generic Associated Channel Label (GAL), to be used as a label based exception mechanism.
Document record
- Document ID
- RFC5586
- Published
- June 2009
- Authors
- M. Bocci; M. Vigoureux; S. Bryant
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 19
- Also known as
- —
Topics
Referenced by
4 later RFCs formally update or obsolete part of this document.
- RFC 6423Using the Generic Associated Channel Label for Pseudowire in the MPLS Transport Profile (MPLS-TP)Current
November 2011
- RFC 7026Retiring TLVs from the Associated Channel Header of the MPLS Generic Associated ChannelCurrent
September 2013
- RFC 7214Moving Generic Associated Channel (G-ACh) IANA Registries to a New RegistryCurrent
May 2014
- RFC 7274Allocating and Retiring Special-Purpose MPLS LabelsUpdated
June 2014
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5718An In-Band Data Communication Network For the MPLS Transport ProfileCurrent
January 2010
- 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 5960MPLS Transport Profile Data Plane ArchitectureUpdated
August 2010
- RFC 6428Proactive Connectivity Verification, Continuity Check, and Remote Defect Indication for the MPLS Transport ProfileUpdated
November 2011
- RFC 7487Configuration of Proactive Operations, Administration, and Maintenance (OAM) Functions for MPLS-Based Transport Networks Using RSVP-TECurrent
March 2015
- RFC 7759Configuration of Proactive Operations, Administration, and Maintenance (OAM) Functions for MPLS-Based Transport Networks Using Label Switched Path (LSP) PingCurrent
February 2016
- RFC 8256Requirements for Hitless MPLS Path Segment MonitoringCurrent
October 2017
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?