draft-ietf-mmusic-sctp-sdp-13.txt   draft-ietf-mmusic-sctp-sdp-14.txt 
MMUSIC C. Holmberg MMUSIC C. Holmberg
Internet-Draft S. Loreto Internet-Draft S. Loreto
Intended status: Standards Track G. Camarillo Intended status: Standards Track G. Camarillo
Expires: September 5, 2015 Ericsson Expires: September 6, 2015 Ericsson
March 4, 2015 March 5, 2015
Stream Control Transmission Protocol (SCTP)-Based Media Transport in the Stream Control Transmission Protocol (SCTP)-Based Media Transport in the
Session Description Protocol (SDP) Session Description Protocol (SDP)
draft-ietf-mmusic-sctp-sdp-13 draft-ietf-mmusic-sctp-sdp-14
Abstract Abstract
SCTP (Stream Control Transmission Protocol) is a transport protocol SCTP (Stream Control Transmission Protocol) is a transport protocol
used to establish associations between two endpoints. used to establish associations between two endpoints.
This specification describes how to describe SCTP associations using This specification describes how to describe SCTP associations using
the Session Description Protocol (SDP), and defines the following new the Session Description Protocol (SDP), and defines the following new
SDP Media Description protocol identifiers (proto values):'SCTP', SDP Media Description protocol identifiers (proto values):'SCTP',
'SCTP/DTLS', 'UDP/DTLS/SCTP' and 'TCP/DTLS/SCTP'. 'SCTP/DTLS', 'UDP/DTLS/SCTP' and 'TCP/DTLS/SCTP'.
skipping to change at page 1, line 43 skipping to change at page 1, line 43
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 5, 2015. This Internet-Draft will expire on September 6, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 41 skipping to change at page 2, line 41
5.3. Mux Category . . . . . . . . . . . . . . . . . . . . . . 7 5.3. Mux Category . . . . . . . . . . . . . . . . . . . . . . 7
6. SDP 'max-message-size' Attribute . . . . . . . . . . . . . . 7 6. SDP 'max-message-size' Attribute . . . . . . . . . . . . . . 7
6.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 7 6.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 7
6.2. Syntax . . . . . . . . . . . . . . . . . . . . . . . . . 8 6.2. Syntax . . . . . . . . . . . . . . . . . . . . . . . . . 8
6.3. Mux Category . . . . . . . . . . . . . . . . . . . . . . 8 6.3. Mux Category . . . . . . . . . . . . . . . . . . . . . . 8
7. UDP/DTLS/SCTP Transport Realization . . . . . . . . . . . . . 8 7. UDP/DTLS/SCTP Transport Realization . . . . . . . . . . . . . 8
8. TCP/DTLS/SCTP Transport Realization . . . . . . . . . . . . . 9 8. TCP/DTLS/SCTP Transport Realization . . . . . . . . . . . . . 9
9. SCTP Association Management . . . . . . . . . . . . . . . . . 9 9. SCTP Association Management . . . . . . . . . . . . . . . . . 9
9.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 9 9.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 9
9.2. SDP sendrecv/sendonly/recvonly/inactive Attribute . . . . 9 9.2. SDP sendrecv/sendonly/recvonly/inactive Attribute . . . . 9
9.3. SDP setup Attribute . . . . . . . . . . . . . . . . . . . 10 9.3. SDP setup Attribute . . . . . . . . . . . . . . . . . . . 9
9.3.1. General . . . . . . . . . . . . . . . . . . . . . . . 10 9.3.1. General . . . . . . . . . . . . . . . . . . . . . . . 9
9.3.2. SCTP Association Initiation . . . . . . . . . . . . . 10 9.3.2. SCTP Association Initiation . . . . . . . . . . . . . 10
9.3.3. TLS Role Determination . . . . . . . . . . . . . . . 10 9.3.3. TLS Role Determination . . . . . . . . . . . . . . . 10
9.4. SDP connection Attribute . . . . . . . . . . . . . . . . 11 9.4. SDP connection Attribute . . . . . . . . . . . . . . . . 11
10. SDP Offer/Answer Procedures . . . . . . . . . . . . . . . . . 11 10. SDP Offer/Answer Procedures . . . . . . . . . . . . . . . . . 11
10.1. General . . . . . . . . . . . . . . . . . . . . . . . . 11 10.1. General . . . . . . . . . . . . . . . . . . . . . . . . 11
10.2. Generating the Initial SDP Offer . . . . . . . . . . . . 12 10.2. Generating the Initial SDP Offer . . . . . . . . . . . . 12
10.3. Generating the SDP Answer . . . . . . . . . . . . . . . 12 10.3. Generating the SDP Answer . . . . . . . . . . . . . . . 12
10.4. Offerer Processing of the SDP Answer . . . . . . . . . . 13 10.4. Offerer Processing of the SDP Answer . . . . . . . . . . 13
10.5. Modifying the Session . . . . . . . . . . . . . . . . . 14 10.5. Modifying the Session . . . . . . . . . . . . . . . . . 13
11. Multihoming Considerations . . . . . . . . . . . . . . . . . 14 11. Multihoming Considerations . . . . . . . . . . . . . . . . . 14
12. NAT Considerations . . . . . . . . . . . . . . . . . . . . . 14 12. NAT Considerations . . . . . . . . . . . . . . . . . . . . . 14
12.1. General . . . . . . . . . . . . . . . . . . . . . . . . 15 12.1. General . . . . . . . . . . . . . . . . . . . . . . . . 14
12.2. ICE Considerations . . . . . . . . . . . . . . . . . . . 15 12.2. ICE Considerations . . . . . . . . . . . . . . . . . . . 15
13. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 15 13. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 15
13.1. Establishment of UDP/DTLS/SCTP association . . . . . . . 15 13.1. Establishment of UDP/DTLS/SCTP association . . . . . . . 15
14. Security Considerations . . . . . . . . . . . . . . . . . . . 16 14. Security Considerations . . . . . . . . . . . . . . . . . . . 16
15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
15.1. New SDP proto values . . . . . . . . . . . . . . . . . . 17 15.1. New SDP proto values . . . . . . . . . . . . . . . . . . 17
15.2. New SDP Attributes . . . . . . . . . . . . . . . . . . . 17 15.2. New SDP Attributes . . . . . . . . . . . . . . . . . . . 17
15.2.1. sctp-port . . . . . . . . . . . . . . . . . . . . . 17 15.2.1. sctp-port . . . . . . . . . . . . . . . . . . . . . 17
15.2.2. max-message-size . . . . . . . . . . . . . . . . . . 18 15.2.2. max-message-size . . . . . . . . . . . . . . . . . . 18
15.3. association-usage Name Registry . . . . . . . . . . . . 18 15.3. association-usage Name Registry . . . . . . . . . . . . 18
skipping to change at page 7, line 22 skipping to change at page 7, line 22
specified, and MUST be discarded if received. specified, and MUST be discarded if received.
5.2. Syntax 5.2. Syntax
The ABNF for the SDP 'sctp-port' attribute is: The ABNF for the SDP 'sctp-port' attribute is:
sctp-port-attr = "a=sctp-port:" port sctp-port-attr = "a=sctp-port:" port
port = (1*5)DIGIT port = (1*5)DIGIT
The SCTP port range is between 0 and 65535 (both included). The SCTP port range is between 0 and 65535 (both included).
Applications MUST NOT use well-known port values, or port
values that have been registered for specific purposes.
Leading zeroes MUST NOT be used. Leading zeroes MUST NOT be used.
5.3. Mux Category 5.3. Mux Category
The mux category [I-D.ietf-mmusic-sdp-mux-attributes] for the SDP The mux category [I-D.ietf-mmusic-sdp-mux-attributes] for the SDP
sctp-port' attribute is SPECIAL. Usage of the attribute is only sctp-port' attribute is SPECIAL. Usage of the attribute is only
applicable when associated with 'UDP/DTLS/SCTP' and 'TCP/DTLS/SCTP' applicable when associated with 'UDP/DTLS/SCTP' and 'TCP/DTLS/SCTP'
proto value m- lines. proto value m- lines.
As the usage of multiple SCTP associations on top of a single DTLS As the usage of multiple SCTP associations on top of a single DTLS
skipping to change at page 13, line 40 skipping to change at page 13, line 38
re-established), initiate the establishing of the SCTP re-established), initiate the establishing of the SCTP
association; and association; and
o MUST, if the offerer is the 'active' endpoint, and if a DTLS o MUST, if the offerer is the 'active' endpoint, and if a DTLS
connection associated with the m- line is to be established (or if connection associated with the m- line is to be established (or if
an existing DTLS connection is to be re-established), initiate the an existing DTLS connection is to be re-established), initiate the
establishing of the DTLS connection (by sending a ClientHello establishing of the DTLS connection (by sending a ClientHello
message). message).
o NOTE: If the m- line proto value is 'UDP/DTLS/SCTP' or 'TCP/DTLS/ o NOTE: If the m- line proto value is 'UDP/DTLS/SCTP' or 'TCP/DTLS/
SCTP', the two actions above are performed in switch order, as the SCTP', the underlying DTLS connection needs to be established
underlying DTLS connection needs to be established before the SCTP before the SCTP association can be established.
association can be established.
If the m- line in the answer contains a zero port value, 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 MUST NOT establish a TCP connection, an SCTP association, or a DTLS
connection, associated with the m- line. connection, associated with the m- line.
10.5. Modifying the Session 10.5. Modifying the Session
When an offerer sends an updated offer, in order to modify a When an offerer sends an updated offer, in order to modify a
previously established SCTP association, it follows the procedures in previously established SCTP association, it follows the procedures in
Section 10.2, with the following exceptions: Section 10.2, with the following exceptions:
skipping to change at page 17, line 38 skipping to change at page 17, line 38
15.2. New SDP Attributes 15.2. New SDP Attributes
15.2.1. sctp-port 15.2.1. sctp-port
[RFC EDITOR NOTE: Please replace RFCXXXX with the RFC number of this [RFC EDITOR NOTE: Please replace RFCXXXX with the RFC number of this
document.] document.]
This document defines a new SDP media-level attribute,'sctp-port', as This document defines a new SDP media-level attribute,'sctp-port', as
follows: follows:
Attribute name: sctp-port Attribute name: sctp-port
Type of attribute: media Type of attribute: media
Mux category: SPECIAL Mux category: SPECIAL
Subject to charset: No Subject to charset: No
Purpose: Indicate the SCTP port value associated Purpose: Indicate the SCTP port value associated
with the SDP Media Description. with the SDP Media Description.
Appropriate values: Integer Appropriate values: Integer
Contact name: Christer Holmberg Contact name: Christer Holmberg
Contact e-mail: christer.holmberg@ericsson.com Contact e-mail: christer.holmberg@ericsson.com
Reference: RFCXXXX Reference: RFCXXXX
15.2.2. max-message-size 15.2.2. max-message-size
[RFC EDITOR NOTE: Please replace RFCXXXX with the RFC number of this [RFC EDITOR NOTE: Please replace RFCXXXX with the RFC number of this
document.] document.]
This document defines a new SDP media-level attribute,'max-message- This document defines a new SDP media-level attribute,'max-message-
size', as follows: size', as follows:
Attribute name: max-message-size Attribute name: max-message-size
Type of attribute: media Type of attribute: media
Mux category: SPECIAL Mux category: SPECIAL
Subject to charset: No Subject to charset: No
Purpose: Indicate the maximum message size that Purpose: Indicate the maximum message size that
an SCTP endpoint is willing to receive an SCTP endpoint is willing to receive
on the SCTP association associated on the SCTP association associated
with the SDP Media Description. with the SDP Media Description.
Appropriate values: Integer Appropriate values: Integer
Contact name: Christer Holmberg Contact name: Christer Holmberg
Contact e-mail: christer.holmberg@ericsson.com Contact e-mail: christer.holmberg@ericsson.com
Reference: RFCXXXX Reference: RFCXXXX
15.3. association-usage Name Registry 15.3. association-usage Name Registry
[RFC EDITOR NOTE: Please replace RFCXXXX with the RFC number of this [RFC EDITOR NOTE: Please replace RFCXXXX with the RFC number of this
document.] document.]
This specification creates a new IANA registry, following the This specification creates a new IANA registry, following the
procedures in [RFC5226], for the "fmt" namespace associated with the procedures in [RFC5226], for the "fmt" namespace associated with the
'SCTP', 'SCTP/DTLS', 'UDP/DTLS/SCTP' and 'TCP/DTLS/SCTP' protocol 'SCTP', 'SCTP/DTLS', 'UDP/DTLS/SCTP' and 'TCP/DTLS/SCTP' protocol
identifiers. Each "fmt" value describes the usage of an entire SCTP identifiers. Each "fmt" value describes the usage of an entire SCTP
skipping to change at page 19, line 33 skipping to change at page 19, line 33
16. Acknowledgments 16. Acknowledgments
The authors wish to thank Harald Alvestrand, Randell Jesup, Paul The authors wish to thank Harald Alvestrand, Randell Jesup, Paul
Kyzivat, Michael Tuexen, Juergen Stoetzer-Bradler, Flemming Andreasen Kyzivat, Michael Tuexen, Juergen Stoetzer-Bradler, Flemming Andreasen
and Ari Keranen for their comments and useful feedback. and Ari Keranen for their comments and useful feedback.
17. Change Log 17. Change Log
[RFC EDITOR NOTE: Please remove this section when publishing] [RFC EDITOR NOTE: Please remove this section when publishing]
Changes from draft-ietf-mmusic-sctp-sdp-13
o Changes based on comments from Paul Kyzivat.
o - Text preventing usage of well-known ports removed.
o - Editorial clarification.
Changes from draft-ietf-mmusic-sctp-sdp-12 Changes from draft-ietf-mmusic-sctp-sdp-12
o Mux category rules added for new SDP attributes. o Mux category rules added for new SDP attributes.
o Reference to draft-ietf-mmusic-sdp-mux-attributes added. o Reference to draft-ietf-mmusic-sdp-mux-attributes added.
o Changes based on comments from Roman Shpount: o Changes based on comments from Roman Shpount:
o - Specify that fingerprint or setup roles must not be modified, o - Specify that fingerprint or setup roles must not be modified,
unless underlying transport protocol is also modified. unless underlying transport protocol is also modified.
 End of changes. 11 change blocks. 
35 lines changed or deleted 40 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/