draft-ietf-mmusic-sctp-sdp-22.txt   draft-ietf-mmusic-sctp-sdp-23.txt 
MMUSIC C. Holmberg MMUSIC C. Holmberg
Internet-Draft Ericsson Internet-Draft Ericsson
Intended status: Standards Track R. Shpount Intended status: Standards Track R. Shpount
Expires: July 29, 2017 TurboBridge Expires: August 14, 2017 TurboBridge
S. Loreto S. Loreto
G. Camarillo G. Camarillo
Ericsson Ericsson
January 25, 2017 February 10, 2017
Session Description Protocol (SDP) Offer/Answer Procedures For Stream Session Description Protocol (SDP) Offer/Answer Procedures For Stream
Control Transmission Protocol (SCTP) over Datagram Transport Layer Control Transmission Protocol (SCTP) over Datagram Transport Layer
Security (DTLS) Transport. Security (DTLS) Transport.
draft-ietf-mmusic-sctp-sdp-22 draft-ietf-mmusic-sctp-sdp-23
Abstract Abstract
The Stream Control Transmission Protocol (SCTP) is a transport The Stream Control Transmission Protocol (SCTP) is a transport
protocol used to establish associations between two endpoints. protocol used to establish associations between two endpoints.
draft-ietf-tsvwg-sctp-dtls-encaps-09 specifies how SCTP can be used draft-ietf-tsvwg-sctp-dtls-encaps-09 specifies how SCTP can be used
on top of the Datagram Transport Layer Security (DTLS) protocol, on top of the Datagram Transport Layer Security (DTLS) protocol,
referred to as SCTP-over-DTLS. referred to as SCTP-over-DTLS.
This specification defines the following new Session Description This specification defines the following new Session Description
skipping to change at page 1, line 46 skipping to change at page 1, line 46
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 July 29, 2017. This Internet-Draft will expire on August 14, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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 4, line 5 skipping to change at page 4, line 5
[I-D.ietf-tsvwg-sctp-dtls-encaps] specifies how SCTP can be used on [I-D.ietf-tsvwg-sctp-dtls-encaps] specifies how SCTP can be used on
top of the Datagram Transport Layer Security (DTLS) protocol, top of the Datagram Transport Layer Security (DTLS) protocol,
referred to as SCTP-over-DTLS. referred to as SCTP-over-DTLS.
This specification defines the following new Session Description This specification defines the following new Session Description
Protocol (SDP) [RFC4566] protocol identifiers (proto Protocol (SDP) [RFC4566] protocol identifiers (proto
values):'UDP/DTLS/SCTP' and 'TCP/DTLS/SCTP'. This specification also values):'UDP/DTLS/SCTP' and 'TCP/DTLS/SCTP'. This specification also
specifies how to use the new proto values with the SDP Offer/Answer specifies how to use the new proto values with the SDP Offer/Answer
mechanism [RFC3264] for negotiating SCTP-over-DTLS associations. mechanism [RFC3264] for negotiating SCTP-over-DTLS associations.
NOTE: Due to the characteristics of TCP, usage of 'TCP/DTLS/SCTP' NOTE: Due to the characteristics of TCP, while multiple SCTP streams
will always force ordered and reliable delivery of the SCTP packets, can still be used, usage of 'TCP/DTLS/SCTP' will always force ordered
which limits the usage of the SCTP options. Therefore, it is and reliable delivery of the SCTP packets, which limits the usage of
RECOMMENDED that TCP is only used in situations where UDP traffic is the SCTP options. Therefore, it is RECOMMENDED that TCP is only used
blocked. in situations where UDP traffic is blocked.
2. Conventions 2. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
3. SCTP Terminology 3. SCTP Terminology
SCTP Association: A protocol relationship between SCTP endpoints, SCTP Association: A protocol relationship between SCTP endpoints,
skipping to change at page 6, line 17 skipping to change at page 6, line 17
description ("m=" line) associated with an SCTP-over-DTLS description ("m=" line) associated with an SCTP-over-DTLS
association. association.
This specification creates an IANA registry for 'association-usage' This specification creates an IANA registry for 'association-usage'
values. values.
4.4.2. SDP Media Description values 4.4.2. SDP Media Description values
m= line parameter parameter value(s) m= line parameter parameter value(s)
------------------------------------------------------------------ ------------------------------------------------------------------
<media>: "application" <media>: 'application'
<proto>: "UDP/DTLS/SCTP" or "TCP/DTLS/SCTP" <proto>: 'UDP/DTLS/SCTP' or 'TCP/DTLS/SCTP'
<port>: UDP port number (for "UDP/DTLS/SCTP") <port>: UDP port number (for 'UDP/DTLS/SCTP')
TCP port number (for ""UDP/DTLS/SCTP") TCP port number (for 'TCP/DTLS/SCTP')
<fmt>: a string denoting the association-usage, <fmt>: a string denoting the association-usage,
limited to the syntax of a 'token' as limited to the syntax of a 'token' as
defined in RFC4566. defined in RFC4566.
4.5. Example 4.5. Example
m=application 12345 UDP/DTLS/SCTP webrtc-datachannel m=application 12345 UDP/DTLS/SCTP webrtc-datachannel
a=sctp-port:5000 a=sctp-port:5000
a=max-message-size:100000 a=max-message-size:100000
skipping to change at page 17, line 18 skipping to change at page 17, line 18
ICE has been negotiated. If ICE is not used, the proto value MUST ICE has been negotiated. If ICE is not used, the proto value MUST
always reflect the transport protocol used at any given time. always reflect the transport protocol used at any given time.
13. Examples 13. Examples
13.1. Establishment of UDP/DTLS/SCTP association 13.1. Establishment of UDP/DTLS/SCTP association
SDP Offer: SDP Offer:
m=application 54111 UDP/DTLS/SCTP webrtc-datachannel m=application 54111 UDP/DTLS/SCTP webrtc-datachannel
c=IN IP4 192.0.2.1 c=IN IP6 2001:DB8::A8FD
a=dtls-id:abc3dl a=dtls-id:abc3dl
a=setup:actpass a=setup:actpass
a=sctp-port:5000 a=sctp-port:5000
a=max-message-size:100000 a=max-message-size:100000
- The offerer indicates that the usage of the - The offerer indicates that the usage of the
UDP/DTLS/SCTP association will be as defined UDP/DTLS/SCTP association will be as defined
for the 'webrtc-datachannel' format value. for the 'webrtc-datachannel' format value.
- The offerer UDP port value is 54111. - The offerer UDP port value is 54111.
- The offerer SCTP port value is 5000. - The offerer SCTP port value is 5000.
- The offerer indicates that it can take either the - The offerer indicates that it can take either the
client or the server DTLS role. client or the server DTLS role.
SDP Answer: SDP Answer:
m=application 64300 UDP/DTLS/SCTP webrtc-datachannel m=application 64300 UDP/DTLS/SCTP webrtc-datachannel
c=IN IP4 192.0.2.2 c=IN IP6 2001:DB8::001D
a=dtls-id:ggr4rd a=dtls-id:ggr4rd
a=setup:passive a=setup:passive
a=sctp-port:6000 a=sctp-port:6000
a=max-message-size:100000 a=max-message-size:100000
- The answerer UDP port value is 64300. - The answerer UDP port value is 64300.
- The answerer SCTP port value is 6000. - The answerer SCTP port value is 6000.
- The answerer takes the server DTLS role. - The answerer takes the server DTLS role.
14. Security Considerations 14. Security Considerations
skipping to change at page 20, line 10 skipping to change at page 20, line 10
[RFC EDITOR NOTE: Please replace RFCXXXX with the RFC number [RFC EDITOR NOTE: Please replace RFCXXXX with the RFC number
of this document.] of this document.]
Figure 1 Figure 1
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. Ben Campbell and Ari Keranen for their comments and useful feedback. Ben Campbell
provided comments as part of his AD review. provided comments as part of his AD review. Brian Carpenter
performed the Gen-ART review.
17. 17.
[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-22
o Changes based on Gen-ART review by Brian Carpenter.
Changes from draft-ietf-mmusic-sctp-sdp-21 Changes from draft-ietf-mmusic-sctp-sdp-21
o Changes based on AD review by Ben Campbell. o Changes based on AD review by Ben Campbell.
Changes from draft-ietf-mmusic-sctp-sdp-20 Changes from draft-ietf-mmusic-sctp-sdp-20
o Informative reference to draft-ietf-rtcweb-data-protocol added. o Informative reference to draft-ietf-rtcweb-data-protocol added.
Changes from draft-ietf-mmusic-sctp-sdp-19 Changes from draft-ietf-mmusic-sctp-sdp-19
skipping to change at page 23, line 45 skipping to change at page 23, line 50
January 2012, <http://www.rfc-editor.org/info/rfc6347>. January 2012, <http://www.rfc-editor.org/info/rfc6347>.
[RFC6544] Rosenberg, J., Keranen, A., Lowekamp, B., and A. Roach, [RFC6544] Rosenberg, J., Keranen, A., Lowekamp, B., and A. Roach,
"TCP Candidates with Interactive Connectivity "TCP Candidates with Interactive Connectivity
Establishment (ICE)", RFC 6544, DOI 10.17487/RFC6544, Establishment (ICE)", RFC 6544, DOI 10.17487/RFC6544,
March 2012, <http://www.rfc-editor.org/info/rfc6544>. March 2012, <http://www.rfc-editor.org/info/rfc6544>.
[I-D.ietf-mmusic-4572-update] [I-D.ietf-mmusic-4572-update]
Lennox, J. and C. Holmberg, "Connection-Oriented Media Lennox, J. and C. Holmberg, "Connection-Oriented Media
Transport over TLS in SDP", draft-ietf-mmusic- Transport over TLS in SDP", draft-ietf-mmusic-
4572-update-11 (work in progress), January 2017. 4572-update-13 (work in progress), February 2017.
[I-D.ietf-mmusic-dtls-sdp] [I-D.ietf-mmusic-dtls-sdp]
Holmberg, C. and R. Shpount, "Using the SDP Offer/Answer Holmberg, C. and R. Shpount, "Using the SDP Offer/Answer
Mechanism for DTLS", draft-ietf-mmusic-dtls-sdp-16 (work Mechanism for DTLS", draft-ietf-mmusic-dtls-sdp-18 (work
in progress), January 2017. in progress), January 2017.
[I-D.ietf-tsvwg-sctp-dtls-encaps] [I-D.ietf-tsvwg-sctp-dtls-encaps]
Tuexen, M., Stewart, R., Jesup, R., and S. Loreto, "DTLS Tuexen, M., Stewart, R., Jesup, R., and S. Loreto, "DTLS
Encapsulation of SCTP Packets", draft-ietf-tsvwg-sctp- Encapsulation of SCTP Packets", draft-ietf-tsvwg-sctp-
dtls-encaps-09 (work in progress), January 2015. dtls-encaps-09 (work in progress), January 2015.
[I-D.ietf-mmusic-sdp-mux-attributes] [I-D.ietf-mmusic-sdp-mux-attributes]
Nandakumar, S., "A Framework for SDP Attributes when Nandakumar, S., "A Framework for SDP Attributes when
Multiplexing", draft-ietf-mmusic-sdp-mux-attributes-16 Multiplexing", draft-ietf-mmusic-sdp-mux-attributes-16
skipping to change at page 24, line 30 skipping to change at page 24, line 35
DOI 10.17487/RFC5245, April 2010, DOI 10.17487/RFC5245, April 2010,
<http://www.rfc-editor.org/info/rfc5245>. <http://www.rfc-editor.org/info/rfc5245>.
[I-D.ietf-rtcweb-data-channel] [I-D.ietf-rtcweb-data-channel]
Jesup, R., Loreto, S., and M. Tuexen, "WebRTC Data Jesup, R., Loreto, S., and M. Tuexen, "WebRTC Data
Channels", draft-ietf-rtcweb-data-channel-13 (work in Channels", draft-ietf-rtcweb-data-channel-13 (work in
progress), January 2015. progress), January 2015.
[I-D.ietf-mmusic-data-channel-sdpneg] [I-D.ietf-mmusic-data-channel-sdpneg]
Drage, K., Makaraju, M., Stoetzer-Bradler, J., Ejzak, R., Drage, K., Makaraju, M., Stoetzer-Bradler, J., Ejzak, R.,
and (. (Unknown), "SDP-based Data Channel Negotiation", and J. Marcon, "SDP-based Data Channel Negotiation",
draft-ietf-mmusic-data-channel-sdpneg-10 (work in draft-ietf-mmusic-data-channel-sdpneg-11 (work in
progress), September 2016. progress), January 2017.
[I-D.ietf-rtcweb-data-protocol] [I-D.ietf-rtcweb-data-protocol]
Jesup, R., Loreto, S., and M. Tuexen, "WebRTC Data Channel Jesup, R., Loreto, S., and M. Tuexen, "WebRTC Data Channel
Establishment Protocol", draft-ietf-rtcweb-data- Establishment Protocol", draft-ietf-rtcweb-data-
protocol-09 (work in progress), January 2015. protocol-09 (work in progress), January 2015.
Authors' Addresses Authors' Addresses
Christer Holmberg Christer Holmberg
Ericsson Ericsson
 End of changes. 13 change blocks. 
21 lines changed or deleted 26 lines changed or added

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