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
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
|
<pre>Network Working Group S. Loreto
Request for Comments: 5509 Ericsson
Category: Standards Track April 2009
<span class="h1">Internet Assigned Numbers Authority (IANA) Registration</span>
<span class="h1">of Instant Messaging and Presence DNS SRV RRs</span>
<span class="h1">for the Session Initiation Protocol (SIP)</span>
Status of this Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (c) 2009 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 in effect on the date of
publication of this document (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
Abstract
This document registers with IANA two new DNS SRV protocol labels for
resolving Instant Messaging and Presence services with SIP.
<span class="grey">Loreto Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc5509">RFC 5509</a> IANA SRV Label for SIP April 2009</span>
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-2">2</a>. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-3">3</a>. DNS SRV Usage of SIP with 'im' and 'pres' URIs . . . . . . . . <a href="#page-3">3</a>
<a href="#section-4">4</a>. Security Considerations . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-5">5</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-5.1">5.1</a>. Instant Messaging SRV Protocol Label Registration . . . . . <a href="#page-5">5</a>
<a href="#section-5.2">5.2</a>. Presence SRV Protocol Label Registration . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-6">6</a>. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-7">7</a>. Normative References . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<span class="grey">Loreto Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc5509">RFC 5509</a> IANA SRV Label for SIP April 2009</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
The Service Record (SRV) [<a href="./rfc2782" title=""A DNS RR for specifying the location of services (DNS SRV)"">RFC2782</a>] identifies the host(s) that will
support particular services. The DNS is queried for SRV RR in the
general form:
_Service._Proto.Name
Service: the symbolic name of the desired service
Proto: the protocol of the desired service
Name: the domain name for which this record is valid
"Address Resolution for Instant Messaging and Presence" [<a href="./rfc3861" title=""Address Resolution for Instant Messaging and Presence"">RFC3861</a>]
provides guidance for locating the services associated with URIs that
employ the following two URI schemes [<a href="./rfc3986" title=""Uniform Resource Identifier (URI): Generic Syntax"">RFC3986</a>]: 'im' for INSTANT
INBOXes [<a href="./rfc3860" title=""Common Profile for Instant Messaging (CPIM)"">RFC3860</a>] and 'pres' for PRESENTITIES [<a href="./rfc3859" title=""Common Profile for Presence (CPP)"">RFC3859</a>].
In order to ensure that the association between "_im" and "_pres" and
their respective underlying services are deterministic, the IANA has
created two independent registries: the Instant Messaging SRV
Protocol Label registry and the Presence SRV Protocol Label registry.
This document defines and registers the "_sip" protocol label in both
registries so that computer programs can resolve 'im:' and 'pres:'
URIs down to SIP addresses.
Moreover, this document explains how the use of SIP for Presence and
Instant Messaging uses SRV.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a> [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. DNS SRV Usage of SIP with 'im' and 'pres' URIs</span>
Although there are standard procedures for resolving 'im' and 'pres'
URIs (<a href="./rfc3861#section-3">Section 3 of [RFC3861]</a>), the labels for SIP are not registered.
<a href="./rfc3428#section-5">Section 5 of [RFC3428]</a> states that if a user agent (UA) is presented
with an IM URI (e.g., "im:fred@example.com") as the address for an
instant message, it SHOULD resolve it to a SIP URI, and place the
resulting URI in the Request-URI of the MESSAGE request before
<span class="grey">Loreto Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc5509">RFC 5509</a> IANA SRV Label for SIP April 2009</span>
sending.
Following the procedures defined in [<a href="./rfc3861" title=""Address Resolution for Instant Messaging and Presence"">RFC3861</a>], in order to resolve
the IM URI, the UA performs a SRV lookup for:
_im._sip.example.com
Assuming that the example.com domain offers a SIP service for instant
messaging at simple.example.com, this will result in a resolution of
_im._sip.example.com. to simple.example.com. Thus, the instant
messaging URI im:fred@example.com would resolve to a SIP URI of
sip:fred@simple.example.com.
SIP supports both pager [<a href="./rfc3428" title=""Session Initiation Protocol (SIP) Extension for Instant Messaging"">RFC3428</a>] and session [<a href="./rfc4975" title=""The Message Session Relay Protocol (MSRP)"">RFC4975</a>] IM mode.
However, a DNS SRV lookup does not specify which SIP IM mode a domain
offer. If the user agent client (UAC) supports both session mode and
pager mode, it is then suggested to try session mode first; if that
mode is rejected, the UAC has to be ready to fall back to pager mode.
<a href="./rfc3856#section-5">Section 5 of [RFC3856]</a> states that procedures defined in [<a href="./rfc3861" title=""Address Resolution for Instant Messaging and Presence"">RFC3861</a>]
are also used to resolve the protocol-independent PRES URI for a
presentity (e.g., "pres:fred@example.com") into a SIP URI.
Following the procedures defined in [<a href="./rfc3861" title=""Address Resolution for Instant Messaging and Presence"">RFC3861</a>], in order to resolve
the PRES URI, the UA performs a SRV lookup for:
_pres._sip.example.com
Assuming that the example.com domain offers a SIP presence service at
simple.example.com, this will result in a resolution of
_pres._sip.example.com. to simple.example.com. Thus, the protocol-
independent PRES URI pres:fred@example.com would resolve to a SIP URI
of sip:fred@simple.example.com.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
This document merely serves for the registration of DNS SRV labels in
the appropriate IANA registry. The document does not specify a
protocol; therefore, there are no security issues associated with it.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. IANA Considerations</span>
This specification registers a new SRV protocol label in both the
Instant Messaging SRV Protocol Label registry and the Presence SRV
Protocol Label registry.
<span class="grey">Loreto Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc5509">RFC 5509</a> IANA SRV Label for SIP April 2009</span>
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Instant Messaging SRV Protocol Label Registration</span>
"Address Resolution for Instant Messaging and Presence" [<a href="./rfc3861" title=""Address Resolution for Instant Messaging and Presence"">RFC3861</a>]
defines an Instant Messaging SRV Protocol Label registry for
protocols that can provide services that conform to the "_im" SRV
Service label. Because SIP is one such protocol, IANA registers the
"_sip" protocol label in the "Instant Messaging SRV Protocol Label
Registry", as follows:
Protocol label: _sip
Specification: <a href="./rfc5509">RFC 5509</a>
Description: Instant messaging protocol label for the use of SIP for
Presence and Instant Messaging protocol as defined by
[<a href="./rfc3428" title=""Session Initiation Protocol (SIP) Extension for Instant Messaging"">RFC3428</a>].
Registrant Contact: Salvatore Loreto <salvatore.loreto@ericsson.com>
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Presence SRV Protocol Label Registration</span>
"Address Resolution for Instant Messaging and Presence" [<a href="./rfc3861" title=""Address Resolution for Instant Messaging and Presence"">RFC3861</a>]
defines a Presence SRV Protocol Label registry for protocols that can
provide services that conform to the "_pres" SRV Service label.
Because the use of SIP for Presence and Instant Messaging is one such
protocol, the IANA registers the "_sip" protocol label in the
"Presence SRV Protocol Label Registry", as follows:
Protocol label: _sip
Specification: <a href="./rfc5509">RFC 5509</a>
Description: Presence protocol label for the use of SIP for Presence
and Instant Messaging protocol as defined by [<a href="./rfc3856" title=""A Presence Event Package for the Session Initiation Protocol (SIP)"">RFC3856</a>].
Registrant Contact: Salvatore Loreto <salvatore.loreto@ericsson.com>
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Acknowledgments</span>
The need for this registration was discussed with Jon Peterson and
Peter Saint-Andre.
Miguel Garcia reviewed this document on behalf of the Real-time
Applications and Infrastructure (RAI) Area Review Team (ART).
<span class="grey">Loreto Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc5509">RFC 5509</a> IANA SRV Label for SIP April 2009</span>
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Normative References</span>
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-RFC2782">RFC2782</a>] Gulbrandsen, A., Vixie, P., and L. Esibov, "A DNS RR for
specifying the location of services (DNS SRV)", <a href="./rfc2782">RFC 2782</a>,
February 2000.
[<a id="ref-RFC3428">RFC3428</a>] Campbell, B., Rosenberg, J., Schulzrinne, H., Huitema, C.,
and D. Gurle, "Session Initiation Protocol (SIP) Extension
for Instant Messaging", <a href="./rfc3428">RFC 3428</a>, December 2002.
[<a id="ref-RFC3856">RFC3856</a>] Rosenberg, J., "A Presence Event Package for the Session
Initiation Protocol (SIP)", <a href="./rfc3856">RFC 3856</a>, August 2004.
[<a id="ref-RFC3859">RFC3859</a>] Peterson, J., "Common Profile for Presence (CPP)",
<a href="./rfc3859">RFC 3859</a>, August 2004.
[<a id="ref-RFC3860">RFC3860</a>] Peterson, J., "Common Profile for Instant Messaging
(CPIM)", <a href="./rfc3860">RFC 3860</a>, August 2004.
[<a id="ref-RFC3861">RFC3861</a>] Peterson, J., "Address Resolution for Instant Messaging
and Presence", <a href="./rfc3861">RFC 3861</a>, August 2004.
[<a id="ref-RFC3986">RFC3986</a>] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66,
<a href="./rfc3986">RFC 3986</a>, January 2005.
[<a id="ref-RFC4975">RFC4975</a>] Campbell, B., Mahy, R., and C. Jennings, "The Message
Session Relay Protocol (MSRP)", <a href="./rfc4975">RFC 4975</a>, September 2007.
Author's Address
Salvatore Loreto
Ericsson
Hirsalantie 11
Jorvas 02420
Finland
Email: Salvatore.Loreto@ericsson.com
Loreto Standards Track [Page 6]
</pre>
|
