6135
PROPOSED STANDARD
An Alternative Connection Model for the Message Session Relay Protocol (MSRP)
Authors: C. Holmberg, S. Blau
Date: February 2011
Area: rai
Working Group: simple
Stream: IETF
Abstract
This document defines an alternative connection model for Message Session Relay Protocol (MSRP) User Agents (UAs); this model uses the connection-oriented media (COMEDIA) mechanism in order to create the MSRP transport connection. The model allows MSRP UAs behind Network Address Translators (NATs) to negotiate which endpoint initiates the establishment of the Transmission Control Protocol (TCP) connection, in order for MSRP messages to traverse the NAT. [STANDARDS-TRACK]
RFC 6135
PROPOSED STANDARD
Internet Engineering Task Force (IETF) C. Holmberg
Request for Comments: 6135 Ericsson
Category: Standards Track S. Blau
ISSN: 2070-1721 Ericsson AB
February 2011
<span class="h1">An Alternative Connection Model for the</span>
<span class="h1">Message Session Relay Protocol (MSRP)</span>
Abstract
This document defines an alternative connection model for Message
Session Relay Protocol (MSRP) User Agents (UAs); this model uses the
connection-oriented media (COMEDIA) mechanism in order to create the
MSRP transport connection. The model allows MSRP UAs behind Network
Address Translators (NATs) to negotiate which endpoint initiates the
establishment of the Transmission Control Protocol (TCP) connection,
in order for MSRP messages to traverse the NAT.
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="https://www.rfc-editor.org/info/rfc6135">http://www.rfc-editor.org/info/rfc6135</a>.
Copyright Notice
Copyright (c) 2011 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">Holmberg & Blau Standards Track [Page 1]</span><span id="page-2" ></span>
<span class="grey"><a href="./rfc6135">RFC 6135</a> MSRP February 2011</span>
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
<a href="#section-2">2</a>. Terminology .....................................................<a href="#page-3">3</a>
<a href="#section-3">3</a>. Applicability Statement .........................................<a href="#page-3">3</a>
<a href="#section-4">4</a>. COMEDIA for MSRP ................................................<a href="#page-3">3</a>
<a href="#section-4.1">4.1</a>. General ....................................................<a href="#page-3">3</a>
<a href="#section-4.2">4.2</a>. a=setup ....................................................<a href="#page-3">3</a>
<a href="#section-4.2.1">4.2.1</a>. General .............................................<a href="#page-3">3</a>
<a href="#section-4.2.2">4.2.2</a>. Attribute Usage .....................................<a href="#page-4">4</a>
<a href="#section-4.3">4.3</a>. TLS ........................................................<a href="#page-5">5</a>
<a href="#section-4.4">4.4</a>. a=connection ...............................................<a href="#page-5">5</a>
<a href="#section-4.5">4.5</a>. MSRP Relay Connection ......................................<a href="#page-6">6</a>
<a href="#section-5">5</a>. Interoperability with the Connection Model Defined in <a href="./rfc4975">RFC 4975</a> ..6
<a href="#section-6">6</a>. Security Considerations .........................................<a href="#page-6">6</a>
<a href="#section-7">7</a>. Acknowledgements ................................................<a href="#page-7">7</a>
<a href="#section-8">8</a>. References ......................................................<a href="#page-7">7</a>
<a href="#section-8.1">8.1</a>. Normative References .......................................<a href="#page-7">7</a>
<a href="#section-8.2">8.2</a>. Informative References .....................................<a href="#page-7">7</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
The Message Session Relay Protocol (MSRP) core specification
[<a href="./rfc4975" title=""The Message Session Relay Protocol (MSRP)"">RFC4975</a>] states that the MSRP User Agent (UA) that sends the Session
Description Protocol (SDP) offer is "active", and it is responsible
for creating the MSRP transport connection towards the remote UA if a
new connection is required. The core specification also allows, but
does not define, alternate mechanisms for MSRP UAs to create MSRP
transport connections.
[<a id="ref-RFC4145">RFC4145</a>] defines a connection-oriented media (COMEDIA) mechanism,
which endpoints can use to negotiate the endpoint that initiates the
creation of media transport connection.
COMEDIA is especially useful when one of the endpoints is located
behind a Network Address Translator (NAT). The endpoint can use the
mechanism to indicate that it will create the media transport
connection, in order for the media to traverse the NAT without the
usage of relays and without being required to support more complex
mechanisms (e.g., "TCP Candidates with Interactive Connectivity
Establishment (ICE)" [<a href="#ref-ICE-TCP" title=""TCP Candidates with Interactive Connectivity Establishment (ICE)"">ICE-TCP</a>]). In addition, COMEDIA allows the
usage of identical procedures in establishing Transmission Control
Protocol (TCP) [<a href="./rfc0793" title=""Transmission Control Protocol"">RFC0793</a>] connections for different types of media.
An example is the Open Mobile Alliance (OMA)-defined "Instant Message
using SIMPLE" [<a href="#ref-OMA-SIMPLE" title=""Instant Messaging using SIMPLE"">OMA-SIMPLE</a>], where one MSRP UA of every MSRP transport
connection represents a media server, which is always located in the
carrier network. The media server has a globally reachable IP
<span class="grey">Holmberg & Blau Standards Track [Page 2]</span><span id="page-3" ></span>
<span class="grey"><a href="./rfc6135">RFC 6135</a> MSRP February 2011</span>
address and handles application-specific policy control as well as
NAT traversal. The OMA IM (Instant Messenger) uses COMEDIA for NAT
traversal, and all OMA IM MSRP clients support COMEDIA.
This document defines how an MSRP UA uses COMEDIA in order to
negotiate which UA will create the MSRP transport TCP connection
towards the other UA. The document also defines how an MSRP UA that
uses COMEDIA can establish an MSRP transport connection with a remote
UA that does not support COMEDIA.
<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>. Applicability Statement</span>
Support of this specification is OPTIONAL for MSRP UAs in general.
UAs that are likely to be deployed in networks with NATs SHOULD
support this specification. It will improve the odds of being able
to make TCP connections successfully traverse NATs, since UAs behind
NATs can be requested to initiate the establishment of the TCP
connections.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. COMEDIA for MSRP</span>
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. General</span>
This section defines how an MSRP UA that supports this specification
uses the COMEDIA SDP attributes defined in [<a href="./rfc4145" title=""TCP-Based Media Transport in the Session Description Protocol (SDP)"">RFC4145</a>].
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. a=setup</span>
<span class="h4"><a class="selflink" id="section-4.2.1" href="#section-4.2.1">4.2.1</a>. General</span>
An MSRP UA uses the SDP a=setup attribute [<a href="./rfc4145" title=""TCP-Based Media Transport in the Session Description Protocol (SDP)"">RFC4145</a>] in order to
negotiate which endpoint will create the MSRP transport connection
towards the other UA.
An MSRP UA MUST always include an explicit a=setup attribute in its
SDP offers and answers, since it might be useful for the other
endpoint, or for entities in the network, to know whether the UA
supports COMEDIA or not.
<span class="grey">Holmberg & Blau Standards Track [Page 3]</span><span id="page-4" ></span>
<span class="grey"><a href="./rfc6135">RFC 6135</a> MSRP February 2011</span>
An MSRP UA MUST support the a=setup "active", "actpass", and
"passive" attribute values. An MSRP UA MUST NOT send the "holdconn"
attribute value. If an MSRP UA receives the "holdconn" attribute
value, it MUST ignore it and process the message as if it did not
contain an a=setup attribute.
<span class="h4"><a class="selflink" id="section-4.2.2" href="#section-4.2.2">4.2.2</a>. Attribute Usage</span>
When the a=setup attribute value is "actpass" or "passive", the IP
address and port values in the MSRP URI of the SDP a=path attribute
MUST contain the actual address and port values on which the UA can
receive a TCP connection for the MSRP transport connection.
In accordance with [<a href="./rfc4145" title=""TCP-Based Media Transport in the Session Description Protocol (SDP)"">RFC4145</a>], if the a=setup attribute value is
"active", the port number value should be 9.
If an MSRP UA can provide a globally reachable IP address that the
other endpoint can use as a destination for a TCP connection, the UA
MUST use the a=setup "actpass" attribute value in SDP offers. This
is in order to allow the remote UA to send an SDP answer with an
a=setup "active" attribute value if the UA is located behind a NAT,
and in order to be compatible with UAs that do not support COMEDIA
and thus always will act as passive endpoints. If an MSRP UA cannot
provide the actual transport address, the UA MUST use the a=setup
"active" attribute value.
The UA MUST NOT use the a=setup "passive" attribute value in an SDP
offer.
The MSRP UA can determine that it provides a globally reachable IP
address in the following scenarios:
o the UA can determine that it is not located behind a NAT;
o the UA relays its MSRP transport connections via a relay (e.g., an
MSRP relay or Traversal Using Relay NAT (TURN) server); or
o the UA has used Session Traversal Utilities for NAT (STUN)
[<a href="./rfc5389" title=""Session Traversal Utilities for NAT (STUN)"">RFC5389</a>] signaling to retrieve the NAT address and port through
the local port to be used for the eventual transport connection,
while also having determined that the NAT has endpoint-independent
mapping and filtering behavior [<a href="./rfc5382" title=""NAT Behavioral Requirements for TCP"">RFC5382</a>], e.g., using the
mechanism defined in [<a href="./rfc5780" title=""NAT Behavior Discovery Using Session Traversal Utilities for NAT (STUN)"">RFC5780</a>].
Some UAs can determine whether the SIP [<a href="./rfc3261" title=""SIP: Session Initiation Protocol"">RFC3261</a>] signaling has
traversed a NAT by inspecting the SIP Via header field in the 200
(OK) response to the initial SIP REGISTER request, and comparing the
IP addresses in the Via sent-by and the received header field
<span class="grey">Holmberg & Blau Standards Track [Page 4]</span><span id="page-5" ></span>
<span class="grey"><a href="./rfc6135">RFC 6135</a> MSRP February 2011</span>
parameters. If the IP addresses are not the same, then the UA can
determine that there is a NAT in the path. Even though the media
transport might not traverse the NAT, it is safe to assume that it
will. This comparing mechanism does not work in all scenarios,
though. For example, if SIP a request crosses a SIP proxy before
crossing a NAT, the UA will not be able to detect the NAT by
comparing the IP addresses.
If an SDP offer includes an a=setup "actpass" attribute value, the
SDP answerer MAY include an a=setup "active" attribute value in the
SDP answer, but SHOULD include an a=setup "passive" attribute value
if it knows that it is not located behind a NAT.
Once the active UA has established the MSRP transport connection, the
UA must immediately send an MSRP SEND request, as defined in
[<a href="./rfc4975" title=""The Message Session Relay Protocol (MSRP)"">RFC4975</a>].
NOTE: According to [<a href="./rfc4975" title=""The Message Session Relay Protocol (MSRP)"">RFC4975</a>], the initiating UA is always active,
but when COMEDIA is used, the a=setup attribute is used to
negotiate which UA becomes active.
<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. TLS</span>
If an MSRP UA conformant to this document uses Transport Layer
Security (TLS), it MUST use the TLS mechanisms defined in [<a href="./rfc4975" title=""The Message Session Relay Protocol (MSRP)"">RFC4975</a>]
and [<a href="./rfc4976" title=""Relay Extensions for the Message Sessions Relay Protocol (MSRP)"">RFC4976</a>].
According to [<a href="./rfc4975" title=""The Message Session Relay Protocol (MSRP)"">RFC4975</a>], the connection can be established with or
without TLS mutual authentication. In case mutual authentication is
not used, the listening device waits until it receives a request on
the connection, at which time it infers the identity of the
connecting device from the associated session description. From the
TLS authentication point of view, it is thus irrelevant whether an
endpoint takes the active or passive role.
If an MSRP UA uses a self-signed TLS certificate to authenticate
itself to MSRP peers, it also includes its certificate fingerprint in
the SDP.
Note that fingerprints can only be exchanged in peer-to-peer
communication, as MSRP relays [<a href="./rfc4976" title=""Relay Extensions for the Message Sessions Relay Protocol (MSRP)"">RFC4976</a>] will not receive the SDP
payloads containing the fingerprint attributes.
<span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a>. a=connection</span>
MSRP UAs MUST NOT use the SDP a=connection attribute. [<a href="./rfc4975" title=""The Message Session Relay Protocol (MSRP)"">RFC4975</a>]
defines connection reuse procedures for MSRP, and this document does
not modify those procedures.
<span class="grey">Holmberg & Blau Standards Track [Page 5]</span><span id="page-6" ></span>
<span class="grey"><a href="./rfc6135">RFC 6135</a> MSRP February 2011</span>
If an MSRP UA receives an a=connection attribute, the UA MUST
ignore it.
<span class="h3"><a class="selflink" id="section-4.5" href="#section-4.5">4.5</a>. MSRP Relay Connection</span>
If an MSRP UA is located behind an MSRP relay [<a href="./rfc4976" title=""Relay Extensions for the Message Sessions Relay Protocol (MSRP)"">RFC4976</a>], the UA MUST
always initiate a transport connection towards the relay, no matter
what value the client has provided in the a=setup attribute.
NOTE: Even if an MSRP UA initiates the TCP connection towards its
relay, the UA will only send a SEND request if the UA is active,
based on the COMEDIA negotiation.
<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>
An MSRP UA conformant to this document can interoperate with a UA
that follows the connection model defined in [<a href="./rfc4975" title=""The Message Session Relay Protocol (MSRP)"">RFC4975</a>]. However, if
an MSRP UA conformant to this document is located behind a NAT, does
not proxy its MSRP communication via an MSRP relay, and receives an
SDP offer from a remote UA that follows the connection model defined
in [<a href="./rfc4975" title=""The Message Session Relay Protocol (MSRP)"">RFC4975</a>], then NAT traversal can only be achieved if the MSRP UA
supports ICE [<a href="#ref-ICE-TCP" title=""TCP Candidates with Interactive Connectivity Establishment (ICE)"">ICE-TCP</a>] or if the network supports Session Border
Controller (SBC)-assisted NAT traversal for TCP.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span>
According to the connection model defined in [<a href="./rfc4975" title=""The Message Session Relay Protocol (MSRP)"">RFC4975</a>], the MSRP UA
that sends the SDP offer becomes the active party, and it is
responsible for creating the MSRP transport connection towards the
remote UA if a new connection is required.
When COMEDIA is used, either the sender or the receiver of the SDP
offer can become the active party. [<a href="./rfc4975" title=""The Message Session Relay Protocol (MSRP)"">RFC4975</a>] requires that the
active party immediately issue an MSRP SEND request once the
connection has been established. This allows the passive party to
bind the inbound TCP connection to the message session identified by
the session id part of its MSRP URI. The use of COMEDIA does not
change this requirement, but the sender of the SDP offer is no longer
assumed to always become the active party.
The active party also takes the role of the TLS client, if TLS is
used to protect the MSRP messages. However, there are no procedures
in [<a href="./rfc4975" title=""The Message Session Relay Protocol (MSRP)"">RFC4975</a>] that would break in case the receiver of the SDP offer
takes the role of the TLS client, and the level of security provided
by TLS is not affected.
<span class="grey">Holmberg & Blau Standards Track [Page 6]</span><span id="page-7" ></span>
<span class="grey"><a href="./rfc6135">RFC 6135</a> MSRP February 2011</span>
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Acknowledgements</span>
Thanks to Ben Campbell, Remi Denis-Courmont, Nancy Greene, Hadriel
Kaplan, Adam Roach, Robert Sparks, Salvatore Loreto, and Shida
Schubert for their guidance and input in producing this document.
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span>
<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Normative References</span>
[<a id="ref-RFC0793">RFC0793</a>] Postel, J., "Transmission Control Protocol", STD 7,
<a href="./rfc793">RFC 793</a>, September 1981.
[<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-RFC4145">RFC4145</a>] Yon, D. and G. Camarillo, "TCP-Based Media Transport in
the Session Description Protocol (SDP)", <a href="./rfc4145">RFC 4145</a>,
September 2005.
[<a id="ref-RFC4975">RFC4975</a>] Campbell, B., Ed., Mahy, R., Ed., and C. Jennings, Ed.,
"The Message Session Relay Protocol (MSRP)", <a href="./rfc4975">RFC 4975</a>,
September 2007.
[<a id="ref-RFC4976">RFC4976</a>] Jennings, C., Mahy, R., and A. Roach, "Relay Extensions
for the Message Sessions Relay Protocol (MSRP)",
<a href="./rfc4976">RFC 4976</a>, September 2007.
<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Informative 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-RFC5382">RFC5382</a>] Guha, S., Ed., Biswas, K., Ford, B., Sivakumar, S., and
P. Srisuresh, "NAT Behavioral Requirements for TCP",
<a href="https://www.rfc-editor.org/bcp/bcp142">BCP 142</a>, <a href="./rfc5382">RFC 5382</a>, October 2008.
[<a id="ref-RFC5389">RFC5389</a>] Rosenberg, J., Mahy, R., Matthews, P., and D. Wing,
"Session Traversal Utilities for NAT (STUN)", <a href="./rfc5389">RFC 5389</a>,
October 2008.
[<a id="ref-RFC5780">RFC5780</a>] MacDonald, D. and B. Lowekamp, "NAT Behavior Discovery
Using Session Traversal Utilities for NAT (STUN)",
<a href="./rfc5780">RFC 5780</a>, May 2010.
<span class="grey">Holmberg & Blau Standards Track [Page 7]</span><span id="page-8" ></span>
<span class="grey"><a href="./rfc6135">RFC 6135</a> MSRP February 2011</span>
[<a id="ref-ICE-TCP">ICE-TCP</a>] Rosenberg, J., Keranen, A., Lowekamp, B., and A. Roach,
"TCP Candidates with Interactive Connectivity
Establishment (ICE)", Work in Progress, February 2011.
[<a id="ref-OMA-SIMPLE">OMA-SIMPLE</a>] Open Mobile Alliance, "Instant Messaging using SIMPLE",
OMA-TS-SIMPLE_IM-V1_0-20090901-D, September 2009.
Authors' Addresses
Christer Holmberg
Ericsson
Hirsalantie 11
Jorvas 02420
Finland
EMail: [email protected]
Staffan Blau
Ericsson AB
PO Box 407
Sweden
EMail: [email protected]
Holmberg & Blau Standards Track [Page 8]
Annotations
Select text to annotate