Skip to main content

IANA Registry for the Session Initiation Protocol (SIP) "Priority" Header Field
draft-ietf-sipcore-priority-00

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 6878.
Author Adam Roach
Last updated 2015-10-14 (Latest revision 2012-12-14)
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Proposed Standard
Formats
Reviews
Additional resources Mailing list discussion
Stream WG state WG Document
Document shepherd (None)
IESG IESG state Became RFC 6878 (Proposed Standard)
Action Holders
(None)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Robert Sparks
IESG note
Send notices to (None)
draft-ietf-sipcore-priority-00
SIPCORE                                                      A. B. Roach
Internet-Draft                                                   Mozilla
Updates: 3261 (if approved)                            December 14, 2012
Intended status: Standards Track
Expires: June 17, 2013

   IANA Registry for the Session Initiation Protocol (SIP) "Priority"
                              Header Field
                     draft-ietf-sipcore-priority-00

Abstract

   This document defines a new IANA registry to keep track of the values
   defined for the Session Initiation Protocol (SIP) "Priority" header
   field.  It updates RFC 3261.

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 June 17, 2013.

Copyright Notice

   Copyright (c) 2012 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.

Roach                     Expires June 17, 2013                 [Page 1]
Internet-Draft     SIP Priority Header Field Registry      December 2012

1.  Introduction

   This document defines a new IANA registry to keep track of the values
   defined for the Session Initiation Protocol (SIP) "Priority" header
   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
   values beyond those originally specified; however, no registry has
   been established for it.

2.  IANA Considerations

   This document adds a new registry, "Priority Header Field Values."
   Its format and initial values are as shown in the following table:

                        +------------+-----------+
                        | Priority   | Reference |
                        +------------+-----------+
                        | non-urgent | RFC 3261  |
                        | normal     | RFC 3261  |
                        | urgent     | RFC 3261  |
                        | emergency  | RFC 3261  |
                        +------------+-----------+

   The policy for registration of values in this registry is "IETF
   Review," as that term is defined by [RFC5226].

3.  Security Considerations

   This document does not have any impact on the security of the SIP
   protocol.  Its purpose is purely administrative in nature.

4.  Normative References

   [RFC3261]  Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
              A., Peterson, J., Sparks, R., Handley, M., and E.
              Schooler, "SIP: Session Initiation Protocol", RFC 3261,
              June 2002.

   [RFC5226]  Narten, T. and H. Alvestrand, "Guidelines for Writing an
              IANA Considerations Section in RFCs", BCP 26, RFC 5226,
              May 2008.

Roach                     Expires June 17, 2013                 [Page 2]
Internet-Draft     SIP Priority Header Field Registry      December 2012

Appendix A.  Acknowledgements

   TBD

Author's Address

   Adam Roach
   Mozilla
   Dallas, TX
   US

   Email: adam@nostrum.com

Roach                     Expires June 17, 2013                 [Page 3]