1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
|
<pre>Internet Engineering Task Force (IETF) A.B. Roach
Request for Comments: 6878 Mozilla
Updates: <a href="./rfc3261">3261</a> March 2013
Category: Standards Track
ISSN: 2070-1721
<span class="h1">IANA Registry for the Session Initiation Protocol (SIP)</span>
<span class="h1">"Priority" Header Field</span>
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 <a href="./rfc3261">RFC 3261</a>.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="http://www.rfc-editor.org/info/rfc6878">http://www.rfc-editor.org/info/rfc6878</a>.
Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) 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.
<span class="grey">Roach Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc6878">RFC 6878</a> SIP Priority Header Field Registry March 2013</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
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 <a href="./rfc3261#section-20.26">[RFC3261], Section 20.26</a>.
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.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. IANA Considerations</span>
This document adds a new sub-registry, "Priority Header Field
Values", to the "Session Initiation Protocol (SIP) Parameters"
registry page. Its format and initial values are as shown in the
following table:
+------------+-----------+
| Priority | Reference |
+------------+-----------+
| non-urgent | <a href="./rfc3261">RFC 3261</a> |
| normal | <a href="./rfc3261">RFC 3261</a> |
| urgent | <a href="./rfc3261">RFC 3261</a> |
| emergency | <a href="./rfc3261">RFC 3261</a> |
+------------+-----------+
The policy for registration of values in this registry is "IETF
Review" as that term is defined by [<a href="./rfc5226" title="">RFC5226</a>]. 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 [<a href="./rfc4412" title=""Communications Resource Priority for the Session Initiation Protocol (SIP)"">RFC4412</a>] or even a different protocol would be more
appropriate for achieving their requirements.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Security Considerations</span>
This document does not have any impact on the security of the SIP
protocol. Its purpose is purely administrative in nature.
<span class="grey">Roach Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc6878">RFC 6878</a> SIP Priority Header Field Registry March 2013</span>
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. References</span>
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Normative References</span>
[<a id="ref-RFC3261">RFC3261</a>] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
A., Peterson, J., Sparks, R., Handley, M., and E.
Schooler, "SIP: Session Initiation Protocol", <a href="./rfc3261">RFC 3261</a>,
June 2002.
[<a id="ref-RFC5226">RFC5226</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC 5226</a>,
May 2008.
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Informative References</span>
[<a id="ref-RFC4412">RFC4412</a>] Schulzrinne, H. and J. Polk, "Communications Resource
Priority for the Session Initiation Protocol (SIP)",
<a href="./rfc4412">RFC 4412</a>, February 2006.
Author's Address
Adam Roach
Mozilla
Dallas, TX
US
EMail: adam@nostrum.com
Roach Standards Track [Page 3]
</pre>
|
