draft-ietf-mpls-retire-ach-tlv-02.txt   draft-ietf-mpls-retire-ach-tlv-03.txt 
Network Working Group A. Farrel Network Working Group A. Farrel
Internet Draft Juniper Networks Internet Draft Juniper Networks
Category: Standards Track S. Bryant Category: Standards Track S. Bryant
Updates: 5586 (if approved) Cisco Systems Updates: 5586 (if approved) Cisco Systems
Expires: December 28, 2013 June 28, 2013 Expires: January 31, 2014 July 31, 2013
Retiring TLVs from the Associated Channel Header of the MPLS Generic Retiring TLVs from the Associated Channel Header of the MPLS Generic
Associated Channel Associated Channel
draft-ietf-mpls-retire-ach-tlv-02.txt draft-ietf-mpls-retire-ach-tlv-03.txt
Abstract Abstract
The MPLS Generic Associated Channel (G-ACh) is a generalization of The MPLS Generic Associated Channel (G-ACh) is a generalization of
the applicability of the Pseudowire (PW) Associated Channel Header the applicability of the Pseudowire (PW) Associated Channel Header
(ACH). RFC 5586 defines the concept of TLV constructs that can be (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 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 the fixed header fields and the G-ACh message. These TLVs are called
ACH TLVs ACH TLVs
skipping to change at page 3, line 43 skipping to change at page 3, line 43
4. IANA Considerations 4. IANA Considerations
This document requests IANA to make two changes to the IANA This document requests IANA to make two changes to the IANA
registries. registries.
4.1. Associated Channel Header TLV Registry 4.1. Associated Channel Header TLV Registry
The "Pseudowire Name Spaces (PWE3)" registry has a sub-registry The "Pseudowire Name Spaces (PWE3)" registry has a sub-registry
called the "Associated Channel Header TLV Registry". IANA is called the "Associated Channel Header TLV Registry". IANA is
requested to entirely delete this registry leaving no record. requested to entirely delete this sub-registry, but to leave a
tombstone record in the top-level list of registries that says:
Associated Channel Header TLV Registry RFC 5586 RFC xxxx
Where "xxxx" is the number of this RFC.
draft-ietf-mpls-retire-ach-tlv-03.txt July 20 13
4.2. Pseudowire Associated Channel Types Registry 4.2. Pseudowire Associated Channel Types Registry
The "Pseudowire Name Spaces (PWE3)" registry has a sub-registry The "Pseudowire Name Spaces (PWE3)" registry has a sub-registry
called the "Pseudowire Associated Channel Types Registry". This called the "Pseudowire Associated Channel Types Registry". This
registry includes a column marked "TLV Follows". IANA is sub-registry includes a column marked "TLV Follows". IANA is
requested to entirely delete this column leaving no record. requested to entirely delete this column leaving no record.
IANA is requested to add a pointer to this RFC in the definition of
this sub-registry.
5. Manageability Considerations 5. Manageability Considerations
This document will have no impact on network or device manageability This document will have no impact on network or device manageability
because there are no ACH Types that allow the use of TLVs. because there are no ACH Types that allow the use of TLVs.
The document removes a feature that might have been used to enhance The document removes a feature that might have been used to enhance
management messages, and especially Operations, Management, and management messages, and especially Operations, Management, and
Administration (OAM) messages. However, given the considerable Administration (OAM) messages. However, given the considerable
experience in defining MPLS OAM messages in the last few years, it experience in defining MPLS OAM messages in the last few years, it
would appear that this feature is not useful. would appear that this feature is not useful.
skipping to change at page 4, line 37 skipping to change at page 4, line 49
G-ACh in a generic way. However, no mechanisms have been proposed at G-ACh in a generic way. However, no mechanisms have been proposed at
the time of writing, and it has generally been considered that it is the time of writing, and it has generally been considered that it is
the responsiblity of the specification that defines G-ACh messages to the responsiblity of the specification that defines G-ACh messages to
consider the security requirements of those messages which may be consider the security requirements of those messages which may be
different for the different applications. different for the different applications.
Otherwise, this document has no implications for security. Otherwise, this document has no implications for security.
7. Acknowledgements 7. Acknowledgements
Thanks to Eric Osborne, Thomas Morin, Lizhong Jin, Greg Mirsky, and Thanks to Eric Osborne, Thomas Morin, Lizhong Jin, Greg Mirsky, Jia
Jia He for suggestions to improve the text. He, and Pearl Liang for suggestions to improve the text.
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC4385] Bryant, S., Swallow, G., Martini, L., and D. McPherson, [RFC4385] Bryant, S., Swallow, G., Martini, L., and D. McPherson,
"Pseudowire Emulation Edge-to-Edge (PWE3) Control Word "Pseudowire Emulation Edge-to-Edge (PWE3) Control Word
 End of changes. 6 change blocks. 
6 lines changed or deleted 16 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/