draft-ietf-mmusic-data-channel-sdpneg-08.txt   draft-ietf-mmusic-data-channel-sdpneg-09.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 J. Stoetzer-Bradler
Expires: August 20, 2016 Nokia Expires: January 26, 2017 Nokia
R. Ejzak R. Ejzak
J. Marcon J. Marcon
Unaffiliated Unaffiliated
February 17, 2016 July 25, 2016
SDP-based Data Channel Negotiation SDP-based Data Channel Negotiation
draft-ietf-mmusic-data-channel-sdpneg-08 draft-ietf-mmusic-data-channel-sdpneg-09
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 August 20, 2016. This Internet-Draft will expire on January 26, 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 28 skipping to change at page 2, line 28
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 . . . . . . . . . . . . . . . . 5
5.1. SDP Syntax . . . . . . . . . . . . . . . . . . . . . . . 5 5.1. SDP Syntax . . . . . . . . . . . . . . . . . . . . . . . 6
5.1.1. SDP Attribute for Data Channel Parameter Negotiation 5 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 . . . . . . . . . . . 7 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 . . . . . . . . . . . . . . 8 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
5.1.1.9. priority Parameter . . . . . . . . . . . . . . . 9 5.1.1.9. priority Parameter . . . . . . . . . . . . . . . 10
5.1.2. Other Media Level Attributes . . . . . . . . . . . . 9 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 . . . . . . . . . . . 11 5.1.2.2. dcsa Multiplexing Category . . . . . . . . . . . 12
5.2. Procedures . . . . . . . . . . . . . . . . . . . . . . . 11 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 . . . . . . . . . 12 5.2.2. Negotiating Data Channel Parameters . . . . . . . . . 13
5.2.3. Opening a Data Channel . . . . . . . . . . . . . . . 13 5.2.3. Opening a Data Channel . . . . . . . . . . . . . . . 14
5.2.4. Closing a Data Channel . . . . . . . . . . . . . . . 15 5.2.4. Closing a Data Channel . . . . . . . . . . . . . . . 16
5.2.5. Various SDP Offer/Answer Scenarios and Considerations 16 5.2.5. Various SDP Offer/Answer Scenarios and Considerations 17
6. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 17 6. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 18
7. Security Considerations . . . . . . . . . . . . . . . . . . . 20 7. Security Considerations . . . . . . . . . . . . . . . . . . . 20
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20
8.1. Subprotocol Identifiers . . . . . . . . . . . . . . . . . 20 8.1. Subprotocol Identifiers . . . . . . . . . . . . . . . . . 20
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 . . . . . . . . . . . . . . . . . . . . . . . . 21 8.2.2. dcsa . . . . . . . . . . . . . . . . . . . . . . . . 22
8.3. New Usage Level . . . . . . . . . . . . . . . . . . . . . 22
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 22 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 22
10. CHANGE LOG . . . . . . . . . . . . . . . . . . . . . . . . . 22 10. CHANGE LOG . . . . . . . . . . . . . . . . . . . . . . . . . 23
10.1. Changes against 'draft-ietf-mmusic-data-channel- 10.1. Changes against 'draft-ietf-mmusic-data-channel-
sdpneg-07' . . . . . . . . . . . . . . . . . . . . . . . 22 sdpneg-08' . . . . . . . . . . . . . . . . . . . . . . . 23
10.2. Changes against 'draft-ietf-mmusic-data-channel- 10.2. Changes against 'draft-ietf-mmusic-data-channel-
sdpneg-06' . . . . . . . . . . . . . . . . . . . . . . . 22 sdpneg-07' . . . . . . . . . . . . . . . . . . . . . . . 23
10.3. Changes against 'draft-ietf-mmusic-data-channel- 10.3. Changes against 'draft-ietf-mmusic-data-channel-
sdpneg-05' . . . . . . . . . . . . . . . . . . . . . . . 23 sdpneg-06' . . . . . . . . . . . . . . . . . . . . . . . 23
10.4. Changes against 'draft-ietf-mmusic-data-channel- 10.4. Changes against 'draft-ietf-mmusic-data-channel-
sdpneg-04' . . . . . . . . . . . . . . . . . . . . . . . 23 sdpneg-05' . . . . . . . . . . . . . . . . . . . . . . . 23
10.5. Changes against 'draft-ietf-mmusic-data-channel- 10.5. Changes against 'draft-ietf-mmusic-data-channel-
sdpneg-03' . . . . . . . . . . . . . . . . . . . . . . . 24 sdpneg-04' . . . . . . . . . . . . . . . . . . . . . . . 24
10.6. Changes against 'draft-ietf-mmusic-data-channel- 10.6. Changes against 'draft-ietf-mmusic-data-channel-
sdpneg-02' . . . . . . . . . . . . . . . . . . . . . . . 25 sdpneg-03' . . . . . . . . . . . . . . . . . . . . . . . 25
10.7. Changes against 'draft-ietf-mmusic-data-channel- 10.7. Changes against 'draft-ietf-mmusic-data-channel-
sdpneg-01' . . . . . . . . . . . . . . . . . . . . . . . 26 sdpneg-02' . . . . . . . . . . . . . . . . . . . . . . . 26
10.8. Changes against 'draft-ietf-mmusic-data-channel- 10.8. Changes against 'draft-ietf-mmusic-data-channel-
sdpneg-01' . . . . . . . . . . . . . . . . . . . . . . . 27
10.9. Changes against 'draft-ietf-mmusic-data-channel-
sdpneg-00' . . . . . . . . . . . . . . . . . . . . . . . 29 sdpneg-00' . . . . . . . . . . . . . . . . . . . . . . . 29
10.9. Changes against 'draft-ejzak-mmusic-data-channel- 10.10. Changes against 'draft-ejzak-mmusic-data-channel-
sdpneg-02' . . . . . . . . . . . . . . . . . . . . . . . 31 sdpneg-02' . . . . . . . . . . . . . . . . . . . . . . . 32
10.10. Changes against '-01' . . . . . . . . . . . . . . . . . 32 10.11. Changes against '-01' . . . . . . . . . . . . . . . . . 33
10.11. Changes against '-00' . . . . . . . . . . . . . . . . . 33 10.12. Changes against '-00' . . . . . . . . . . . . . . . . . 33
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 33 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 34
11.1. Normative References . . . . . . . . . . . . . . . . . . 33 11.1. Normative References . . . . . . . . . . . . . . . . . . 34
11.2. Informative References . . . . . . . . . . . . . . . . . 34 11.2. Informative References . . . . . . . . . . . . . . . . . 35
Appendix A. Generic Data Channel Negotiation Aspects When Not Appendix A. Generic Data Channel Negotiation Aspects When Not
Using DCEP . . . . . . . . . . . . . . . . . . . . . 34 Using DCEP . . . . . . . . . . . . . . . . . . . . . 35
A.1. Stream Identifier Numbering . . . . . . . . . . . . . . . 35 A.1. Stream Identifier Numbering . . . . . . . . . . . . . . . 36
A.2. Generic Data Channel Negotiation Not Using DCEP . . . . . 36 A.2. Generic Data Channel Negotiation Not Using DCEP . . . . . 37
A.2.1. Overview . . . . . . . . . . . . . . . . . . . . . . 36 A.2.1. Overview . . . . . . . . . . . . . . . . . . . . . . 37
A.2.2. Opening a Data Channel . . . . . . . . . . . . . . . 36 A.2.2. Opening a Data Channel . . . . . . . . . . . . . . . 37
A.2.3. Closing a Data Channel . . . . . . . . . . . . . . . 37 A.2.3. Closing a Data Channel . . . . . . . . . . . . . . . 38
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 37 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 38
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 SCTP/DTLS (SCTP over the Datagram
Transport Layer Security protocol). RTCWeb allows applications to Transport Layer Security protocol). RTCWeb allows applications to
use data channels. RTCWeb defines an in-band DCEP, however other in- use data channels. RTCWeb defines an in-band DCEP, however other in-
band or out-of-band protocols may be used for establishing data band or out-of-band protocols may be used for establishing data
channels. Each data channel consists of paired SCTP streams sharing channels. Each data channel consists of paired SCTP streams sharing
the same SCTP Stream Identifier. Data channels are created by the same SCTP Stream Identifier. Data channels are created by
skipping to change at page 5, line 5 skipping to change at page 5, line 7
JavaScript application then this stack resides in the browser. If JavaScript application then this stack resides in the browser. If
the application is a native application then this stack resides in the application is a native application then this stack resides in
the application and is accessible via some sort of APIs. the application and is accessible via some sort of APIs.
Data channel properties: Fixed properties assigned to a data Data channel properties: Fixed properties assigned to a data
channel at the time of its creation. Some of these properties channel at the time of its creation. Some of these properties
determine the way the data channel stack transmits data on this determine the way the data channel stack transmits data on this
channel (e.g., stream identifier, reliability, order of channel (e.g., stream identifier, reliability, order of
delivery...). delivery...).
Data channel subprotocol: The application protocol which is
transported over a single data channel. Data channel subprotocol
messages are sent as data channel payload over an established data
channel. If an SDP offer/answer exchange is used as specified in
this document to negotiate the establishment of data channels,
corresponding data channel properties, associated data channel
subprotocols and data channel subprotocol properties, then the
data channel subprotocols may be identified by the values of the
"subprotocol" parameters of the SDP "a=dcmap" attribute as
described in Section 5.1.1.5. Within this document the term "data
channel subprotocol" is often abbreviated as just "subprotocol".
DCEP: Data Channel Establishment Protocol defined in DCEP: Data Channel Establishment Protocol defined in
[I-D.ietf-rtcweb-data-protocol]. [I-D.ietf-rtcweb-data-protocol].
In-band: Transmission through the peer-to-peer SCTP association. In-band: Transmission through the peer-to-peer SCTP association.
Out-of-band: Transmission through the application signaling path. Out-of-band: Transmission through the application signaling path.
Peer: From the perspective of one of the agents in a session, its Peer: From the perspective of one of the agents in a session, its
peer is the other agent. Specifically, from the perspective of peer is the other agent. Specifically, from the perspective of
the SDP offerer, the peer is the SDP answerer. From the the SDP offerer, the peer is the SDP answerer. From the
skipping to change at page 10, line 8 skipping to change at page 10, line 24
5.1.2. Other Media Level Attributes 5.1.2. Other Media Level Attributes
In the SDP, each data channel declaration MAY also be followed by In the SDP, each data channel declaration MAY also be followed by
other media level SDP attributes, which are either specifically other media level SDP attributes, which are either specifically
defined for or applied to the subprotocol in use. Each of these defined for or applied to the subprotocol in use. Each of these
attributes is represented by one new attribute line, and it includes attributes is represented by one new attribute line, and it includes
the contents of a media-level SDP attribute already defined for use the contents of a media-level SDP attribute already defined for use
with this (sub)protocol in another IETF (Internet Engineering Task with this (sub)protocol in another IETF (Internet Engineering Task
Force) document. Subprotocol specific attributes MAY also be defined Force) document. Subprotocol specific attributes MAY also be defined
for exclusive use with data channel transport, but SHOULD use the for exclusive use with data channel transport, but MUST use the same
same syntax described here for other subprotocol related attributes. syntax described here for other subprotocol related attributes.
5.1.2.1. dcsa Attribute 5.1.2.1. dcsa Attribute
Each SDP attribute, related to the subprotocol, that would normally Each SDP attribute, related to the subprotocol, that would normally
be used to negotiate the subprotocol using SDP is replaced with an be used to negotiate the subprotocol using SDP is replaced with an
attribute of the form "a=dcsa:stream-id original-attribute", where attribute of the form "a=dcsa:stream-id original-attribute", where
dcsa stands for "data channel subprotocol attribute", stream-id is dcsa stands for "data channel subprotocol attribute", stream-id is
the SCTP stream identifier assigned to this subprotocol instance, and the SCTP stream identifier assigned to this subprotocol instance, and
original-attribute represents the contents of the subprotocol related original-attribute represents the contents of the subprotocol related
attribute to be included. attribute to be included.
skipping to change at page 21, line 35 skipping to change at page 21, line 35
8.2. New SDP Attributes 8.2. New SDP Attributes
8.2.1. dcmap 8.2.1. dcmap
NOTE to RFC Editor: Please replace "XXXX" with the number of this NOTE to RFC Editor: Please replace "XXXX" with the number of this
RFC. RFC.
This document defines a new SDP media-level attribute "a=dcmap:" as This document defines a new SDP media-level attribute "a=dcmap:" as
follows: follows:
+---------------------+-----------------------------------------+ +-----------------------+-------------------------------------------+
| Attribute name: | dcmap | | Contact name: | MMUSIC Chairs |
| Type of attribute: | media | | Contact email: | mmusic-chairs@ietf.org |
| Mux category: | SPECIAL | | Attribute name: | dcmap |
| Charset Dependent: | No | | Attribute syntax: | As per Section 5.1.1.1 |
| Purpose: | Define data channel specific parameters | | Attribute semantics: | As per Section 5.1.1.1 |
| Appropriate values: | As defined in Section 5.1.1 | | Usage level: | media |
| Contact name: | MMUSIC Chairs | | Charset dependent: | No |
| Contact e-mail: | mmusic-chairs@ietf.org | | Purpose: | Define data channel specific parameters |
| Reference: | RFCXXXX | | Appropriate values: | As per Section 5.1.1.1 |
+---------------------+-----------------------------------------+ | O/A procedures: | As per Section 5.2 |
| Mux category: | SPECIAL. See Section 5.1.1.2 |
| Reference: | RFCXXXX |
+-----------------------+-------------------------------------------+
8.2.2. dcsa 8.2.2. dcsa
NOTE to RFC Editor: Please replace "XXXX" with the number of this NOTE to RFC Editor: Please replace "XXXX" with the number of this
RFC. RFC.
This document defines a new SDP media-level attribute "a=dcsa:" as This document defines a new SDP media-level attribute "a=dcsa:" as
follows: follows:
+---------------------+---------------------------------------------+ +-----------------------+-------------------------------------------+
| Attribute name: | dcsa | | Contact name: | MMUSIC Chairs |
| Type of attribute: | media | | Contact email: | mmusic-chairs@ietf.org |
| Mux category: | SPECIAL | | Attribute name: | dcsa |
| Charset Dependent: | No | | Attribute syntax: | As per Section 5.1.2.1 |
| Purpose: | Define data channel subprotocol specific | | Attribute semantics: | As per Section 5.1.2.1 |
| | attributes | | Usage level: | media |
| Appropriate values: | As defined in Section 5.1.2.1 | | Charset dependent: | No |
| Contact name: | MMUSIC Chairs | | Purpose: | Define data channel subprotocol specific |
| Contact e-mail: | mmusic-chairs@ietf.org | | | attributes |
| Reference: | RFCXXXX | | Appropriate values: | As per Section 5.1.2.1 |
+---------------------+---------------------------------------------+ | O/A procedures: | As per Section 5.2 |
| Mux category: | SPECIAL. See Section 5.1.2.2 |
| Reference: | RFCXXXX |
+-----------------------+-------------------------------------------+
8.3. New Usage Level
This document introduces a new "Data Channel Subprotocol Attribute"
(dcsa) usage level to the SDP to the IANA SDP att-field registry.
SDP attributes that are defined for use at the dcsa usage level only
shall use the dcsa usage level when registering the attribute. If
existing media attributes are used in a datachannel subprotocol
specific way (Section 5.1.2.1), then a new dcsa usage level MUST be
defined for the existing media attribute. Where the SDP attribute is
applicable to a particular subprotocol/s this SHALL also be
registered by indicating the applicable subprotocol identifiers (see
Section 8.1) along with the dcsa usage level. E.g.
+-----------------------+-------------------------------------------+
| ... | ... |
| 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 Roni Even, Christian Groves, Gunnar and Gavin Llewellyn, and to thank Flemming Andreasen, Roni Even,
Hellstrom, Christer Holmberg, Paul Kyzivat, Jonathan Lennox, and Uwe Christian Groves, Gunnar Hellstrom, Christer Holmberg, Paul Kyzivat,
Rauschenbach for their invaluable comments. Jonathan Lennox, and Uwe Rauschenbach for their invaluable comments.
10. CHANGE LOG 10. CHANGE LOG
10.1. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-07' 10.1. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-08'
o Addition of definition of "data channel subprotocol" to Section 3
as proposed on the MMUSIC list, https://www.ietf.org/mail-
archive/web/mmusic/current/msg15827.html.
o Addition of [I-D.ietf-mmusic-rfc4566bis] to list of normative
references.
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].
o Addition of new Section 8.3.
10.2. 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.2. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-06' 10.3. 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.3. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-05' 10.4. 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 23, line 42 skipping to change at page 24, line 32
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.4. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-04' 10.5. 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 24, line 34 skipping to change at page 25, line 26
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.5. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-03' 10.6. 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 25, line 44 skipping to change at page 26, line 36
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.6. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-02' 10.7. 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 26, line 45 skipping to change at page 27, line 37
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.7. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-01' 10.8. 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 5 skipping to change at page 29, line 44
* 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.8. Changes against 'draft-ietf-mmusic-data-channel-sdpneg-00' 10.9. 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 31, line 39 skipping to change at page 32, line 30
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.9. Changes against 'draft-ejzak-mmusic-data-channel-sdpneg-02' 10.10. 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 32, line 41 skipping to change at page 33, line 32
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.10. Changes against '-01' 10.11. 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.11. Changes against '-00' 10.12. 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 33, line 37 skipping to change at page 34, line 29
[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]
Handley, M., Jacobson, V., Perkins, D., and A. Begen,
"SDP: Session Description Protocol", draft-ietf-mmusic-
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,
DOI 10.17487/RFC5234, January 2008, DOI 10.17487/RFC5234, January 2008,
<http://www.rfc-editor.org/info/rfc5234>. <http://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., 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-15 (work in progress), September 2015. mmusic-sctp-sdp-16 (work in progress), February 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-12 Multiplexing", draft-ietf-mmusic-sdp-mux-attributes-13
(work in progress), January 2016. (work in progress), June 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.
[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,
 End of changes. 42 change blocks. 
83 lines changed or deleted 141 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/