Internet DRAFT - draft-rosen-rph-reg-policy
draft-rosen-rph-reg-policy
sipcore B. Rosen
Internet-Draft NeuStar
Updates: 4412 (if approved) August 19, 2013
Intended status: Standards Track
Expires: February 20, 2014
Resource Priority Header (RPH) Registry Management Policy to IETF Review
draft-rosen-rph-reg-policy-01
Abstract
RFC4412 defines "Resource-Priority Namespaces" and "Resource-Priority
Priority-values" registries. The management policy of these
registries is "Standards Action". This document normatively updates
RFC4412 ti change the management policy of these registries to "IETF
Review".
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
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.
Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved.
Rosen Expires February 20, 2014 [Page 1]
Internet-Draft RPH Registry Management August 2013
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 . . . . . . . . . . . . . . . . . . . . 2
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 3
1. Introduction
[RFC4412] defines "Resource-Priority Namespaces" and "Resource-
Priority Priority-values" registries. The management policy of these
registries is "Standards Action" as defined in [RFC5226]. Experience
has suggested 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. This document updates [RFC4412]
to change the management policy of the registries to "IETF Review".
2. Security Considerations
This document does not introduce any the security considerations
beyond those in [RFC4412].
3. IANA Considerations
Change the management policy of management policy of the "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.
Rosen Expires February 20, 2014 [Page 2]
Internet-Draft RPH Registry Management August 2013
Author's Address
Brian Rosen
NeuStar
470 Conrad Dr.
Mars, PA 16046
US
Phone: +1 724 382 1051
Email: br@brianrosen.net
Rosen Expires February 20, 2014 [Page 3]
