Moving Generic Associated Channel (G-ACh) IANA Registries to a New Registry
RFC 7214
Internet Engineering Task Force (IETF) L. Andersson
Request for Comments: 7214 Huawei
Updates: 5586, 6374, 6378, 6427, 6428 C. Pignataro
Category: Standards Track Cisco
ISSN: 2070-1721 May 2014
Moving Generic Associated Channel (G-ACh) IANA Registries
to a New Registry
Abstract
RFC 5586 generalized the applicability of the pseudowire Associated
Channel Header (PW-ACH) into the Generic Associated Channel G-ACh.
However, registries and allocations of G-ACh parameters had been
distributed throughout different, sometimes unrelated, registries.
This document coalesces these into a new "Generic Associated Channel
(G-ACh) Parameters" registry under the "Multiprotocol Label Switching
Architecture (MPLS)" heading. This document updates RFC 5586.
This document also updates RFCs 6374, 6378, 6427, and 6428.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
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.
Andersson & Pignataro Standards Track [Page 1]
RFC 7214 Creating G-ACh registries May 2014
Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
2.1. Creation of a New Generic Associated Channel (G-ACh)
Parameters IANA Registry . . . . . . . . . . . . . . . . 3
2.2. Renaming and Moving the Pseudowire Associated Channel
Types Registry . . . . . . . . . . . . . . . . . . . . . 3
2.3. Consolidating G-ACh Registries . . . . . . . . . . . . . 4
3. RFC Updates . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Security Considerations . . . . . . . . . . . . . . . . . . . 5
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
6.1. Normative References . . . . . . . . . . . . . . . . . . 5
6.2. Informative References . . . . . . . . . . . . . . . . . 6
1. Introduction
RFC 5586 generalized the PW-ACH into the G-ACh. However, registries
and allocations of G-ACh namespaces had been distributed throughout
different registries. This document coalesces these into a new
"Generic Associated Channel (G-ACh) Parameters" registry in the
"Multiprotocol Label Switching Architecture (MPLS)" name space. This
reorganization achieves two purposes: it allocates the G-ACh
registries in their natural place in the MPLS names space, and it
provides a single view of the G-ACh registries, to simplify future
assignments and avoid potential conflicts. This is an update to RFC
5586 [RFC5586].
Andersson & Pignataro Standards Track [Page 2]
RFC 7214 Creating G-ACh registries May 2014
Further, the "Pseudowire Associated Channel Types" registry is
renamed to "Generalized Associated Channel (G-ACh) Types (including
Pseudowire Associated Channel Types)" to make its generalized status
explicit, and it is moved into the newly created registry.
Additionally, RFC 6374 [RFC6374], RFC 6378 [RFC6378], RFC 6427
[RFC6427], and RFC 6428 [RFC6428] specify allocations within the
G-ACh that are now moved into the new registry.
With respect to where to find these IANA registries, the RFCs listed
above are updated as indicated in Section 3; however, the registries
themselves are not changed (with the exception of one being renamed).
They are moved unchanged to the new registry.
2. IANA Considerations
Show full document text