RFC 7026: Retiring TLVs from the Associated Channel Header of the MPLS Generic Associated Channel
In plain English — editorial summary, not part of the RFC
The MPLS Generic Associated Channel (G-ACh) is a generalization of the applicability of the pseudowire (PW) Associated Channel Header (ACH). RFC 5586 defines the concept of TLV constructs that can be carried in messages on the G-ACh by placing them in the ACH between the fixed header fields and the G-ACh message. These TLVs are called ACH TLVs No Associated Channel Type yet defined uses an ACH TLV. Furthermore, it is believed that handling TLVs in hardware introduces significant problems to the fast path, and since G-ACh messages are intended to be processed substantially in hardware, the use of ACH TLVs is undesirable. This document updates RFC 5586 by retiring ACH TLVs and removing the associated registry.
Document record
- Document ID
- RFC7026
- Published
- September 2013
- Authors
- A. Farrel; S. Bryant
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 5
- Also known as
- —
- Updates:
- RFC 5586
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7769Media Access Control (MAC) Address Withdrawal over Static PseudowireCurrent
February 2016
- RFC 8104Pseudowire (PW) Endpoint Fast Failure ProtectionCurrent
March 2017
- RFC 5718An In-Band Data Communication Network For the MPLS Transport ProfileCurrent
January 2010
- RFC 8469Recommendation to Use the Ethernet Control WordCurrent
November 2018
- RFC 4717Encapsulation Methods for Transport of Asynchronous Transfer Mode (ATM) over MPLS NetworksCurrent
December 2006
- RFC 4619Encapsulation Methods for Transport of Frame Relay over Multiprotocol Label Switching (MPLS) NetworksCurrent
September 2006
- RFC 4618Encapsulation Methods for Transport of PPP/High-Level Data Link Control (HDLC) over MPLS NetworksCurrent
September 2006
- RFC 4448Encapsulation Methods for Transport of Ethernet over MPLS NetworksUpdated
April 2006
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?