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
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
|
<pre>Network Working Group G. Camarillo
Request for Comments: 4569 Ericsson
Category: Informational July 2006
<span class="h1">Internet Assigned Numbers Authority (IANA) Registration</span>
<span class="h1">of the Message Media Feature Tag</span>
Status of This Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2006).
Abstract
This document registers with the IANA a new media feature tag
associated with the 'message' media type. This media feature tag
indicates that a particular device supports 'message' as a streaming
media type. Media feature tags can be used to route calls to devices
that support certain features.
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
<a href="#section-2">2</a>. Security Considerations .........................................<a href="#page-2">2</a>
<a href="#section-3">3</a>. IANA Considerations .............................................<a href="#page-2">2</a>
<a href="#section-4">4</a>. Acknowledgements ................................................<a href="#page-3">3</a>
<a href="#section-5">5</a>. Normative References ............................................<a href="#page-3">3</a>
<span class="grey">Camarillo Informational [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc4569">RFC 4569</a> Message Feature Tag July 2006</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
The Session Description Protocol (SDP) specification [<a href="#ref-5" title=""SDP: Session Description Protocol"">5</a>] defines a
number of media types. <a href="./rfc3840">RFC 3840</a> [<a href="#ref-4" title=""Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)"">4</a>] registers with the IANA media
feature tags associated with all those media types except for the
'message' media type. This document registers a new media feature
tag that is associated with the 'message' media type.
The reason why the 'message' media feature tag was not registered by
<a href="./rfc3840">RFC 3840</a> was that when <a href="./rfc3840">RFC 3840</a> was published, the SDP specification
was <a href="./rfc2327">RFC 2327</a> [<a href="#ref-1" title=""SDP: Session Description Protocol"">1</a>]. <a href="./rfc3840">RFC 3840</a> defined media feature tags for all the
media types defined by <a href="./rfc2327">RFC 2327</a>. However, <a href="./rfc2327">RFC 2327</a> did not define
the 'message' media type. This media type was defined by the revised
SDP specification [<a href="#ref-5" title=""SDP: Session Description Protocol"">5</a>], which was published after <a href="./rfc3840">RFC 3840</a>.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Security Considerations</span>
<a href="./rfc3840#section-11.1">Section 11.1 of RFC 3840</a> [<a href="#ref-4" title=""Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)"">4</a>] discusses security considerations
related to the use of media feature tags.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. IANA Considerations</span>
This specification registers a new media feature tag in the SIP [<a href="#ref-3" title=""SIP: Session Initiation Protocol"">3</a>]
tree per the procedures defined in <a href="./rfc2506">RFC 2506</a> [<a href="#ref-2" title=""Media Feature Tag Registration Procedure"">2</a>] and <a href="./rfc3840">RFC 3840</a> [<a href="#ref-4" title=""Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)"">4</a>].
Media feature tag name: sip.message
ASN.1 Identifier: 21
Summary of the media feature indicated by this tag: This feature
tag indicates that the device supports message as a streaming
media type.
Values appropriate for use with this feature tag: Boolean.
The feature tag is intended primarily for use in the following
applications, protocols, services, or negotiation mechanisms: This
feature tag is most useful in a communications application for
describing the capabilities of a device, such as a phone or PDA.
Examples of typical use: Routing a call to a phone that can
support session-based instant messaging.
Related standards or documents: <a href="./rfc4569">RFC 4569</a>.
Security Considerations: Security considerations for this media
feature tag are discussed in <a href="./rfc3840#section-11.1">Section 11.1 of RFC 3840</a>.
<span class="grey">Camarillo Informational [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc4569">RFC 4569</a> Message Feature Tag July 2006</span>
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Acknowledgements</span>
The need for this registration was discussed with Jonathan Rosenberg,
Colin Perkins, and Jon Peterson.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Normative References</span>
[<a id="ref-1">1</a>] Handley, M. and V. Jacobson, "SDP: Session Description
Protocol", <a href="./rfc2327">RFC 2327</a>, April 1998.
[<a id="ref-2">2</a>] Holtman, K., Mutz, A., and T. Hardie, "Media Feature Tag
Registration Procedure", <a href="https://www.rfc-editor.org/bcp/bcp31">BCP 31</a>, <a href="./rfc2506">RFC 2506</a>, March 1999.
[<a id="ref-3">3</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-4">4</a>] Rosenberg, J., Schulzrinne, H., and P. Kyzivat, "Indicating User
Agent Capabilities in the Session Initiation Protocol (SIP)",
<a href="./rfc3840">RFC 3840</a>, August 2004.
[<a id="ref-5">5</a>] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
Description Protocol", <a href="./rfc4566">RFC 4566</a>, July 2006.
Author's Address
Gonzalo Camarillo
Ericsson
Hirsalantie 11
Jorvas 02420
Finland
EMail: Gonzalo.Camarillo@ericsson.com
<span class="grey">Camarillo Informational [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc4569">RFC 4569</a> Message Feature Tag July 2006</span>
Full Copyright Statement
Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions
contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Acknowledgement
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
Camarillo Informational [Page 4]
</pre>
|
