idnits 2.17.00 (12 Aug 2021) /tmp/idnits30970/draft-rosen-rph-reg-policy-00.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 -- The document date (February 8, 2013) is 3388 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 (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 ecrit B. Rosen 3 Internet-Draft NeuStar 4 Intended status: Standards Track February 8, 2013 5 Expires: August 12, 2013 7 Resource Priority Header (RPH) Registry Management Policy to IETF Review 8 draft-rosen-rph-reg-policy-00 10 Abstract 12 RFC4412 defines "Resource-Priority Namespaces" and "Resource-Priority 13 Priority-values" registries. The management policy of these 14 registries is "Standards Action". This document changes the 15 management policy of these registries to "IETF Review". 17 Status of this Memo 19 This Internet-Draft is submitted in full conformance with the 20 provisions of BCP 78 and BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF). Note that other groups may also distribute 24 working documents as Internet-Drafts. The list of current Internet- 25 Drafts is at http://datatracker.ietf.org/drafts/current/. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 This Internet-Draft will expire on August 12, 2013. 34 Copyright Notice 36 Copyright (c) 2013 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents 41 (http://trustee.ietf.org/license-info) in effect on the date of 42 publication of this document. Please review these documents 43 carefully, as they describe your rights and restrictions with respect 44 to this document. Code Components extracted from this document must 45 include Simplified BSD License text as described in Section 4.e of 46 the Trust Legal Provisions and are provided without warranty as 47 described in the Simplified BSD License. 49 Table of Contents 51 1. Security Considerations . . . . . . . . . . . . . . . . . . . . 3 52 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 53 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 54 4. Normative References . . . . . . . . . . . . . . . . . . . . . 3 55 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 3 57 1. Security Considerations 59 This document does not introduce any the security considerations 60 beyond those in [RFC4412] 62 2. Introduction 64 [RFC4412] defines "Resource-Priority Namespaces" and "Resource- 65 Priority Priority-values" registries. The management policy of these 66 registries is "Standards Action" as defined in [RFC5226]. Experience 67 has suggested that a document that only defines a new namespace with 68 its priorities, and does not create new protocol semantics, should 69 not be a standards-track document. This document updates [RFC4412] 70 to change the management policy of the registries to "IETF Review". 72 3. IANA Considerations 74 Change the management policy of management policy of the "Resource- 75 Priority Namespaces" and "Resource-Priority Priority-values" 76 registries to "IETF Review" as defined in [RFC5226]. 78 4. Normative References 80 [RFC4412] Schulzrinne, H. and J. Polk, "Communications Resource 81 Priority for the Session Initiation Protocol (SIP)", 82 RFC 4412, February 2006. 84 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 85 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 86 May 2008. 88 Author's Address 90 Brian Rosen 91 NeuStar 92 470 Conrad Dr. 93 Mars, PA 16046 94 US 96 Phone: +1 724 382 1051 97 Email: br@brianrosen.net