idnits 2.17.1 draft-leiba-netmod-regpolicy-update-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. -- The draft header indicates that this document updates RFC6241, but the abstract doesn't seem to directly say this. It does mention RFC6241 though, so this could be OK. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (December 21, 2015) is 3049 days in the past. Is this intentional? Checking references for intended status: Best Current Practice ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group B. Leiba 3 Internet-Draft Huawei Technologies 4 Updates: 6241 (if approved) December 21, 2015 5 Intended status: Best Current Practice 6 Expires: June 21, 2016 8 Changing the Registration Policy for the NETCONF Capability URNs 9 Registry 10 draft-leiba-netmod-regpolicy-update-02 12 Abstract 14 The registration policy for the Network Configuration Protocol 15 (NETCONF) Capability URNs registry, set up by RFC 6241, has turned 16 out to be unnecessarily strict. This document changes that 17 registration policy to "IETF Review", allowing registrations from 18 certain well reviewed Experimental RFCs, in addition to Standards 19 Track RFCs. 21 Status of this Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at http://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on June 21, 2016. 38 Copyright Notice 40 Copyright (c) 2015 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents (http://trustee.ietf.org/ 45 license-info) in effect on the date of publication of this document. 46 Please review these documents carefully, as they describe your rights 47 and restrictions with respect to this document. Code Components 48 extracted from this document must include Simplified BSD License text 49 as described in Section 4.e of the Trust Legal Provisions and are 50 provided without warranty as described in the Simplified BSD License. 52 1. Introduction 53 The Network Configuration Protocol (NETCONF) Capability URNs registry 54 [RFC6241], was set up with a registration policy of "Standards 55 Action" [RFC5226], allowing registrations only from Standards Track 56 RFCs. This provided thorough review of the specifications that are 57 requesting NETCONF Capability URNs. It has turned out to be 58 desirable to allocate capability URNs for certain Experimental RFCs 59 also, provided those specifications are also carefully reviewed. The 60 existing registration policy is, therefore, unnecessarily strict, 61 requiring exception handling by the IESG. This document changes that 62 registration policy to "IETF Review", which also allows registrations 63 from certain well reviewed Experimental RFCs, or, for example, 64 corrections to registry errors from Informational RFCs, with IETF 65 review and consensus. 67 2. IANA Considerations 69 IANA is asked to change the registration policy for the Network 70 Configuration Protocol (NETCONF) Capability URNs registry to "IETF 71 Review", and to add this document to the registry's reference field. 73 Registrations made from RFCs that are not on the Standards Track need 74 to be carefully reviewed through IETF Last Call and consultation with 75 relevant working groups, such as NETCONF. The Operations and 76 Management Area Directors should confirm the appropriate level of 77 review during IESG Evaluation. 79 3. Security Considerations 81 This document is purely procedural, and there are no related security 82 considerations. 84 4. NOTE 86 [RFC Editor: Please remove this section and make sure the title of 87 the references section is "Normative References". The version of 88 xml2rfc that I'm using ignores my section title and just calls it 89 "References".] 91 5. References 93 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 94 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 95 May 2008. 97 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J.Ed., 98 and A. Bierman, Ed., "Network Configuration Protocol 99 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 100 . 102 Author's Address 103 Barry Leiba 104 Huawei Technologies 106 Phone: +1 646 827 0648 107 Email: barryleiba@computer.org 108 URI: http://internetmessagingtechnology.org/