draft-ietf-mpls-moving-iana-registries-04.txt   rfc7214.txt 
Network Working Group L. Andersson Internet Engineering Task Force (IETF) L. Andersson
Internet-Draft Huawei Request for Comments: 7214 Huawei
Updates: 5586, 6374, 6378, 6427, 6428, C. Pignataro Updates: 5586, 6374, 6378, 6427, 6428 C. Pignataro
RFC-ietf-mpls-gach-adv, Cisco Category: Standards Track Cisco
RFC-ietf-mpls-tp-ethernet-addressing January 26, 2014 ISSN: 2070-1721 May 2014
(if approved)
Intended status: Standards Track
Expires: July 30, 2014
Moving Generic Associated Channel (G-ACh) IANA Registries to a New Moving Generic Associated Channel (G-ACh) IANA Registries
Registry to a New Registry
draft-ietf-mpls-moving-iana-registries-04
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) Parameters" registry under the "Multiprotocol Label Switching (G-ACh) Parameters" registry under the "Multiprotocol Label Switching
Architecture (MPLS)" heading. This document updates RFC 5586. Architecture (MPLS)" heading. This document updates RFC 5586.
This document also updates RFC 6374, RFC 6428, RFC 6378, RFC 6427, This document also updates RFCs 6374, 6378, 6427, and 6428.
RFC-ietf-mpls-gach-adv, and RFC-ietf-mpls-tp-ethernet-addressing.
Status of this Memo
This Internet-Draft is submitted in full conformance with the Status of This Memo
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering This is an Internet Standards Track document.
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
This Internet-Draft will expire on July 30, 2014. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7214.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 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
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 . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 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)
Parameters IANA Registry . . . . . . . . . . . . . . . . . 3 Parameters IANA Registry . . . . . . . . . . . . . . . . 3
2.2. Renaming and Moving the Pseudowire Associated Channel 2.2. Renaming and Moving the Pseudowire Associated Channel
Types Registry . . . . . . . . . . . . . . . . . . . . . . 4 Types Registry . . . . . . . . . . . . . . . . . . . . . 3
2.3. Consolidating G-ACh Registries . . . . . . . . . . . . . . 4 2.3. Consolidating G-ACh Registries . . . . . . . . . . . . . 4
3. RFC Updates . . . . . . . . . . . . . . . . . . . . . . . . . . 5 3. RFC Updates . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 4. Security Considerations . . . . . . . . . . . . . . . . . . . 5
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
6.1. Normative References . . . . . . . . . . . . . . . . . . . 6 6.1. Normative References . . . . . . . . . . . . . . . . . . 5
6.2. Informative References . . . . . . . . . . . . . . . . . . 6 6.2. Informative References . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7
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 (G-ACh) Parameters" registry in the "Generic Associated Channel (G-ACh) Parameters" registry in the
"Multiprotocol Label Switching Architecture (MPLS)" name space. This "Multiprotocol Label Switching Architecture (MPLS)" name space. This
reorganization achieves two purposes: it allocates the G-ACh reorganization achieves two purposes: it allocates the G-ACh
registries in their natural place in the MPLS names space, and it is registries in their natural place in the MPLS names space, and it
needed to get a single view of the G-ACh registries, to simplify provides a single view of the G-ACh registries, to simplify future
future assignments, and to avoid potential conflicts. This is an assignments and avoid potential conflicts. This is an update to RFC
update to RFC RFC 5586 [RFC5586]. 5586 [RFC5586].
Further, the "Pseudowire Associated Channel Types" registry is Further, the "Pseudowire Associated Channel Types" registry is
renamed to "MPLS Generalized Associated Channel (G-ACh) Types renamed to "Generalized Associated Channel (G-ACh) Types (including
(including Pseudowire Associated Channel Types)" to make its Pseudowire Associated Channel Types)" to make its generalized status
generalized status explicit, and is moved into the newly created explicit, and it is moved into the newly created registry.
registry.
Additionally, RFC 6374 [RFC6374], RFC 6428 [RFC6428], RFC 6378] Additionally, RFC 6374 [RFC6374], RFC 6378 [RFC6378], RFC 6427
[RFC6378], RFC 6427 [RFC6427], RFC-ietf-mpls-gach-adv [RFC6427], and RFC 6428 [RFC6428] specify allocations within the
[I-D.ietf-mpls-gach-adv], and RFC-ietf-mpls-tp-ethernet-addressing
[I-D.ietf-mpls-tp-ethernet-addressing] specify allocations within the
G-ACh that are now moved into the new registry. G-ACh that are now moved into the new registry.
With respect to where to find these IANA registries, the RFCs listed With respect to where to find these IANA registries, the RFCs listed
above are updated as indicated in Section 3; however the registries above are updated as indicated in Section 3; however, the registries
themselves are not changed (with the exception of one being renamed). themselves are not changed (with the exception of one being renamed).
They are moved unchanged to the new registry. They are moved unchanged to the new registry.
Editor's note:
Need to fix the references to RFC-ietf-mpls-gach-adv and RFC-ietf-
mpls-tp-ethernet-addressing
2. IANA Considerations 2. IANA Considerations
IANA is requested to add this document as a reference for any IANA has added this document as a reference for each registry that
registry that is moved or renamed as a result of actions requested by has been moved or renamed as a result of actions requested by this
this document. document.
IANA is also requested to replace all the relocated registries with IANA has replaced all the relocated registries with pointers to the
pointers to the new URL or with a redirect. new URL or with a redirect.
2.1. Creation of a New Generic Associated Channel (G-ACh) Parameters 2.1. Creation of a New Generic Associated Channel (G-ACh) Parameters
IANA Registry IANA Registry
IANA is requested to create a new "Generic Associated Channel (G-ACh) IANA has created a new "Generic Associated Channel (G-ACh)
Parameters" registry under the "Multiprotocol Label Switching Parameters" registry. This is the common registry that will include
Architecture (MPLS)" heading. This is the common registry that will all the registries being moved in Sections 2.2 and 2.3.
include all the registries being moved in Sections 2.2 and 2.3.
2.2. Renaming and Moving the Pseudowire Associated Channel Types 2.2. Renaming and Moving the Pseudowire Associated Channel Types
Registry Registry
This document renames the "Pseudowire Associated Channel Types" This document renames the "Pseudowire Associated Channel Types"
registry [IANA-PWE3] into "MPLS Generalized Associated Channel registry [IANA-PWE3] to "MPLS Generalized Associated Channel (G-ACh)
(G-ACh) Types (including Pseudowire Associated Channel Types)". This Types (including Pseudowire Associated Channel Types)". This
registry is moved and included as the first registry in the "Generic registry has been moved and included in the "Generic Associated
Associated Channel (G-ACh) Parameters" registry created in Channel (G-ACh) Parameters" registry created in Section 2.1 because
Section 2.1 because any additional registries are dependent upon the any additional registries are dependent upon the Associated Channel
Associated Channel Header Type. Header Type.
At the time of publishing this document and moving the registry, the At the time of publishing this document and moving the registry, the
following RFCs have G-ACh Types allocated: [I-D.ietf-mpls-gach-adv], following RFCs have G-ACh Types allocated: [RFC4385], [RFC5586],
[RFC4385], [RFC5586], [RFC5718], [RFC5885], [RFC6374], [RFC6378], [RFC5718], [RFC5885], [RFC6374], [RFC6378], [RFC6426], [RFC6427],
[RFC6426], [RFC6427], [RFC6428], [RFC6435], [RFC6478], and [RFC6671]. [RFC6428], [RFC6435], [RFC6478], and [RFC6671].
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
related registries to the common "MPLS Generic Associated Channel registries related to G-ACh to the common "Generic Associated Channel
(G-ACh) Parameters" registry created in Section 2.1: (G-ACh) Parameters" registry created in Section 2.1.
o From the PWE Parameters Registry [IANA-PWE3]: o From the PWE Parameters Registry [IANA-PWE3]:
* MPLS Generalized Associated Channel (G-ACh) Types [RFC5586] * MPLS Generalized Associated Channel (G-ACh) Types [RFC5586]
* G-ACh Advertisement Protocol Application Registry
[I-D.ietf-mpls-gach-adv]
* G-ACh Advertisement Protocol TLV Registry
[I-D.ietf-mpls-gach-adv]
* G-ACh Advertisement Protocol: Ethernet Interface Parameters
[I-D.ietf-mpls-tp-ethernet-addressing]
* CC/CV MEP-ID TLV Registry [RFC6428] * CC/CV MEP-ID TLV Registry [RFC6428]
o From the MPLS LSP Ping Parameters Registry [IANA-LSP-Ping]: o From the MPLS LSP Ping Parameters Registry [IANA-LSP-Ping]:
* Measurement Timestamp Type [RFC6374] * Measurement Timestamp Type [RFC6374]
* Loss/Delay Measurement Control Code: Query Codes [RFC6374] * Loss/Delay Measurement Control Code: Query Codes [RFC6374]
* Loss/Delay Measurement Control Code: Response Codes [RFC6374] * Loss/Delay Measurement Control Code: Response Codes [RFC6374]
* MPLS Loss/Delay Measurement TLV Object [RFC6374] * MPLS Loss/Delay Measurement TLV Object [RFC6374]
o From the MPLS OAM Parameters Registry [IANA-MPLS-OAM]: o From the MPLS OAM Parameters Registry [IANA-MPLS-OAM]:
* MPLS Fault OAM Message Type Registry [RFC6427] * MPLS Fault OAM Message Type Registry [RFC6427]
* MPLS Fault OAM Flag Registry [RFC6427] * MPLS Fault OAM Flag Registry [RFC6427]
skipping to change at page 5, line 20 skipping to change at page 4, line 39
* MPLS Fault OAM Message Type Registry [RFC6427] * MPLS Fault OAM Message Type Registry [RFC6427]
* MPLS Fault OAM Flag Registry [RFC6427] * MPLS Fault OAM Flag Registry [RFC6427]
* MPLS Fault OAM TLV Registry [RFC6427] * MPLS Fault OAM TLV Registry [RFC6427]
* MPLS PSC Request Registry [RFC6378] * MPLS PSC Request Registry [RFC6378]
* MPLS PSC TLV Registry [RFC6378] * MPLS PSC TLV Registry [RFC6378]
Note that all the sub-registries in [IANA-MPLS-OAM] are moved from Note that all the sub-registries in [IANA-MPLS-OAM] have been
"Multiprotocol Label Switching (MPLS) Operations, Administration, removed from "Multiprotocol Label Switching (MPLS) Operations,
and Management (OAM) Parameters" registry. The IANA is therefore Administration, and Management (OAM) Parameters" registry.
requested to remove the "MPLS OAM" registry. Therefore, the IANA has removed the MPLS OAM registry, per this
document.
3. RFC Updates 3. RFC Updates
This document updates [RFC5586] renaming the "Pseudowire Associated This document updates [RFC5586] renaming the "Pseudowire Associated
Channel Types" [IANA-PWE3] into "MPLS Generalized Associated Channel Channel Types" [IANA-PWE3] to "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 registries to a common "MPLS Generic Associated Channel related registries to a common "MPLS Generic Associated Channel
(G-ACh) Parameters" registry: RFC 6374, RFC 6428, RFC 6378, RFC 6427, (G-ACh) Parameters" registry: RFCs 6374, 6378, 6427, and 6428.
RFC-ietf-mpls-gach-adv, and RFC-ietf-mpls-tp-ethernet-addressing.
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
The authors want to thank Amanda Barber and Scott Bradner for review The authors want to thank Amanda Baber and Scott Bradner for review
and valuable comments. and valuable comments.
6. References 6. References
6.1. Normative References 6.1. Normative References
[I-D.ietf-mpls-gach-adv]
Frost, D., Bryant, S., and M. Bocci, "MPLS Generic
Associated Channel (G-ACh) Advertisement Protocol",
draft-ietf-mpls-gach-adv-08 (work in progress), June 2013.
[I-D.ietf-mpls-tp-ethernet-addressing]
Frost, D., Bryant, S., and M. Bocci, "MPLS-TP Next-Hop
Ethernet Addressing",
draft-ietf-mpls-tp-ethernet-addressing-08 (work in
progress), July 2013.
[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
November 2011. 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
RFC 6428, November 2011. 6428, November 2011.
6.2. Informative References 6.2. Informative References
[IANA-LSP-Ping] [IANA-LSP-Ping]
Internet Assigned Numbers Authority, "Multi-Protocol Label IANA, "Multi-Protocol Label Switching (MPLS) Label
Switching (MPLS) Label Switched Paths (LSPs) Ping Switched Paths (LSPs) Ping Parameters",
Parameters",
<http://www.iana.org/assignments/ <http://www.iana.org/assignments/
mpls-lsp-ping-parameters>. mpls-lsp-ping-parameters>.
[IANA-MPLS-OAM] [IANA-MPLS-OAM]
Internet Assigned Numbers Authority, "Multiprotocol Label IANA, "Multiprotocol Label Switching (MPLS) Operations,
Switching (MPLS) Operations, Administration, and Administration, and Management (OAM) Parameters", content
Management (OAM) Parameters", has been moved to
<http://www.iana.org/assignments/mpls-oam-parameters>. <http://www.iana.org/assignments/g-ach-parameters/>.
[IANA-PWE3] [IANA-PWE3]
Internet Assigned Numbers Authority, "Pseudowire Name IANA, "Pseudowire Name Spaces (PWE3)",
Spaces (PWE3)",
<http://www.iana.org/assignments/pwe3-parameters>. <http://www.iana.org/assignments/pwe3-parameters>.
[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 for "Pseudowire Emulation Edge-to-Edge (PWE3) Control Word for
Use over an MPLS PSN", RFC 4385, February 2006. Use over an MPLS PSN", RFC 4385, February 2006.
[RFC5718] Beller, D. and A. Farrel, "An In-Band Data Communication [RFC5718] Beller, D. and A. Farrel, "An In-Band Data Communication
Network For the MPLS Transport Profile", RFC 5718, Network For the MPLS Transport Profile", RFC 5718, January
January 2010. 2010.
[RFC5885] Nadeau, T. and C. Pignataro, "Bidirectional Forwarding [RFC5885] Nadeau, T. and C. Pignataro, "Bidirectional Forwarding
Detection (BFD) for the Pseudowire Virtual Circuit Detection (BFD) for the Pseudowire Virtual Circuit
Connectivity Verification (VCCV)", RFC 5885, June 2010. Connectivity Verification (VCCV)", RFC 5885, June 2010.
[RFC6426] Gray, E., Bahadur, N., Boutros, S., and R. Aggarwal, "MPLS [RFC6426] Gray, E., Bahadur, N., Boutros, S., and R. Aggarwal, "MPLS
On-Demand Connectivity Verification and Route Tracing", On-Demand Connectivity Verification and Route Tracing",
RFC 6426, November 2011. RFC 6426, November 2011.
[RFC6435] Boutros, S., Sivabalan, S., Aggarwal, R., Vigoureux, M., [RFC6435] Boutros, S., Sivabalan, S., Aggarwal, R., Vigoureux, M.,
and X. Dai, "MPLS Transport Profile Lock Instruct and and X. Dai, "MPLS Transport Profile Lock Instruct and
Loopback Functions", RFC 6435, November 2011. Loopback Functions", RFC 6435, November 2011.
[RFC6478] Martini, L., Swallow, G., Heron, G., and M. Bocci, [RFC6478] Martini, L., Swallow, G., Heron, G., and M. Bocci,
"Pseudowire Status for Static Pseudowires", RFC 6478, "Pseudowire Status for Static Pseudowires", RFC 6478, May
May 2012. 2012.
[RFC6671] Betts, M., "Allocation of a Generic Associated Channel [RFC6671] Betts, M., "Allocation of a Generic Associated Channel
Type for ITU-T MPLS Transport Profile Operation, Type for ITU-T MPLS Transport Profile Operation,
Maintenance, and Administration (MPLS-TP OAM)", RFC 6671, Maintenance, and Administration (MPLS-TP OAM)", RFC 6671,
November 2012. November 2012.
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 Systems, Inc. Cisco Systems, Inc.
Email: cpignata@cisco.com EMail: cpignata@cisco.com
 End of changes. 37 change blocks. 
122 lines changed or deleted 85 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/