sipcoreInternet Engineering Task Force (IETF) B. RosenInternet-DraftRequest for Comments: 7134 NeuStar Updates: 4412(if approved) August 19,February 2013Intended status:Category: Standards TrackExpires: February 20, 2014ISSN: 2070-1721 The Management Policy of the Resource Priority Header (RPH) RegistryManagement PolicyChanged toIETF Review draft-rosen-rph-reg-policy-01"IETF Review" AbstractRFC4412RFC 4412 defines the "Resource-Priority Namespaces" and"Resource-Priority"Resource- Priority Priority-values" registries. The management policy of these registries is "Standards Action". This document normatively updatesRFC4412 tiRFC 4412 to change the management policy of these registries to "IETF Review". Status of This Memo ThisInternet-Draftissubmitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documentsan Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF).Note that other groups may also distribute working documents as Internet-Drafts. The listIt represents the consensus ofcurrent Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents validthe IETF community. It has received public review and has been approved fora maximumpublication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741. Information about the current status ofsix monthsthis document, any errata, and how to provide feedback on it may beupdated, replaced, or obsoleted by other documentsobtained atany time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on February 20, 2014.http://www.rfc-editor.org/info/rfc7134. Copyright Notice Copyright (c) 2013 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. Security Considerations . . . . . . . . . . . . . . . . . . . 2 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2 4. Normative References . . . . . . . . . . . . . . . . . . . . 2Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 31. Introduction [RFC4412] defines the "Resource-Priority Namespaces" and "Resource- Priority Priority-values" registries. The management policy of these registries is "Standards Action"as defined in[RFC5226]. Experiencehas suggestedsuggests that a document that only defines a new namespace with its priorities, and does not create new protocol semantics, should not be astandards-trackStandards- Track document.ThisTherefore, this document updates [RFC4412] to change the management policy of the registries to "IETF Review". 2. Security Considerations This document does not introduce anythesecurity considerations beyond those discussed in [RFC4412]. 3. IANA ConsiderationsChangeIANA has changed the management policy ofmanagement policy ofthe"Resource- Priority"Resource-Priority Namespaces" and "Resource-Priority Priority-values" registries to "IETF Review"as defined in[RFC5226]. 4. Normative References [RFC4412] Schulzrinne, H. and J. Polk, "Communications Resource Priority for the Session Initiation Protocol (SIP)", RFC 4412, February 2006. [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008. Author's Address Brian Rosen NeuStar 470 Conrad Dr. Mars, PA 16046 US Phone: +1 724 382 1051Email:EMail: br@brianrosen.net