ietf-corpus

rfc-6878

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

A.B. Roach
date2013-03 streamIETF areaart wgsipcore statusPROPOSED STANDARD pages3 canonicalhttps://www.rfc-editor.org/rfc/rfc6878 doi10.17487/RFC6878 errataview
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.

updates

Extracted elements (5)

design-rationale §2

The IETF Review policy was selected over lighter-weight registration policies because new Priority values carry potential architectural implications. Documents contemplating new Priority values should consider whether SIP Resource-Priority (RFC 4412) or a different protocol would better meet their requirements.

sip, registry

interoperability-note §1

This document updates RFC 3261 by establishing a formal registry for the Priority header field values originally defined in RFC 3261 Section 20.26, which lacked a registry despite being specified in a way that allows for new values.

sip, registry

normative-requirement §2 REQUIRED

Registration of new values in the 'Priority Header Field Values' registry requires 'IETF Review' as defined by RFC 5226. This policy was chosen over lighter-weight policies due to the potential architectural impact of semantics associated with new Priority values.

sip, registry

registry §2

A new IANA sub-registry titled 'Priority Header Field Values' is added to the 'Session Initiation Protocol (SIP) Parameters' registry. Initial values are: non-urgent, normal, urgent, and emergency, all referencing RFC 3261.

sip, registry

security-consideration §3

This document has no impact on the security of the SIP protocol; its purpose is purely administrative in establishing an IANA registry for Priority header field values.

sip, security