draft-lcap-mpls-moving-iana-registries-00.txt   draft-lcap-mpls-moving-iana-registries-01.txt 
Network Working Group L. Andersson Network Working Group L. Andersson
Internet-Draft Huawei Internet-Draft Huawei
Updates: 5586, 6374, 6378, 6427, 6428, C. Pignataro Updates: 5586, 6374, 6378, 6427, 6428, C. Pignataro
RFC-ietf-mpls-gach- adv, Cisco RFC-ietf-mpls-gach-adv, Cisco
RFC-ietf-mpls-tp- ethernet-addressing August 20, 2013 RFC-ietf-mpls-tp-ethernet-addressing August 23, 2013
(if approved) (if approved)
Intended status: Standards Track Intended status: Standards Track
Expires: February 21, 2014 Expires: February 24, 2014
Moving Generic Associated Channel (G-ACh) IANA registries to a new Moving Generic Associated Channel (G-ACh) IANA registries to a new
registry registry
draft-lcap-mpls-moving-iana-registries-00 draft-lcap-mpls-moving-iana-registries-01
Abstract Abstract
RFC 5586 generalized the applicability of the pseudowire Associated RFC 5586 generalized the applicability of the pseudowire Associated
Channel Header (PW-ACH) into the Generic Associated Channel G-Ach. Channel Header (PW-ACH) into the Generic Associated Channel G-Ach.
However, registries and allocations of G-ACh parameters had been However, registries and allocations of G-ACh parameters had been
distributed throughout different, sometimes unrelated, registries. distributed throughout different, sometimes unrelated, registries.
This document coalesces these into a new "Generic Associated Channel This document coalesces these into a new "Generic Associated Channel
(G-ACh)" registry under the "Multiprotocol Label Switching (G-ACh)" registry under the "Multiprotocol Label Switching
Architecture (MPLS)" heading. This is an update to RFC 5586 Architecture (MPLS)" heading. This is an update to RFC 5586
[RFC5586]. [RFC5586].
This document also updates RFC 6374, RFC 6428, RFC 6378, RFC 6427, This document also updates RFC 6374, RFC 6428, RFC 6378, RFC 6427,
RFC-ietf-mpls-gach-adv-08, and RFC-ietf-mpls-gach-adv-08, and
RFC-ietf-mpls-tp-ethernet-addressing-08. RFC-ietf-mpls-tp-ethernet-addressing-08.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on February 21, 2014. This Internet-Draft will expire on February 24, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
skipping to change at page 3, line 7 skipping to change at page 2, line 19
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Creation of a new Generic Associated Channel (G-ACh) 2.1. Creation of a new Generic Associated Channel (G-ACh)
IANA registry . . . . . . . . . . . . . . . . . . . . . . . 4 IANA registry . . . . . . . . . . . . . . . . . . . . . . . 3
2.2. Renaming the Pseudowire Associated Channel Types 2.2. Renaming the Pseudowire Associated Channel Types
registry . . . . . . . . . . . . . . . . . . . . . . . . . 4 registry . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.3. Consolidating G-ACh registries . . . . . . . . . . . . . . 5 2.3. Consolidating G-ACh registries . . . . . . . . . . . . . . 4
3. RFC Updates . . . . . . . . . . . . . . . . . . . . . . . . . . 6 3. RFC Updates . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5
6. Normative References . . . . . . . . . . . . . . . . . . . . . 6 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7 6.1. Normative References . . . . . . . . . . . . . . . . . . . 5
6.2. Informative References . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction 1. Introduction
RFC 5586 generalized the PW-ACH into the G-Ach. However, registries RFC 5586 generalized the PW-ACH into the G-Ach. However, registries
and allocations of G-ACh namespaces had been distributed throughout and allocations of G-ACh namespaces had been distributed throughout
different registries. This document coalesces these into a new different registries. This document coalesces these into a new
"Generic Associated Channel registry" in the "Multiprotocol Label "Generic Associated Channel registry" in the "Multiprotocol Label
Switching Architecture (MPLS)" name space. This is an update to RFC Switching Architecture (MPLS)" name space. This is an update to RFC
RFC 5586 [RFC5586]. RFC 5586 [RFC5586].
skipping to change at page 4, line 45 skipping to change at page 3, line 45
2. IANA Considerations 2. IANA Considerations
2.1. Creation of a new Generic Associated Channel (G-ACh) IANA registry 2.1. Creation of a new Generic Associated Channel (G-ACh) IANA registry
IANA is requested to create a new "Generic Associated Channel IANA is requested to create a new "Generic Associated Channel
(G-ACh)" registry under the "Multiprotocol Label Switching (G-ACh)" registry under the "Multiprotocol Label Switching
Architecture (MPLS)" heading. Architecture (MPLS)" heading.
2.2. Renaming the Pseudowire Associated Channel Types registry 2.2. Renaming the Pseudowire Associated Channel Types registry
This document renames the "Pseudowire Associated Channel Types" [PWE- This document renames the "Pseudowire Associated Channel Types"
IANA] into "MPLS Generalized Associated Channel (G-ACh) Types [IANA-PWE3] into "MPLS Generalized Associated Channel (G-ACh) Types
(including Pseudowire Associated Channel Types)". This registry is (including Pseudowire Associated Channel Types)". This registry is
included as the first registry because any additional registration is included as the first registry because any additional registration is
dependent upon the Associated Channel Header Type. dependent upon the Associated Channel Header Type.
2.3. Consolidating G-ACh registries 2.3. Consolidating G-ACh registries
This document further updates the following RFCs by moving the G-ACh This document further updates the following RFCs by moving the G-ACh
related registrations to a common "MPLS Generic Associated Channel related registrations to a common "MPLS Generic Associated Channel
Parameters" registry: Parameters" registry:
skipping to change at page 6, line 7 skipping to change at page 5, line 7
* MPLS PSC TLV Registry [RFC6378] * MPLS PSC TLV Registry [RFC6378]
All the sub-registries are moved from "Multiprotocol Label All the sub-registries are moved from "Multiprotocol Label
Switching (MPLS) Operations, Administration, and Management (OAM) Switching (MPLS) Operations, Administration, and Management (OAM)
Parameters" registry. The IANA is therefore requested to remove Parameters" registry. The IANA is therefore requested to remove
this registry. this registry.
3. RFC Updates 3. RFC Updates
This document updates [RFC 5586] renaming the "Pseudowire Associated This document updates [RFC5586] renaming the "Pseudowire Associated
Channel Types" [PWE-IANA] into "MPLS Generalized Associated Channel Channel Types" [IANA-PWE3] into "MPLS Generalized Associated Channel
(G-ACh) Types (including Pseudowire Associated Channel Types)". (G-ACh) Types (including Pseudowire Associated Channel Types)".
This document also updates the following RFCs by moving the G-ACh This document also updates the following RFCs by moving the G-ACh
related registrations to a common "MPLS Generic Associated Channel related registrations to a common "MPLS Generic Associated Channel
(G-ACh)" registry: RFC 6374, RFC 6428, RFC 6378, RFC 6427, RFC-ietf- (G-ACh)" registry: RFC 6374, RFC 6428, RFC 6378, RFC 6427, RFC-ietf-
mpls-gach-adv-08, and RFC-ietf-mpls-tp-ethernet-addressing-08. mpls-gach-adv-08, and RFC-ietf-mpls-tp-ethernet-addressing-08.
All the registries listed above are moved without any changes to All the registries listed above are moved without any changes to
their content. The reason to move them is to create on single place their content. The reason to move them is to create on single place
where it is possible to find all the G-ACh parameters. where it is possible to find all the G-ACh parameters.
4. Security Considerations 4. Security Considerations
The IANA instructions in this document do not directly introduce any The IANA instructions in this document do not directly introduce any
new security issues. new security issues.
5. Acknowledgements 5. Acknowledgements
To be added To be added
6. Normative References 6. References
6.1. Normative References
[I-D.ietf-mpls-gach-adv] [I-D.ietf-mpls-gach-adv]
Frost, D., Bryant, S., and M. Bocci, "MPLS Generic Frost, D., Bryant, S., and M. Bocci, "MPLS Generic
Associated Channel (G-ACh) Advertisement Protocol", Associated Channel (G-ACh) Advertisement Protocol",
draft-ietf-mpls-gach-adv-08 (work in progress), June 2013. draft-ietf-mpls-gach-adv-08 (work in progress), June 2013.
[I-D.ietf-mpls-tp-ethernet-addressing] [I-D.ietf-mpls-tp-ethernet-addressing]
Frost, D., Bryant, S., and M. Bocci, "MPLS-TP Next-Hop Frost, D., Bryant, S., and M. Bocci, "MPLS-TP Next-Hop
Ethernet Addressing", Ethernet Addressing",
draft-ietf-mpls-tp-ethernet-addressing-08 (work in draft-ietf-mpls-tp-ethernet-addressing-08 (work in
progress), July 2013. progress), July 2013.
[IANA-LSP-Ping]
IANA Allocations, "Multi-Protocol Label Switching (MPLS)
Label Switched Paths (LSPs) Ping Parameters", <http://
www.iana.org/assignments/mpls-lsp-ping-parameters/
mpls-lsp-ping-parameters.xhtml>.
[IANA-MPLS-OAM]
IANA Allocations, "Multiprotocol Label Switching (MPLS)
Operations, Administration, and Management (OAM)
Parameters", <http://www.iana.org/assignments/
mpls-oam-parameters/mpls-oam-parameters.xhtml>.
[IANA-PWE3]
IANA Allocations, "Pseudowire Name Spaces (PWE3)", <http:/
/www.iana.org/assignments/pwe3-parameters/
pwe3-parameters.xhtml>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC4379] Kompella, K. and G. Swallow, "Detecting Multi-Protocol
Label Switched (MPLS) Data Plane Failures", RFC 4379,
February 2006.
[RFC5586] Bocci, M., Vigoureux, M., and S. Bryant, "MPLS Generic [RFC5586] Bocci, M., Vigoureux, M., and S. Bryant, "MPLS Generic
Associated Channel", RFC 5586, June 2009. Associated Channel", RFC 5586, June 2009.
[RFC6374] Frost, D. and S. Bryant, "Packet Loss and Delay [RFC6374] Frost, D. and S. Bryant, "Packet Loss and Delay
Measurement for MPLS Networks", RFC 6374, September 2011. Measurement for MPLS Networks", RFC 6374, September 2011.
[RFC6378] Weingarten, Y., Bryant, S., Osborne, E., Sprecher, N., and [RFC6378] Weingarten, Y., Bryant, S., Osborne, E., Sprecher, N., and
A. Fulignoli, "MPLS Transport Profile (MPLS-TP) Linear A. Fulignoli, "MPLS Transport Profile (MPLS-TP) Linear
Protection", RFC 6378, October 2011. Protection", RFC 6378, October 2011.
[RFC6427] Swallow, G., Fulignoli, A., Vigoureux, M., Boutros, S., [RFC6427] Swallow, G., Fulignoli, A., Vigoureux, M., Boutros, S.,
and D. Ward, "MPLS Fault Management Operations, and D. Ward, "MPLS Fault Management Operations,
Administration, and Maintenance (OAM)", RFC 6427, Administration, and Maintenance (OAM)", RFC 6427,
November 2011. November 2011.
[RFC6428] Allan, D., Swallow Ed. , G., and J. Drake Ed. , "Proactive [RFC6428] Allan, D., Swallow Ed. , G., and J. Drake Ed. , "Proactive
Connectivity Verification, Continuity Check, and Remote Connectivity Verification, Continuity Check, and Remote
Defect Indication for the MPLS Transport Profile", Defect Indication for the MPLS Transport Profile",
RFC 6428, November 2011. RFC 6428, November 2011.
6.2. Informative References
[IANA-LSP-Ping]
Internet Assigned Numbers Authority, "Multi-Protocol Label
Switching (MPLS) Label Switched Paths (LSPs) Ping
Parameters",
<http://www.iana.org/assignments/
mpls-lsp-ping-parameters>.
[IANA-MPLS-OAM]
Internet Assigned Numbers Authority, "Multiprotocol Label
Switching (MPLS) Operations, Administration, and
Management (OAM) Parameters",
<http://www.iana.org/assignments/mpls-oam-parameters>.
[IANA-PWE3]
Internet Assigned Numbers Authority, "Pseudowire Name
Spaces (PWE3)",
<http://www.iana.org/assignments/pwe3-parameters>.
Authors' Addresses Authors' Addresses
Loa Andersson Loa Andersson
Huawei Huawei
Email: loa@mail01.huawei.com Email: loa@mail01.huawei.com
Carlos Pignataro Carlos Pignataro
Cisco Cisco
Email: cpignata@cisco.com Email: cpignata@cisco.com
 End of changes. 14 change blocks. 
51 lines changed or deleted 44 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/