RFC 6878

IANA Registry for the Session Initiation Protocol (SIP) "Priority" Header Field 🎀

Okay bestie, this RFC is written by Adam Roach from Mozilla 💖 It's a Standards Track document, dated March 2013, and it updates RFC 3261 🦋 It's published as RFC 6878, and the ISSN is 2070-1721 ✨

---

Abstract ✨

Okay so this one is literally about making a brand new IANA registry 🗂️ to keep track of the values for the SIP "Priority" header field 💅 It also updates RFC 3261 🫶

Status of This Memo 🌸

This is an Internet Standards Track document 💜

It's a product of the Internet Engineering Task Force (IETF) 🌈 It represents the consensus of the IETF community, received public review, and got approved for publication by the Internet Engineering Steering Group (IESG) 👑 For more on Internet Standards, check Section 2 of RFC 5741 🦋

Want the current status, any errata, or to send feedback? Go to http://www.rfc-editor.org/info/rfc6878 🍓

Copyright Notice 🎀

Copyright (c) 2013 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. Please review those carefully, because they spell out your rights and restrictions for this document 🫶 Code Components pulled out of this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions, and they come without warranty as described in the Simplified BSD License 🌈

1. Introduction ✨

Okay so the big idea here is a brand new IANA registry 🗂️ that tracks the values for the SIP "Priority" header field 💅 That header field was defined in [RFC3261], Section 20.26 🦋 It was specified in a way that lets people create new values beyond the original ones, but nobody ever set up a registry for it 🙈

2. IANA Considerations 🌸

This document adds a new sub-registry called "Priority Header Field Values" to the "Session Initiation Protocol (SIP) Parameters" registry page 🎀 Its format and initial values look like this:

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

The policy for registering values in this registry is "IETF Review," as defined by [RFC5226] 💜 This policy was picked over lighter-weight options because new values could have a real architectural impact through their semantics 👑 So if you're thinking about adding a Priority value, first consider whether SIP Resource-Priority [RFC4412] or even a totally different protocol would better meet your requirements 🫶

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. References 🦋

4.1. 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.

4.2. Informative References 🌸

[RFC4412] : Schulzrinne, H. and J. Polk, "Communications Resource Priority for the Session Initiation Protocol (SIP)", RFC 4412, February 2006.

Author's Address 🎀

Adam Roach Mozilla Dallas, TX US

EMail: adam@nostrum.com 💜