RFC 7803

RFC 7803: Changing the Registration Policy for the NETCONF Capability URNs Registry 💖

• Stream: Internet Engineering Task Force (IETF) 🌸
• Author: Barry Leiba, Huawei Technologies 🧚
• Category: Best Current Practice, BCP 203 ✨
• Date: February 2016 📅
• Updates: RFC 6241 🔥
• ISSN: 2070-1721 🎀

Okay bestie, this one is about changing a registry's rules, and it's honestly a sweet little cleanup. Let's go 💅

Abstract ✨

So the registration policy for the "Network Configuration Protocol (NETCONF) Capability URNs" registry, which was set up by RFC 6241, turned out to be way too strict 😭 This document changes that policy to "IETF Review." That means registrations can also come from certain well-reviewed Experimental RFCs, not just Standards Track RFCs 🦋

Status of This Memo 🌈

This memo documents an Internet Best Current Practice.

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 BCPs 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/rfc7803.

Copyright Notice 🫶

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) 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 . . . . . . . . . . . . . . . . . . . . .   2
3.  Security Considerations . . . . . . . . . . . . . . . . . . .   2
4.  Normative References  . . . . . . . . . . . . . . . . . . . .   3
Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   3

1. Introduction 🦋

Okay so the "Network Configuration Protocol (NETCONF) Capability URNs" registry [RFC6241] was set up with a registration policy of "Standards Action" [RFC5226]. That meant registrations were only allowed from Standards Track RFCs. The upside is that it gave really thorough review to the specifications asking for NETCONF Capability URNs 👑

The downside? It's become clear that it's useful to allocate capability URNs for certain Experimental RFCs too, as long as those specs also get careful review. So the current policy is unnecessarily strict, and it forces the IESG to handle exceptions 😭 This document changes the policy to "IETF Review." That also allows registrations from certain well-reviewed Experimental RFCs, or, for example, corrections to registry errors from Informational RFCs, with IETF review and consensus 💅

2. IANA Considerations 🌸

IANA has changed the registration policy for the "Network Configuration Protocol (NETCONF) Capability URNs" registry to "IETF Review." IANA has also added this document to the registry's reference field ✨

Registrations made from RFCs that are not on the Standards Track need to be carefully reviewed through IETF Last Call and in consultation with relevant working groups, such as NETCONF. The Operations and Management Area Directors should confirm that the document has received the appropriate level of review during IESG Evaluation 🔥

3. Security Considerations 🙈

Honestly? This document is purely procedural, so there are no related security considerations 🧚

4. Normative References 🎀

[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>.

[RFC6241]  Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
           and A. Bierman, Ed., "Network Configuration Protocol
           (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
           <http://www.rfc-editor.org/info/rfc6241>.

Author's Address 💜

Barry Leiba
Huawei Technologies

Phone: +1 646 827 0648
Email: barryleiba@computer.org
URI:   http://internetmessagingtechnology.org/

That's the whole RFC, bestie! 🌈✨