idnits 2.17.1 draft-rosen-rph-reg-policy-01.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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC4412, updated by this document, for RFC5378 checks: 2003-06-24) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (August 19, 2013) is 3903 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (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: 1 error (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 sipcore B. Rosen 3 Internet-Draft NeuStar 4 Updates: 4412 (if approved) August 19, 2013 5 Intended status: Standards Track 6 Expires: February 20, 2014 8 Resource Priority Header (RPH) Registry Management Policy to IETF Review 9 draft-rosen-rph-reg-policy-01 11 Abstract 13 RFC4412 defines "Resource-Priority Namespaces" and "Resource-Priority 14 Priority-values" registries. The management policy of these 15 registries is "Standards Action". This document normatively updates 16 RFC4412 ti change the management policy of these registries to "IETF 17 Review". 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at http://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on February 20, 2014. 36 Copyright Notice 38 Copyright (c) 2013 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 54 2. Security Considerations . . . . . . . . . . . . . . . . . . . 2 55 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2 56 4. Normative References . . . . . . . . . . . . . . . . . . . . 2 57 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 3 59 1. Introduction 61 [RFC4412] defines "Resource-Priority Namespaces" and "Resource- 62 Priority Priority-values" registries. The management policy of these 63 registries is "Standards Action" as defined in [RFC5226]. Experience 64 has suggested that a document that only defines a new namespace with 65 its priorities, and does not create new protocol semantics, should 66 not be a standards-track document. This document updates [RFC4412] 67 to change the management policy of the registries to "IETF Review". 69 2. Security Considerations 71 This document does not introduce any the security considerations 72 beyond those in [RFC4412]. 74 3. IANA Considerations 76 Change the management policy of management policy of the "Resource- 77 Priority Namespaces" and "Resource-Priority Priority-values" 78 registries to "IETF Review" as defined in [RFC5226]. 80 4. Normative References 82 [RFC4412] Schulzrinne, H. and J. Polk, "Communications Resource 83 Priority for the Session Initiation Protocol (SIP)", RFC 84 4412, February 2006. 86 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 87 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 88 May 2008. 90 Author's Address 92 Brian Rosen 93 NeuStar 94 470 Conrad Dr. 95 Mars, PA 16046 96 US 98 Phone: +1 724 382 1051 99 Email: br@brianrosen.net