draft-ietf-mmusic-data-channel-sdpneg-12.txt   draft-ietf-mmusic-data-channel-sdpneg-13.txt 
MMUSIC K. Drage, Ed. MMUSIC K. Drage, Ed.
Internet-Draft M. Makaraju Internet-Draft Unaffiliated
Intended status: Standards Track Nokia Intended status: Standards Track M. Makaraju
Expires: September 19, 2017 J. Stoetzer-Bradler Expires: March 14, 2018 Nokia
J. Stoetzer-Bradler
R. Ejzak R. Ejzak
J. Marcon J. Marcon
Unaffiliated Unaffiliated
March 27, 2017 September 10, 2017
SDP-based Data Channel Negotiation SDP-based Data Channel Negotiation
draft-ietf-mmusic-data-channel-sdpneg-12 draft-ietf-mmusic-data-channel-sdpneg-13
Abstract Abstract
The Real-Time Communication in WEB-browsers (RTCWeb) working group is The Real-Time Communication in WEB-browsers (RTCWeb) working group is
charged to provide protocols to support direct interactive rich charged to provide protocols to support direct interactive rich
communications using audio, video, and data between two peers' web- communications using audio, video, and data between two peers' web-
browsers. For the support of data communication, the RTCWeb working browsers. For the support of data communication, the RTCWeb working
group has in particular defined the concept of bi-directional data group has in particular defined the concept of bi-directional data
channels over SCTP (Stream Control Transmission Protocol), where each channels over SCTP (Stream Control Transmission Protocol), where each
data channel might be used to transport other protocols, called data channel might be used to transport other protocols, called
skipping to change at page 1, line 44 skipping to change at page 1, line 44
channels are used. channels are used.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 https://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 19, 2017. This Internet-Draft will expire on March 14, 2018.
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 (https://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
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
skipping to change at page 3, line 11 skipping to change at page 3, line 11
7. Security Considerations . . . . . . . . . . . . . . . . . . . 20 7. Security Considerations . . . . . . . . . . . . . . . . . . . 20
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20
8.1. Subprotocol Identifiers . . . . . . . . . . . . . . . . . 21 8.1. Subprotocol Identifiers . . . . . . . . . . . . . . . . . 21
8.2. New SDP Attributes . . . . . . . . . . . . . . . . . . . 21 8.2. New SDP Attributes . . . . . . . . . . . . . . . . . . . 21
8.2.1. dcmap . . . . . . . . . . . . . . . . . . . . . . . . 21 8.2.1. dcmap . . . . . . . . . . . . . . . . . . . . . . . . 21
8.2.2. dcsa . . . . . . . . . . . . . . . . . . . . . . . . 22 8.2.2. dcsa . . . . . . . . . . . . . . . . . . . . . . . . 22
8.3. New Usage Level . . . . . . . . . . . . . . . . . . . . . 22 8.3. New Usage Level . . . . . . . . . . . . . . . . . . . . . 22
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 23 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 23
10. CHANGE LOG . . . . . . . . . . . . . . . . . . . . . . . . . 23 10. CHANGE LOG . . . . . . . . . . . . . . . . . . . . . . . . . 23
10.1. Changes against 'draft-ietf-mmusic-data-channel- 10.1. Changes against 'draft-ietf-mmusic-data-channel-
sdpneg-11' . . . . . . . . . . . . . . . . . . . . . . . 23 sdpneg-12' . . . . . . . . . . . . . . . . . . . . . . . 23
10.2. Changes against 'draft-ietf-mmusic-data-channel- 10.2. Changes against 'draft-ietf-mmusic-data-channel-
sdpneg-10' . . . . . . . . . . . . . . . . . . . . . . . 23 sdpneg-11' . . . . . . . . . . . . . . . . . . . . . . . 23
10.3. Changes against 'draft-ietf-mmusic-data-channel- 10.3. Changes against 'draft-ietf-mmusic-data-channel-
sdpneg-09' . . . . . . . . . . . . . . . . . . . . . . . 23 sdpneg-10' . . . . . . . . . . . . . . . . . . . . . . . 23
10.4. Changes against 'draft-ietf-mmusic-data-channel- 10.4. Changes against 'draft-ietf-mmusic-data-channel-
sdpneg-08' . . . . . . . . . . . . . . . . . . . . . . . 24 sdpneg-09' . . . . . . . . . . . . . . . . . . . . . . . 23
10.5. Changes against 'draft-ietf-mmusic-data-channel- 10.5. Changes against 'draft-ietf-mmusic-data-channel-
sdpneg-07' . . . . . . . . . . . . . . . . . . . . . . . 25 sdpneg-08' . . . . . . . . . . . . . . . . . . . . . . . 24
10.6. Changes against 'draft-ietf-mmusic-data-channel- 10.6. Changes against 'draft-ietf-mmusic-data-channel-
sdpneg-06' . . . . . . . . . . . . . . . . . . . . . . . 25 sdpneg-07' . . . . . . . . . . . . . . . . . . . . . . . 25
10.7. Changes against 'draft-ietf-mmusic-data-channel- 10.7. Changes against 'draft-ietf-mmusic-data-channel-
sdpneg-05' . . . . . . . . . . . . . . . . . . . . . . . 25 sdpneg-06' . . . . . . . . . . . . . . . . . . . . . . . 25
10.8. Changes against 'draft-ietf-mmusic-data-channel- 10.8. Changes against 'draft-ietf-mmusic-data-channel-
sdpneg-04' . . . . . . . . . . . . . . . . . . . . . . . 26 sdpneg-05' . . . . . . . . . . . . . . . . . . . . . . . 25
10.9. Changes against 'draft-ietf-mmusic-data-channel- 10.9. Changes against 'draft-ietf-mmusic-data-channel-
sdpneg-03' . . . . . . . . . . . . . . . . . . . . . . . 27 sdpneg-04' . . . . . . . . . . . . . . . . . . . . . . . 26
10.10. Changes against 'draft-ietf-mmusic-data-channel- 10.10. Changes against 'draft-ietf-mmusic-data-channel-
sdpneg-02' . . . . . . . . . . . . . . . . . . . . . . . 28 sdpneg-03' . . . . . . . . . . . . . . . . . . . . . . . 27
10.11. Changes against 'draft-ietf-mmusic-data-channel- 10.11. Changes against 'draft-ietf-mmusic-data-channel-
sdpneg-01' . . . . . . . . . . . . . . . . . . . . . . . 29 sdpneg-02' . . . . . . . . . . . . . . . . . . . . . . . 28
10.12. Changes against 'draft-ietf-mmusic-data-channel- 10.12. Changes against 'draft-ietf-mmusic-data-channel-
sdpneg-01' . . . . . . . . . . . . . . . . . . . . . . . 29
10.13. Changes against 'draft-ietf-mmusic-data-channel-
sdpneg-00' . . . . . . . . . . . . . . . . . . . . . . . 31 sdpneg-00' . . . . . . . . . . . . . . . . . . . . . . . 31
10.13. Changes against 'draft-ejzak-mmusic-data-channel- 10.14. Changes against 'draft-ejzak-mmusic-data-channel-
sdpneg-02' . . . . . . . . . . . . . . . . . . . . . . . 34 sdpneg-02' . . . . . . . . . . . . . . . . . . . . . . . 34
10.14. Changes against '-01' . . . . . . . . . . . . . . . . . 35 10.15. Changes against '-01' . . . . . . . . . . . . . . . . . 35
10.15. Changes against '-00' . . . . . . . . . . . . . . . . . 35 10.16. Changes against '-00' . . . . . . . . . . . . . . . . . 35
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 35 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 35
11.1. Normative References . . . . . . . . . . . . . . . . . . 35 11.1. Normative References . . . . . . . . . . . . . . . . . . 36
11.2. Informative References . . . . . . . . . . . . . . . . . 36 11.2. Informative References . . . . . . . . . . . . . . . . . 37
Appendix A. Generic Data Channel Negotiation Aspects When Not Appendix A. Generic Data Channel Negotiation Aspects When Not
Using DCEP . . . . . . . . . . . . . . . . . . . . . 37 Using DCEP . . . . . . . . . . . . . . . . . . . . . 37
A.1. Stream Identifier Numbering . . . . . . . . . . . . . . . 38 A.1. Stream Identifier Numbering . . . . . . . . . . . . . . . 38
A.2. Generic Data Channel Negotiation Not Using DCEP . . . . . 38 A.2. Generic Data Channel Negotiation Not Using DCEP . . . . . 39
A.2.1. Overview . . . . . . . . . . . . . . . . . . . . . . 38 A.2.1. Overview . . . . . . . . . . . . . . . . . . . . . . 39
A.2.2. Opening a Data Channel . . . . . . . . . . . . . . . 39 A.2.2. Opening a Data Channel . . . . . . . . . . . . . . . 39
A.2.3. Closing a Data Channel . . . . . . . . . . . . . . . 40 A.2.3. Closing a Data Channel . . . . . . . . . . . . . . . 40
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 40 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 40
1. Introduction 1. Introduction
The RTCWeb working group has defined the concept of bi-directional The RTCWeb working group has defined the concept of bi-directional
data channels running on top of the Stream Control Transmission data channels running on top of the Stream Control Transmission
Protocol (SCTP). RTCWeb allows applications to use data channels. Protocol (SCTP). RTCWeb allows applications to use data channels.
RTCWeb defines an in-band Data Channel Establishment Protocol (DCEP), RTCWeb defines an in-band Data Channel Establishment Protocol (DCEP),
skipping to change at page 23, line 25 skipping to change at page 23, line 25
The authors wish to acknowledge the borrowing of ideas from other The authors wish to acknowledge the borrowing of ideas from other
internet drafts by Salvatore Loreto, Gonzalo Camarillo, Peter Dunkley internet drafts by Salvatore Loreto, Gonzalo Camarillo, Peter Dunkley
and Gavin Llewellyn, and to thank Flemming Andreasen, Roni Even, and Gavin Llewellyn, and to thank Flemming Andreasen, Roni Even,
Christian Groves, Gunnar Hellstrom, Christer Holmberg, Paul Kyzivat, Christian Groves, Gunnar Hellstrom, Christer Holmberg, Paul Kyzivat,
Jonathan Lennox, Uwe Rauschenbach and Roman Shpount for their Jonathan Lennox, Uwe Rauschenbach and Roman Shpount for their
invaluable comments. invaluable comments.
10. CHANGE LOG 10. CHANGE LOG
10.1. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-11' 10.1. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-12'
o Modification of Keith's address information.
10.2. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-11'
o dcmap-stream-id syntax change to limit size to 5 digits. o dcmap-stream-id syntax change to limit size to 5 digits.
o Add missing 'x' prefix to quoted-visible syntax. o Add missing 'x' prefix to quoted-visible syntax.
o Align SDP offerer and answerer handling when both max-retr and o Align SDP offerer and answerer handling when both max-retr and
max-time are present. max-time are present.
o Use of TEST-NET-1 ip addresses in examples. o Use of TEST-NET-1 ip addresses in examples.
o Add missing a=dtls-id in one example. o Add missing a=dtls-id in one example.
10.2. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-10' 10.3. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-10'
o Removal of the "a=connection" attribute lines from all SDP o Removal of the "a=connection" attribute lines from all SDP
examples. examples.
10.3. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-09' 10.4. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-09'
o In the introduction: o In the introduction:
* Replacement of the sentence "The RTCWeb working group has * Replacement of the sentence "The RTCWeb working group has
defined the concept of bi-directional data channels running on defined the concept of bi-directional data channels running on
top of SCTP/DTLS (SCTP over the Datagram Transport Layer top of SCTP/DTLS (SCTP over the Datagram Transport Layer
Security protocol)" with "The RTCWeb working group has defined Security protocol)" with "The RTCWeb working group has defined
the concept of bi-directional data channels running on top of the concept of bi-directional data channels running on top of
the Stream Control Transmission Protocol (SCTP)". the Stream Control Transmission Protocol (SCTP)".
skipping to change at page 24, line 37 skipping to change at page 24, line 42
o In the text after the second SDP answer in section Section 6 o In the text after the second SDP answer in section Section 6
replacement of "... (after SCTP/DTLS association is setup)" with replacement of "... (after SCTP/DTLS association is setup)" with
"... (after the SCTP association is set up)". "... (after the SCTP association is set up)".
o Addition of [I-D.ietf-mmusic-dtls-sdp] to the list of informative o Addition of [I-D.ietf-mmusic-dtls-sdp] to the list of informative
references. references.
o Addition of "a=dtls-id" attribute lines to the SDP offer/answer o Addition of "a=dtls-id" attribute lines to the SDP offer/answer
examples in Section 6. examples in Section 6.
10.4. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-08' 10.5. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-08'
o Addition of definition of "data channel subprotocol" to Section 3 o Addition of definition of "data channel subprotocol" to Section 3
as proposed on the MMUSIC list, https://www.ietf.org/mail- as proposed on the MMUSIC list, https://www.ietf.org/mail-
archive/web/mmusic/current/msg15827.html. archive/web/mmusic/current/msg15827.html.
o Addition of [I-D.ietf-mmusic-rfc4566bis] to list of normative o Addition of [I-D.ietf-mmusic-rfc4566bis] to list of normative
references. references.
o Updates of tables in Section 8.2.1 and Section 8.2.2 as per o Updates of tables in Section 8.2.1 and Section 8.2.2 as per
section 8.2.4 of [I-D.ietf-mmusic-rfc4566bis]. section 8.2.4 of [I-D.ietf-mmusic-rfc4566bis].
o Addition of new Section 8.3. o Addition of new Section 8.3.
10.5. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-07' 10.6. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-07'
o Addition of two new paragraphs to Section 5.1.2.1 regarding o Addition of two new paragraphs to Section 5.1.2.1 regarding
subprotocol attribute relationship with transport protocol. subprotocol attribute relationship with transport protocol.
o Addition of a note to Section 8.1 regarding subprotocols o Addition of a note to Section 8.1 regarding subprotocols
simultaneously defined for data channel and Websocket usage. simultaneously defined for data channel and Websocket usage.
o Addition of two further SDP offer/answer considerations to o Addition of two further SDP offer/answer considerations to
Section 5.2.5 regarding unknown subprotocol attributes and known Section 5.2.5 regarding unknown subprotocol attributes and known
subprotocol attributes with unknown data channel transport related subprotocol attributes with unknown data channel transport related
semantic. semantic.
10.6. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-06' 10.7. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-06'
o Changes addressing Christian Groves's WGLC review comments raised o Changes addressing Christian Groves's WGLC review comments raised
in http://www.ietf.org/mail-archive/web/mmusic/current/ in http://www.ietf.org/mail-archive/web/mmusic/current/
msg15357.html and http://www.ietf.org/mail- msg15357.html and http://www.ietf.org/mail-
archive/web/mmusic/current/msg15359.html. archive/web/mmusic/current/msg15359.html.
10.7. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-05' 10.8. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-05'
o In IANA registration Section 8.2.1 and Section 8.2.2 replacement o In IANA registration Section 8.2.1 and Section 8.2.2 replacement
of contact name and e-mail address with "MMUSIC Chairs" and of contact name and e-mail address with "MMUSIC Chairs" and
"mmusic-chairs@ietf.org". "mmusic-chairs@ietf.org".
o In Section 5.1.2.1 replacement of "Thus in the example above, the o In Section 5.1.2.1 replacement of "Thus in the example above, the
original attribute line "a=accept- types:text/plain" is original attribute line "a=accept- types:text/plain" is
represented by the attribute line "a=dcsa:2 accept-types:text/ represented by the attribute line "a=dcsa:2 accept-types:text/
plain", which specifies that this instance of MSRP being plain", which specifies that this instance of MSRP being
transported on the SCTP association using the data channel with transported on the SCTP association using the data channel with
skipping to change at page 26, line 14 skipping to change at page 26, line 16
o Move of the last but one paragraph of Section 5.1.2.1 starting o Move of the last but one paragraph of Section 5.1.2.1 starting
with "The same syntax applies to ..." right in front of the formal with "The same syntax applies to ..." right in front of the formal
syntax definition of the "dcsa" attribute. syntax definition of the "dcsa" attribute.
o Modifications of the text in Section 5.1.1.2 and Section 5.1.2.2 o Modifications of the text in Section 5.1.1.2 and Section 5.1.2.2
in order not to explicitly restrict usage of the "a=dcmap:" and in order not to explicitly restrict usage of the "a=dcmap:" and
"a=dcsa:" attributes to "m" lines with proto values "UDP/DTLS/ "a=dcsa:" attributes to "m" lines with proto values "UDP/DTLS/
SCTP" or "TCP/DTLS/SCTP". SCTP" or "TCP/DTLS/SCTP".
10.8. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-04' 10.9. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-04'
o In Section 5.1.1.5 the first (and only) paragraph was "The o In Section 5.1.1.5 the first (and only) paragraph was "The
'subprotocol' parameter indicates which protocol the client 'subprotocol' parameter indicates which protocol the client
expects to exchange via the channel. 'Subprotocol' is an optional expects to exchange via the channel. 'Subprotocol' is an optional
parameter. If the 'subprotocol' parameter is not present, then parameter. If the 'subprotocol' parameter is not present, then
its value defaults to the empty string." Replacement of this its value defaults to the empty string." Replacement of this
paragraph with following two paragraphs: paragraph with following two paragraphs:
* The 'subprotocol' parameter indicates which protocol the client * The 'subprotocol' parameter indicates which protocol the client
expects to exchange via the channel. This parameter maps to expects to exchange via the channel. This parameter maps to
skipping to change at page 27, line 8 skipping to change at page 27, line 10
o Addition of new Section 5.1.1.2 describing the mux category of the o Addition of new Section 5.1.1.2 describing the mux category of the
dcmap SDP attribute. This section and the new "a=dcsa:" attribute dcmap SDP attribute. This section and the new "a=dcsa:" attribute
related mux category section are similar to the "Mux Category" related mux category section are similar to the "Mux Category"
sections of the "a=sctp-port:" and "a=max-message-size:" sections of the "a=sctp-port:" and "a=max-message-size:"
attributes in [I-D.ietf-mmusic-sctp-sdp]. attributes in [I-D.ietf-mmusic-sctp-sdp].
o Addition of new Section 5.1.2.2 describing the mux category of the o Addition of new Section 5.1.2.2 describing the mux category of the
dcsa SDP attribute. dcsa SDP attribute.
10.9. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-03' 10.10. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-03'
o In Section 1 replacement of "RTCWeb leaves it open for other o In Section 1 replacement of "RTCWeb leaves it open for other
applications to use data channels and its in-band DCEP or out-of- applications to use data channels and its in-band DCEP or out-of-
band non-DCEP protocols for creating them" with "... to use data band non-DCEP protocols for creating them" with "... to use data
channels and its in-band DCEP or other in-band or out-of-band channels and its in-band DCEP or other in-band or out-of-band
protocols for creating them". Additionally replacement of "In protocols for creating them". Additionally replacement of "In
particular, the SDP offer generated by the application includes no particular, the SDP offer generated by the application includes no
channel-specific information" with "... generated by the RTCweb channel-specific information" with "... generated by the RTCweb
data channel stack includes no channel-specific information". data channel stack includes no channel-specific information".
skipping to change at page 28, line 17 skipping to change at page 28, line 20
o In Section 5.2.1 replacement of "However, an SDP offer/answer o In Section 5.2.1 replacement of "However, an SDP offer/answer
exchange MUST NOT be initiated if the associated SCTP stream is exchange MUST NOT be initiated if the associated SCTP stream is
already negotiated via DCEP" with "However, an SCTP stream MUST already negotiated via DCEP" with "However, an SCTP stream MUST
NOT be referenced in a dcmap or dcsa attribute of an SDP offer/ NOT be referenced in a dcmap or dcsa attribute of an SDP offer/
answer exchange if the associated SCTP stream has already been answer exchange if the associated SCTP stream has already been
negotiated via DCEP". negotiated via DCEP".
o In the examples in Section 6 addition of the previously missing o In the examples in Section 6 addition of the previously missing
colons to the "a=sctp-port" attribute lines. colons to the "a=sctp-port" attribute lines.
10.10. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-02' 10.11. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-02'
o Move of reference [I-D.ietf-rtcweb-jsep] from the list of o Move of reference [I-D.ietf-rtcweb-jsep] from the list of
normative references to the list of informative references. normative references to the list of informative references.
o Addition of [IANA-SDP-Parameters] to the list of informative o Addition of [IANA-SDP-Parameters] to the list of informative
references and addition of following two sentences to the first references and addition of following two sentences to the first
paragraph after the ABNF definition: "Note however that not all paragraph after the ABNF definition: "Note however that not all
SDP attributes are suitable as "a=dcsa:" parameter. SDP attributes are suitable as "a=dcsa:" parameter.
[IANA-SDP-Parameters] contains the lists of IANA registered [IANA-SDP-Parameters] contains the lists of IANA registered
session and media level or media level only SDP attributes." session and media level or media level only SDP attributes."
skipping to change at page 29, line 19 skipping to change at page 29, line 21
a=dcmap". a=dcmap".
o Move of reference [WebRtcAPI] from list of normative references to o Move of reference [WebRtcAPI] from list of normative references to
list of informative references. list of informative references.
o Removal of almost all text parts, which discussed JavaScript or o Removal of almost all text parts, which discussed JavaScript or
other API specific aspects. Such API specific aspects were mainly other API specific aspects. Such API specific aspects were mainly
discussed in sub-sections of Section 5 and Section 5 of draft- discussed in sub-sections of Section 5 and Section 5 of draft-
ietf-mmusic-data-channel-sdpneg-02. ietf-mmusic-data-channel-sdpneg-02.
10.11. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-01' 10.12. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-01'
o New Section 4 regarding applicability to SDP offer/answer only. o New Section 4 regarding applicability to SDP offer/answer only.
o Addition of new Section 8.1 "Subprotocol identifiers" as o Addition of new Section 8.1 "Subprotocol identifiers" as
subsection of the "IANA Considerations" related Section 8. Also subsection of the "IANA Considerations" related Section 8. Also
removal of the temporary note "To be completed. As [I-D.ietf- removal of the temporary note "To be completed. As [I-D.ietf-
rtcweb-data-protocol] this document should refer to IANA's rtcweb-data-protocol] this document should refer to IANA's
WebSocket Subprotocol Name Registry defined in [RFC6455]." WebSocket Subprotocol Name Registry defined in [RFC6455]."
o In Section 5.2.2: o In Section 5.2.2:
skipping to change at page 31, line 26 skipping to change at page 31, line 29
* In the last but one paragraph replacement of "must" with "The * In the last but one paragraph replacement of "must" with "The
application MUST also close...". application MUST also close...".
o In Section 5.1.2 addition of following note after the formal o In Section 5.1.2 addition of following note after the formal
definition of the 'a=dcsa' attribute: "Note that the above definition of the 'a=dcsa' attribute: "Note that the above
reference to RFC 4566 defines were the attribute definition can be reference to RFC 4566 defines were the attribute definition can be
found; it does not provide any limitation on support of attributes found; it does not provide any limitation on support of attributes
defined in other documents in accordance with this attribute defined in other documents in accordance with this attribute
definition." definition."
10.12. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-00' 10.13. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-00'
o In Section 3 "WebRTC data channel" was defined as "A bidirectional o In Section 3 "WebRTC data channel" was defined as "A bidirectional
channel consisting of paired SCTP outbound and inbound streams." channel consisting of paired SCTP outbound and inbound streams."
Replacement of this definition with "Data channel: A WebRTC data Replacement of this definition with "Data channel: A WebRTC data
channel as specified in [I-D.ietf-rtcweb-data-channel]", and channel as specified in [I-D.ietf-rtcweb-data-channel]", and
consistent usage of "data channel" in the remainder of the consistent usage of "data channel" in the remainder of the
document including the document's headline." document including the document's headline."
o In Section 5 removal of following note: 'OPEN ISSUE: The syntax in o In Section 5 removal of following note: 'OPEN ISSUE: The syntax in
[I-D.ietf-mmusic-sctp-sdp] may change as that document progresses. [I-D.ietf-mmusic-sctp-sdp] may change as that document progresses.
skipping to change at page 34, line 11 skipping to change at page 34, line 14
to handle cases where a successful SDP answer is not received, in to handle cases where a successful SDP answer is not received, in
which case the state of the session SHOULD be kept per the last which case the state of the session SHOULD be kept per the last
successful SDP offer/answer." successful SDP offer/answer."
o Although dedicated to "a=dcmap" and "a=dcsa" SDP syntax aspects o Although dedicated to "a=dcmap" and "a=dcsa" SDP syntax aspects
Section 5.1.1 contained already procedural descriptions related to Section 5.1.1 contained already procedural descriptions related to
data channel reliability negotiation. Creation of new data channel reliability negotiation. Creation of new
Section 5.2.2 and moval of reliability negotiation related text to Section 5.2.2 and moval of reliability negotiation related text to
this new section. this new section.
10.13. Changes against 'draft-ejzak-mmusic-data-channel-sdpneg-02' 10.14. Changes against 'draft-ejzak-mmusic-data-channel-sdpneg-02'
o Removal of note "[ACTION ITEM]" from section "subprotocol o Removal of note "[ACTION ITEM]" from section "subprotocol
parameter". As [I-D.ietf-rtcweb-data-protocol] this document parameter". As [I-D.ietf-rtcweb-data-protocol] this document
should refer to IANA's WebSocket Subprotocol Name Registry defined should refer to IANA's WebSocket Subprotocol Name Registry defined
in [RFC6455]. in [RFC6455].
o In whole document, replacement of "unreliable" with "partially o In whole document, replacement of "unreliable" with "partially
reliable", which is used in [I-D.ietf-rtcweb-data-channel] and in reliable", which is used in [I-D.ietf-rtcweb-data-channel] and in
[I-D.ietf-rtcweb-data-protocol] in most places. [I-D.ietf-rtcweb-data-protocol] in most places.
skipping to change at page 35, line 14 skipping to change at page 35, line 16
o In the "Examples" section, in the first two SDP offer examples in o In the "Examples" section, in the first two SDP offer examples in
the a=dcmap attribute lines 'label="BGCP"' was replaced with the a=dcmap attribute lines 'label="BGCP"' was replaced with
'label="BFCP"'. 'label="BFCP"'.
o In all examples, the "m" line proto value "DTLS/SCTP" was replaced o In all examples, the "m" line proto value "DTLS/SCTP" was replaced
with "UDP/DTLS/SCTP" and the "a=fmtp" attribute lines were with "UDP/DTLS/SCTP" and the "a=fmtp" attribute lines were
replaced with "a=max-message-size" attribute lines, as per draft- replaced with "a=max-message-size" attribute lines, as per draft-
ietf-mmusic-sctp-sdp-12. ietf-mmusic-sctp-sdp-12.
10.14. Changes against '-01' 10.15. Changes against '-01'
o Formal syntax for dcmap and dcsa attribute lines. o Formal syntax for dcmap and dcsa attribute lines.
o Making subprotocol as an optional parameter in dcmap. o Making subprotocol as an optional parameter in dcmap.
o Specifying disallowed parameter combinations for max-time and max- o Specifying disallowed parameter combinations for max-time and max-
retr. retr.
o Clarifications on WebRTC data channel close procedures. o Clarifications on WebRTC data channel close procedures.
10.15. Changes against '-00' 10.16. Changes against '-00'
o Revisions to identify difference between internal and external o Revisions to identify difference between internal and external
negotiation and their usage. negotiation and their usage.
o Introduction of more generic terminology, e.g. "application" o Introduction of more generic terminology, e.g. "application"
instead of "browser". instead of "browser".
o Clarification of how "max-retr and max-time affect the usage of o Clarification of how "max-retr and max-time affect the usage of
unreliable and reliable WebRTC data channels. unreliable and reliable WebRTC data channels.
skipping to change at page 35, line 45 skipping to change at page 36, line 4
o Updates of examples to take into account the SDP syntax changes o Updates of examples to take into account the SDP syntax changes
introduced with draft-ietf-mmusic-sctp-sdp-07. introduced with draft-ietf-mmusic-sctp-sdp-07.
o Removal of the SCTP port number from the a=dcmap and a=dcsa o Removal of the SCTP port number from the a=dcmap and a=dcsa
attributes as this is now contained in the a=sctp-port attribute, attributes as this is now contained in the a=sctp-port attribute,
and as draft-ietf-mmusic-sctp-sdp-07 supports only one SCTP and as draft-ietf-mmusic-sctp-sdp-07 supports only one SCTP
association on top of the DTLS connection. association on top of the DTLS connection.
11. References 11. References
11.1. Normative References 11.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
Description Protocol", RFC 4566, DOI 10.17487/RFC4566, Description Protocol", RFC 4566, DOI 10.17487/RFC4566,
July 2006, <http://www.rfc-editor.org/info/rfc4566>. July 2006, <https://www.rfc-editor.org/info/rfc4566>.
[I-D.ietf-mmusic-rfc4566bis] [I-D.ietf-mmusic-rfc4566bis]
Handley, M., Jacobson, V., Perkins, C., and A. Begen, Handley, M., Jacobson, V., Perkins, C., and A. Begen,
"SDP: Session Description Protocol", draft-ietf-mmusic- "SDP: Session Description Protocol", draft-ietf-mmusic-
rfc4566bis-17 (work in progress), June 2016. rfc4566bis-17 (work in progress), June 2016.
[RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model [RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model
with Session Description Protocol (SDP)", RFC 3264, with Session Description Protocol (SDP)", RFC 3264,
DOI 10.17487/RFC3264, June 2002, DOI 10.17487/RFC3264, June 2002,
<http://www.rfc-editor.org/info/rfc3264>. <https://www.rfc-editor.org/info/rfc3264>.
[RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax [RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234, Specifications: ABNF", STD 68, RFC 5234,
DOI 10.17487/RFC5234, January 2008, DOI 10.17487/RFC5234, January 2008,
<http://www.rfc-editor.org/info/rfc5234>. <https://www.rfc-editor.org/info/rfc5234>.
[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-sctp-sdp] [I-D.ietf-mmusic-sctp-sdp]
Holmberg, C., Shpount, R., Loreto, S., and G. Camarillo, Holmberg, C., Shpount, R., Loreto, S., and G. Camarillo,
"Session Description Protocol (SDP) Offer/Answer "Session Description Protocol (SDP) Offer/Answer
Procedures For Stream Control Transmission Protocol (SCTP) Procedures For Stream Control Transmission Protocol (SCTP)
over Datagram Transport Layer Security (DTLS) Transport.", over Datagram Transport Layer Security (DTLS) Transport.",
draft-ietf-mmusic-sctp-sdp-25 (work in progress), March draft-ietf-mmusic-sctp-sdp-26 (work in progress), April
2017. 2017.
[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.
11.2. Informative References 11.2. Informative References
[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.
[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, "Session Description Protocol
Mechanism for DTLS", draft-ietf-mmusic-dtls-sdp-22 (work (SDP) Offer/Answer Considerations for Datagram Transport
in progress), March 2017. Layer Security (DTLS) and Transport Layer Security (TLS)",
draft-ietf-mmusic-dtls-sdp-30 (work in progress),
September 2017.
[RFC4960] Stewart, R., Ed., "Stream Control Transmission Protocol", [RFC4960] Stewart, R., Ed., "Stream Control Transmission Protocol",
RFC 4960, DOI 10.17487/RFC4960, September 2007, RFC 4960, DOI 10.17487/RFC4960, September 2007,
<http://www.rfc-editor.org/info/rfc4960>. <https://www.rfc-editor.org/info/rfc4960>.
[IANA-SDP-Parameters] [IANA-SDP-Parameters]
"Session Description Protocol (SDP) Parameters", Internet "Session Description Protocol (SDP) Parameters", Internet
Assigned Numbers Authority Protocol Assignments Session Assigned Numbers Authority Protocol Assignments Session
Description Protocol (SDP) Parameters, Description Protocol (SDP) Parameters,
<http://www.iana.org/assignments/sdp-parameters/ <http://www.iana.org/assignments/sdp-parameters/
sdp-parameters.xhtml>. sdp-parameters.xhtml>.
[WebRtcAPI] [WebRtcAPI]
Bergkvist, A., Burnett, D., Jennings, C., and A. Bergkvist, A., Burnett, D., Jennings, C., and A.
skipping to change at page 40, line 18 skipping to change at page 40, line 32
negotiated without DCEP, the data channel stack always performs an negotiated without DCEP, the data channel stack always performs an
SCTP SSN reset for this channel. SCTP SSN reset for this channel.
Depending upon the method used for DCEP-less negotiation and the Depending upon the method used for DCEP-less negotiation and the
subprotocol associated with the data channel, the closing might in subprotocol associated with the data channel, the closing might in
addition be signaled to the peer via SDP offer/answer negotiation. addition be signaled to the peer via SDP offer/answer negotiation.
Authors' Addresses Authors' Addresses
Keith Drage (editor) Keith Drage (editor)
Nokia Unaffiliated
Quadrant, Stonehill Green, Westlea
Swindon
UK
Email: Keith.Drage@nokia.com Email: drageke@ntlworld.com
Maridi R. Makaraju (Raju) Maridi R. Makaraju (Raju)
Nokia Nokia
2000 Lucent Lane 2000 Lucent Lane
Naperville, Illinois Naperville, Illinois
US US
Email: Raju.Makaraju@nokia.com Email: Raju.Makaraju@nokia.com
Juergen Stoetzer-Bradler Juergen Stoetzer-Bradler
Unaffiliated
Email: Juergen.S-B.ietf@email.de Email: Juergen.S-B.ietf@email.de
Richard Ejzak Richard Ejzak
Unaffiliated Unaffiliated
Email: richard.ejzak@gmail.com Email: richard.ejzak@gmail.com
Jerome Marcon Jerome Marcon
Unaffiliated Unaffiliated
 End of changes. 49 change blocks. 
58 lines changed or deleted 62 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/