ietf-corpus

rfc-7214

Moving Generic Associated Channel (G-ACh) IANA Registries to a New Registry

L. Andersson, C. Pignataro
date2014-05 streamIETF areartg wgmpls statusPROPOSED STANDARD pages7 canonicalhttps://www.rfc-editor.org/rfc/rfc7214 doi10.17487/RFC7214
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.

updates

Extracted elements (10)

design-rationale §3

All relocated registries were moved without any changes to their content — the sole purpose of the move was to create a single place where all G-ACh parameters can be found. The "Associated Channel Types" sub-registry was placed as the parent because all other G-ACh registries depend upon the Associated Channel Header Type.

mpls, registry

design-rationale §1

The reorganization achieves two purposes: it places the G-ACh registries in their natural location within the MPLS namespace, and it provides a single consolidated view of all G-ACh registries. This simplifies future assignments and avoids potential conflicts that arose from parameters being scattered across unrelated registries.

mpls, registry

interoperability-note §3

This document updates RFCs 5586, 6374, 6378, 6427, and 6428 solely by relocating their G-ACh-related registries. Implementations referencing IANA registry URLs from those RFCs should follow the redirects to the new "Generic Associated Channel (G-ACh) Parameters" registry location.

mpls, registry

normative-requirement §2 REQUIRED

IANA must add this document as a reference for each registry that was moved or renamed, and must replace all relocated registries with pointers to the new URL or with a redirect.

mpls, registry

registry §2.3

Five registries were moved from the MPLS OAM Parameters Registry (IANA-MPLS-OAM) into the new G-ACh Parameters registry: MPLS Fault OAM Message Type, MPLS Fault OAM Flag, MPLS Fault OAM TLV (all RFC 6427), MPLS PSC Request, and MPLS PSC TLV (both RFC 6378). The MPLS OAM registry itself was subsequently removed as all its sub-registries had been relocated.

mpls, registry

registry §2.3

Four registries were moved from the MPLS LSP Ping Parameters Registry (IANA-LSP-Ping) into the new G-ACh Parameters registry: Measurement Timestamp Type, Loss/Delay Measurement Control Code: Query Codes, Loss/Delay Measurement Control Code: Response Codes, and MPLS Loss/Delay Measurement TLV Object — all from RFC 6374.

mpls, registry, measurement

registry §2.1

IANA created a new "Generic Associated Channel (G-ACh) Parameters" registry under the "Multiprotocol Label Switching Architecture (MPLS)" heading. This serves as the common parent registry consolidating all G-ACh-related sub-registries previously scattered across unrelated registries.

mpls, registry

registry §2.2

The "Pseudowire Associated Channel Types" registry (previously in IANA-PWE3) was renamed to "MPLS Generalized Associated Channel (G-ACh) Types (including Pseudowire Associated Channel Types)" and moved into the new G-ACh Parameters registry. At the time of publication, allocations from RFCs 4385, 5586, 5718, 5885, 6374, 6378, 6426, 6427, 6428, 6435, 6478, and 6671 were included.

mpls, registry

registry §2.3

Two registries were moved from the PWE Parameters Registry (IANA-PWE3) into the new G-ACh Parameters registry: "MPLS Generalized Associated Channel (G-ACh) Types" (RFC 5586) and "CC/CV MEP-ID TLV Registry" (RFC 6428).

mpls, registry

security-consideration §4

The IANA registry consolidation instructions in this document do not directly introduce any new security issues. The registries are moved with their content unchanged.

security, mpls