draft-ietf-sipcore-priority-00.txt   rfc6878.txt 
SIPCORE A. B. Roach Internet Engineering Task Force (IETF) A.B. Roach
Internet-Draft Mozilla Request for Comments: 6878 Mozilla
Updates: 3261 (if approved) December 14, 2012 Updates: 3261 March 2013
Intended status: Standards Track Category: Standards Track
Expires: June 17, 2013 ISSN: 2070-1721
IANA Registry for the Session Initiation Protocol (SIP) "Priority" IANA Registry for the Session Initiation Protocol (SIP)
Header Field "Priority" Header Field
draft-ietf-sipcore-priority-00
Abstract Abstract
This document defines a new IANA registry to keep track of the values This document defines a new IANA registry to keep track of the values
defined for the Session Initiation Protocol (SIP) "Priority" header defined for the Session Initiation Protocol (SIP) "Priority" header
field. It updates RFC 3261. field. It updates RFC 3261.
Status of this Memo 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 This is an Internet Standards Track document.
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 This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
This Internet-Draft will expire on June 17, 2013. 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/rfc6878.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
1. Introduction 1. Introduction
This document defines a new IANA registry to keep track of the values This document defines a new IANA registry to keep track of the values
defined for the Session Initiation Protocol (SIP) "Priority" header defined for the Session Initiation Protocol (SIP) "Priority" header
field. This header field was defined in [RFC3261], section 20.26. field. This header field was defined in [RFC3261], Section 20.26.
It was clearly specified in a way that allows for the creation of new It was clearly specified in a way that allows for the creation of new
values beyond those originally specified; however, no registry has values beyond those originally specified; however, no registry has
been established for it. been established for it.
2. IANA Considerations 2. IANA Considerations
This document adds a new registry, "Priority Header Field Values." This document adds a new sub-registry, "Priority Header Field
Its format and initial values are as shown in the following table: Values", to the "Session Initiation Protocol (SIP) Parameters"
registry page. Its format and initial values are as shown in the
following table:
+------------+-----------+ +------------+-----------+
| Priority | Reference | | Priority | Reference |
+------------+-----------+ +------------+-----------+
| non-urgent | RFC 3261 | | non-urgent | RFC 3261 |
| normal | RFC 3261 | | normal | RFC 3261 |
| urgent | RFC 3261 | | urgent | RFC 3261 |
| emergency | RFC 3261 | | emergency | RFC 3261 |
+------------+-----------+ +------------+-----------+
The policy for registration of values in this registry is "IETF The policy for registration of values in this registry is "IETF
Review," as that term is defined by [RFC5226]. Review" as that term is defined by [RFC5226]. This policy was chosen
over lighter-weight policies due the potential architectural impact
of the semantics associated with new values. Efforts contemplating
adding a Priority value should consider whether the SIP Resource-
Priority [RFC4412] or even a different protocol would be more
appropriate for achieving their requirements.
3. Security Considerations 3. Security Considerations
This document does not have any impact on the security of the SIP This document does not have any impact on the security of the SIP
protocol. Its purpose is purely administrative in nature. protocol. Its purpose is purely administrative in nature.
4. Normative References 4. References
4.1. Normative References
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
A., Peterson, J., Sparks, R., Handley, M., and E. A., Peterson, J., Sparks, R., Handley, M., and E.
Schooler, "SIP: Session Initiation Protocol", RFC 3261, Schooler, "SIP: Session Initiation Protocol", RFC 3261,
June 2002. June 2002.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008. May 2008.
Appendix A. Acknowledgements 4.2. Informative References
TBD [RFC4412] Schulzrinne, H. and J. Polk, "Communications Resource
Priority for the Session Initiation Protocol (SIP)",
RFC 4412, February 2006.
Author's Address Author's Address
Adam Roach Adam Roach
Mozilla Mozilla
Dallas, TX Dallas, TX
US US
Email: adam@nostrum.com EMail: adam@nostrum.com
 End of changes. 14 change blocks. 
29 lines changed or deleted 36 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/