draft-ietf-mmusic-sctp-sdp-25.txt   draft-ietf-mmusic-sctp-sdp-26.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: September 14, 2017 TurboBridge Expires: October 22, 2017 TurboBridge
S. Loreto S. Loreto
G. Camarillo G. Camarillo
Ericsson Ericsson
March 13, 2017 April 20, 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-25 draft-ietf-mmusic-sctp-sdp-26
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 September 14, 2017. This Internet-Draft will expire on October 22, 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 3, line 34 skipping to change at page 3, line 34
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 25 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 25
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 [RFC0793] streams. Connection-Oriented Media and establishing TCP [RFC0793] streams. Connection-Oriented Media
Transport over the Transport Layer Security (TLS) Protocol in SDP Transport over the Transport Layer Security (TLS) Protocol in SDP
[I-D.ietf-mmusic-4572-update] extends RFC4145 [RFC4145] for [RFC8122] extends RFC4145 [RFC4145] for describing TCP-based media
describing TCP-based media streams that are protected using TLS. streams that are protected using TLS.
The Stream Control Transmission Protocol (SCTP) [RFC4960] is a The Stream Control Transmission Protocol (SCTP) [RFC4960] is a
reliable transport protocol used to transport data between two reliable transport protocol used to transport data between two
endpoints using SCTP associations. endpoints using SCTP associations.
[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
skipping to change at page 11, line 48 skipping to change at page 11, line 48
ports MUST be used by both endpoints. ports MUST be used by both endpoints.
NOTE: Closing and establishing a new SCTP association using the SDP NOTE: Closing and establishing a new SCTP association using the SDP
'sctp-port' attribute will not affect the state of the underlying 'sctp-port' attribute will not affect the state of the underlying
DTLS association. DTLS association.
9.4. DTLS Association (UDP/DTLS/SCTP And TCP/DTLS/SCTP) 9.4. DTLS Association (UDP/DTLS/SCTP And TCP/DTLS/SCTP)
A DTLS association is managed according to the procedures in A DTLS association is managed according to the procedures in
[I-D.ietf-mmusic-dtls-sdp]. Hence, the SDP 'setup' attribute is used [I-D.ietf-mmusic-dtls-sdp]. Hence, the SDP 'setup' attribute is used
to negotiate the (D)TLS roles ('client' and 'server') to negotiate the (D)TLS roles ('client' and 'server') [RFC8122].
[I-D.ietf-mmusic-4572-update].
NOTE: The SDP 'setup' attribute is used to negotiate both the DTLS NOTE: The SDP 'setup' attribute is used to negotiate both the DTLS
roles and the TCP roles (Section 9.5). roles and the TCP roles (Section 9.5).
NOTE: As described in [RFC5245], if the Interactive Connectivity NOTE: As described in [RFC5245], if the Interactive Connectivity
Establishment (ICE) mechanism [RFC5245] is used, all ICE candidates Establishment (ICE) mechanism [RFC5245] is used, all ICE candidates
associated with a DTLS association are considered part of the same associated with a DTLS association are considered part of the same
DTLS association. Thus, a switch from one candidate pair to another DTLS association. Thus, a switch from one candidate pair to another
candidate pair will not trigger the establishment of a new DTLS candidate pair will not trigger the establishment of a new DTLS
association. association.
skipping to change at page 12, line 41 skipping to change at page 12, line 41
10.1. General 10.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-over-DTLS association. Unless negotiating and establishing an SCTP-over-DTLS association. Unless
explicitly stated, the procedures apply to both the 'UDP/DTLS/SCTP' explicitly stated, the procedures apply to both the 'UDP/DTLS/SCTP'
and 'TCP/DTLS/SCTP' m- line proto values. and 'TCP/DTLS/SCTP' m- line proto values.
Each endpoint MUST associate one or more certificate fingerprints, Each endpoint MUST associate one or more certificate fingerprints,
using the SDP 'fingerprint' attribute with the m- line, following the using the SDP 'fingerprint' attribute with the m- line, following the
procedures in [I-D.ietf-mmusic-4572-update]. procedures in [RFC8122].
The authentication certificates are interpreted and validated as The authentication certificates are interpreted and validated as
defined in [I-D.ietf-mmusic-4572-update]. Self-signed certificates defined in [RFC8122]. Self-signed certificates can be used securely,
can be used securely, provided that the integrity of the SDP provided that the integrity of the SDP description is assured as
description is assured as defined in [I-D.ietf-mmusic-4572-update]. defined in [RFC8122].
Each endpoint MUST associate an SDP 'dtls-id' attribute with the m- Each endpoint MUST associate an SDP 'tls-id' attribute with the m-
line, following the procedures in [I-D.ietf-mmusic-dtls-sdp]. line, following the procedures in [I-D.ietf-mmusic-dtls-sdp].
10.2. Generating the Initial SDP Offer 10.2. Generating the Initial SDP Offer
When the offerer creates an initial offer, the offerer: When the offerer creates an initial offer, the offerer:
o MUST associate an SDP setup attribute with the m- line; o MUST associate an SDP setup attribute with the m- line;
o MUST associate an SDP 'sctp-port' attribute with the m- line; o MUST associate an SDP 'sctp-port' attribute with the m- line;
skipping to change at page 18, line 8 skipping to change at page 18, line 8
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 IP6 2001:DB8::A8FD c=IN IP6 2001:DB8::A8FD
a=dtls-id:abc3dl a=tls-id:abc3de65cddef001be82
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 IP6 2001:DB8::001D c=IN IP6 2001:DB8::001D
a=dtls-id:ggr4rd a=tls-id:dbc8de77cddef001be90
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
[RFC4566] defines general SDP security considerations, while [RFC4566] defines general SDP security considerations, while
[RFC3264], [RFC4145] and [I-D.ietf-mmusic-4572-update] define [RFC3264], [RFC4145] and [RFC8122] define security considerations
security considerations when using the SDP offer/answer mechanism to when using the SDP offer/answer mechanism to negotiate media streams.
negotiate media streams.
[RFC4960] defines general SCTP security considerations and [RFC4960] defines general SCTP security considerations and
[I-D.ietf-tsvwg-sctp-dtls-encaps] defines security considerations [I-D.ietf-tsvwg-sctp-dtls-encaps] defines security considerations
when using SCTP on top of DTLS. when using SCTP on top of DTLS.
This specification does not introduce new security considerations in This specification does not introduce new security considerations in
addition to those defined in the specifications listed above. addition to those defined in the specifications listed above.
15. IANA Considerations 15. IANA Considerations
skipping to change at page 20, line 50 skipping to change at page 20, line 50
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. Brian Carpenter provided comments as part of his AD review. Brian Carpenter
performed the Gen-ART review. 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-25
o SDP 'dtls-id' attribute re-named to 'tls-id'.
Changes from draft-ietf-mmusic-sctp-sdp-24 Changes from draft-ietf-mmusic-sctp-sdp-24
o Minor editorial fix by Roman. o Minor editorial fix by Roman.
Changes from draft-ietf-mmusic-sctp-sdp-23 Changes from draft-ietf-mmusic-sctp-sdp-23
o Changes based on IESG review. o Changes based on IESG review.
o - Proto value clarifications. o - Proto value clarifications.
Changes from draft-ietf-mmusic-sctp-sdp-22 Changes from draft-ietf-mmusic-sctp-sdp-22
skipping to change at page 24, line 42 skipping to change at page 24, line 47
[RFC6347] Rescorla, E. and N. Modadugu, "Datagram Transport Layer [RFC6347] Rescorla, E. and N. Modadugu, "Datagram Transport Layer
Security Version 1.2", RFC 6347, DOI 10.17487/RFC6347, Security Version 1.2", RFC 6347, DOI 10.17487/RFC6347,
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] [RFC8122] Lennox, J. and C. Holmberg, "Connection-Oriented Media
Lennox, J. and C. Holmberg, "Connection-Oriented Media Transport over the Transport Layer Security (TLS) Protocol
Transport over TLS in SDP", draft-ietf-mmusic- in the Session Description Protocol (SDP)", RFC 8122,
4572-update-13 (work in progress), February 2017. DOI 10.17487/RFC8122, March 2017,
<http://www.rfc-editor.org/info/rfc8122>.
[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-18 (work Mechanism for DTLS", draft-ietf-mmusic-dtls-sdp-24 (work
in progress), January 2017. in progress), April 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
(work in progress), December 2016. (work in progress), December 2016.
skipping to change at page 25, line 31 skipping to change at page 25, line 36
<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 J. Marcon, "SDP-based Data Channel Negotiation", and J. Marcon, "SDP-based Data Channel Negotiation",
draft-ietf-mmusic-data-channel-sdpneg-11 (work in draft-ietf-mmusic-data-channel-sdpneg-12 (work in
progress), January 2017. progress), March 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. 17 change blocks. 
26 lines changed or deleted 29 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/