The Management Policy of the Resource Priority Header (RPH) Registry Changed to "IETF Review"

Internet Engineering Task Force (IETF)                          B. Rosen
Request for Comments: 7134                                       NeuStar
Updates: <a href="./rfc4412">4412</a>                                                 March 2014
Category: Standards Track
ISSN: 2070-1721


  <span class="h1">The Management Policy of the Resource Priority Header (RPH) Registry</span>
                        <span class="h1">Changed to "IETF Review"</span>

Abstract

   <a href="./rfc4412">RFC 4412</a> defines the "Resource-Priority Namespaces" and "Resource-
   Priority Priority-values" registries.  The management policy of these
   registries is "Standards Action".  This document normatively updates
   <a href="./rfc4412">RFC 4412</a> to change the management policy of these registries to "IETF
   Review".

Status of This Memo

   This is an Internet Standards Track document.

   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
   Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   <a href="https://www.rfc-editor.org/info/rfc7134">http://www.rfc-editor.org/info/rfc7134</a>.

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) 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.





<span class="grey">Rosen                        Standards Track                    [Page 1]</span>

<span id="page-2" ></span>
<span class="grey"><a href="./rfc7134">RFC 7134</a>                 RPH Registry Management              March 2014</span>


<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>.  Introduction</span>

   [<a id="ref-RFC4412">RFC4412</a>] defines the "Resource-Priority Namespaces" and "Resource-
   Priority Priority-values" registries.  The management policy of these
   registries is "Standards Action" [<a href="./rfc5226" title="">RFC5226</a>].  Experience suggests that
   a document that only defines a new namespace with its priorities, and
   does not create new protocol semantics, should not be a Standards-
   Track document.  Therefore, this document updates [<a href="./rfc4412" title=""Communications Resource Priority for the Session Initiation Protocol (SIP)"">RFC4412</a>] to change
   the management policy of the registries to "IETF Review".

<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>.  Security Considerations</span>

   This document does not introduce any security considerations beyond
   those discussed in [<a href="./rfc4412" title=""Communications Resource Priority for the Session Initiation Protocol (SIP)"">RFC4412</a>].

<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>.  IANA Considerations</span>

   IANA has changed the management policy of the "Resource-Priority
   Namespaces" and "Resource-Priority Priority-values" registries to
   "IETF Review" [<a href="./rfc5226" title="">RFC5226</a>].

<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>.  Normative References</span>

   [<a id="ref-RFC4412">RFC4412</a>]  Schulzrinne, H. and J. Polk, "Communications Resource
              Priority for the Session Initiation Protocol (SIP)", <a href="./rfc4412">RFC</a>
              <a href="./rfc4412">4412</a>, February 2006.

   [<a id="ref-RFC5226">RFC5226</a>]  Narten, T. and H. Alvestrand, "Guidelines for Writing an
              IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC 5226</a>,
              May 2008.

Author's Address

   Brian Rosen
   NeuStar
   470 Conrad Dr.
   Mars, PA  16046
   US

   Phone: +1 724 382 1051
   EMail: [email protected]










Rosen                        Standards Track                    [Page 2]