The Management Policy of the Resource Priority Header (RPH) Registry Changed to "IETF Review"
A change to the review policy for Resource-Priority registry entries
Rosen, B., "The Management Policy of the Resource Priority Header (RPH) Registry Changed to "IETF Review"", RFC 7134, DOI 10.17487/RFC7134, March 2014, <https://www.rfc-editor.org/info/rfc7134>.
@misc{rfc7134,
series = {Request for Comments},
number = 7134,
howpublished = {RFC 7134},
publisher = {RFC Editor},
doi = {10.17487/RFC7134},
url = {https://www.rfc-editor.org/info/rfc7134},
author = {B. Rosen},
title = {{The Management Policy of the Resource Priority Header (RPH) Registry Changed to "IETF Review"}},
pagetotal = 2,
year = 2014,
month = mar,
} RFC text
Contents
Internet Engineering Task Force (IETF) B. Rosen
Request for Comments: 7134 NeuStar
Updates: 4412 March 2014
Category: Standards Track
ISSN: 2070-1721
The Management Policy of the Resource Priority Header (RPH) Registry
Changed to "IETF Review"
Abstract
RFC 4412 defines the "Resource-Priority Namespaces" and "Resource-
Priority Priority-values" registries. The management policy of these
registries is "Standards Action". This document normatively updates
RFC 4412 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 Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7134.
Copyright Notice
Copyright (c) 2014 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.
1. Introduction
[RFC4412] defines the "Resource-Priority Namespaces" and "Resource-
Priority Priority-values" registries. The management policy of these
registries is "Standards Action" [RFC5226]. 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 [RFC4412] to change
the management policy of the registries to "IETF Review".
2. Security Considerations
This document does not introduce any security considerations beyond
those discussed in [RFC4412].
3. IANA Considerations
IANA has changed the management policy of the "Resource-Priority
Namespaces" and "Resource-Priority Priority-values" registries to
"IETF Review" [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 1051
EMail: br@brianrosen.net
ISO Plain Language
On this page
§1Why Change the Policy
RFC 4412 defines the Resource-Priority Namespaces and Resource-Priority Priority-values registries. Their management policy was Standards Action.
The RFC says a document that only defines a new namespace and its priorities, without creating new protocol semantics, should not need to be a Standards Track document. It therefore changes the registries' policy to IETF Review.
A proposal that only adds a namespace and priorities may not need a full Standards Track document. This RFC changes the review rule for those registry entries.
§2The Updated Registry Rule
The new management policy is IETF Review for both the Resource-Priority Namespaces registry and the Resource-Priority Priority-values registry. The RFC states that IANA has changed the policy for both registries.
This document normatively updates RFC 4412.
Both named registries now use IETF Review for new entries, replacing the earlier Standards Action policy.
§3Security Considerations
The RFC says it does not introduce security considerations beyond those discussed in RFC 4412.
The document changes registry management and adds no security considerations beyond RFC 4412.