RFC 7214

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

📅 published May 2014, from ietf

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

okay bestie, so this is RFC 7214 🎀 It's a Standards Track doc from May 2014 (ISSN 2070-1721), written by Loa Andersson (Huawei) and Carlos Pignataro (Cisco). It updates RFC 5586, RFC 6374, RFC 6378, RFC 6427, and RFC 6428 💅 The title block doesn't list any "Obsoletes" entry, so nothing gets retired here. The whole vibe is about reorganizing where the G-ACh registries live so everything is in one place 🦋

Abstract 💖

okay so RFC 5586 took the pseudowire Associated Channel Header (PW-ACH) and glowed it up into the Generic Associated Channel (G-ACh) 🌸 but the registries and allocations for G-ACh parameters were scattered everywhere, across different (sometimes totally unrelated) registries 😭 this document gathers them all into one new "Generic Associated Channel (G-ACh) Parameters" registry under the "Multiprotocol Label Switching Architecture (MPLS)" heading 🧚 it updates RFC 5586 ✨

it also updates RFCs 6374, 6378, 6427, and 6428 🫶

Status of This Memo 🌈

this is an Internet Standards Track document ✨

it's a product of the Internet Engineering Task Force (IETF) 💅 it represents the consensus of the IETF community, received public review, and got approved for publication by the Internet Engineering Steering Group (IESG) 👑 if you want more on Internet Standards, check out Section 2 of RFC 5741 🎀

info about the current status, any errata, and how to give feedback lives at http://www.rfc-editor.org/info/rfc7214 🍓

Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved. 💖

this doc is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) as they stand on the publication date 📜 please actually read them, because they spell out your rights and restrictions for this document 🙈 any Code Components pulled out of this document have to include Simplified BSD License text, as described in Section 4.e of the Trust Legal Provisions, and they come with no 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 ✨

okay so RFC 5586 turned the PW-ACH into the G-ACh 🌸 but the registries and allocations of G-ACh namespaces were spread across a bunch of different registries 😭 this document brings them together into one new "Generic Associated Channel (G-ACh) Parameters" registry in the "Multiprotocol Label Switching Architecture (MPLS)" name space 💅 this reorg does two things: it puts the G-ACh registries in their natural home in the MPLS name space, and it gives you a single view of them, so future assignments are easier and potential conflicts are less likely 🧚 this is an update to RFC 5586 [RFC5586] ✨

also, the "Pseudowire Associated Channel Types" registry gets renamed to "Generalized Associated Channel (G-ACh) Types (including Pseudowire Associated Channel Types)" so its generalized status is super explicit, and it moves into the newly created registry 🦋

plus, RFC 6374 [RFC6374], RFC 6378 [RFC6378], RFC 6427 [RFC6427], and RFC 6428 [RFC6428] make allocations within the G-ACh that are now moving into the new registry 🫶

for where to find these IANA registries, the RFCs above get updated as Section 3 explains 💖 the registries themselves aren't changed (except for one that gets renamed) 🌈 they're moved unchanged into the new registry 🍓

2. IANA Considerations 👑

IANA has added this document as a reference for each registry that has been moved or renamed because of the actions requested here 🎀

IANA has replaced all the relocated registries with pointers to the new URL or with a redirect 💅

2.1. Creation of a New Generic Associated Channel (G-ACh) Parameters IANA Registry 🧚

IANA created a new "Generic Associated Channel (G-ACh) Parameters" registry 🌸 it's the common registry that will include all the registries being moved in Sections 2.2 and 2.3 ✨

2.2. Renaming and Moving the Pseudowire Associated Channel Types Registry 🦋

this document renames the "Pseudowire Associated Channel Types" registry [IANA-PWE3] to "MPLS Generalized Associated Channel (G-ACh) Types (including Pseudowire Associated Channel Types)" 💖 it's been moved and included in the "Generic Associated Channel (G-ACh) Parameters" registry from Section 2.1, because any additional registries depend on the Associated Channel Header Type 🫶

when this document was published and the registry moved, these RFCs had G-ACh Types allocated: [RFC4385], [RFC5586], [RFC5718], [RFC5885], [RFC6374], [RFC6378], [RFC6426], [RFC6427], [RFC6428], [RFC6435], [RFC6478], and [RFC6671] 🌈

2.3. Consolidating G-ACh Registries 🍓

this document also updates the following RFCs by moving their G-ACh registries into the common "Generic Associated Channel (G-ACh) Parameters" registry from Section 2.1 🎀

  • from the PWE Parameters Registry [IANA-PWE3]:
    • MPLS Generalized Associated Channel (G-ACh) Types [RFC5586]
    • CC/CV MEP-ID TLV Registry [RFC6428]
  • from the MPLS LSP Ping Parameters Registry [IANA-LSP-Ping]:
    • Measurement Timestamp Type [RFC6374]
    • Loss/Delay Measurement Control Code: Query Codes [RFC6374]
    • Loss/Delay Measurement Control Code: Response Codes [RFC6374]
    • MPLS Loss/Delay Measurement TLV Object [RFC6374]
  • from the MPLS OAM Parameters Registry [IANA-MPLS-OAM]:
    • MPLS Fault OAM Message Type Registry [RFC6427]
    • MPLS Fault OAM Flag Registry [RFC6427]
    • MPLS Fault OAM TLV Registry [RFC6427]
    • MPLS PSC Request Registry [RFC6378]
    • MPLS PSC TLV Registry [RFC6378]

plot twist 😭 all the sub-registries in [IANA-MPLS-OAM] have been removed from the "Multiprotocol Label Switching (MPLS) Operations, Administration, and Management (OAM) Parameters" registry, so IANA removed the MPLS OAM registry per this document 💀

3. RFC Updates 🌸

this document updates [RFC5586] by renaming the "Pseudowire Associated Channel Types" [IANA-PWE3] to "MPLS Generalized Associated Channel (G-ACh) Types (including Pseudowire Associated Channel Types)" 💅

it also updates RFCs 6374, 6378, 6427, and 6428 by moving their G-ACh related registries into a common "MPLS Generic Associated Channel (G-ACh) Parameters" registry ✨

all the registries listed above are moved without any changes to their content 🦋 the whole point is to create one single place where you can find all the G-ACh parameters 🫶

4. Security Considerations 🔥

the IANA instructions in this document don't directly introduce any new security issues 💅

5. Acknowledgements 💖

the authors want to thank Amanda Baber and Scott Bradner for their review and valuable comments 🧚 iconic behavior 👑

6. References 🌈

6.1. Normative References 🦋

[RFC5586] Bocci, M., Vigoureux, M., and S. Bryant, "MPLS Generic Associated Channel", RFC 5586, June 2009.

[RFC6374] Frost, D. and S. Bryant, "Packet Loss and Delay Measurement for MPLS Networks", RFC 6374, September 2011.

[RFC6378] Weingarten, Y., Bryant, S., Osborne, E., Sprecher, N., and A. Fulignoli, "MPLS Transport Profile (MPLS-TP) Linear Protection", RFC 6378, October 2011.

[RFC6427] Swallow, G., Fulignoli, A., Vigoureux, M., Boutros, S., and D. Ward, "MPLS Fault Management Operations, Administration, and Maintenance (OAM)", RFC 6427, November 2011.

[RFC6428] Allan, D., Swallow Ed. , G., and J. Drake Ed. , "Proactive Connectivity Verification, Continuity Check, and Remote Defect Indication for the MPLS Transport Profile", RFC 6428, November 2011.

6.2. Informative References 💜

[IANA-LSP-Ping] IANA, "Multi-Protocol Label Switching (MPLS) Label Switched Paths (LSPs) Ping Parameters", http://www.iana.org/assignments/mpls-lsp-ping-parameters.

[IANA-MPLS-OAM] IANA, "Multiprotocol Label Switching (MPLS) Operations, Administration, and Management (OAM) Parameters", content has been moved to http://www.iana.org/assignments/g-ach-parameters/.

[IANA-PWE3] IANA, "Pseudowire Name Spaces (PWE3)", 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 🫶

Loa Andersson 🎀 Huawei EMail: loa@mail01.huawei.com

Carlos Pignataro 💅 Cisco Systems, Inc. EMail: cpignata@cisco.com

📦 where this page comes from