Retiring TLVs from the Associated Channel Header of the MPLS Generic Associated Channel
draft-farbryantrel-mpls-retire-ach-tlv-02
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Adrian Farrel , Stewart Bryant | ||
| Last updated | 2013-06-10 (Latest revision 2013-05-23) | ||
| Replaced by | draft-ietf-mpls-retire-ach-tlv | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-mpls-retire-ach-tlv | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
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 TLVs in undesirable. This document updates RFC 5586 by retiring ACH TLVs and removing the associated registry.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)