| MMUSIC | C. Holmberg |
| Internet-Draft | S. Loreto |
| Intended status: Standards Track | G. Camarillo |
| Expires: June 22, 2015 | Ericsson |
| December 19, 2014 |
Stream Control Transmission Protocol (SCTP)-Based Media Transport in the Session Description Protocol (SDP)
draft-ietf-mmusic-sctp-sdp-10
SCTP (Stream Control Transmission Protocol) is a transport protocol used to establish associations between two endpoints.
This specification describes how to describe SCTP associations using the Session Description Protocol (SDP), and defines the following new SDP Media Description protocol identifiers (proto values):'SCTP', 'SCTP/DTLS', 'UDP/DTLS/SCTP' and 'TCP/DTLS/SCTP'.
The specification also describes how to use the new proto values together with the SDP Offer/Answer mechanism in order to negotiate and establish SCTP associations, and how to indicate the SCTP application usage.
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."
This Internet-Draft will expire on June 22, 2015.
Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) 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.
SDP (Session Description Protocol) [RFC4566] provides a general-purpose format for describing multimedia sessions in announcements or invitations. TCP-Based Media Transport in the Session Description Protocol (SDP) [RFC4145] specifies a general mechanism for describing and establishing TCP (Transmission Control Protocol) [RFC5246] streams. Connection-Oriented Media Transport over the Transport Layer Security (TLS) Protocol in the Session Description Protocol (SDP) [RFC4572] extends RFC4145 [RFC4145] for describing TCP-based media streams that are protected using TLS.
SCTP (Stream Control Transmission Protocol) is a transport protocol used to establish associations between two endpoints.
This specification describes how to describe SCTP associations using the Session Description Protocol (SDP) [RFC4566], and defines the following new SDP Media Description [RFC4566] protocol identifiers (proto values):'SCTP', 'SCTP/DTLS', 'UDP/DTLS/SCTP' and 'TCP/DTLS/SCTP'.
The specification also describes how to use the new proto values together with the SDP Offer/Answer mechanism [RFC3264] in order to negotiate and establish SCTP associations, and how to indicate the SCTP application usage.
NOTE: TLS is designed to run on top of a byte-stream oriented transport protocol providing a reliable, in-sequence delivery like TCP. [RFC6083] presents serious limitations with transporting SCTP on top of TLS. Therefore, defining a mechanism to negotiate media streams transported using SCTP on top of TLS is outside the scope of this specification.
In this document, the key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" are to be interpreted as described in BCP 14, RFC 2119 [RFC2119] and indicate requirement levels for compliant implementations.
SCTP Association: A protocol relationship between SCTP endpoints, composed of the two SCTP endpoints and protocol state information including Verification Tags and the currently active set of Transmission Sequence Numbers (TSNs), etc. An association can be uniquely identified by the transport addresses used by the endpoints in the association. Two SCTP endpoints MUST NOT have more than one SCTP association between them at any given time.
SCTP Stream: A unidirectional logical channel established from one to another associated SCTP endpoint, within which all user messages are delivered in sequence except for those submitted to the unordered delivery service.
SCTP Transport address: A transport address is traditionally defined by a network-layer address, a transport-layer protocol, and a transport-layer port number. In the case of SCTP running over IP, a transport address is defined by the combination of an IP address and an SCTP port number (where SCTP is the transport protocol).
This section defines the following new SDP Media Description (m- line) protocol identifiers (proto values) for describing an SCTP association: 'SCTP', 'SCTP/DTLS', 'UDP/DTLS/SCTP' and 'TCP/DTLS/SCTP'. The section also describes how an m- line, associated with the proto values, is created.
The following is the format for an 'm' line, as specified in RFC4566 [RFC4566]:
m=<media> <port> <proto> <fmt> ...
The 'SCTP', 'SCTP/DTLS', 'UDP/DTLS/SCTP' and 'TCP/DTLS/SCTP' proto values are similar to both the 'UDP' and 'TCP' proto values in that they only describe the transport-layer protocol and not the upper-layer protocol.
NOTE: When the 'UDP/DTLS/SCTP' and 'TCP/DTLS/SCTP' proto values are used, the underlying transport protocol is either UDP or TCP, SCTP is carried on top of either of those transport-layer protocols.
The m- line fmt value, identifying the application-layer protocol, MUST be registered by IANA.
The new proto values are defined as below:
[RFC4566] defines that specifications defining new proto values must define the rules by which their media format (fmt) namespace is managed. Use of an existing MIME subtype for the format is encouraged. If no MIME subtype exists, it is recommended that a suitable one is registered through the IETF process [RFC6838] [RFC4289] by production of, or reference to, a standards-track RFC that defines the transport protocol for the format.
An m- line with a proto value of 'SCTP', 'SCTP/DTLS', 'UDP/DTLS/SCTP' or 'TCP/DTLS/SCTP' always describe a single SCTP association.
In addition, such m- line MUST further indicate the application-layer protocol using an 'fmt' identifier. There MUST be exactly one 'fmt' value per m- line associated with the proto values defined in this specification. The "fmt" namespace associated with those proto values describes the generic application usage of the entire SCTP association, including the associated SCTP streams.
NOTE: A mechanism on how to describe, and manage, individual SCTP streams within an SCTP association, is outside the scope of this specification.
sctp-m-line = %x6d "="
("application" SP sctp-port SP "SCTP" SP sctp-fmt CRLF) /
("application" SP sctp-port SP "SCTP/DTLS" SP sctp-fmt CRLF) /
("application" SP udp-port SP "UDP/DTLS/SCTP" SP sctp-fmt CRLF) /
("application" SP udp-port SP "TCP/DTLS/SCTP" SP sctp-fmt CRLF)
sctp-port = port
udp-port = port
sctp-fmt = association-usage
association-usage = token
m=application 12345 UDP/DTLS/SCTP webrtc-datachannel a=max-message-size: 100000
This section defines a new SDP media-level attribute, 'sctp-port'. The attribute can be associated with an SDP media descriptor (m- line) with a 'UDP/DTLS/SCTP' or a 'TCP/DTLS/SCTP' proto value, in which case the m- line port value indicates the port of the transport-layer protocol (UDP or TCP), on which SCTP is carried.
If the SDP sctp-port attribute is not present, the m- line MUST be discarded.
Usage of the SDP sctp-port attribute with other proto values is not specified, and MUST be discarded if received.
sctp-port-attr = "a=sctp-port:" port
port = 1*DIGIT
The SDP 'max-message-size' attribute can be associated with an m- line to indicate the maximum message size that an SCTP endpoint is willing to receive on the SCTP association associated with the m- line.
The remote peer MUST assume that larger messages will be rejected by the SCTP endpoint. SCTP endpoints need to decide on appropriate behavior in case a message that exceeds the maximum size needs to be sent.
If the SDP 'max-message-size' attribute contains a maximum message size value of zero, it indicates the SCTP endpoint will handle messages of any size, subject to memory capacity etc.
If the SDP 'max-message-size' attribute is not present, the default value is 64K.
max-message-size-attr = "a=max-message-size:" max-message-size
max-message-size = 1*DIGIT
The SDP 'fmtp' attribute can be used with an m- line, associated with an SCTP association, to indicate the maximum message size that an SCTP endpoint is willing to receive, for a particular SCTP association usage, on that SCTP association.
The remote peer MUST assume that larger messages will be rejected by the SCTP endpoint. SCTP endpoints need to decide on appropriate behavior in case a message that exceeds the maximum size needs to be sent.
If the SDP 'fmtp' attribute contains a maximum message size value of zero, it indicates the SCTP endpoint will handle messages of any size, subject to memory capacity etc.
If the SDP 'fmtp' attribute is not present, the default value is 64K.
NOTE: This specification only defines the usage of the SDP 'max-message-size' attribute when associated with an m- line containing one of the following proto field values: 'SCTP', 'SCTP/DTLS', 'UDP/DTLS/SCTP' or 'TCP/DTLS/SCTP'. Usage of the attribute with other proto values needs to be defined in a separate specification.
sctpmap-attr = "a=fmtp:" association-usage [max-message-size]
max-message-size = "max-message-size" EQUALS 1*DIGIT
The UDP/DTLS/SCTP transport is realized as described below:
The TCP/DTLS/SCTP transport is realized as described below:
NOTE: DTLS on top of TCP, without using the framing method defined in [RFC4571] is outside the scope of this specification. A separate proto value would need to be registered for such transport realization.
The management of an SCTP association is identical to the management of a TCP connection. An SCTP endpoints MUST follow the rules in Section 6 of [RFC4145] to manage SCTP associations. Whether to use the SCTP ordered or unordered delivery service is up to the applications using the SCTP association, and this specification does not define a mechanism to indicate the type of delivery service using SDP.
This specification does not define semantics for the SDP direction attributes [RFC4566]. Specifications for an individual SCTP association usage MAY define how the attributes can be used with that usage. Unless semantics of these attributes for an SCTP association usage have been defined, SDP direction attributes MUST be discarded if present.
The SDP setup attribute is used to determine the 'active/passive' status of the endpoints, following the procedures for TCP in [RFC4145].
Both the 'active' and 'passive' endpoint MUST initiate the SCTP association, and MUST use the same SCTP port as client port and server port (in order to prevent two separate SCTP associations from being established).
NOTE: The procedure above is different from TCP, where only the 'active' endpoint initiates the TCP connection [RFC4145].
If the m- line proto value is 'TCP/DTLS/SCTP', only the 'active' endpoint will initiate the TCP connection, following the procedures in [RFC4145]. Both endpoints will still initiate the SCTP association on top of the TCP connection.
If the m- line proto value is 'SCTP/DTLS', 'UDP/DTLS/SCTP' or 'TCP/DTLS/SCTP', the 'active/passive' status is used to determine the TLS roles of the endpoints. Following the procedures in [RFC4572], the 'active' endpoint will take the TLS client role.
Once a DTLS connection has been established, if the 'active/passive' status of the endpoints change (as result of an offer/answer transaction) during a session, a new DTLS connection MUST be established. Therefore, endpoints SHOULD NOT change the 'active/passive' status during a session, unless they want to establish a new DTLS connection.
If the transport parameters or the key fingerprints change, the endpoints MUST establish a new DTLS connection. In such case the 'active/passive' status of the endpoints will again be determined following the procedures in [RFC4145], and the new status will be used to determine the TLS roles of the endpoints associated with the new DTLS connection.
NOTE: The procedure above is identical to the one defined for SRTP-DTLS in [RFC5763].
The SDP connection attribute is used following the procedures in [RFC4145], with the additional SCTP specific considerations described in this section.
If the m- line proto value is 'TCP/DTLS/SCTP', an SDP connection attribute associated with that m- line applies to both the SCTP association and the TCP connection. Therefore, an attribute 'new' value indicates that both a new SCTP association, and a new TCP connection, have to be established, following the procedures in [RFC4145].
NOTE: This specification does not define a mechanism which allows re-establishing of a new SCTP association, while maintaining the TCP connection.
The SDP connection attribute value does not automatically impact an existing DTLS connection. Section 10.3.3 describes in which cases a new DTLS connections will be established.
NOTE: If the m- line proto value is 'SCTP/DTLS', and if the SCTP association is re-established, the DTLS connection also needs to be re-established.
This section defines the SDP Offer/Answer [RFC3264] procedures for negotiating and establishing an SCTP association. Unless explicitly stated, the procedures apply to all m- line proto values ('SCTP', 'SCTP/DTLS', 'UDP/DTLS/SCTP' and 'TCP/DTLS/SCTP') defined in this specification.
If the m- line proto value is 'SCTP/DTLS', 'UDP/DTLS/SCTP' or 'TCP/DTLS/SCTP', each endpoint MUST provide a certificate fingerprint, using the SDP 'fingerprint' attribute [RFC4145], if the endpoint supports, and is willing to use, a cipher suite with an associated certificate.
The authentication certificates are interpreted and validated as defined in [RFC4572]. Self-signed certificates can be used securely, provided that the integrity of the SDP description is assured as defined in [RFC4572].
NOTE: The procedures apply to a specific m- line describing an SCTP association. If an offer or answer contains multiple m- lines describing SCTP associations, the procedures are applied separately to each m- line.
When the offerer creates an initial offer, the offerer:
When the answerer receives an offer, which contains an m- line describing an SCTP association, if the answerer accepts the m- line it:
Once the answerer has sent the answer, the answerer:
If the answerer does not accept the m- line in the offer, it MUST assign a zero port value to the corresponding m- line in the answer. In addition, the answerer MUST NOT establish an SCTP association, or a DTLS connection, associated with the m- line.
When the offerer receives an answer, which contains an m- line with a non-zero port value, describing an SCTP association, the offerer:
If the m- line in the answer contains a zero port value, the offerer MUST NOT establish a TCP connection, an SCTP association, or a DTLS connection, associated with the m- line.
When an offerer sends an updated offer, in order to modify a previously established SCTP association, it follows the procedures in Section 11.2, with the following exceptions:
NOTE: Different SCTP association usages might define protocol procedures etc that need to be performed before an SCTP association is terminated. Such procedures are outside the scope of this specification.
SCTP supports multihoming. An SCTP endpoint is considered multihomed if it has more than one IP address on which SCTP can be used. An SCTP endpoint inform the remote peer about its IP addresses using the address parameters in the INIT/INIT-ACK chunk. Therefore, when SDP is used to describe an SCTP association, while the "c=" line contains the address which was used to negotiate the SCTP association, multihomed SCTP endpoints might end up using other IP addresses.
If an endpoint removes the IP address [RFC5061] that it offered in the SDP "c=" line associated with the SCTP association, it MUST send a new Offer, in which the "c=" line contains an IP address with is valid within the SCTP association.
NOTE: In some network environments, intermediaries performing gate- and firewall control use the address information in the SDP "c=" and "m=" lines to authorize media, and will not pass media sent using other addresses. In such network environment, if an SCTP endpoints wants to change the address information on which media is sent and received, it needs to send an updated Offer, in which the SDP "c=" and "m=" lines contain the new address information.
Multihoming is not supported when sending SCTP on top of DTLS, as DTLS does not expose address management to its upper layer.
SCTP features not present in UDP or TCP, including the checksum (CRC32c) value calculated on the whole packet (rather than just the header), and multihoming, introduce new challenges for NAT traversal. [I-D.ietf-behave-sctpnat] defines an SCTP specific variant of NAT, which provides similar features of Network Address and Port Translation (NAPT).
Current NATs typically do not support SCTP. [RFC6951] defines a mechanism for sending SCTP on top of UDP, which makes it possible to use SCTP with NATs and firewalls that do not support SCTP.
At the time of writing this specification, no procedures have been defined for using ICE (Interactive Connectivity Establishment) [RFC5768] together with SCTP. Such procedures, including the associated SDP Offer/Answer procedures, are outside the scope of this specification, and might be defined in a future specification.
TODO: ADD EXAMPLES HERE
[RFC4566] defines general SDP security considerations, while [RFC3264], [RFC4145] and [RFC4572] define security considerations when using the SDP offer/answer mechanism to negotiate media streams.
[RFC4960] defines general SCTP security considerations. security considerations on SCTP in general, while [RFC6083] defines security considerations when using DTLS on top of SCTP.
This specification does not introduce new security considerations in addition to those defined in the specifications listed above.
[RFC EDITOR NOTE: Please replace RFCXXXX with the RFC number of this document.]
This document updates the "Session Description Protocol (SDP) Parameters" registry, following the procedures in [RFC4566], by adding the following values to the table in the SDP "proto" field registry:
| Type | SDP Name | Reference |
|---|---|---|
| proto | SCTP | [RFCXXXX] |
| proto | SCTP/DTLS | [RFCXXXX] |
| proto | UDP/DTLS/SCTP | [RFCXXXX] |
| TCP/DTLS/SCTP | [RFCXXXX] |
[RFC EDITOR NOTE: Please replace RFCXXXX with the RFC number of this document.]
This document defines a new SDP media-level attribute,'sctp-port', as follows:
Attribute name: sctp-port Type of attribute: media Subject to charset: No Purpose: Indicate the SCTP port value associated with the SDP Media Description. Appropriate values: Integer Contact name: Christer Holmberg Contact e-mail: christer.holmberg@ericsson.com Reference: RFCXXXX
[RFC EDITOR NOTE: Please replace RFCXXXX with the RFC number of this document.]
This specification creates a new IANA registry, following the procedures in [RFC5226], for the "fmt" namespace associated with the 'SCTP', 'SCTP/DTLS', 'UDP/DTLS/SCTP' and 'TCP/DTLS/SCTP' protocol identifiers. Each "fmt" value describes the usage of an entire SCTP association, including all SCTP streams associated with the SCTP association.
NOTE: Usage indication of individual SCTP streams is outside the scope of this specification.
The "fmt" value, "association-usage", used with these "proto" is required. It is defined in [Section 4].
As part of this registry, IANA maintains the following information:
association-usage names are to be subject to the "First Come First Served" IANA registration policy [RFC5226].
IANA is asked to add initial values to the registry.
| name | Reference |
-+--------------------+-------------------------------------+
| webrtc-datachannel | draft-ietf-rtcweb-data-protocol-xx |
-+----------------------------------------------------------|
Figure 1
The authors wish to thank Harald Alvestrand, Randell Jesup, Paul Kyzivat, Michael Tuexen for their comments and useful feedback.
[RFC EDITOR NOTE: Please remove this section when publishing]
Changes from draft-ietf-mmusic-sctp-sdp-09
Changes from draft-ietf-mmusic-sctp-sdp-08
| [RFC5763] | Fischl, J., Tschofenig, H. and E. Rescorla, "Framework for Establishing a Secure Real-time Transport Protocol (SRTP) Security Context Using Datagram Transport Layer Security (DTLS)", RFC 5763, May 2010. |
| [RFC5768] | Rosenberg, J., "Indicating Support for Interactive Connectivity Establishment (ICE) in the Session Initiation Protocol (SIP)", RFC 5768, April 2010. |
| [RFC6083] | Tuexen, M., Seggelmann, R. and E. Rescorla, "Datagram Transport Layer Security (DTLS) for Stream Control Transmission Protocol (SCTP)", RFC 6083, January 2011. |
| [RFC6951] | Tuexen, M. and R. Stewart, "UDP Encapsulation of Stream Control Transmission Protocol (SCTP) Packets for End-Host to End-Host Communication", RFC 6951, May 2013. |
| [I-D.ietf-behave-sctpnat] | Stewart, R., Tuexen, M. and I. Ruengeler, "Stream Control Transmission Protocol (SCTP) Network Address Translation", Internet-Draft draft-ietf-behave-sctpnat-09, September 2013. |