RFC 7892

IANA Allocation Procedures for the GMPLS OTN Signal Type Registry

📅 published May 2016, from ietf

RFC 7892 💖 IANA Allocation Procedures for the GMPLS OTN Signal Type Registry

Okay bestie, here's the title block tea ☕✨. This is RFC 7892, and it's by Z. Ali, A. Bonfanti, and M. Hartley from Cisco Systems 💅, plus F. Zhang from Huawei Technologies 🌸. It came out in May 2016 as a Standards Track document (ISSN 2070-1721) 🔥. It updates RFC 7139 and doesn't list anything it obsoletes 🦋.

Abstract ✨

So IANA set up the "OTN Signal Type" subregistry inside the "Generalized Multi-Protocol Label Switching (GMPLS) Signaling Parameters" registry back in RFC 7139 🎀. This document updates that subregistry so it can also take registrations through Specification Required 💜.

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, got public review, and was approved for publication by the Internet Engineering Steering Group (IESG) 👑. If you want more on Internet Standards, check out Section 2 of RFC 7841 🍓.

For the current status of this document, any errata, and how to send feedback, go to http://www.rfc-editor.org/info/rfc7892 💅.

Copyright (c) 2016 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) as they're in effect on the publication date 📖. Please actually read these, because they spell out your rights and restrictions for this document 🙈. Code Components pulled out of this document have to include the Simplified BSD License text described in Section 4.e of the Trust Legal Provisions, and they come with no warranty, as the Simplified BSD License describes 💜.

This document might contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008 🦋. The people who control the copyright in some of that older material may not have given the IETF Trust permission to allow modifications outside the IETF Standards Process 😭. So unless you get a proper license from those copyright holders, this document can't be modified outside the IETF Standards Process, and derivative works can't be created outside it either. The one exceptions are formatting it for publication as an RFC or translating it into languages other than English 🫶.

Table of Contents 🗂️

1. Introduction ................................................... 2
2. Security Considerations ........................................ 3
3. IANA Considerations ............................................ 3
4. References ..................................................... 3
   4.1. Normative References ...................................... 3
   4.2. Informative References .................................... 3
Acknowledgments ................................................... 4
Authors' Addresses ................................................ 4

1. Introduction 🦋

IANA keeps the "OTN Signal Type" subregistry of the "Generalized Multi-Protocol Label Switching (GMPLS) Signaling Parameters" registry for OTN signal types, as defined in [RFC4328] and updated by [RFC7139] 🌸. This subregistry only uses the Standards Action registration policy from [RFC5226] 🙃. This document updates [RFC7139] so the "OTN Signal Type" subregistry can also use the Specification Required policy from [RFC5226] 💖.

2. Security Considerations 💀

Okay, the big security tea: this document doesn't introduce any new security considerations to the existing GMPLS signaling protocols 🔐. For the specific security measures, go check [RFC7139] 🎀. Also, [RFC5920] gives an overview of security vulnerabilities and protection mechanisms for the GMPLS control plane 🛡️. Take it seriously, bestie 😤.

3. IANA Considerations 📋

IANA maintains the "OTN Signal Type" subregistry of the "Generalized Multi-Protocol Label Switching (GMPLS) Signaling Parameters" registry 🧾. Right now it's defined to use the Standards Action registration policy from [RFC5226] 💅.

Per this document, IANA has updated the registration policies for the "OTN Signal Type" subregistry 🎉. Standards Track documents get "Standards Action", and other documents get "Specification Required" ✨.

4. References 📚

4.1. Normative References 🔥

[RFC4328]  Papadimitriou, D., Ed., "Generalized Multi-Protocol Label
           Switching (GMPLS) Signaling Extensions for G.709 Optical
           Transport Networks Control", RFC 4328,
           DOI 10.17487/RFC4328, January 2006,
           <http://www.rfc-editor.org/info/rfc4328>.

[RFC7139]  Zhang, F., Ed., Zhang, G., Belotti, S., Ceccarelli, D.,
           and K. Pithewan, "GMPLS Signaling Extensions for Control
           of Evolving G.709 Optical Transport Networks", RFC 7139,
           DOI 10.17487/RFC7139, March 2014,
           <http://www.rfc-editor.org/info/rfc7139>.

[RFC5226]  Narten, T. and H. Alvestrand, "Guidelines for Writing an
           IANA Considerations Section in RFCs", BCP 26, RFC 5226,
           DOI 10.17487/RFC5226, May 2008,
           <http://www.rfc-editor.org/info/rfc5226>.

4.2. Informative References 🌈

[RFC5920]  Fang, L., Ed., "Security Framework for MPLS and GMPLS
           Networks", RFC 5920, DOI 10.17487/RFC5920, July 2010,
           <http://www.rfc-editor.org/info/rfc5920>.

Acknowledgments 🫶

The authors want to thank Lou Berger, Deborah Brungard, Daniele Ceccarelli, Adrian Farrel, Vijay Gurbani, Huub van Helvoort, Barry Leiba, and Robert Sparks for their comments 💕.

Authors' Addresses 💌

Zafar Ali
Cisco Systems

Email: zali@cisco.com


Antonello Bonfanti
Cisco Systems

Email: abonfant@cisco.com


Matt Hartley
Cisco Systems

Email: mhartley@cisco.com


Fatai Zhang
Huawei Technologies

Email: zhangfatai@huawei.com
📦 where this page comes from