idnits 2.17.1 draft-ietf-sipcore-priority-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC3261, updated by this document, for RFC5378 checks: 2000-07-17) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (December 14, 2012) is 4148 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 SIPCORE A. B. Roach 3 Internet-Draft Mozilla 4 Updates: 3261 (if approved) December 14, 2012 5 Intended status: Standards Track 6 Expires: June 17, 2013 8 IANA Registry for the Session Initiation Protocol (SIP) "Priority" 9 Header Field 10 draft-ietf-sipcore-priority-00 12 Abstract 14 This document defines a new IANA registry to keep track of the values 15 defined for the Session Initiation Protocol (SIP) "Priority" header 16 field. It updates RFC 3261. 18 Status of this Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at http://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on June 17, 2013. 35 Copyright Notice 37 Copyright (c) 2012 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (http://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 1. Introduction 52 This document defines a new IANA registry to keep track of the values 53 defined for the Session Initiation Protocol (SIP) "Priority" header 54 field. This header field was defined in [RFC3261], section 20.26. 55 It was clearly specified in a way that allows for the creation of new 56 values beyond those originally specified; however, no registry has 57 been established for it. 59 2. IANA Considerations 61 This document adds a new registry, "Priority Header Field Values." 62 Its format and initial values are as shown in the following table: 64 +------------+-----------+ 65 | Priority | Reference | 66 +------------+-----------+ 67 | non-urgent | RFC 3261 | 68 | normal | RFC 3261 | 69 | urgent | RFC 3261 | 70 | emergency | RFC 3261 | 71 +------------+-----------+ 73 The policy for registration of values in this registry is "IETF 74 Review," as that term is defined by [RFC5226]. 76 3. Security Considerations 78 This document does not have any impact on the security of the SIP 79 protocol. Its purpose is purely administrative in nature. 81 4. Normative References 83 [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, 84 A., Peterson, J., Sparks, R., Handley, M., and E. 85 Schooler, "SIP: Session Initiation Protocol", RFC 3261, 86 June 2002. 88 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 89 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 90 May 2008. 92 Appendix A. Acknowledgements 94 TBD 96 Author's Address 98 Adam Roach 99 Mozilla 100 Dallas, TX 101 US 103 Email: adam@nostrum.com