draft-ietf-mmusic-data-channel-sdpneg-09.txt   draft-ietf-mmusic-data-channel-sdpneg-10.txt 
MMUSIC K. Drage, Ed. MMUSIC K. Drage, Ed.
Internet-Draft M. Makaraju Internet-Draft M. Makaraju
Intended status: Standards Track J. Stoetzer-Bradler Intended status: Standards Track Nokia
Expires: January 26, 2017 Nokia Expires: April 3, 2017 J. Stoetzer-Bradler
R. Ejzak R. Ejzak
J. Marcon J. Marcon
Unaffiliated Unaffiliated
July 25, 2016 September 30, 2016
SDP-based Data Channel Negotiation SDP-based Data Channel Negotiation
draft-ietf-mmusic-data-channel-sdpneg-09 draft-ietf-mmusic-data-channel-sdpneg-10
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 2, line 4 skipping to change at page 2, line 4
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 January 26, 2017. This Internet-Draft will expire on April 3, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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 2, line 27 skipping to change at page 2, line 27
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 . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Applicability Statement . . . . . . . . . . . . . . . . . . . 5 4. Applicability Statement . . . . . . . . . . . . . . . . . . . 5
5. SDP Offer/Answer Negotiation . . . . . . . . . . . . . . . . 5 5. SDP Offer/Answer Negotiation . . . . . . . . . . . . . . . . 6
5.1. SDP Syntax . . . . . . . . . . . . . . . . . . . . . . . 6 5.1. SDP Syntax . . . . . . . . . . . . . . . . . . . . . . . 6
5.1.1. SDP Attribute for Data Channel Parameter Negotiation 6 5.1.1. SDP Attribute for Data Channel Parameter Negotiation 6
5.1.1.1. dcmap Attribute . . . . . . . . . . . . . . . . . 6 5.1.1.1. dcmap Attribute . . . . . . . . . . . . . . . . . 6
5.1.1.2. dcmap Multiplexing Category . . . . . . . . . . . 8 5.1.1.2. dcmap Multiplexing Category . . . . . . . . . . . 8
5.1.1.3. dcmap-stream-id Parameter . . . . . . . . . . . . 8 5.1.1.3. dcmap-stream-id Parameter . . . . . . . . . . . . 8
5.1.1.4. label Parameter . . . . . . . . . . . . . . . . . 8 5.1.1.4. label Parameter . . . . . . . . . . . . . . . . . 8
5.1.1.5. subprotocol Parameter . . . . . . . . . . . . . . 9 5.1.1.5. subprotocol Parameter . . . . . . . . . . . . . . 9
5.1.1.6. max-retr Parameter . . . . . . . . . . . . . . . 9 5.1.1.6. max-retr Parameter . . . . . . . . . . . . . . . 9
5.1.1.7. max-time Parameter . . . . . . . . . . . . . . . 9 5.1.1.7. max-time Parameter . . . . . . . . . . . . . . . 9
5.1.1.8. ordered Parameter . . . . . . . . . . . . . . . . 9 5.1.1.8. ordered Parameter . . . . . . . . . . . . . . . . 9
skipping to change at page 2, line 49 skipping to change at page 2, line 49
5.1.2. Other Media Level Attributes . . . . . . . . . . . . 10 5.1.2. Other Media Level Attributes . . . . . . . . . . . . 10
5.1.2.1. dcsa Attribute . . . . . . . . . . . . . . . . . 10 5.1.2.1. dcsa Attribute . . . . . . . . . . . . . . . . . 10
5.1.2.2. dcsa Multiplexing Category . . . . . . . . . . . 12 5.1.2.2. dcsa Multiplexing Category . . . . . . . . . . . 12
5.2. Procedures . . . . . . . . . . . . . . . . . . . . . . . 12 5.2. Procedures . . . . . . . . . . . . . . . . . . . . . . . 12
5.2.1. Managing Stream Identifiers . . . . . . . . . . . . . 12 5.2.1. Managing Stream Identifiers . . . . . . . . . . . . . 12
5.2.2. Negotiating Data Channel Parameters . . . . . . . . . 13 5.2.2. Negotiating Data Channel Parameters . . . . . . . . . 13
5.2.3. Opening a Data Channel . . . . . . . . . . . . . . . 14 5.2.3. Opening a Data Channel . . . . . . . . . . . . . . . 14
5.2.4. Closing a Data Channel . . . . . . . . . . . . . . . 16 5.2.4. Closing a Data Channel . . . . . . . . . . . . . . . 16
5.2.5. Various SDP Offer/Answer Scenarios and Considerations 17 5.2.5. Various SDP Offer/Answer Scenarios and Considerations 17
6. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 18 6. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 18
7. Security Considerations . . . . . . . . . . . . . . . . . . . 20 7. Security Considerations . . . . . . . . . . . . . . . . . . . 21
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22
8.1. Subprotocol Identifiers . . . . . . . . . . . . . . . . . 20 8.1. Subprotocol Identifiers . . . . . . . . . . . . . . . . . 22
8.2. New SDP Attributes . . . . . . . . . . . . . . . . . . . 21 8.2. New SDP Attributes . . . . . . . . . . . . . . . . . . . 22
8.2.1. dcmap . . . . . . . . . . . . . . . . . . . . . . . . 21 8.2.1. dcmap . . . . . . . . . . . . . . . . . . . . . . . . 22
8.2.2. dcsa . . . . . . . . . . . . . . . . . . . . . . . . 22 8.2.2. dcsa . . . . . . . . . . . . . . . . . . . . . . . . 23
8.3. New Usage Level . . . . . . . . . . . . . . . . . . . . . 22 8.3. New Usage Level . . . . . . . . . . . . . . . . . . . . . 23
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 22 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 24
10. CHANGE LOG . . . . . . . . . . . . . . . . . . . . . . . . . 23 10. CHANGE LOG . . . . . . . . . . . . . . . . . . . . . . . . . 24
10.1. Changes against 'draft-ietf-mmusic-data-channel- 10.1. Changes against 'draft-ietf-mmusic-data-channel-
sdpneg-08' . . . . . . . . . . . . . . . . . . . . . . . 23 sdpneg-09' . . . . . . . . . . . . . . . . . . . . . . . 24
10.2. Changes against 'draft-ietf-mmusic-data-channel- 10.2. Changes against 'draft-ietf-mmusic-data-channel-
sdpneg-07' . . . . . . . . . . . . . . . . . . . . . . . 23 sdpneg-08' . . . . . . . . . . . . . . . . . . . . . . . 25
10.3. Changes against 'draft-ietf-mmusic-data-channel- 10.3. Changes against 'draft-ietf-mmusic-data-channel-
sdpneg-06' . . . . . . . . . . . . . . . . . . . . . . . 23 sdpneg-07' . . . . . . . . . . . . . . . . . . . . . . . 25
10.4. Changes against 'draft-ietf-mmusic-data-channel- 10.4. Changes against 'draft-ietf-mmusic-data-channel-
sdpneg-05' . . . . . . . . . . . . . . . . . . . . . . . 23 sdpneg-06' . . . . . . . . . . . . . . . . . . . . . . . 25
10.5. Changes against 'draft-ietf-mmusic-data-channel- 10.5. Changes against 'draft-ietf-mmusic-data-channel-
sdpneg-04' . . . . . . . . . . . . . . . . . . . . . . . 24 sdpneg-05' . . . . . . . . . . . . . . . . . . . . . . . 26
10.6. Changes against 'draft-ietf-mmusic-data-channel- 10.6. Changes against 'draft-ietf-mmusic-data-channel-
sdpneg-03' . . . . . . . . . . . . . . . . . . . . . . . 25 sdpneg-04' . . . . . . . . . . . . . . . . . . . . . . . 26
10.7. Changes against 'draft-ietf-mmusic-data-channel- 10.7. Changes against 'draft-ietf-mmusic-data-channel-
sdpneg-02' . . . . . . . . . . . . . . . . . . . . . . . 26 sdpneg-03' . . . . . . . . . . . . . . . . . . . . . . . 27
10.8. Changes against 'draft-ietf-mmusic-data-channel- 10.8. Changes against 'draft-ietf-mmusic-data-channel-
sdpneg-01' . . . . . . . . . . . . . . . . . . . . . . . 27 sdpneg-02' . . . . . . . . . . . . . . . . . . . . . . . 28
10.9. Changes against 'draft-ietf-mmusic-data-channel- 10.9. Changes against 'draft-ietf-mmusic-data-channel-
sdpneg-00' . . . . . . . . . . . . . . . . . . . . . . . 29 sdpneg-01' . . . . . . . . . . . . . . . . . . . . . . . 29
10.10. Changes against 'draft-ejzak-mmusic-data-channel- 10.10. Changes against 'draft-ietf-mmusic-data-channel-
sdpneg-02' . . . . . . . . . . . . . . . . . . . . . . . 32 sdpneg-00' . . . . . . . . . . . . . . . . . . . . . . . 32
10.11. Changes against '-01' . . . . . . . . . . . . . . . . . 33 10.11. Changes against 'draft-ejzak-mmusic-data-channel-
10.12. Changes against '-00' . . . . . . . . . . . . . . . . . 33 sdpneg-02' . . . . . . . . . . . . . . . . . . . . . . . 34
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 34 10.12. Changes against '-01' . . . . . . . . . . . . . . . . . 35
11.1. Normative References . . . . . . . . . . . . . . . . . . 34 10.13. Changes against '-00' . . . . . . . . . . . . . . . . . 36
11.2. Informative References . . . . . . . . . . . . . . . . . 35 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 36
11.1. Normative 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 . . . . . . . . . . . . . . . . . . . . . 35 Using DCEP . . . . . . . . . . . . . . . . . . . . . 38
A.1. Stream Identifier Numbering . . . . . . . . . . . . . . . 36 A.1. Stream Identifier Numbering . . . . . . . . . . . . . . . 38
A.2. Generic Data Channel Negotiation Not Using DCEP . . . . . 37 A.2. Generic Data Channel Negotiation Not Using DCEP . . . . . 39
A.2.1. Overview . . . . . . . . . . . . . . . . . . . . . . 37 A.2.1. Overview . . . . . . . . . . . . . . . . . . . . . . 39
A.2.2. Opening a Data Channel . . . . . . . . . . . . . . . 37 A.2.2. Opening a Data Channel . . . . . . . . . . . . . . . 39
A.2.3. Closing a Data Channel . . . . . . . . . . . . . . . 38 A.2.3. Closing a Data Channel . . . . . . . . . . . . . . . 40
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 38 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 SCTP/DTLS (SCTP over the Datagram data channels running on top of the Stream Control Transmission
Transport Layer Security protocol). RTCWeb allows applications to Protocol (SCTP). RTCWeb allows applications to use data channels.
use data channels. RTCWeb defines an in-band DCEP, however other in- RTCWeb defines an in-band Data Channel Establishment Protocol (DCEP),
band or out-of-band protocols may be used for establishing data however other in-band or out-of-band protocols may be used for
channels. Each data channel consists of paired SCTP streams sharing establishing data channels. Each data channel consists of paired
the same SCTP Stream Identifier. Data channels are created by SCTP streams sharing the same SCTP Stream Identifier. Data channels
endpoint applications through the WebRTC API (Application Programming are created by endpoint applications through the WebRTC API
Interface), or other users of a data channel like CLUE. They can be (Application Programming Interface), or other users of a data channel
used to transport proprietary or well-defined protocols, which in the like CLUE. They can be used to transport proprietary or well-defined
latter case can be signaled by the data channel "subprotocol" protocols, which in the latter case can be signaled by the data
parameter, conceptually similar to the WebSocket "subprotocol". channel "subprotocol" parameter, conceptually similar to the
However, apart from the "subprotocol" value transmitted to the peer, WebSocket "subprotocol". However, apart from the "subprotocol" value
RTCWeb leaves it open how endpoint applications can agree on how to transmitted to the peer, RTCWeb leaves it open how endpoint
instantiate a given subprotocol on a data channel, and whether it is applications can agree on how to instantiate a given subprotocol on a
signaled in-band using DCEP or out-of-band using a non-DCEP protocol data channel, and whether it is signaled in-band using DCEP or out-
(or both). In particular, the SDP offer generated by the RTCweb data of-band using a non-DCEP protocol (or both). In particular, the SDP
channel stack includes no channel-specific information. offer generated by the RTCweb data channel stack includes no channel-
specific information.
This document defines SDP offer/answer negotiation procedures to This document defines SDP offer/answer negotiation procedures to
establish data channels for transport of well-defined subprotocols, establish data channels for transport of well-defined subprotocols,
to enable out-of-band negotiation. to enable out-of-band negotiation. These procedures are based on
generic SDP offer/answer negotiation rules for SCTP based media
transport as specified in [I-D.ietf-mmusic-sctp-sdp] for the SDP "m"
line proto values UDP/DTLS/SCTP and TCP/DTLS/SCTP. In future data
channels could be defined over other SCTP based protocols, such as
SCTP over IP. However, corresponding potential other "m" line proto
values are not considered in this document.
This document makes use of MSRP (Message Session Relay Protocol) in This document makes use of MSRP (Message Session Relay Protocol) in
many of the examples. It does not provide a complete specification many of the examples. It does not provide a complete specification
of how to negotiate the use of a data channel to transport MSRP. of how to negotiate the use of a data channel to transport MSRP.
Procedures specific to each subprotocol such as MSRP are documented Procedures specific to each subprotocol such as MSRP are documented
elsewhere. The use of MSRP in some examples is only to show how the elsewhere. The use of MSRP in some examples is only to show how the
generic procedures described herein might apply to a specific generic procedures described herein might apply to a specific
subprotocol. subprotocol.
2. Conventions 2. Conventions
skipping to change at page 8, line 18 skipping to change at page 8, line 28
5.1.1.2. dcmap Multiplexing Category 5.1.1.2. dcmap Multiplexing Category
Multiplexing characteristics of SDP attributes are described in Multiplexing characteristics of SDP attributes are described in
[I-D.ietf-mmusic-sdp-mux-attributes]. Various SDP attribute [I-D.ietf-mmusic-sdp-mux-attributes]. Various SDP attribute
multiplexing categories are introduced there. multiplexing categories are introduced there.
The multiplexing category of the "a=dcmap:" attribute is SPECIAL. The multiplexing category of the "a=dcmap:" attribute is SPECIAL.
As the usage of multiple SCTP associations on top of a single DTLS As the usage of multiple SCTP associations on top of a single DTLS
connection is outside the scope of [I-D.ietf-mmusic-sctp-sdp], no association is outside the scope of [I-D.ietf-mmusic-sctp-sdp], no
"a=dcmap:" attribute multiplexing rules are specified for the "a=dcmap:" attribute multiplexing rules are specified for the
UDP/DTLS/SCTP and TCP/DTLS/SCTP proto values. This document also UDP/DTLS/SCTP and TCP/DTLS/SCTP proto values. If future extensions
does not specify multiplexing rules for this attribute for SCTP or of [I-D.ietf-mmusic-sctp-sdp] define how to negotiate multiplexing of
SCTP/DTLS proto values. If future extensions of multiple SCTP associations on top of a single DTLS association, or
[I-D.ietf-mmusic-sctp-sdp] define how to negotiate multiplexing of how to add multiple SCTP associations to one BUNDLE group, then
multiple SCTP associations on top of a single DTLS connection, or how
to add multiple SCTP associations to one BUNDLE group, then
multiplexing rules for the "a=dcmap:" attribute need to be defined as multiplexing rules for the "a=dcmap:" attribute need to be defined as
well, for instance in an extension of this SDP based data channel well, for instance in an extension of this SDP based data channel
negotiation specification. negotiation specification.
5.1.1.3. dcmap-stream-id Parameter 5.1.1.3. dcmap-stream-id Parameter
The 'dcmap-stream-id' parameter indicates the SCTP stream identifier The 'dcmap-stream-id' parameter indicates the SCTP stream identifier
within the SCTP association used to form the data channel. within the SCTP association used to form the data channel.
5.1.1.4. label Parameter 5.1.1.4. label Parameter
skipping to change at page 12, line 15 skipping to change at page 12, line 15
to be described for the data channel transport. A data channel to be described for the data channel transport. A data channel
specific usage of a subprotocol attribute is expected to be specified specific usage of a subprotocol attribute is expected to be specified
in the same document, which registers the subprotocol's identifier in the same document, which registers the subprotocol's identifier
for data channel usage as described in Section 8.1. for data channel usage as described in Section 8.1.
5.1.2.2. dcsa Multiplexing Category 5.1.2.2. dcsa Multiplexing Category
The multiplexing category of the "a=dcsa:" attribute is SPECIAL. The multiplexing category of the "a=dcsa:" attribute is SPECIAL.
As the usage of multiple SCTP associations on top of a single DTLS As the usage of multiple SCTP associations on top of a single DTLS
connection is outside the scope of [I-D.ietf-mmusic-sctp-sdp], no association is outside the scope of [I-D.ietf-mmusic-sctp-sdp], no
"a=dcsa:" attribute multiplexing rules are specified for the "a=dcsa:" attribute multiplexing rules are specified for the
UDP/DTLS/SCTP and TCP/DTLS/SCTP proto values. This document does UDP/DTLS/SCTP and TCP/DTLS/SCTP proto values. If future extensions
also not specify multiplexing rules for this attribute for SCTP or of [I-D.ietf-mmusic-sctp-sdp] define how to negotiate multiplexing of
SCTP/DTLS proto values. If future extensions of multiple SCTP associations on top of a single DTLS association, or
[I-D.ietf-mmusic-sctp-sdp] define how to negotiate multiplexing of how to add multiple SCTP associations to one BUNDLE group, then
multiple SCTP associations on top of a single DTLS connection, or how
to add multiple SCTP associations to one BUNDLE group, then
multiplexing rules for the "a=dcsa:" attribute need to be defined as multiplexing rules for the "a=dcsa:" attribute need to be defined as
well, for instance in an extension of this SDP based data channel well, for instance in an extension of this SDP based data channel
negotiation specification. negotiation specification.
5.2. Procedures 5.2. Procedures
5.2.1. Managing Stream Identifiers 5.2.1. Managing Stream Identifiers
If a SDP offer/answer exchange (could be the initial or a subsequent If a SDP offer/answer exchange (could be the initial or a subsequent
one) results in a UDP/DTLS/SCTP or TCP/DTLS/SCTP based media one) results in a UDP/DTLS/SCTP or TCP/DTLS/SCTP based media
skipping to change at page 17, line 20 skipping to change at page 17, line 20
SCTP SSN reset of both incoming and outgoing streams is completed). SCTP SSN reset of both incoming and outgoing streams is completed).
This restriction is to avoid the race conditions between arrival of This restriction is to avoid the race conditions between arrival of
"SDP offer which reuses stream" with "SCTP SSN reset which closes "SDP offer which reuses stream" with "SCTP SSN reset which closes
outgoing stream" at the peer. outgoing stream" at the peer.
5.2.5. Various SDP Offer/Answer Scenarios and Considerations 5.2.5. Various SDP Offer/Answer Scenarios and Considerations
SDP offer has no "a=dcmap:" attributes. SDP offer has no "a=dcmap:" attributes.
* Initial SDP offer: No data channel is negotiated yet. The DTLS * Initial SDP offer: No data channel is negotiated yet. The DTLS
connection and SCTP association is negotiated and, if agreed, association and SCTP association is negotiated and, if agreed,
established as per [I-D.ietf-mmusic-sctp-sdp]. established as per [I-D.ietf-mmusic-sctp-sdp].
* Subsequent SDP offer: All the SDP offer/answer negotiated data * Subsequent SDP offer: All the SDP offer/answer negotiated data
channels are expected be closed now. The DTLS/SCTP association channels are expected be closed now. The DTLS/SCTP association
remains open for SDP offer/answer or DCEP negotiation of data remains open for SDP offer/answer or DCEP negotiation of data
channels. channels.
SDP answer has no "a=dcmap:" attributes. SDP answer has no "a=dcmap:" attributes.
* Initial SDP answer: Either the peer does not support "a=dcmap:" * Initial SDP answer: Either the peer does not support "a=dcmap:"
attributes or it rejected all the data channels. In either attributes or it rejected all the data channels. In either
case the offerer closes all the SDP offer/answer negotiated case the offerer closes all the SDP offer/answer negotiated
data channels that were open at the time of initial offer. The data channels that were open at the time of initial offer. The
DTLS connection and SCTP association will still be setup. DTLS association and SCTP association will still be setup.
* Subsequent SDP answer: All the SDP offer/answer negotiated data * Subsequent SDP answer: All the SDP offer/answer negotiated data
channels are expected be closed now. The DTLS/SCTP association channels are expected be closed now. The SCTP association
remains open for future SDP offer/answer or DCEP negotiation of remains open for future SDP offer/answer or DCEP negotiation of
data channels. data channels.
SDP offer or answer has no "a=dcmap:" attributes but has "a=dcsa:" SDP offer or answer has no "a=dcmap:" attributes but has "a=dcsa:"
attributes. attributes.
* This is considered an error case. In this case the receiver of * This is considered an error case. In this case the receiver of
such an SDP offer or answer SHOULD ignore the "a=dcsa:" such an SDP offer or answer SHOULD ignore the "a=dcsa:"
attributes and SHOULD process the SDP offer or answer as per attributes and SHOULD process the SDP offer or answer as per
above case 'SDP offer has no "a=dcmap:" attributes' or case above case 'SDP offer has no "a=dcmap:" attributes' or case
skipping to change at page 18, line 29 skipping to change at page 19, line 4
entire "a=dcsa" attribute line. entire "a=dcsa" attribute line.
SDP offer or answer has an "a=dcsa" attribute, whose subprotocol SDP offer or answer has an "a=dcsa" attribute, whose subprotocol
attribute is known, but whose subprotocol attribute semantic is attribute is known, but whose subprotocol attribute semantic is
not known for the data channel transport case. not known for the data channel transport case.
* The receiver of such an SDP offer or answer SHOULD ignore this * The receiver of such an SDP offer or answer SHOULD ignore this
entire "a=dcsa" attribute line. entire "a=dcsa" attribute line.
6. Examples 6. Examples
SDP offer: SDP offer:
m=application 10001 UDP/DTLS/SCTP webrtc-datachannel m=application 10001 UDP/DTLS/SCTP webrtc-datachannel
c=IN IP4 10.10.10.1 c=IN IP4 10.10.10.1
a=max-message-size:100000 a=max-message-size:100000
a=sctp-port:5000 a=sctp-port:5000
a=setup:actpass a=setup:actpass
a=connection:new a=connection:new
a=fingerprint:SHA-1 \ a=fingerprint:SHA-1 \
4A:AD:B9:B1:3F:82:18:3B:54:02:12:DF:3E:5D:49:6B:19:E5:7C:AB 4A:AD:B9:B1:3F:82:18:3B:54:02:12:DF:3E:5D:49:6B:19:E5:7C:AB
a=dtls-id:4a7565
a=dcmap:0 subprotocol="BFCP";label="BFCP" a=dcmap:0 subprotocol="BFCP";label="BFCP"
SDP answer: SDP answer:
m=application 10002 UDP/DTLS/SCTP webrtc-datachannel m=application 10002 UDP/DTLS/SCTP webrtc-datachannel
c=IN IP4 10.10.10.2 c=IN IP4 10.10.10.2
a=max-message-size:100000 a=max-message-size:100000
a=sctp-port:5002 a=sctp-port:5002
a=setup:passive a=setup:passive
a=connection:new a=connection:new
a=fingerprint:SHA-1 \ a=fingerprint:SHA-1 \
5B:AD:67:B1:3E:82:AC:3B:90:02:B1:DF:12:5D:CA:6B:3F:E5:54:FA 5B:AD:67:B1:3E:82:AC:3B:90:02:B1:DF:12:5D:CA:6B:3F:E5:54:FA
a=dtls-id:532d42
Figure 1: Example 1 Figure 1: Example 1
In the above example the SDP answerer rejected the data channel with In the above example the SDP answerer rejected the data channel with
stream id 0 either for explicit reasons or because it does not stream id 0 either for explicit reasons or because it does not
understand the "a=dcmap:" attribute. As a result the offerer will understand the "a=dcmap:" attribute. As a result the offerer will
close the data channel created with the SDP offer/answer negotiation close the data channel created with the SDP offer/answer negotiation
option. The SCTP association will still be setup over DTLS. At this option. The SCTP association will still be setup over DTLS. At this
point the offerer or the answerer may use DCEP negotiation to open point the offerer or the answerer may use DCEP negotiation to open
data channels. data channels.
skipping to change at page 19, line 14 skipping to change at page 20, line 6
In the above example the SDP answerer rejected the data channel with In the above example the SDP answerer rejected the data channel with
stream id 0 either for explicit reasons or because it does not stream id 0 either for explicit reasons or because it does not
understand the "a=dcmap:" attribute. As a result the offerer will understand the "a=dcmap:" attribute. As a result the offerer will
close the data channel created with the SDP offer/answer negotiation close the data channel created with the SDP offer/answer negotiation
option. The SCTP association will still be setup over DTLS. At this option. The SCTP association will still be setup over DTLS. At this
point the offerer or the answerer may use DCEP negotiation to open point the offerer or the answerer may use DCEP negotiation to open
data channels. data channels.
SDP offer: SDP offer:
m=application 10001 UDP/DTLS/SCTP webrtc-datachannel m=application 10001 UDP/DTLS/SCTP webrtc-datachannel
c=IN IP4 10.10.10.1 c=IN IP4 10.10.10.1
a=max-message-size:100000 a=max-message-size:100000
a=sctp-port:5000 a=sctp-port:5000
a=setup:actpass a=setup:actpass
a=connection:new a=connection:new
a=fingerprint:SHA-1 \ a=fingerprint:SHA-1 \
4A:AD:B9:B1:3F:82:18:3B:54:02:12:DF:3E:5D:49:6B:19:E5:7C:AB 4A:AD:B9:B1:3F:82:18:3B:54:02:12:DF:3E:5D:49:6B:19:E5:7C:AB
a=dtls-id:4a7565
a=dcmap:0 subprotocol="BFCP";label="BFCP" a=dcmap:0 subprotocol="BFCP";label="BFCP"
a=dcmap:2 subprotocol="MSRP";label="MSRP" a=dcmap:2 subprotocol="MSRP";label="MSRP"
a=dcsa:2 accept-types:message/cpim text/plain a=dcsa:2 accept-types:message/cpim text/plain
a=dcsa:2 path:msrp://alice.example.com:10001/2s93i93idj;dc a=dcsa:2 path:msrp://alice.example.com:10001/2s93i93idj;dc
SDP answer: SDP answer:
m=application 10002 UDP/DTLS/SCTP webrtc-datachannel m=application 10002 UDP/DTLS/SCTP webrtc-datachannel
c=IN IP4 10.10.10.2 c=IN IP4 10.10.10.2
a=max-message-size:100000 a=max-message-size:100000
a=sctp-port:5002 a=sctp-port:5002
a=setup:passive a=setup:passive
a=connection:new a=connection:new
a=fingerprint:SHA-1 \ a=fingerprint:SHA-1 \
5B:AD:67:B1:3E:82:AC:3B:90:02:B1:DF:12:5D:CA:6B:3F:E5:54:FA 5B:AD:67:B1:3E:82:AC:3B:90:02:B1:DF:12:5D:CA:6B:3F:E5:54:FA
a=dtls-id:532d42
a=dcmap:2 subprotocol="MSRP";label="MSRP" a=dcmap:2 subprotocol="MSRP";label="MSRP"
a=dcsa:2 accept-types:message/cpim text/plain a=dcsa:2 accept-types:message/cpim text/plain
a=dcsa:2 path:msrp://bob.example.com:10002/si438dsaodes;dc a=dcsa:2 path:msrp://bob.example.com:10002/si438dsaodes;dc
Figure 2: Example 2 Figure 2: Example 2
In the above example the SDP offer contains data channels for BFCP In the above example the SDP offer contains data channels for BFCP
(Binary Floor Control Protocol) and MSRP subprotocols. The SDP (Binary Floor Control Protocol) and MSRP subprotocols. The SDP
answer rejected BFCP and accepted MSRP. So, the offerer closes the answer rejected BFCP and accepted MSRP. So, the offerer closes the
data channel for BFCP and both offerer and answerer may start using data channel for BFCP and both offerer and answerer may start using
the MSRP data channel (after SCTP/DTLS association is setup). The the MSRP data channel (after the SCTP association is set up). The
data channel with stream id 0 is free and can be used for future DCEP data channel with stream id 0 is free and can be used for future DCEP
or SDP offer/answer negotiation. or SDP offer/answer negotiation.
Continuing the example in Figure 2. Continuing the example in Figure 2.
Subsequent SDP offer: Subsequent SDP offer:
m=application 10001 UDP/DTLS/SCTP webrtc-datachannel m=application 10001 UDP/DTLS/SCTP webrtc-datachannel
c=IN IP4 10.10.10.1 c=IN IP4 10.10.10.1
a=max-message-size:100000 a=max-message-size:100000
a=sctp-port:5000 a=sctp-port:5000
a=setup:actpass a=setup:actpass
a=connection:existing a=connection:existing
a=fingerprint:SHA-1 \ a=fingerprint:SHA-1 \
4A:AD:B9:B1:3F:82:18:3B:54:02:12:DF:3E:5D:49:6B:19:E5:7C:AB 4A:AD:B9:B1:3F:82:18:3B:54:02:12:DF:3E:5D:49:6B:19:E5:7C:AB
a=dtls-id:4a7565
a=dcmap:4 subprotocol="MSRP";label="MSRP" a=dcmap:4 subprotocol="MSRP";label="MSRP"
a=dcsa:4 accept-types:message/cpim text/plain a=dcsa:4 accept-types:message/cpim text/plain
a=dcsa:4 path:msrp://alice.example.com:10001/2s93i93idj;dc a=dcsa:4 path:msrp://alice.example.com:10001/2s93i93idj;dc
Subsequent SDP answer: Subsequent SDP answer:
m=application 10002 UDP/DTLS/SCTP webrtc-datachannel m=application 10002 UDP/DTLS/SCTP webrtc-datachannel
c=IN IP4 10.10.10.2 c=IN IP4 10.10.10.2
a=max-message-size:100000 a=max-message-size:100000
a=sctp-port:5002 a=sctp-port:5002
a=setup:passive a=setup:passive
a=connection:existing a=connection:existing
a=fingerprint:SHA-1 \ a=fingerprint:SHA-1 \
5B:AD:67:B1:3E:82:AC:3B:90:02:B1:DF:12:5D:CA:6B:3F:E5:54:FA 5B:AD:67:B1:3E:82:AC:3B:90:02:B1:DF:12:5D:CA:6B:3F:E5:54:FA
a=dtls-id:532d42
a=dcmap:4 subprotocol="MSRP";label="MSRP" a=dcmap:4 subprotocol="MSRP";label="MSRP"
a=dcsa:4 accept-types:message/cpim text/plain a=dcsa:4 accept-types:message/cpim text/plain
a=dcsa:4 path:msrp://bob.example.com:10002/si438dsaodes;dc a=dcsa:4 path:msrp://bob.example.com:10002/si438dsaodes;dc
Figure 3: Example 3 Figure 3: Example 3
The above example is a continuation of the example in Figure 2. The The above example is a continuation of the example in Figure 2. The
SDP offer now removes the MSRP data channel with stream id 2, but SDP offerer now removes the MSRP data channel with stream id 2, but
opens a new MSRP data channel with stream id 4. The answerer accepts opens a new MSRP data channel with stream id 4. The answerer accepts
the entire offer. As a result the offerer closes the earlier the entire offer. As a result the offerer closes the earlier
negotiated MSRP related data channel and both offerer and answerer negotiated MSRP related data channel and both offerer and answerer
may start using new the MSRP related data channel. may start using new the MSRP related data channel.
7. Security Considerations 7. Security Considerations
No security considerations are envisaged beyond those already No security considerations are envisaged beyond those already
documented in [RFC4566]. documented in [RFC4566].
skipping to change at page 23, line 5 skipping to change at page 24, line 20
| Usage level: | dcsa(MSRP) | | Usage level: | dcsa(MSRP) |
| ... | ... | | ... | ... |
+-----------------------+-------------------------------------------+ +-----------------------+-------------------------------------------+
9. Acknowledgments 9. Acknowledgments
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, and Uwe Rauschenbach for their invaluable comments. Jonathan Lennox, Uwe Rauschenbach and Roman Shpount for their
invaluable comments.
10. CHANGE LOG 10. CHANGE LOG
10.1. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-08' 10.1. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-09'
o In the introduction:
* Replacement of the sentence "The RTCWeb working group has
defined the concept of bi-directional data channels running on
top of SCTP/DTLS (SCTP over the Datagram Transport Layer
Security protocol)" with "The RTCWeb working group has defined
the concept of bi-directional data channels running on top of
the Stream Control Transmission Protocol (SCTP)".
* Addition of following sentences to the second paragraph: "These
procedures are based on generic SDP offer/answer negotiation
rules for SCTP based media transport as specified in
[I-D.ietf-mmusic-sctp-sdp] for the SDP "m" line proto values
UDP/DTLS/SCTP and TCP/DTLS/SCTP. In future data channels could
be defined over other SCTP based protocols, such as SCTP over
IP. However, corresponding potential other "m" line proto
values are not considered in this document."
o Replacement of "DTLS connection" with "DTLS association"
throughout the document.
o In sections Section 5.1.1.2 and Section 5.1.2.2 removal of the
sentences "This document also does not specify multiplexing rules
for this attribute for SCTP or SCTP/DTLS proto values".
o In the text related to "Subsequent SDP answer" in section
Section 5.2.5 replacement of "The DTLS/SCTP association remains
open ..." with "The SCTP association remains open ...".
o In the text after the second SDP answer in section Section 6
replacement of "... (after SCTP/DTLS association is setup)" with
"... (after the SCTP association is set up)".
o Addition of [I-D.ietf-mmusic-dtls-sdp] to the list of informative
references.
o Addition of "a=dtls-id" attribute lines to the SDP offer/answer
examples in Section 6.
10.2. 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.2. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-07' 10.3. 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.3. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-06' 10.4. 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.4. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-05' 10.5. 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 24, line 32 skipping to change at page 26, line 42
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.5. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-04' 10.6. 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 25, line 26 skipping to change at page 27, line 34
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.6. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-03' 10.7. 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 26, line 36 skipping to change at page 28, line 44
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.7. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-02' 10.8. 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."
o In the introduction replacement of last sentence "This document o In the introduction replacement of last sentence "This document
defines SDP-based out-of-band negotiation procedures to establish defines SDP-based out-of-band negotiation procedures to establish
data channels for transport of well-defined subprotocols" with data channels for transport of well-defined subprotocols" with
"This document defines SDP offer/answer negotiation procedures to "This document defines SDP offer/answer negotiation procedures to
establish data channels for transport of well-defined establish data channels for transport of well-defined
subprotocols, to enable out-of-band negotiation". subprotocols, to enable out-of-band negotiation".
skipping to change at page 27, line 37 skipping to change at page 29, line 45
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.8. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-01' 10.9. 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 29, line 44 skipping to change at page 32, line 5
* 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.9. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-00' 10.10. 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 32, line 30 skipping to change at page 34, line 39
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.10. Changes against 'draft-ejzak-mmusic-data-channel-sdpneg-02' 10.11. 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 33, line 32 skipping to change at page 35, line 41
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.11. Changes against '-01' 10.12. 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.12. Changes against '-00' 10.13. 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 34, line 30 skipping to change at page 36, line 38
[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>. <http://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, <http://www.rfc-editor.org/info/rfc4566>.
[I-D.ietf-mmusic-rfc4566bis] [I-D.ietf-mmusic-rfc4566bis]
Handley, M., Jacobson, V., Perkins, D., 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>. <http://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,
skipping to change at page 35, line 9 skipping to change at page 37, line 14
[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., Loreto, S., and G. Camarillo, "Stream Holmberg, C., Loreto, S., and G. Camarillo, "Stream
Control Transmission Protocol (SCTP)-Based Media Transport Control Transmission Protocol (SCTP)-Based Media Transport
in the Session Description Protocol (SDP)", draft-ietf- in the Session Description Protocol (SDP)", draft-ietf-
mmusic-sctp-sdp-16 (work in progress), February 2016. mmusic-sctp-sdp-17 (work in progress), August 2016.
[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-13 Multiplexing", draft-ietf-mmusic-sdp-mux-attributes-14
(work in progress), June 2016. (work in progress), September 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]
Holmberg, C. and R. Shpount, "Using the SDP Offer/Answer
Mechanism for DTLS", draft-ietf-mmusic-dtls-sdp-14 (work
in progress), July 2016.
[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>. <http://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>.
skipping to change at page 38, line 38 skipping to change at page 41, line 4
Authors' Addresses Authors' Addresses
Keith Drage (editor) Keith Drage (editor)
Nokia Nokia
Quadrant, Stonehill Green, Westlea Quadrant, Stonehill Green, Westlea
Swindon Swindon
UK UK
Email: Keith.Drage@nokia.com Email: Keith.Drage@nokia.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
Nokia
Lorenzstrasse 10
D-70435 Stuttgart
Germany
Email: Juergen.Stoetzer-Bradler@nokia.com 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. 62 change blocks. 
99 lines changed or deleted 160 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/