draft-ietf-mpls-moving-iana-registries-01.txt   draft-ietf-mpls-moving-iana-registries-02.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 December 20, 2013 RFC-ietf-mpls-tp-ethernet-addressing December 22, 2013
(if approved) (if approved)
Intended status: Standards Track Intended status: Standards Track
Expires: June 23, 2014 Expires: June 25, 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-ietf-mpls-moving-iana-registries-01 draft-ietf-mpls-moving-iana-registries-02
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 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 RFC 6374, RFC 6428, RFC 6378, RFC 6427,
RFC-ietf-mpls-gach-adv-08, and RFC-ietf-mpls-gach-adv, and RFC-ietf-mpls-tp-ethernet-addressing.
RFC-ietf-mpls-tp-ethernet-addressing-08.
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 June 23, 2014. This Internet-Draft will expire on June 25, 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
skipping to change at page 2, line 22 skipping to change at page 2, line 21
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 . . . . . . . . . . . . . . . . . . . . . . . . . 3
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)
IANA registry . . . . . . . . . . . . . . . . . . . . . . . 3 IANA registry . . . . . . . . . . . . . . . . . . . . . . . 3
2.2. Renaming the Pseudowire Associated Channel Types 2.2. Renaming and moving the Pseudowire Associated Channel
registry . . . . . . . . . . . . . . . . . . . . . . . . . 4 Types registry . . . . . . . . . . . . . . . . . . . . . . 4
2.3. Consolidating G-ACh registries . . . . . . . . . . . . . . 4 2.3. Consolidating G-ACh registries . . . . . . . . . . . . . . 4
3. RFC Updates . . . . . . . . . . . . . . . . . . . . . . . . . . 5 3. RFC Updates . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
6.1. Normative References . . . . . . . . . . . . . . . . . . . 5 6.1. Normative References . . . . . . . . . . . . . . . . . . . 6
6.2. Informative References . . . . . . . . . . . . . . . . . . 6 6.2. Informative References . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 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 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].
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 "MPLS Generalized Associated Channel (G-ACh) Types
(including Pseudowire Associated Channel Types)" to make its (including Pseudowire Associated Channel Types)" to make its
generalized status explicit, and is moved into the newly created generalized status explicit, and is moved into the newly created
registry. registry.
Additionally, RFC 6374 [RFC6374], RFC 6428 [RFC6428], RFC 6378] Additionally, RFC 6374 [RFC6374], RFC 6428 [RFC6428], RFC 6378]
[RFC6378], RFC 6427 [RFC6427], RFC-ietf-mpls-gach-adv-08 [RFC6378], RFC 6427 [RFC6427], RFC-ietf-mpls-gach-adv
[I-D.ietf-mpls-gach-adv], and RFC-ietf-mpls-tp-ethernet-addressing-08 [I-D.ietf-mpls-gach-adv], and RFC-ietf-mpls-tp-ethernet-addressing
[I-D.ietf-mpls-tp-ethernet-addressing] specify allocations within the [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: Editor's note:
Need to fix the references to RFC-ietf-mpls-gach-adv-08 and RFC-ietf- Need to fix the references to RFC-ietf-mpls-gach-adv and RFC-ietf-
mpls-tp-ethernet-addressing-08 mpls-tp-ethernet-addressing
2. IANA Considerations 2. IANA Considerations
IANA is requested to add this document as a reference for any IANA is requested to add this document as a reference for any
registry that is moved or renamed as a result of actions requested by registry that is moved or renamed as a result of actions requested by
this document. this document.
IANA is also requested to replace all the relocated registries with IANA is also requested to replace all the relocated registries with
pointers to the new URL or with a redirect. pointers to the new URL or with a redirect.
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 and moving the Pseudowire Associated Channel Types
registry
This document renames the "Pseudowire Associated Channel Types" This document renames the "Pseudowire Associated Channel Types"
[IANA-PWE3] 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 moved and included as the first registration in the registry created
dependent upon the Associated Channel Header Type. in Section 2.1 because any additional registration is dependent upon
the Associated Channel Header Type.
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],
[RFC4385], [RFC5586], [RFC5718], [RFC5885], [RFC6374], [RFC6378],
[RFC6426], [RFC6427], [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 G-ACh
related registrations to a common "MPLS Generic Associated Channel related registrations to a common "MPLS Generic Associated Channel
Parameters" registry: Parameters" registry:
o From the PWE Registry [IANA-PWE3]: o From the PWE Registry [IANA-PWE3]:
* MPLS Generalized Associated Channel (G-ACh) Types [RFC5586] * MPLS Generalized Associated Channel (G-ACh) Types [RFC5586]
skipping to change at page 5, line 22 skipping to change at page 5, line 31
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] 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, 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.
skipping to change at page 7, line 5 skipping to change at page 7, line 10
Internet Assigned Numbers Authority, "Multiprotocol Label Internet Assigned Numbers Authority, "Multiprotocol Label
Switching (MPLS) Operations, Administration, and Switching (MPLS) Operations, Administration, and
Management (OAM) Parameters", Management (OAM) Parameters",
<http://www.iana.org/assignments/mpls-oam-parameters>. <http://www.iana.org/assignments/mpls-oam-parameters>.
[IANA-PWE3] [IANA-PWE3]
Internet Assigned Numbers Authority, "Pseudowire Name Internet Assigned Numbers Authority, "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,
"Pseudowire Emulation Edge-to-Edge (PWE3) Control Word for
Use over an MPLS PSN", RFC 4385, February 2006.
[RFC5718] Beller, D. and A. Farrel, "An In-Band Data Communication
Network For the MPLS Transport Profile", RFC 5718,
January 2010.
[RFC5885] Nadeau, T. and C. Pignataro, "Bidirectional Forwarding
Detection (BFD) for the Pseudowire Virtual Circuit
Connectivity Verification (VCCV)", RFC 5885, June 2010.
[RFC6426] Gray, E., Bahadur, N., Boutros, S., and R. Aggarwal, "MPLS
On-Demand Connectivity Verification and Route Tracing",
RFC 6426, November 2011.
[RFC6435] Boutros, S., Sivabalan, S., Aggarwal, R., Vigoureux, M.,
and X. Dai, "MPLS Transport Profile Lock Instruct and
Loopback Functions", RFC 6435, November 2011.
[RFC6478] Martini, L., Swallow, G., Heron, G., and M. Bocci,
"Pseudowire Status for Static Pseudowires", RFC 6478,
May 2012.
[RFC6671] Betts, M., "Allocation of a Generic Associated Channel
Type for ITU-T MPLS Transport Profile Operation,
Maintenance, and Administration (MPLS-TP OAM)", RFC 6671,
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 Cisco
Email: cpignata@cisco.com Email: cpignata@cisco.com
 End of changes. 15 change blocks. 
20 lines changed or deleted 54 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/