Debian Codegraph @

rfc6135.html

raw
1 <pre>Internet Engineering Task Force (IETF) C. Holmberg
2 Request for Comments: 6135 Ericsson
3 Category: Standards Track S. Blau
4 ISSN: 2070-1721 Ericsson AB
5 February 2011
6
7
8 <span class="h1">An Alternative Connection Model for the</span>
9 <span class="h1">Message Session Relay Protocol (MSRP)</span>
10
11 Abstract
12
13 This document defines an alternative connection model for Message
14 Session Relay Protocol (MSRP) User Agents (UAs); this model uses the
15 connection-oriented media (COMEDIA) mechanism in order to create the
16 MSRP transport connection. The model allows MSRP UAs behind Network
17 Address Translators (NATs) to negotiate which endpoint initiates the
18 establishment of the Transmission Control Protocol (TCP) connection,
19 in order for MSRP messages to traverse the NAT.
20
21 Status of This Memo
22
23 This is an Internet Standards Track document.
24
25 This document is a product of the Internet Engineering Task Force
26 (IETF). It represents the consensus of the IETF community. It has
27 received public review and has been approved for publication by the
28 Internet Engineering Steering Group (IESG). Further information on
29 Internet Standards is available in <a href="./rfc5741#section-2">Section&nbsp;2 of RFC 5741</a>.
30
31 Information about the current status of this document, any errata,
32 and how to provide feedback on it may be obtained at
33 <a href="http://www.rfc-editor.org/info/rfc6135">http://www.rfc-editor.org/info/rfc6135</a>.
34
35 Copyright Notice
36
37 Copyright (c) 2011 IETF Trust and the persons identified as the
38 document authors. All rights reserved.
39
40 This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
41 Provisions Relating to IETF Documents
42 (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
43 publication of this document. Please review these documents
44 carefully, as they describe your rights and restrictions with respect
45 to this document. Code Components extracted from this document must
46 include Simplified BSD License text as described in Section 4.e of
47 the Trust Legal Provisions and are provided without warranty as
48 described in the Simplified BSD License.
49
50
51
52 <span class="grey">Holmberg &amp; Blau Standards Track [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc6135">RFC 6135</a> MSRP February 2011</span>
55
56
57 Table of Contents
58
59 <a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
60 <a href="#section-2">2</a>. Terminology .....................................................<a href="#page-3">3</a>
61 <a href="#section-3">3</a>. Applicability Statement .........................................<a href="#page-3">3</a>
62 <a href="#section-4">4</a>. COMEDIA for MSRP ................................................<a href="#page-3">3</a>
63 <a href="#section-4.1">4.1</a>. General ....................................................<a href="#page-3">3</a>
64 <a href="#section-4.2">4.2</a>. a=setup ....................................................<a href="#page-3">3</a>
65 <a href="#section-4.2.1">4.2.1</a>. General .............................................<a href="#page-3">3</a>
66 <a href="#section-4.2.2">4.2.2</a>. Attribute Usage .....................................<a href="#page-4">4</a>
67 <a href="#section-4.3">4.3</a>. TLS ........................................................<a href="#page-5">5</a>
68 <a href="#section-4.4">4.4</a>. a=connection ...............................................<a href="#page-5">5</a>
69 <a href="#section-4.5">4.5</a>. MSRP Relay Connection ......................................<a href="#page-6">6</a>
70 <a href="#section-5">5</a>. Interoperability with the Connection Model Defined in <a href="./rfc4975">RFC 4975</a> ..6
71 <a href="#section-6">6</a>. Security Considerations .........................................<a href="#page-6">6</a>
72 <a href="#section-7">7</a>. Acknowledgements ................................................<a href="#page-7">7</a>
73 <a href="#section-8">8</a>. References ......................................................<a href="#page-7">7</a>
74 <a href="#section-8.1">8.1</a>. Normative References .......................................<a href="#page-7">7</a>
75 <a href="#section-8.2">8.2</a>. Informative References .....................................<a href="#page-7">7</a>
76
77 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
78
79 The Message Session Relay Protocol (MSRP) core specification
80 [<a href="./rfc4975" title="&quot;The Message Session Relay Protocol (MSRP)&quot;">RFC4975</a>] states that the MSRP User Agent (UA) that sends the Session
81 Description Protocol (SDP) offer is "active", and it is responsible
82 for creating the MSRP transport connection towards the remote UA if a
83 new connection is required. The core specification also allows, but
84 does not define, alternate mechanisms for MSRP UAs to create MSRP
85 transport connections.
86
87 [<a id="ref-RFC4145">RFC4145</a>] defines a connection-oriented media (COMEDIA) mechanism,
88 which endpoints can use to negotiate the endpoint that initiates the
89 creation of media transport connection.
90
91 COMEDIA is especially useful when one of the endpoints is located
92 behind a Network Address Translator (NAT). The endpoint can use the
93 mechanism to indicate that it will create the media transport
94 connection, in order for the media to traverse the NAT without the
95 usage of relays and without being required to support more complex
96 mechanisms (e.g., "TCP Candidates with Interactive Connectivity
97 Establishment (ICE)" [<a href="#ref-ICE-TCP" title="&quot;TCP Candidates with Interactive Connectivity Establishment (ICE)&quot;">ICE-TCP</a>]). In addition, COMEDIA allows the
98 usage of identical procedures in establishing Transmission Control
99 Protocol (TCP) [<a href="./rfc0793" title="&quot;Transmission Control Protocol&quot;">RFC0793</a>] connections for different types of media.
100
101 An example is the Open Mobile Alliance (OMA)-defined "Instant Message
102 using SIMPLE" [<a href="#ref-OMA-SIMPLE" title="&quot;Instant Messaging using SIMPLE&quot;">OMA-SIMPLE</a>], where one MSRP UA of every MSRP transport
103 connection represents a media server, which is always located in the
104 carrier network. The media server has a globally reachable IP
105
106
107
108 <span class="grey">Holmberg &amp; Blau Standards Track [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc6135">RFC 6135</a> MSRP February 2011</span>
111
112
113 address and handles application-specific policy control as well as
114 NAT traversal. The OMA IM (Instant Messenger) uses COMEDIA for NAT
115 traversal, and all OMA IM MSRP clients support COMEDIA.
116
117 This document defines how an MSRP UA uses COMEDIA in order to
118 negotiate which UA will create the MSRP transport TCP connection
119 towards the other UA. The document also defines how an MSRP UA that
120 uses COMEDIA can establish an MSRP transport connection with a remote
121 UA that does not support COMEDIA.
122
123 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span>
124
125 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
126 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
127 document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a> [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>].
128
129 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Applicability Statement</span>
130
131 Support of this specification is OPTIONAL for MSRP UAs in general.
132 UAs that are likely to be deployed in networks with NATs SHOULD
133 support this specification. It will improve the odds of being able
134 to make TCP connections successfully traverse NATs, since UAs behind
135 NATs can be requested to initiate the establishment of the TCP
136 connections.
137
138 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. COMEDIA for MSRP</span>
139
140 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. General</span>
141
142 This section defines how an MSRP UA that supports this specification
143 uses the COMEDIA SDP attributes defined in [<a href="./rfc4145" title="&quot;TCP-Based Media Transport in the Session Description Protocol (SDP)&quot;">RFC4145</a>].
144
145 <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. a=setup</span>
146
147 <span class="h4"><a class="selflink" id="section-4.2.1" href="#section-4.2.1">4.2.1</a>. General</span>
148
149 An MSRP UA uses the SDP a=setup attribute [<a href="./rfc4145" title="&quot;TCP-Based Media Transport in the Session Description Protocol (SDP)&quot;">RFC4145</a>] in order to
150 negotiate which endpoint will create the MSRP transport connection
151 towards the other UA.
152
153 An MSRP UA MUST always include an explicit a=setup attribute in its
154 SDP offers and answers, since it might be useful for the other
155 endpoint, or for entities in the network, to know whether the UA
156 supports COMEDIA or not.
157
158
159
160
161
162
163
164 <span class="grey">Holmberg &amp; Blau Standards Track [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc6135">RFC 6135</a> MSRP February 2011</span>
167
168
169 An MSRP UA MUST support the a=setup "active", "actpass", and
170 "passive" attribute values. An MSRP UA MUST NOT send the "holdconn"
171 attribute value. If an MSRP UA receives the "holdconn" attribute
172 value, it MUST ignore it and process the message as if it did not
173 contain an a=setup attribute.
174
175 <span class="h4"><a class="selflink" id="section-4.2.2" href="#section-4.2.2">4.2.2</a>. Attribute Usage</span>
176
177 When the a=setup attribute value is "actpass" or "passive", the IP
178 address and port values in the MSRP URI of the SDP a=path attribute
179 MUST contain the actual address and port values on which the UA can
180 receive a TCP connection for the MSRP transport connection.
181
182 In accordance with [<a href="./rfc4145" title="&quot;TCP-Based Media Transport in the Session Description Protocol (SDP)&quot;">RFC4145</a>], if the a=setup attribute value is
183 "active", the port number value should be 9.
184
185 If an MSRP UA can provide a globally reachable IP address that the
186 other endpoint can use as a destination for a TCP connection, the UA
187 MUST use the a=setup "actpass" attribute value in SDP offers. This
188 is in order to allow the remote UA to send an SDP answer with an
189 a=setup "active" attribute value if the UA is located behind a NAT,
190 and in order to be compatible with UAs that do not support COMEDIA
191 and thus always will act as passive endpoints. If an MSRP UA cannot
192 provide the actual transport address, the UA MUST use the a=setup
193 "active" attribute value.
194
195 The UA MUST NOT use the a=setup "passive" attribute value in an SDP
196 offer.
197
198 The MSRP UA can determine that it provides a globally reachable IP
199 address in the following scenarios:
200
201 o the UA can determine that it is not located behind a NAT;
202
203 o the UA relays its MSRP transport connections via a relay (e.g., an
204 MSRP relay or Traversal Using Relay NAT (TURN) server); or
205
206 o the UA has used Session Traversal Utilities for NAT (STUN)
207 [<a href="./rfc5389" title="&quot;Session Traversal Utilities for NAT (STUN)&quot;">RFC5389</a>] signaling to retrieve the NAT address and port through
208 the local port to be used for the eventual transport connection,
209 while also having determined that the NAT has endpoint-independent
210 mapping and filtering behavior [<a href="./rfc5382" title="&quot;NAT Behavioral Requirements for TCP&quot;">RFC5382</a>], e.g., using the
211 mechanism defined in [<a href="./rfc5780" title="&quot;NAT Behavior Discovery Using Session Traversal Utilities for NAT (STUN)&quot;">RFC5780</a>].
212
213 Some UAs can determine whether the SIP [<a href="./rfc3261" title="&quot;SIP: Session Initiation Protocol&quot;">RFC3261</a>] signaling has
214 traversed a NAT by inspecting the SIP Via header field in the 200
215 (OK) response to the initial SIP REGISTER request, and comparing the
216 IP addresses in the Via sent-by and the received header field
217
218
219
220 <span class="grey">Holmberg &amp; Blau Standards Track [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc6135">RFC 6135</a> MSRP February 2011</span>
223
224
225 parameters. If the IP addresses are not the same, then the UA can
226 determine that there is a NAT in the path. Even though the media
227 transport might not traverse the NAT, it is safe to assume that it
228 will. This comparing mechanism does not work in all scenarios,
229 though. For example, if SIP a request crosses a SIP proxy before
230 crossing a NAT, the UA will not be able to detect the NAT by
231 comparing the IP addresses.
232
233 If an SDP offer includes an a=setup "actpass" attribute value, the
234 SDP answerer MAY include an a=setup "active" attribute value in the
235 SDP answer, but SHOULD include an a=setup "passive" attribute value
236 if it knows that it is not located behind a NAT.
237
238 Once the active UA has established the MSRP transport connection, the
239 UA must immediately send an MSRP SEND request, as defined in
240 [<a href="./rfc4975" title="&quot;The Message Session Relay Protocol (MSRP)&quot;">RFC4975</a>].
241
242 NOTE: According to [<a href="./rfc4975" title="&quot;The Message Session Relay Protocol (MSRP)&quot;">RFC4975</a>], the initiating UA is always active,
243 but when COMEDIA is used, the a=setup attribute is used to
244 negotiate which UA becomes active.
245
246 <span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. TLS</span>
247
248 If an MSRP UA conformant to this document uses Transport Layer
249 Security (TLS), it MUST use the TLS mechanisms defined in [<a href="./rfc4975" title="&quot;The Message Session Relay Protocol (MSRP)&quot;">RFC4975</a>]
250 and [<a href="./rfc4976" title="&quot;Relay Extensions for the Message Sessions Relay Protocol (MSRP)&quot;">RFC4976</a>].
251
252 According to [<a href="./rfc4975" title="&quot;The Message Session Relay Protocol (MSRP)&quot;">RFC4975</a>], the connection can be established with or
253 without TLS mutual authentication. In case mutual authentication is
254 not used, the listening device waits until it receives a request on
255 the connection, at which time it infers the identity of the
256 connecting device from the associated session description. From the
257 TLS authentication point of view, it is thus irrelevant whether an
258 endpoint takes the active or passive role.
259
260 If an MSRP UA uses a self-signed TLS certificate to authenticate
261 itself to MSRP peers, it also includes its certificate fingerprint in
262 the SDP.
263
264 Note that fingerprints can only be exchanged in peer-to-peer
265 communication, as MSRP relays [<a href="./rfc4976" title="&quot;Relay Extensions for the Message Sessions Relay Protocol (MSRP)&quot;">RFC4976</a>] will not receive the SDP
266 payloads containing the fingerprint attributes.
267
268 <span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a>. a=connection</span>
269
270 MSRP UAs MUST NOT use the SDP a=connection attribute. [<a href="./rfc4975" title="&quot;The Message Session Relay Protocol (MSRP)&quot;">RFC4975</a>]
271 defines connection reuse procedures for MSRP, and this document does
272 not modify those procedures.
273
274
275
276 <span class="grey">Holmberg &amp; Blau Standards Track [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc6135">RFC 6135</a> MSRP February 2011</span>
279
280
281 If an MSRP UA receives an a=connection attribute, the UA MUST
282 ignore it.
283
284 <span class="h3"><a class="selflink" id="section-4.5" href="#section-4.5">4.5</a>. MSRP Relay Connection</span>
285
286 If an MSRP UA is located behind an MSRP relay [<a href="./rfc4976" title="&quot;Relay Extensions for the Message Sessions Relay Protocol (MSRP)&quot;">RFC4976</a>], the UA MUST
287 always initiate a transport connection towards the relay, no matter
288 what value the client has provided in the a=setup attribute.
289
290 NOTE: Even if an MSRP UA initiates the TCP connection towards its
291 relay, the UA will only send a SEND request if the UA is active,
292 based on the COMEDIA negotiation.
293
294 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Interoperability with the Connection Model Defined in <a href="./rfc4975">RFC 4975</a></span>
295
296 An MSRP UA conformant to this document can interoperate with a UA
297 that follows the connection model defined in [<a href="./rfc4975" title="&quot;The Message Session Relay Protocol (MSRP)&quot;">RFC4975</a>]. However, if
298 an MSRP UA conformant to this document is located behind a NAT, does
299 not proxy its MSRP communication via an MSRP relay, and receives an
300 SDP offer from a remote UA that follows the connection model defined
301 in [<a href="./rfc4975" title="&quot;The Message Session Relay Protocol (MSRP)&quot;">RFC4975</a>], then NAT traversal can only be achieved if the MSRP UA
302 supports ICE [<a href="#ref-ICE-TCP" title="&quot;TCP Candidates with Interactive Connectivity Establishment (ICE)&quot;">ICE-TCP</a>] or if the network supports Session Border
303 Controller (SBC)-assisted NAT traversal for TCP.
304
305 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span>
306
307 According to the connection model defined in [<a href="./rfc4975" title="&quot;The Message Session Relay Protocol (MSRP)&quot;">RFC4975</a>], the MSRP UA
308 that sends the SDP offer becomes the active party, and it is
309 responsible for creating the MSRP transport connection towards the
310 remote UA if a new connection is required.
311
312 When COMEDIA is used, either the sender or the receiver of the SDP
313 offer can become the active party. [<a href="./rfc4975" title="&quot;The Message Session Relay Protocol (MSRP)&quot;">RFC4975</a>] requires that the
314 active party immediately issue an MSRP SEND request once the
315 connection has been established. This allows the passive party to
316 bind the inbound TCP connection to the message session identified by
317 the session id part of its MSRP URI. The use of COMEDIA does not
318 change this requirement, but the sender of the SDP offer is no longer
319 assumed to always become the active party.
320
321 The active party also takes the role of the TLS client, if TLS is
322 used to protect the MSRP messages. However, there are no procedures
323 in [<a href="./rfc4975" title="&quot;The Message Session Relay Protocol (MSRP)&quot;">RFC4975</a>] that would break in case the receiver of the SDP offer
324 takes the role of the TLS client, and the level of security provided
325 by TLS is not affected.
326
327
328
329
330
331
332 <span class="grey">Holmberg &amp; Blau Standards Track [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc6135">RFC 6135</a> MSRP February 2011</span>
335
336
337 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Acknowledgements</span>
338
339 Thanks to Ben Campbell, Remi Denis-Courmont, Nancy Greene, Hadriel
340 Kaplan, Adam Roach, Robert Sparks, Salvatore Loreto, and Shida
341 Schubert for their guidance and input in producing this document.
342
343 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span>
344
345 <span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Normative References</span>
346
347 [<a id="ref-RFC0793">RFC0793</a>] Postel, J., "Transmission Control Protocol", STD 7,
348 <a href="./rfc793">RFC 793</a>, September 1981.
349
350 [<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
351 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
352
353 [<a id="ref-RFC4145">RFC4145</a>] Yon, D. and G. Camarillo, "TCP-Based Media Transport in
354 the Session Description Protocol (SDP)", <a href="./rfc4145">RFC 4145</a>,
355 September 2005.
356
357 [<a id="ref-RFC4975">RFC4975</a>] Campbell, B., Ed., Mahy, R., Ed., and C. Jennings, Ed.,
358 "The Message Session Relay Protocol (MSRP)", <a href="./rfc4975">RFC 4975</a>,
359 September 2007.
360
361 [<a id="ref-RFC4976">RFC4976</a>] Jennings, C., Mahy, R., and A. Roach, "Relay Extensions
362 for the Message Sessions Relay Protocol (MSRP)",
363 <a href="./rfc4976">RFC 4976</a>, September 2007.
364
365 <span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Informative References</span>
366
367 [<a id="ref-RFC3261">RFC3261</a>] Rosenberg, J., Schulzrinne, H., Camarillo, G.,
368 Johnston, A., Peterson, J., Sparks, R., Handley, M.,
369 and E. Schooler, "SIP: Session Initiation Protocol",
370 <a href="./rfc3261">RFC 3261</a>, June 2002.
371
372 [<a id="ref-RFC5382">RFC5382</a>] Guha, S., Ed., Biswas, K., Ford, B., Sivakumar, S., and
373 P. Srisuresh, "NAT Behavioral Requirements for TCP",
374 <a href="https://www.rfc-editor.org/bcp/bcp142">BCP 142</a>, <a href="./rfc5382">RFC 5382</a>, October 2008.
375
376 [<a id="ref-RFC5389">RFC5389</a>] Rosenberg, J., Mahy, R., Matthews, P., and D. Wing,
377 "Session Traversal Utilities for NAT (STUN)", <a href="./rfc5389">RFC 5389</a>,
378 October 2008.
379
380 [<a id="ref-RFC5780">RFC5780</a>] MacDonald, D. and B. Lowekamp, "NAT Behavior Discovery
381 Using Session Traversal Utilities for NAT (STUN)",
382 <a href="./rfc5780">RFC 5780</a>, May 2010.
383
384
385
386
387
388 <span class="grey">Holmberg &amp; Blau Standards Track [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc6135">RFC 6135</a> MSRP February 2011</span>
391
392
393 [<a id="ref-ICE-TCP">ICE-TCP</a>] Rosenberg, J., Keranen, A., Lowekamp, B., and A. Roach,
394 "TCP Candidates with Interactive Connectivity
395 Establishment (ICE)", Work in Progress, February 2011.
396
397 [<a id="ref-OMA-SIMPLE">OMA-SIMPLE</a>] Open Mobile Alliance, "Instant Messaging using SIMPLE",
398 OMA-TS-SIMPLE_IM-V1_0-20090901-D, September 2009.
399
400 Authors' Addresses
401
402 Christer Holmberg
403 Ericsson
404 Hirsalantie 11
405 Jorvas 02420
406 Finland
407
408 EMail: [email protected]
409
410
411 Staffan Blau
412 Ericsson AB
413 PO Box 407
414 Sweden
415
416 EMail: [email protected]
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444 Holmberg &amp; Blau Standards Track [Page 8]
445 </pre>