RFC 7212: MPLS Generic Associated Channel (G-ACh) Advertisement Protocol
In plain English — editorial summary, not part of the RFC
The MPLS Generic Associated Channel (G-ACh) provides an auxiliary logical data channel associated with a Label Switched Path (LSP), a pseudowire, or a section (link) over which a variety of protocols may flow. These protocols are commonly used to provide Operations, Administration, and Maintenance (OAM) mechanisms associated with the primary data channel. This document specifies simple procedures by which an endpoint of an LSP, pseudowire, or section may inform the other endpoints of its capabilities and configuration parameters, or other application-specific information. This information may then be used by the receiver to validate or adjust its local configuration, and by the network operator for diagnostic purposes.
Document record
- Document ID
- RFC7212
- Published
- June 2014
- Authors
- D. Frost; S. Bryant; M. Bocci
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 23
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7213MPLS Transport Profile (MPLS-TP) Next-Hop Ethernet AddressingCurrent
June 2014
- RFC 7211Operations Model for Router KeyingCurrent
June 2014
- RFC 7214Moving Generic Associated Channel (G-ACh) IANA Registries to a New RegistryCurrent
May 2014
- RFC 7210Database of Long-Lived Symmetric Cryptographic KeysCurrent
April 2014
- RFC 7215Locator/Identifier Separation Protocol (LISP) Network Element Deployment ConsiderationsCurrent
April 2014
- RFC 7209Requirements for Ethernet VPN (EVPN)Current
May 2014
- RFC 7226Requirements for Advanced Multipath in MPLS NetworksCurrent
May 2014
- RFC 7196Making Route Flap Damping UsableCurrent
May 2014
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?