draft-ietf-mmusic-sctp-sdp-11.txt   draft-ietf-mmusic-sctp-sdp-12.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: June 22, 2015 Ericsson Expires: July 19, 2015 Ericsson
December 19, 2014 January 15, 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-11 draft-ietf-mmusic-sctp-sdp-12
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 June 22, 2015. This Internet-Draft will expire on July 19, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 3, line 6 skipping to change at page 3, line 6
11.2. Generating the Initial SDP Offer . . . . . . . . . . . . 10 11.2. Generating the Initial SDP Offer . . . . . . . . . . . . 10
11.3. Generating the SDP Answer . . . . . . . . . . . . . . . 11 11.3. Generating the SDP Answer . . . . . . . . . . . . . . . 11
11.4. Offerer Processing of the SDP Answer . . . . . . . . . . 12 11.4. Offerer Processing of the SDP Answer . . . . . . . . . . 12
11.5. Modifying the Session . . . . . . . . . . . . . . . . . 12 11.5. Modifying the Session . . . . . . . . . . . . . . . . . 12
12. Multihoming Considerations . . . . . . . . . . . . . . . . . 13 12. Multihoming Considerations . . . . . . . . . . . . . . . . . 13
13. NAT Considerations . . . . . . . . . . . . . . . . . . . . . 13 13. NAT Considerations . . . . . . . . . . . . . . . . . . . . . 13
13.1. General . . . . . . . . . . . . . . . . . . . . . . . . 13 13.1. General . . . . . . . . . . . . . . . . . . . . . . . . 13
13.2. ICE Considerations . . . . . . . . . . . . . . . . . . . 14 13.2. ICE Considerations . . . . . . . . . . . . . . . . . . . 14
14. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 14 14. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 14
15. Security Considerations . . . . . . . . . . . . . . . . . . . 14 14.1. Establishment of UDP/DTLS/SCTP association . . . . . . . 14
16. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 15. Security Considerations . . . . . . . . . . . . . . . . . . . 15
16.1. New SDP proto values . . . . . . . . . . . . . . . . . . 14 16. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
16.1. New SDP proto values . . . . . . . . . . . . . . . . . . 15
16.2. New SDP Attributes . . . . . . . . . . . . . . . . . . . 15 16.2. New SDP Attributes . . . . . . . . . . . . . . . . . . . 15
16.2.1. sctp-port . . . . . . . . . . . . . . . . . . . . . 15 16.2.1. sctp-port . . . . . . . . . . . . . . . . . . . . . 15
16.2.2. max-message-size . . . . . . . . . . . . . . . . . . 15 16.2.2. max-message-size . . . . . . . . . . . . . . . . . . 16
16.3. association-usage Name Registry . . . . . . . . . . . . 16 16.3. association-usage Name Registry . . . . . . . . . . . . 16
17. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 16 17. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 17
18. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 17 18. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 17
19. References . . . . . . . . . . . . . . . . . . . . . . . . . 17 19. References . . . . . . . . . . . . . . . . . . . . . . . . . 18
19.1. Normative References . . . . . . . . . . . . . . . . . . 17 19.1. Normative References . . . . . . . . . . . . . . . . . . 18
19.2. Informative References . . . . . . . . . . . . . . . . . 19 19.2. Informative References . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20
1. Introduction 1. Introduction
SDP (Session Description Protocol) [RFC4566] provides a general- SDP (Session Description Protocol) [RFC4566] provides a general-
purpose format for describing multimedia sessions in announcements or purpose format for describing multimedia sessions in announcements or
invitations. TCP-Based Media Transport in the Session Description invitations. TCP-Based Media Transport in the Session Description
Protocol (SDP) [RFC4145] specifies a general mechanism for describing Protocol (SDP) [RFC4145] specifies a general mechanism for describing
and establishing TCP (Transmission Control Protocol) [RFC5246] and establishing TCP (Transmission Control Protocol) [RFC5246]
streams. Connection-Oriented Media Transport over the Transport streams. Connection-Oriented Media Transport over the Transport
Layer Security (TLS) Protocol in the Session Description Protocol Layer Security (TLS) Protocol in the Session Description Protocol
skipping to change at page 10, line 32 skipping to change at page 10, line 32
11.1. General 11.1. General
This section defines the SDP Offer/Answer [RFC3264] procedures for This section defines the SDP Offer/Answer [RFC3264] procedures for
negotiating and establishing an SCTP association. Unless explicitly negotiating and establishing an SCTP association. Unless explicitly
stated, the procedures apply to all m- line proto values ('SCTP', stated, the procedures apply to all m- line proto values ('SCTP',
'SCTP/DTLS', 'UDP/DTLS/SCTP' and 'TCP/DTLS/SCTP') defined in this 'SCTP/DTLS', 'UDP/DTLS/SCTP' and 'TCP/DTLS/SCTP') defined in this
specification. specification.
If the m- line proto value is 'SCTP/DTLS', 'UDP/DTLS/SCTP' or If the m- line proto value is 'SCTP/DTLS', 'UDP/DTLS/SCTP' or
'TCP/DTLS/SCTP', each endpoint MUST provide a certificate 'TCP/DTLS/SCTP', each endpoint MUST provide a certificate
fingerprint, using the SDP 'fingerprint' attribute [RFC4145], if the fingerprint, using the SDP 'fingerprint' attribute [RFC4572], if the
endpoint supports, and is willing to use, a cipher suite with an endpoint supports, and is willing to use, a cipher suite with an
associated certificate. associated certificate.
The authentication certificates are interpreted and validated as The authentication certificates are interpreted and validated as
defined in [RFC4572]. Self-signed certificates can be used securely, defined in [RFC4572]. Self-signed certificates can be used securely,
provided that the integrity of the SDP description is assured as provided that the integrity of the SDP description is assured as
defined in [RFC4572]. defined in [RFC4572].
NOTE: The procedures apply to a specific m- line describing an SCTP NOTE: The procedures apply to a specific m- line describing an SCTP
association. If an offer or answer contains multiple m- lines association. If an offer or answer contains multiple m- lines
skipping to change at page 14, line 15 skipping to change at page 14, line 15
13.2. ICE Considerations 13.2. ICE Considerations
At the time of writing this specification, no procedures have been At the time of writing this specification, no procedures have been
defined for using ICE (Interactive Connectivity Establishment) defined for using ICE (Interactive Connectivity Establishment)
[RFC5768] together with SCTP. Such procedures, including the [RFC5768] together with SCTP. Such procedures, including the
associated SDP Offer/Answer procedures, are outside the scope of this associated SDP Offer/Answer procedures, are outside the scope of this
specification, and might be defined in a future specification. specification, and might be defined in a future specification.
14. Examples 14. Examples
TODO: ADD EXAMPLES HERE 14.1. Establishment of UDP/DTLS/SCTP association
SDP Offer:
m=application 54111 UDP/DTLS/SCTP webrtc-datachannel
c=IN IP4 192.0.2.1
a=setup:actpass
a=connection:new
a=sctp-port:5000
a=max-message-size: 100000
- The offerer indicates that the usage of the
UDP/DTLS/SCTP association will be as defined
for the 'webrtc-datachannel' format value.
- The offerer UDP port value is 54111.
- The offerer SCTP port value is 5000.
- The offerer indicates that it can take either the
active or the passive role.
SDP Answer:
m=application 64300 UDP/DTLS/SCTP webrtc-datachannel
c=IN IP4 192.0.2.2
a=setup:passive
a=sctp-port:6000
a=max-message-size: 100000
- The answerer UDP port value is 64300.
- The answerer SCTP port value is 6000.
- The answerer takes the passive role.
15. Security Considerations 15. Security Considerations
[RFC4566] defines general SDP security considerations, while [RFC4566] defines general SDP security considerations, while
[RFC3264], [RFC4145] and [RFC4572] define security considerations [RFC3264], [RFC4145] and [RFC4572] define security considerations
when using the SDP offer/answer mechanism to negotiate media streams. when using the SDP offer/answer mechanism to negotiate media streams.
[RFC4960] defines general SCTP security considerations. security [RFC4960] defines general SCTP security considerations. security
considerations on SCTP in general, while [RFC6083] defines security considerations on SCTP in general, while [RFC6083] defines security
considerations when using DTLS on top of SCTP. considerations when using DTLS on top of SCTP.
skipping to change at page 17, line 9 skipping to change at page 17, line 37
17. Acknowledgments 17. Acknowledgments
The authors wish to thank Harald Alvestrand, Randell Jesup, Paul The authors wish to thank Harald Alvestrand, Randell Jesup, Paul
Kyzivat, Michael Tuexen for their comments and useful feedback. Kyzivat, Michael Tuexen for their comments and useful feedback.
18. Change Log 18. 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-11
o Example added.
Changes from draft-ietf-mmusic-sctp-sdp-10 Changes from draft-ietf-mmusic-sctp-sdp-10
o SDP max-message-size attribute added to IANA considerations. o SDP max-message-size attribute added to IANA considerations.
o Changes based on comments from Paul Kyzivat: o Changes based on comments from Paul Kyzivat:
o - Text about max message size removed from fmtp attribute section. o - Text about max message size removed from fmtp attribute section.
Changes from draft-ietf-mmusic-sctp-sdp-09 Changes from draft-ietf-mmusic-sctp-sdp-09
o 'DTLS/SCTP' split into 'UDP/DTLS/SCTP' and 'TCP/DTLS/SCTP' o 'DTLS/SCTP' split into 'UDP/DTLS/SCTP' and 'TCP/DTLS/SCTP'
o Procedures for realizing UDP/DTLS/SCTP- and TCP/DTLS/SCTP o Procedures for realizing UDP/DTLS/SCTP- and TCP/DTLS/SCTP
transports added. transports added.
Changes from draft-ietf-mmusic-sctp-sdp-08 Changes from draft-ietf-mmusic-sctp-sdp-08
o Default SCTP port removed: o Default SCTP port removed:
o - Usage of SDP sctp-port attribute mandatory. o - Usage of SDP sctp-port attribute mandatory.
 End of changes. 13 change blocks. 
16 lines changed or deleted 49 lines changed or added

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