draft-ietf-mmusic-sctp-sdp-24.txt   draft-ietf-mmusic-sctp-sdp-25.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 10, 2017 TurboBridge Expires: September 14, 2017 TurboBridge
S. Loreto S. Loreto
G. Camarillo G. Camarillo
Ericsson Ericsson
March 9, 2017 March 13, 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-24 draft-ietf-mmusic-sctp-sdp-25
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 10, 2017. This Internet-Draft will expire on September 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 17, line 27 skipping to change at page 17, line 27
from one of those UDP candidates. The proto value MUST match the from one of those UDP candidates. The proto value MUST match the
transport protocol associated with the default candidate. If UDP transport protocol associated with the default candidate. If UDP
transport is used for the default candidate, then 'UDP/DTLS/SCTP' transport is used for the default candidate, then 'UDP/DTLS/SCTP'
proto value MUST be used. If TCP transport is used for the default proto value MUST be used. If TCP transport is used for the default
candidate, then 'TCP/DTLS/SCTP' proto value MUST be used. Note that candidate, then 'TCP/DTLS/SCTP' proto value MUST be used. Note that
under normal circumstances the proto value for offers and answers under normal circumstances the proto value for offers and answers
sent during ICE nomination SHOULD be 'UDP/DTLS/SCTP'. sent during ICE nomination SHOULD be 'UDP/DTLS/SCTP'.
When a subsequent SDP offer or answer is sent after ICE nomination is When a subsequent SDP offer or answer is sent after ICE nomination is
complete, and does not initiate ICE restart, it will contain only the complete, and does not initiate ICE restart, it will contain only the
currently nominated ICE candidate pair. In this case, the proto nominated ICE candidate pair. In this case, the proto value MUST
value MUST match the transport protocol associated with the currently match the transport protocol associated with the nominated ICE
negotiated ICE candidate pair. If UDP transport is used for the candidate pair. If UDP transport is used for the nominated pair,
currently nominated pair, then 'UDP/DTLS/SCTP' proto value MUST be then 'UDP/DTLS/SCTP' proto value MUST be used. If TCP transport is
used. If TCP transport is used for the currently negotiated pair, used for the nominated pair, then 'TCP/DTLS/SCTP' proto value MUST be
then 'TCP/DTLS/SCTP' proto value MUST be used. Please note that if used. Please note that if an endpoint switches between TCP-based and
an endpoint switches between TCP-based and UDP-based candidates UDP-based candidates during the nomination process the endpoint is
during the nomination process the endpoint is not required to send an not required to send an SDP offer for the sole purpose of keeping the
SDP offer for the sole purpose of keeping the proto value of the proto value of the associated m- line in sync.
associated m- line in sync.
NOTE: The text in the paragraph above only applies when the usage of NOTE: The text in the paragraph above only applies when the usage of
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:
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-24
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
o Changes based on Gen-ART review by Brian Carpenter. 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
 End of changes. 7 change blocks. 
14 lines changed or deleted 17 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/