MMUSIC                                                     K. Drage, Ed.
Internet-Draft                                               M. Makaraju
Intended status: Standards Track                     J. Stoetzer-Bradler
Expires: January 22, February 5, 2016                                 Alcatel-Lucent
                                                                R. Ejzak
                                                               J. Marcon
                                                            Unaffiliated
                                                           July 21,
                                                          August 4, 2015

                   SDP-based Data Channel Negotiation
                draft-ietf-mmusic-data-channel-sdpneg-03
                draft-ietf-mmusic-data-channel-sdpneg-04

Abstract

   The Real-Time Communication in WEB-browsers (RTCWeb) working group is
   charged to provide protocols to support direct interactive rich
   communications using audio, video, and data between two peers' web-
   browsers.  For the support of data communication, the RTCWeb working
   group has in particular defined the concept of bi-directional data
   channels over SCTP, where each data channel might be used to
   transport other protocols, called sub-protocols.  Data channel setup
   can be done using either the in-band Data Channel Establishment
   Protocol (DCEP) or using some out-of-band non-DCEP protocol.  This
   document specifies how the SDP offer/answer exchange can be used to
   achieve such an out-of-band non-DCEP negotiation.  Even though data
   channels are designed for RTCWeb use initially they may be used by
   other protocols like, but not limited to, the CLUE protocol.  This
   document is intended to be used wherever data channels are used.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on January 22, February 5, 2016.

Copyright Notice

   Copyright (c) 2015 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Conventions . . . . . . . . . . . . . . . . . . . . . . . . .   3   4
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Applicability Statement . . . . . . . . . . . . . . . . . . .   4
   5.  Data Channels . . . . . . . . . . . . . . . . . . . . . . . .   5
     5.1.  Stream Identifier Numbering . . . . . . . . . . . . . . .   5
     5.2.  Generic Non-DCEP Negotiation  . . . . . . . . . . . . . .   6
       5.2.1.  Overview  . . . . . . . . . . . . . . . . . . . . . .   6
       5.2.2.  Opening a Data Channel  . . . . . . . . . . . . . . .   6
       5.2.3.  Closing a Data Channel  . . . . . . . . . . . . . . .   8
   6.
   5.  SDP Offer/Answer Negotiation  . . . . . . . . . . . . . . . .   8
     6.1.   5
     5.1.  SDP Syntax  . . . . . . . . . . . . . . . . . . . . . . .   9
       6.1.1.   5
       5.1.1.  SDP Attribute for Data Channel Parameter Negotiation    9
         6.1.1.1.    5
         5.1.1.1.  dcmap Attribute . . . . . . . . . . . . . . . . .   9
         6.1.1.2.   5
         5.1.1.2.  dcmap-stream-id Parameter . . . . . . . . . . . .  11
         6.1.1.3.   7
         5.1.1.3.  label Parameter . . . . . . . . . . . . . . . . .  11
         6.1.1.4.   7
         5.1.1.4.  subprotocol Parameter . . . . . . . . . . . . . .  11
         6.1.1.5.   7
         5.1.1.5.  max-retr Parameter  . . . . . . . . . . . . . . .  11
         6.1.1.6.   7
         5.1.1.6.  max-time Parameter  . . . . . . . . . . . . . . .  12
         6.1.1.7.   8
         5.1.1.7.  ordered Parameter . . . . . . . . . . . . . . . .  12
       6.1.2.   8
       5.1.2.  Sub-Protocol Specific Attributes  . . . . . . . . . .  12
     6.2.   8
     5.2.  Procedures  . . . . . . . . . . . . . . . . . . . . . . .  14
       6.2.1.  10
       5.2.1.  Managing Stream Identifiers . . . . . . . . . . . . .  14
       6.2.2.  10
       5.2.2.  Negotiating Data Channel Parameters . . . . . . . . .  14
       6.2.3.  10
       5.2.3.  Opening a Data Channel  . . . . . . . . . . . . . . .  15
       6.2.4.  11
       5.2.4.  Closing a Data Channel  . . . . . . . . . . . . . . .  17
       6.2.5.  13
       5.2.5.  Various SDP Offer/Answer Scenarios and Considerations  18
   7.  14
   6.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .  19
   8.  15
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  21
   9.  17
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  21
     9.1.  17
     8.1.  Subprotocol Identifiers . . . . . . . . . . . . . . . . .  21
     9.2.  17
     8.2.  New SDP Attributes  . . . . . . . . . . . . . . . . . . .  22
       9.2.1.  18
       8.2.1.  dcmap . . . . . . . . . . . . . . . . . . . . . . . .  22
       9.2.2.  18
       8.2.2.  dcsa  . . . . . . . . . . . . . . . . . . . . . . . .  22
   10.  18
   9.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  22
   11.  18
   10. CHANGE LOG  . . . . . . . . . . . . . . . . . . . . . . . . .  22
     11.1.  18
     10.1.  Changes against 'draft-ietf-mmusic-data-channel-
            sdpneg-03' . . . . . . . . . . . . . . . . . . . . . . .  18
     10.2.  Changes against 'draft-ietf-mmusic-data-channel-
            sdpneg-02' . . . . . . . . . . . . . . . . . . . . . . .  22
     11.2.  19
     10.3.  Changes against 'draft-ietf-mmusic-data-channel-
            sdpneg-01' . . . . . . . . . . . . . . . . . . . . . . .  23
     11.3.  20
     10.4.  Changes against 'draft-ietf-mmusic-data-channel-
            sdpneg-00' . . . . . . . . . . . . . . . . . . . . . . .  25
     11.4.  23
     10.5.  Changes against 'draft-ejzak-mmusic-data-channel-
            sdpneg-02' . . . . . . . . . . . . . . . . . . . . . . .  28
     11.5.  25
     10.6.  Changes against '-01'  . . . . . . . . . . . . . . . . .  29
     11.6.  26
     10.7.  Changes against '-00'  . . . . . . . . . . . . . . . . .  29
   12.  27
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  30
     12.1.  27
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  30
     12.2.  27
     11.2.  Informative References . . . . . . . . . . . . . . . . .  31
   Authors' Addresses  28
   Appendix A.  Generic Data Channel Negotiation Aspects When Not
                Using DCEP . . . . . . . . . . . . . . . . . . . . .  29
     A.1.  Stream Identifier Numbering . .  32

1.  Introduction

   The RTCWeb working group has defined the concept of . . . . . . . . . . . . .  30
     A.2.  Generic Data Channel Negotiation Not Using DCEP . . . . .  30
       A.2.1.  Overview  . . . . . . . . . . . . . . . . . . . . . .  30
       A.2.2.  Opening a Data Channel  . . . . . . . . . . . . . . .  31
       A.2.3.  Closing a Data Channel  . . . . . . . . . . . . . . .  32
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  32

1.  Introduction

   The RTCWeb working group has defined the concept of bi-directional
   data channels running on top of SCTP/DTLS.  RTCWeb leaves it open for
   other applications to use data channels and its in-band DCEP or out-
   of-band non-DCEP other
   in-band or out-of-band protocols for creating them.  Each data
   channel consists of paired SCTP streams sharing the same SCTP Stream
   Identifier.  Data channels are created by endpoint applications
   through the WebRTC API, or other users of data channel like CLUE, and
   can be used to transport proprietary or well-defined protocols, which
   in the latter case can be signaled by the data channel "sub-protocol"
   parameter, conceptually similar to the WebSocket "sub-protocol".
   However, apart from the "sub-protocol" value transmitted to the peer,
   RTCWeb leaves it open how endpoint applications can agree on how to
   instantiate a given sub-protocol on a data channel, and whether it is
   signaled in-band using DCEP or out-of-band using a non-DCEP protocol
   (or both).  In particular, the SDP offer generated by the application RTCweb data
   channel stack includes no channel-specific information.

   This document defines SDP offer/answer negotiation procedures to
   establish data channels for transport of well-defined sub-protocols,
   to enable out-of-band negotiation.

2.  Conventions

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

3.  Terminology

   This document uses the following terms:

      Data channel: A WebRTC data channel as specified in
      [I-D.ietf-rtcweb-data-channel].

      Data channel stack: An entity which, upon application request,
      runs the data channel protocol to keep track of states, sending
      and receive data.  If the application is a browser based
      JavaScript application then this stack resides in the browser.  If
      the application is a native application then this stack resides in
      the application and is accessible via some sort of APIs.

      Data channel properties: Fixed properties assigned to a data
      channel at the time of its creation.  Some of these properties
      determine the way the data channel stack transmits data on this
      channel (e.g., stream identifier, reliability, order of
      delivery...).

      DCEP: Data Channel Establishment Protocol defined in
      [I-D.ietf-rtcweb-data-protocol].

      In-band: Transmission through the peer-to-peer SCTP association.

      Out-of-band: Transmission through the application signaling path.

      Peer: From the perspective of one of the agents in a session, its
      peer is the other agent.  Specifically, from the perspective of
      the SDP offerer, the peer is the SDP answerer.  From the
      perspective of the SDP answerer, the peer is the SDP offerer.

      SCTP Stream Sequence Number (SSN): the SCTP stream sequence number
      as specified in [RFC4960].

      Stream identifier: The identifier of the outbound and inbound SCTP
      streams composing a data channel.

4.  Applicability Statement

   The mechanism in this specification only applies to the Session
   Description Protocol (SDP) [RFC4566], when used together with the SDP
   offer/answer mechanism [RFC3264].  Declarative usage of SDP is out of
   scope of this document, and is thus undefined.

5.  Data Channels  SDP Offer/Answer Negotiation

   This section summarizes defines an SDP extension by which two clients can
   negotiate data channel-specific and sub-protocol-specific parameters
   without using DCEP [I-D.ietf-rtcweb-data-protocol].  This SDP
   extension only defines usage in the context of SDP offer/answer.

   Appendix A provides information how data channels work in general.

   A WebRTC application creates a data channel by providing a number of
   setup parameters (sub-protocol, label, reliability, order of
   delivery, priority).  The application also specifies if it wants to
   make use of general and
   especially summarizes some key aspects, which should be considered
   for the negotiation using the DCEP
   [I-D.ietf-rtcweb-data-protocol], or if the application intends to
   negotiate of data channels using the if DCEP is not used.

5.1.  SDP offer/answer protocol.

   In any case, the Syntax

   Two new SDP attributes are defined to support SDP offer/answer
   negotiation of data channels.  The first attribute provides for
   negotiation of channel-specific parameters.  The second attribute
   provides for negotiation of sub-protocol-specific parameters.

5.1.1.  SDP Attribute for Data Channel Parameter Negotiation

   Associated with the SDP offer generated by the browser is per
   [I-D.ietf-mmusic-sctp-sdp].  In brief, it contains one "m" line for that defines the SCTP association on top of which
   for data channels will run:

   m=application 54111 UDP/DTLS/SCTP webrtc-datachannel
   c=IN IP4 79.97.215.79
   a=max-message-size:100000
   a=sctp-port 5000
   a=setup:actpass
   a=connection:new
   a=fingerprint:SHA-1 \
       4A:AD:B9:B1:3F:82:18:3B:54:02:12:DF:3E:5D:49:6B:19:E5:7C:AB

   Note: A WebRTC browser will only use "m" line format "webrtc-
   datachannel", and will not use other formats (defined in Section 4), each SDP offer and answer
   includes one "a=dcmap:" attribute that defines the "m" line data channel
   parameters for
   other protocols such as t38.  [I-D.ietf-mmusic-sctp-sdp] supports
   only one SCTP association each data channel to be established on top of negotiated.  Each such
   attribute line specifies the following parameters for a DTLS session.

   Note: This SDP syntax does not contain any channel-specific
   information.

5.1.  Stream Identifier Numbering

   [Editor's note: This entire Section 5.1 could possibly be removed as
   there is another section (Section 6.2.1) which is dedicated to data channel:
   SCTP stream id usage.]

   Independently from the requested type identifier, sub-protocol, label, reliability, order of negotiation, the application
   creating a data channel can either pass
   delivery, and priority.

   The intention in exchanging these attributes is to create, on two
   peers, without use of DCEP [I-D.ietf-rtcweb-data-protocol], matched
   pairs of oppositely directed data channels having the browser the stream
   identifier to assign to same set of
   attributes.  It is assumed that the data channel or else let the browser pick
   one identifier from properties
   (reliable/partially reliable, ordered/unordered) are suitable per the ones unused.

   To avoid glare situations, each endpoint can moreover own an
   exclusive set of stream identifiers, in which case an endpoint can
   only create a data channel with
   sub-protocol transport requirements.

5.1.1.1.  dcmap Attribute

   "a=dcmap:" is a stream identifier it owns.

   Which set of stream identifiers media level attribute having following ABNF syntax.

   Formal Syntax:

   Name: dcmap

   Value: dcmap-value

   Usage Level: media

   Charset Dependent: no

   Syntax:

   dcmap-value     = dcmap-stream-id
                     [ SP dcmap-opt *(";" dcmap-opt) ]
   dcmap-opt       = ordering-opt / subprotocol-opt / label-opt
                     / maxretr-opt / maxtime-opt
                     ; Either only maxretr-opt or maxtime-opt
                     ; is owned by present.

   dcmap-stream-id = 1*DIGIT
   ordering-opt    = "ordered=" ordering-value
   ordering-value  = "true" / "false"
   subprotocol-opt = "subprotocol=" quoted-string
   label-opt       = "label=" quoted-string
   maxretr-opt     = "max-retr=" maxretr-value
   maxretr-value   = <from-Reliability-Parameter of
                      I-D.ietf-rtcweb-data-protocol>
                     ; number of retransmissions
   maxtime-opt     = "max-time=" maxtime-value
   maxtime-value   = <from-Reliability-Parameter of
                     I-D.ietf-rtcweb-data-protocol>
                     ; milliseconds

   quoted-string   = DQUOTE *(quoted-char / escaped-char) DQUOTE
   quoted-char     = SP / quoted-visible
   quoted-visible  = %21 / %23-24 / %26-7E ; VCHAR without " or %
   escaped-char    = "%" HEXDIG HEXDIG
   DQUOTE          = <from-RFC5234>
   integer         = <from-RFC5234>

   Examples:

   a=dcmap:0
   a=dcmap:1 subprotocol="BFCP";max-time=60000
   a=dcmap:2 subprotocol="MSRP";ordered=true;label="MSRP"
   a=dcmap:3 label="Label 1";ordered=false;max-retr=5
   a=dcmap:4 label="foo%09bar";ordered=true;max-time=15000;max-retr=3
      Note: The last example (a=dcmap:4) shows a 'label' parameter value
      which endpoint is
   determined by convention contains one non-printable 'escaped-char' character (the
      tabulator character).

   Within an 'a=dcmap' attribute line's 'dcmap-opt' value either only
   one 'maxretr-opt' parameter or other means.

      For data channels negotiated with the DCEP, one endpoint owns by
      convention 'maxtime-opt' parameter MAY be
   present.  Both MUST NOT be present.

5.1.1.2.  dcmap-stream-id Parameter

   The 'dcmap-stream-id' parameter indicates the even SCTP stream identifiers, whereas identifier
   within the other owns SCTP association used to form the
      odd stream identifiers, as defined in
      [I-D.ietf-rtcweb-data-protocol].

      For data channels negotiated via some non-DCEP protocol, no
      convention is defined by default.

5.2.  Generic Non-DCEP Negotiation

   [Editor's note: As this document now focuses on SDP offer/answer
   negotiation only, should this entire Section 5.2 (and all its sub-
   sections) be removed?  Parts channel.

5.1.1.3.  label Parameter

   The 'label' parameter indicates the name of the information provided in these
   sub-sections might channel.  It
   represents a label that can be moved used to Section 6, Section 6.2.1 and
   Section 6.2.3 as indicated below distinguish, in further editor notes.  Another
   option might be the context of
   the WebRTC API [WebRtcAPI], an RTCDataChannel object from other
   RTCDataChannel objects.  This parameter maps to move this section and the 'Label' parameter
   defined in [I-D.ietf-rtcweb-data-protocol].  The 'label' parameter is
   optional.  If it is not present, then its sub-section value defaults to an
   informative appendix.]

5.2.1.  Overview

   DCEP negotiation only provides for negotiation of data channel
   transport parameters and does not provide for negotiation of sub-
   protocol specific parameters.  Non-DCEP negotiation can the empty
   string.

   Note: The empty string MAY also be defined explicitly used as 'label' value,
   such that 'label=""' is equivalent to
   allow negotiation of parameters beyond those handled by DCEP
   negotiation, e.g., parameters specific the 'label' parameter not being
   present at all.  [I-D.ietf-rtcweb-data-protocol] allows the
   DATA_CHANNEL_OPEN message's 'Label' value to be an empty string.

5.1.1.4.  subprotocol Parameter

   The 'subprotocol' parameter indicates which protocol the client
   expects to exchange via the sub-protocol
   instantiated on a particular data channel.  See Section 6.1.2 for  'Subprotocol' is an
   example of such a optional
   parameter.

   [Editor's note: The information in  If the preceding paragraph might be
   moved 'subprotocol' parameter is not present, then its
   value defaults to Section 6.] the empty string.

5.1.1.5.  max-retr Parameter

   This parameter indicates that the data channel is partially reliable.
   The following procedures are common to all methods of non-DCEP
   negotiation, whether in-band (communicated using proprietary means on
   an already established data channel) or out-of-band (using SDP offer/
   answer or some other protocol associated with the signaling channel).

   [Editor's note: The preceding paragraph could be deleted.]

5.2.2.  Opening a Data Channel

   In 'max-retr' parameter indicates the case maximal number of non-DCEP negotiation, times a user
   message will be retransmitted.  The max-retr parameter is optional.
   If the endpoint application has max-retr parameter is not present, then the
   option to fully control maximal number of
   retransmissions is determined as per the stream identifier assignments.  However
   these assignments have generic SCTP retransmission
   rules as specified in [RFC4960].  This parameter maps to coexist with the assignments controlled by 'Number
   of RTX' parameter defined in [I-D.ietf-rtcweb-data-protocol].

5.1.1.6.  max-time Parameter

   This parameter indicates that the data channel stack for is partially reliable.
   A user message will no longer be transmitted or retransmitted after a
   specified life-time given in milliseconds in the DCEP negotiated data channels (if
   any).  It 'max-time'
   parameter.  The max-time parameter is optional.  If the responsibility of max-time
   parameter is not present, then the application to ensure
   consistent assignment of stream identifiers.

   [Editor's note: The information generic SCTP retransmission timing
   rules apply as specified in the preceding paragraph could be
   moved [RFC4960].  This parameter maps to Section 6.2.1.]

   When the application requests
   'Lifetime in ms' parameter defined in
   [I-D.ietf-rtcweb-data-protocol].

5.1.1.7.  ordered Parameter

   The 'ordered' parameter with value "true" indicates that the receiver
   MUST dispatch DATA chunks in the creation of a new data channel to
   be set up via non-DCEP negotiation, the data channel stack creates upper layer
   while preserving the data channel locally without sending any DATA_CHANNEL_OPEN
   message in-band [Editor's note: order.  The information in this first part of
   the sentence could be moved to section 6.2.3], and sets the data
   channel state to Connecting if the SCTP association ordered parameter is not yet
   established, or sets the data channel state to Open if optional and
   takes two values: "true" for ordered and "false" for unordered
   delivery with "true" as the SCTP
   association default value.  Any other value is already established.  The side which starts non-DCEP
   negotiation creates a data channel using underlying data channel
   stack API
   ignored and the data channel default "ordered=true" is put into open state immediately
   (assuming ICE, SCTP procedures were already done).  [Editor's note:
   The API related information could be deleted.]  However, assumed.  In the
   application can't send data on absence of
   this data channel until non-DCEP
   negotiation parameter "ordered=true" is complete with the peer. assumed.  This is because the peer
   needs parameter maps to be aware and accept the
   ordered or unordered data channel via non-DCEP
   negotiation.  The peer after accepting types as defined in
   [I-D.ietf-rtcweb-data-protocol].

5.1.2.  Sub-Protocol Specific Attributes

   In the SDP, each data channel offer can
   start sending data immediately.  This implies that declaration MAY also be followed by
   other SDP attributes specific to the offerer may
   get data channel sub-protocol messages before non-DCEP negotiation in use.  Each of
   these attributes is
   complete represented by one new attribute line, and it
   includes the application should be ready to handle it.  [Editor's
   note: The information contents of a media-level SDP attribute already defined
   for use with this (sub)protocol in these last four sentences could another IETF specification.  Sub-
   protocol-specific attributes might also be moved to
   Section 6.2.3.]

   If the peer rejects the defined for exclusive use
   with data channel part of the offer then it
   doesn't have to do anything as transport, but should use the data channel was not created same syntax described
   here for other sub-protocol-specific attributes.

   Each sub-protocol specific SDP attribute that would normally be used
   to negotiate the subprotocol using SDP is replaced with an attribute
   of the stack.  The offerer on form "a=dcsa:stream-id original-attribute", where dcsa stands
   for "data channel sub-protocol attribute", stream-id is the other hand needs SCTP
   stream identifier assigned to close this sub-protocol instance, and
   original-attribute represents the data
   channel that was opened by invoking relevant data channel stack API
   procedures.

   [Editor's note: The information in contents of the preceding paragraph could be
   moved sub-protocol
   related attribute to Section 6.2.3 (to a new bullet point there).]

   It is also worth noting be included.

   Formal Syntax:

   Name: dcsa

   Value: dcsa-value

   Usage Level: media

   Charset Dependent: no

   Syntax:

   dcsa-value      = stream-id SP attribute
   attribute       = <from-RFC4566>

   Example:

   a=dcsa:2 accept-types:text/plain

   Note that a data channel stack implementation may the above reference to RFC 4566 defines where the attribute
   definition can be found; it does not provide any API to create and close data channels; instead the
   data channels are used limitation on the fly
   support of attributes defined in other documents in accordance with
   this attribute definition.  Note however that not all SDP attributes
   are suitable as needed just by communicating via
   non-DCEP means "a=dcsa:" parameter.  [IANA-SDP-Parameters] contains
   the lists of IANA registered session and media level or media level
   only SDP attributes.

   Thus in the example above, the original attribute line "a=accept-
   types:text/plain" is represented by even having some local configuration/assumptions the attribute line "a=dcsa:2
   accept-types:text/plain", which specifies that this instance of MSRP
   being transported on both the peers.

   [Editor's note: The preceding paragraph could be deleted.]

   The application then negotiates SCTP association using the data channel properties and sub-
   protocol properties with
   stream id 2 accepts plain text files.

   As opposed to the peer's application using a mechanism
   different from DCEP.

   [Editor's note: The preceding paragraph could be deleted.]

   [ASSUMPTION] The peer MUST then symmetrically create a data channel
   with "a=dcmap:" attribute parameters, these negotiated data channel properties.  This is
   parameters are subject to offer/answer negotiation following the only way
   procedures defined in the sub-protocol specific documents.

   The same syntax applies to any other SDP attribute required for
   negotiation of this instance of the peer's sub-protocol.

   Note: This document does not provide a complete specification of how
   to negotiate the use of a data channel stack to know which properties transport MSRP.  Procedures
   specific to apply
   when transmitting data on this channel.  [Editor's note: The previous
   sentence could each sub-protocol such as MSRP will be deleted.] documented
   elsewhere.  The data channel stack MUST allow data
   channel creation with any non-conflicting stream identifier so that
   both peers can create use of MSRP is only an example of how the data channel with generic
   procedures described herein might apply to a specific sub-protocol.

5.2.  Procedures

5.2.1.  Managing Stream Identifiers

   If an SDP offer/answer exchange (could be the same stream
   identifier.  [Editor's note: The information initial or a subsequent
   one) results in a UDP/DTLS/SCTP or TCP/DTLS/SCTP based media
   description being accepted, and if this sentence could
   be moved to Section 6.2.3.]

   In case the non-DCEP negotiation is correlated with an SDP offer/
   answer offer/answer exchange that establishes
   results in the establishment of a new SCTP association, then the SCTP
   initialization completion triggers a callback from the data channel
   stack to an application on both the ends to change SDP
   offerer owns the data channel
   state from Connecting to Open.  The details even SCTP stream ids of this interface is
   specific to the data channel user application.  Browser based
   applications (could include hybrid apps) will use [WebRtcAPI], while
   native applications use a compatible API, which is yet to be
   specified.  See Section 6.2.3 for details on when the data channel
   stack can assume the data channel is open, new SCTP association
   and on when the
   application can assume answerer owns the data channel odd SCTP stream identifiers.  If this "m"
   line is open.

   [Editor's note: The preceding paragraph could be deleted.]

5.2.3.  Closing a Data Channel

   When the application requests removed from the closing signaling session (its port number set to
   zero), and if usage of this or of a non-DCEP negotiated
   data channel, the data channel stack always performs an new UDP/DTLS/SCTP or TCP/DTLS/
   SCTP SSN
   reset for this channel.

   [Editor's note: The preceding paragraph could be deleted.]

   Depending upon based "m" line is renegotiated later on, then the method used for non-DCEP negotiation even and the sub-
   protocol associated with the data channel, the closing might in
   addition be signaled to the peer via non-DCEP odd
   SCTP stream identifier ownership is redetermined as well as described
   above.

   This specification allows simultaneous use of SDP offer/answer and
   DCEP negotiation.

   [Editor's note: The preceding paragraph could  However, an SCTP stream MUST NOT be deleted.]

6.  SDP Offer/Answer Negotiation

   This section defines referenced in
   a method dcmap or dcsa attribute of non-DCEP negotiation by which two
   clients can negotiate data channel-specific and sub-protocol-specific
   parameters, using the out-of-band an SDP offer/answer exchange.  This exchange if the
   associated SCTP stream has already been negotiated via DCEP.  Stream
   ids that are not currently used in SDP extension can only be used with the for DCEP
   negotiation.  Stream id allocation per SDP offer/answer model.

6.1.  SDP Syntax

   Two new SDP attributes are defined to support negotiation
   may not align with DTLS role based allocation.  This could cause
   glare conditions when one side trying to do SDP offer/answer
   negotiation of on a stream id while the other end trying to open a data channels.  The first attribute provides for
   negotiation of channel-specific parameters.  The second attribute
   provides for negotiation of sub-protocol-specific parameters.

6.1.1.  SDP Attribute for Data Channel Parameter Negotiation

   Associated with
   channel on the SDP "m" line same stream id using DCEP negotiation.  To avoid these
   glare conditions this specification recommends that defines the SCTP association
   for data channels (defined in Section 4), each channel
   stack user always selects stream ids per above described SDP offer and offer/
   answer
   includes one "a=dcmap:" attribute that defines rule even when DCEP negotiation is used.  To avoid glare
   conditions, it is possible to come up with a different stream id
   allocation scheme, but such schemes are outside the scope of this
   specification.

5.2.2.  Negotiating Data Channel Parameters

   Conveying a reliable data channel
   parameters for each data channel to be negotiated.  Each such is achieved by including neither
   'max-retr' nor 'max-time' in corresponding SDP offer's or answer's
   "a=dcmap" attribute line specifies the following parameters for line.  Conveying a partially reliable data channel:
   SCTP stream identifier, sub-protocol, label, reliability, order
   channel is achieved by including only one of
   delivery, 'max-retr' or 'max-
   time'.  By definition max-retr and priority.

   The intention max-time are mutually exclusive,
   so at most one of exchanging these attributes is to create data
   channels on both the peers with them MAY be present in the same set "a=dcmap" attribute
   line.  If an SDP offer contains both of attributes without
   actually using these parameters then the DCEP [I-D.ietf-rtcweb-data-protocol].  It is
   assumed that
   receiver of such an SDP offer MUST reject the SDP offer.  If an SDP
   answer contains both of these parameters then the offerer MAY treat
   it as an error and MAY assume the associated SDP offer/answer failed
   and MAY take appropriate recovery actions.  These recovery options
   are outside the scope of this specification.

   The SDP answer SHALL echo the same subprotocol, max-retr, max-time,
   ordered parameters, if those were present in the offer, and MAY
   include a label parameter.  They MAY appear in any order, which could
   be different from the SDP offer, in the SDP answer.

   When sending a subsequent offer or an answer, and for as long as the
   data channel properties (reliable/partially
   reliable, ordered/unordered) is still open, the sender MUST replicate the same
   information.

   Data channel types defined in [I-D.ietf-rtcweb-data-protocol] are suitable per
   mapped to SDP in the sub-protocol
   transport requirements.

6.1.1.1.  dcmap Attribute

   "a=dcmap:" is a media level attribute having following ABNF syntax.

   Formal Syntax:

   Name: dcmap

   Value: dcmap-value

   Usage Level: media

   Charset Dependent: no

   Syntax:

   dcmap-value     = dcmap-stream-id
                     [ SP dcmap-opt *(";" dcmap-opt) ]
   dcmap-opt       = ordering-opt / subprotocol-opt / label-opt
                     / maxretr-opt / maxtime-opt
                     ; Either only maxretr-opt or maxtime-opt
                     ; manner, where "ordered=true" is present.

   dcmap-stream-id = 1*DIGIT
   ordering-opt    = "ordered=" ordering-value
   ordering-value  = "true" / "false"
   subprotocol-opt = "subprotocol=" quoted-string
   label-opt       = "label=" quoted-string
   maxretr-opt     = "max-retr=" maxretr-value
   maxretr-value   = <from-Reliability-Parameter of
                      I-D.ietf-rtcweb-data-protocol>
                     ; number the
   default and may be omitted:

   DATA_CHANNEL_RELIABLE
         ordered=true

   DATA_CHANNEL_RELIABLE_UNORDERED
         ordered=false

   DATA_CHANNEL_PARTIAL_RELIABLE_REXMIT
         ordered=true;max-retr=<number of retransmissions
   maxtime-opt     = "max-time=" maxtime-value
   maxtime-value   = <from-Reliability-Parameter retransmissions>

   DATA_CHANNEL_PARTIAL_RELIABLE_REXMIT_UNORDERED
         ordered=false;max-retr=<number of
                     I-D.ietf-rtcweb-data-protocol>
                     ; milliseconds

   quoted-string   = DQUOTE *(quoted-char / escaped-char) DQUOTE
   quoted-char     = SP / quoted-visible
   quoted-visible  = %21 / %23-24 / %26-7E ; VCHAR without " or %
   escaped-char    = "%" HEXDIG HEXDIG
   DQUOTE          = <from-RFC5234>
   integer         = <from-RFC5234>

   Examples:

   a=dcmap:0
   a=dcmap:1 subprotocol="BFCP";max-time=60000
   a=dcmap:2 subprotocol="MSRP";ordered=true;label="MSRP"
   a=dcmap:3 label="Label 1";ordered=false;max-retr=5
   a=dcmap:4 label="foo%09bar";ordered=true;max-time=15000;max-retr=3
      Note: retransmissions>

   DATA_CHANNEL_PARTIAL_RELIABLE_TIMED
         ordered=true;max-time=<lifetime in milliseconds>

   DATA_CHANNEL_PARTIAL_RELIABLE_TIMED_UNORDERED
         ordered=false;max-time=<lifetime in milliseconds>

5.2.3.  Opening a Data Channel

   The last example (a=dcmap:4) shows procedure for opening a 'label' parameter value
      which contains one non-printable 'escaped-char' character (the
      tabulator character).

   Within data channel using SDP offer/answer
   negotiation starts with the agent preparing to send an 'a=dcmap' attribute line's 'dcmap-opt' value either only
   one 'maxretr-opt' parameter or one 'maxtime-opt' parameter MAY SDP offer.  If
   a peer receives an SDP offer before starting to send a new SDP offer
   with data channels that are to be
   present.  Both SDP offer/answer negotiated, or
   loses an SDP offer glare resolution procedure in this case, it MUST NOT be present.

6.1.1.2.  dcmap-stream-id Parameter

   The 'dcmap-stream-id' parameter indicates
   wait until the SCTP stream identifier
   within ongoing SDP offer/answer completes before resuming the SCTP association used
   SDP offer/answer negotiation procedure.

   The agent that intends to form the send an SDP offer to create data channel.

6.1.1.3.  label Parameter

   The 'label' parameter indicates channels
   through SDP offer/answer negotiation performs the name of following:

   o  Creates data channels using stream identifiers from the channel.  It
   represents owned set
      (see Section 5.2.1).

   o  Generates a label that can be used to distinguish, in new SDP offer.

   o  Determines the context list of
   the WebRTC API [WebRtcAPI], an RTCDataChannel object from other
   RTCDataChannel objects.  This parameter maps to the 'Label' parameter
   defined in [I-D.ietf-rtcweb-data-protocol].  The 'label' parameter is
   optional.  If it is not present, then its value defaults stream identifiers assigned to data
      channels opened through SDP offer/answer negotiation.

   o  Completes the empty
   string.

   Note: The empty string MAY also be explicitly used as 'label' value,
   such that 'label=""' is equivalent to SDP offer with the 'label' parameter not being
   present at all.  [I-D.ietf-rtcweb-data-protocol] allows dcmap and dcsa attributes needed,
      if any, for each SDP offer/answer negotiated data channel, as
      described in Section 5.1 and in Section 5.2.2.

   o  Sends the
   DATA_CHANNEL_OPEN message's 'Label' value to be an empty string.

6.1.1.4.  subprotocol Parameter SDP offer.

   The 'subprotocol' parameter indicates which protocol the client
   expects to exchange via the channel.  'Subprotocol' is peer receiving such an optional
   parameter.  If SDP offer performs the 'subprotocol' parameter is not present, then its
   value defaults to following:

   o  Parses and applies the empty string.

6.1.1.5.  max-retr Parameter

   This parameter indicates SDP offer.  Note that the typical parser
      normally ignores unknown SDP attributes, which includes data
      channel is partially reliable.
   The 'max-retr' parameter indicates related attributes.

   o  Analyzes the maximal number a user message
   will be retransmitted.  The max-retr parameter is optional.  If channel parameters and sub-protocol attributes to
      determine whether to accept each offered data channel.

   o  For accepted data channels, it creates peer instances for the
   max-retr parameter is not present, then data
      channels with the maximal number of
   retransmissions is determined as per agent using the generic SCTP retransmission
   rules as specified channel parameters described in [RFC4960].  This parameter maps to
      the 'Number
   of RTX' parameter defined in [I-D.ietf-rtcweb-data-protocol].

6.1.1.6.  max-time Parameter

   This parameter indicates SDP offer.  Note that the data channel agent is partially reliable.
   A user message will no longer be transmitted or retransmitted after a
   specified life-time given in milliseconds asked to create data
      channels with SCTP stream identifiers contained in the 'max-time'
   parameter.  The max-time parameter is optional.  If SDP offer
      if the max-time
   parameter SDP offer is not present, then accepted.

   o  Generates an SDP answer.

   o  Completes the generic SCTP retransmission timing
   rules apply as specified in [RFC4960].  This parameter maps to SDP answer with the
   'Lifetime dcmap and optional dcsa
      attributes needed for each SDP offer/answer negotiated data
      channel, as described in ms' parameter defined Section 5.1 and in
   [I-D.ietf-rtcweb-data-protocol].

6.1.1.7.  ordered Parameter Section 5.2.2.

   o  Sends the SDP answer.

   The 'ordered' parameter with value "true" indicates that agent receiving such an SDP answer performs the receiver
   MUST dispatch DATA chunks following:

   o  Closes any created data channels for which the expected dcmap and
      dcsa attributes are not present in the data channel to SDP answer.

   o  Applies the upper layer
   while preserving SDP answer.

   Each agent application MUST wait to send data until it has
   confirmation that the order.  The ordered parameter is optional and
   takes two values: "true" for ordered and "false" for unordered
   delivery with "true" as data channel at the default value.  Any other value is
   ignored and default "ordered=true" peer is assumed.  In the absence of instantiated.  For
   WebRTC, this parameter "ordered=true" is assumed. when both data channel stacks have channel parameters
   instantiated.  This parameter maps to the
   ordered or unordered occurs:

   o  At both peers when a data channel types is created without an
      established SCTP association, as soon as defined in
   [I-D.ietf-rtcweb-data-protocol].

6.1.2.  Sub-Protocol Specific Attributes

   In the SDP, each data channel declaration MAY also be followed by
   other SDP attributes specific to the sub-protocol in use.  Each of
   these attributes SCTP association is represented by one new attribute line, and it
   includes
      successfully established.

   o  At the contents of a media-level agent receiving an SDP attribute already defined
   for use with this (sub)protocol in another IETF specification.  Sub-
   protocol-specific attributes might also be defined offer for exclusive use
   with which there is an
      established SCTP association, as soon as it creates an SDP offer/
      answer negotiated data channel transport, but should use based on information signaled in
      the same syntax described
   here for other sub-protocol-specific attributes.

   Each sub-protocol specific SDP attribute that would normally be used
   to negotiate offer.

   o  At the subprotocol using agent sending an SDP offer to create a new SDP offer/answer
      negotiated data channel for which there is replaced with an attribute established SCTP
      association, when it receives the SDP answer confirming acceptance
      of the form "a=dcsa:stream-id original-attribute", where dcsa stands
   for "data data channel sub-protocol attribute", stream-id or when it begins to receive data on the data
      channel from the peer, whichever occurs first.

   Note: DCEP is not used, that is neither the SCTP
   stream identifier assigned to this sub-protocol instance, and
   original-attribute represents SDP offerer nor the contents SDP
   answerer send an in-band DCEP DATA_CHANNEL_OPEN message.

5.2.4.  Closing a Data Channel

   When the application requests the closing of a data channel that was
   negotiated via SDP offer/answer, the sub-protocol
   related attribute data channel stack always
   performs an SCTP SSN reset for this channel.

   It is specific to the sub-protocol whether this closing MUST in
   addition be included.

   Formal Syntax:

   Name: dcsa

   Value: dcsa-value

   Usage Level: media

   Charset Dependent: no

   Syntax:

   dcsa-value      = stream-id SP attribute
   attribute       = <from-RFC4566>

   Example:

   a=dcsa:2 accept-types:text/plain

   Note that the above reference signaled to RFC 4566 defines where the attribute
   definition peer via a new SDP offer/answer exchange.

   The intention to close a data channel can be found; it does not provide any limitation on
   support of attributes defined in other documents in accordance with
   this attribute definition.  Note however that not all signaled by sending a
   new SDP attributes
   are suitable as "a=dcsa:" parameter.  [IANA-SDP-Parameters] contains offer which excludes the lists of IANA registered session "a=dcmap:" and media level or media level
   only SDP attributes.

   Thus in "a=dcsa:" attribute
   lines for the example above, data channel.  The offerer SHOULD NOT change the original attribute line "a=accept-
   types:text/plain" is represented by port
   value for the attribute "m" line "a=dcsa:2
   accept-types:text/plain", which specifies that this instance of MSRP (e.g. to zero) when closing a data channel
   (unless all data channels are being transported on closed and the SCTP association using
   is no longer needed), since this would close the SCTP association and
   impact all of the data channel with
   stream id 2 channels.  If the answerer accepts plain text files.

   As opposed to the SDP
   offer then the answerer MUST close those data channel channels whose
   "a=dcmap:" and "a=dcsa:" attribute parameters, these
   parameters are subject to offer/answer negotiation following lines were excluded from the
   procedures defined
   received SDP offer, unless those data channels were already closed,
   and the answerer MUST also exclude the corresponding attribute lines
   in the sub-protocol specific documents.

   The same syntax applies answer.  In addition to any other SDP attribute required for
   negotiation of this instance of that, the sub-protocol.

   Note: This document does SDP answerer MAY exclude
   other data channels which were closed but not provide a complete specification of how yet communicated to negotiate the use of a data channel
   peer.  So, the offerer MUST inspect the answer to transport MSRP.  Procedures
   specific see if it has to each sub-protocol such as MSRP will be documented
   elsewhere.  The use of MSRP is only an example of how
   close other data channels which are now not included in the generic
   procedures described herein might apply to a specific sub-protocol.

6.2.  Procedures

6.2.1.  Managing Stream Identifiers answer.

   If an a new SDP offer/answer exchange (could is used to close data channels then the
   data channel(s) SHOULD only be closed by the initial or answerer/offerer after a subsequent
   one) results
   successful SDP answer is sent/received.

      This delayed closure is RECOMMENDED in order to handle cases where
      a UDP/DTLS/SCTP or TCP/DTLS/SCTP based media
   description being accepted, and if this successful SDP offer/answer exchange
   results answer is not received, in which case the establishment state
      of the session SHOULD be kept per the last successful SDP offer/
      answer.

   If a new client receives a data channel close indication (due to inband
   SCTP association, SSN reset or some other reason) without associated SDP offer
   then the client SHOULD generate an SDP
   offerer owns the even SCTP stream ids of offer which excludes this new SCTP association
   and the answerer owns
   closed data channel.

   The application MUST also close any data channel that was negotiated
   via SDP offer/answer, for which the odd SCTP stream identifiers.  If this "m"
   line is removed from the signaling session (its port number set to
   zero), and if usage of this or of a new UDP/DTLS/SCTP or TCP/DTLS/
   SCTP based "m" line is renegotiated later on, then the even and odd
   SCTP stream identifier ownership is redetermined as well as described
   above.

   This specification allows simultaneous use of SDP offer/answer and
   DCEP negotiation.  However, an SDP offer/answer exchange MUST NOT be
   initiated if the associated SCTP stream is already negotiated via
   DCEP.  Stream ids that identifiers are not currently used listed
   in an incoming SDP can be used for
   DCEP negotiation.  Stream id allocation per offer.

   A closed data channel using local close (SCTP SSN reset), without an
   additional SDP offer/answer
   negotiation to close it, may not align with DTLS role based allocation. be reused for a new data
   channel.  This
   could cause glare conditions when one side trying to do can only be done via new SDP offer/
   answer negotiation on a stream id while offer/answer, describing
   the other end trying to open
   a new sub-protocol and its attributes, only after the corresponding
   data channel on close acknowledgement is received from the same stream id using DCEP negotiation.  To peer (i.e.
   SCTP SSN reset of both incoming and outgoing streams is completed).
   This restriction is to avoid these glare the race conditions this specification recommends that between arrival of
   "SDP offer which reuses stream" with "SCTP SSN reset which closes
   outgoing stream" at the peer.

5.2.5.  Various SDP Offer/Answer Scenarios and Considerations

      SDP offer has no "a=dcmap" attributes

      *  Initial SDP offer: No data channel stack user always selects stream ids is negotiated yet.  The DTLS
         connection and SCTP association is negotiated and, if agreed,
         established as per above described [I-D.ietf-mmusic-sctp-sdp].

      *  Subsequent SDP offer: All the SDP offer/answer rule even when DCEP negotiation is used.  To avoid
   glare conditions, it is possible to come up with a different stream
   id allocation scheme, but such schemes are outside the scope of this
   specification.

6.2.2.  Negotiating Data Channel Parameters

   Conveying a reliable data channel is achieved by including neither
   'max-retr' nor 'max-time' in corresponding SDP offer's or answer's
   a=dcmap attribute line.  Conveying a partially reliable negotiated data channel
   is achieved by including only one of 'max-retr' or 'max-time'.  By
   definition max-retr and max-time
         channels are mutually exclusive, so at most
   one of them MAY expected be present in a=dcmap.  If an closed now.  The DTLS/SCTP association
         remains open for SDP offer contains both
   of these parameters then the receiver offer/answer or DCEP negotiation of such an SDP offer MUST
   reject the SDP offer.  If an data
         channels.

      SDP answer contains both of these
   parameters then has no "a=dcmap" attributes

      *  Initial SDP answer: Either the offerer MAY treat peer does not support dcmap
         attributes or it as an error and MAY assume rejected all the data channels.  In either
         case the offerer closes all the associated SDP offer/answer failed and MAY take appropriate
   recovery actions.  These recovery options are outside negotiated
         data channels that were open at the scope time of
   this specification. initial offer.  The SDP answer SHALL echo the same subprotocol, max-retr, max-time,
   ordered parameters, if those were present in the offer,
         DTLS connection and MAY
   include a label parameter.  They MAY appear in any order, which could SCTP association will still be different from the setup.

      *  Subsequent SDP offer, in answer: All the SDP answer.

   When sending a subsequent offer or an answer, and for as long as the
   data channel is still open, the sender MUST replicate the same
   information.

   Data channel types defined in [I-D.ietf-rtcweb-data-protocol] offer/answer negotiated data
         channels are
   mapped to SDP in the following manner, where "ordered=true" is the
   default and may expected be omitted:

   DATA_CHANNEL_RELIABLE
         ordered=true

   DATA_CHANNEL_RELIABLE_UNORDERED
         ordered=false

   DATA_CHANNEL_PARTIAL_RELIABLE_REXMIT
         ordered=true;max-retr=<number of retransmissions>

   DATA_CHANNEL_PARTIAL_RELIABLE_REXMIT_UNORDERED
         ordered=false;max-retr=<number of retransmissions>

   DATA_CHANNEL_PARTIAL_RELIABLE_TIMED
         ordered=true;max-time=<lifetime in milliseconds>

   DATA_CHANNEL_PARTIAL_RELIABLE_TIMED_UNORDERED
         ordered=false;max-time=<lifetime in milliseconds>

6.2.3.  Opening a Data Channel closed now.  The procedure DTLS/SCTP association
         remains open for opening a data channel using future SDP offer/answer or DCEP negotiation starts with the agent preparing to send an SDP offer.  If
   a peer receives an of
         data channels.

      SDP offer before starting to send has no "a=dcsa" attributes for a new SDP offer
   with data channels that channel.

      *  This is allowed and indicates there are no sub-protocol
         parameters to be SDP offer/answer negotiated, or
   loses an convey.

      SDP offer glare resolution procedure answer has no "a=dcsa" attributes for a data channel.

      *  This is allowed and indicates there are no sub-protocol
         parameters to convey in this case, it MUST
   wait until the ongoing SDP offer/answer completes before resuming the SDP offer/answer negotiation procedure. answer.  The agent that intends to send an number of dcsa
         attributes in the SDP offer answer does not have to create data channels
   through SDP offer/answer negotiation performs match the following:

   o  Creates data channels using stream identifiers from number
         of dcsa attributes in the owned set
      (see Section 6.2.1).

   o  Generates a new SDP offer.

   o  Determines the list of stream identifiers assigned to data
      channels opened through

6.  Examples

   SDP offer/answer negotiation.

   o  Completes the offer:
     m=application 10001 UDP/DTLS/SCTP webrtc-datachannel
     c=IN IP4 10.10.10.1
     a=max-message-size:100000
     a=sctp-port:5000
     a=setup:actpass
     a=connection:new
     a=fingerprint:SHA-1 \
         4A:AD:B9:B1:3F:82:18:3B:54:02:12:DF:3E:5D:49:6B:19:E5:7C:AB
     a=dcmap:0 subprotocol="BFCP";label="BFCP"

   SDP offer with the dcmap and dcsa attributes needed,
      if any, for each SDP offer/answer negotiated data channel, as
      described in Section 6.1 and in Section 6.2.2.

   o  Sends the SDP offer.

   The peer receiving such an SDP offer performs answer:
     m=application 10002 UDP/DTLS/SCTP webrtc-datachannel
     c=IN IP4 10.10.10.2
     a=max-message-size:100000
     a=sctp-port:5002
     a=setup:passive
     a=connection:new
     a=fingerprint:SHA-1 \
         5B:AD:67:B1:3E:82:AC:3B:90:02:B1:DF:12:5D:CA:6B:3F:E5:54:FA

                            Figure 1: Example 1

   In the following:

   o  Parses and applies above example the SDP offer.  Note that answerer rejected the typical parser
      normally ignores unknown SDP attributes, which includes data channel related attributes.

   o  Analyzes the channel parameters and sub-protocol attributes to
      determine whether to accept each offered data channel.

   o  For accepted data channels, it creates peer instances with
   stream id 0 either for explicit reasons or because it does not
   understand the data
      channels with "a=dcmap" attribute.  As a result the agent using offerer will
   close the data channel parameters described in created with the SDP offer.  Note that offer/answer negotiation
   option.  The SCTP association will still be setup over DTLS.  At this
   point the agent is asked offerer or the answerer may use DCEP negotiation to create open
   data
      channels with SCTP stream identifiers contained in the channels.

   SDP offer
      if offer:
     m=application 10001 UDP/DTLS/SCTP webrtc-datachannel
     c=IN IP4 10.10.10.1
     a=max-message-size:100000
     a=sctp-port:5000
     a=setup:actpass
     a=connection:new
     a=fingerprint:SHA-1 \
         4A:AD:B9:B1:3F:82:18:3B:54:02:12:DF:3E:5D:49:6B:19:E5:7C:AB
     a=dcmap:0 subprotocol="BFCP";label="BFCP"
     a=dcmap:2 subprotocol="MSRP";label="MSRP"
     a=dcsa:2 accept-types:message/cpim text/plain text/
     a=dcsa:2 path:msrp://alice.example.com:10001/2s93i93idj;dc

   SDP answer:
     m=application 10002 UDP/DTLS/SCTP webrtc-datachannel
     c=IN IP4 10.10.10.2
     a=max-message-size:100000
     a=sctp-port:5002
     a=setup:passive
     a=connection:new
     a=fingerprint:SHA-1 \
         5B:AD:67:B1:3E:82:AC:3B:90:02:B1:DF:12:5D:CA:6B:3F:E5:54:FA
     a=dcmap:2 subprotocol="MSRP";label="MSRP"
     a=dcsa:2 accept-types:message/cpim text/plain
     a=dcsa:2 path:msrp://bob.example.com:10002/si438dsaodes;dc

                            Figure 2: Example 2

   In the above example the SDP offer is accepted.

   o  Generates an SDP answer.

   o  Completes the contains data channels for BFCP
   and MSRP sub-protocols.  The SDP answer with the dcmap rejected BFCP and optional dcsa
      attributes needed for each SDP offer/answer negotiated data
      channel, as described in Section 6.1 and in Section 6.2.2.

   o  Sends accepted
   MSRP.  So, the SDP answer.

   The agent receiving such an SDP answer performs offerer should close the following:

   o  Closes any created data channels channel for which the expected dcmap BFCP and
      dcsa attributes are not present in the SDP answer.

   o  Applies the SDP answer.

   Each agent application MUST wait to send data until it has
   confirmation that
   both offerer and answerer may start using the MSRP data channel at the peer is instantiated.  For
   WebRTC, this
   (after SCTP/DTLS association is when both data channel stacks have channel parameters
   instantiated.  This occurs:

   o  At both peers when a setup).  The data channel with stream
   id 0 is created without an
      established SCTP association, as soon as the SCTP association is
      successfully established.

   o  At the agent receiving an SDP offer free and can be used for which there is an
      established SCTP association, as soon as it creates an future DCEP or SDP offer/
      answer negotiated data channel based offer/answer
   negotiation.

   Continuing on information signaled in the earlier example in Figure 1.

   Subsequent SDP offer.

   o  At the agent sending an offer:
     m=application 10001 UDP/DTLS/SCTP webrtc-datachannel
     c=IN IP4 10.10.10.1
     a=max-message-size:100000
     a=sctp-port:5000
     a=setup:actpass
     a=connection:existing
     a=fingerprint:SHA-1 \
         4A:AD:B9:B1:3F:82:18:3B:54:02:12:DF:3E:5D:49:6B:19:E5:7C:AB
     a=dcmap:4 subprotocol="MSRP";label="MSRP"
     a=dcsa:4 accept-types:message/cpim text/plain
     a=dcsa:4 path:msrp://alice.example.com:10001/2s93i93idj;dc

   Subsequent SDP offer to create answer:
     m=application 10002 UDP/DTLS/SCTP webrtc-datachannel
     c=IN IP4 10.10.10.2
     a=max-message-size:100000
     a=sctp-port:5002
     a=setup:passive
     a=connection:existing
     a=fingerprint:SHA-1 \
         5B:AD:67:B1:3E:82:AC:3B:90:02:B1:DF:12:5D:CA:6B:3F:E5:54:FA
     a=dcmap:4 subprotocol="MSRP";label="MSRP"
     a=dcsa:4 accept-types:message/cpim text/plain
     a=dcsa:4 path:msrp://bob.example.com:10002/si438dsaodes;dc

                            Figure 3: Example 3

   The above example is a new continuation of the example in Figure 1.  The
   SDP offer/answer
      negotiated offer now removes the MSRP data channel for which there is an established SCTP
      association, when it receives the SDP answer confirming acceptance
      of the data channel or when it begins to receive data on the with stream id 2, but
   opens a new MSRP data channel from with stream id 4.  The answerer accepts
   the peer, whichever occurs first.

6.2.4.  Closing entire offer.  As a Data Channel

   When result the application requests offerer closes the closing of a earlier
   negotiated MSRP related data channel that was
   negotiated via SDP offer/answer, and both offerer and answerer
   may start using new the MSRP related data channel stack always
   performs an SCTP SSN reset for this channel.

   It is specific to the sub-protocol whether this closing MUST

7.  Security Considerations

   No security considerations are envisaged beyond those already
   documented in
   addition be signaled to the peer via a [RFC4566].

8.  IANA Considerations

8.1.  Subprotocol Identifiers

   Registration of new SDP offer/answer exchange. subprotocol identifiers is performed using the
   existing IANA table "WebSocket Subprotocol Name Registry".

   The intention to close a data channel can following text should be signaled by sending a
   new SDP offer which excludes the "a=dcmap:" and "a=dcsa:" attribute
   lines for added following the data channel.  The offerer SHOULD NOT change title of the port
   value table.

   "This table also includes subprotocol identifiers specified for the "m" line (e.g. to zero) when closing usage
   within a WebRTC data channel
   (unless all data channels are being closed and channel."

   The following reference should be added to under the SCTP association
   is heading
   reference: "RFC XXXX".

   This document assigns no longer needed), since new values to this would close table.

   NOTE to RFC Editor: Please replace "XXXX" with the SCTP association and
   impact all number of the data channels.  If the answerer accepts the this
   RFC.

8.2.  New SDP
   offer then Attributes

8.2.1.  dcmap

   [Editor's note: This section still needs to be completed.]

8.2.2.  dcsa

   [Editor's note: This section still needs to be completed.]

9.  Acknowledgments

   The authors wish to acknowledge the answerer MUST close those data channels whose
   "a=dcmap:" and "a=dcsa:" attribute lines were excluded borrowing of ideas from the
   received SDP offer, unless those data channels were already closed, other
   internet drafts by Salvatore Loreto, Gonzalo Camarillo, Peter Dunkley
   and Gavin Llewellyn, and the answerer MUST also exclude the corresponding attribute lines
   in the answer.  In addition to that, the SDP answerer MAY exclude thank Roni Even, Christian Groves,
   Christer Holmberg, Paul Kyzivat, Jonathan Lennox, and Uwe
   Rauschenbach for their invaluable comments.

10.  CHANGE LOG

10.1.  Changes against 'draft-ietf-mmusic-data-channel-sdpneg-03'

   o  In Section 1 replacement of "RTCWeb leaves it open for other
      applications to use data channels which were closed but not yet communicated to the
   peer.  So, the offerer MUST inspect the answer to see if it has and its in-band DCEP or out-of-
      band non-DCEP protocols for creating them" with "... to
   close other use data
      channels which are now not included in and its in-band DCEP or other in-band or out-of-band
      protocols for creating them".  Additionally replacement of "In
      particular, the answer.

   If a new SDP offer/answer is used to close data channels then offer generated by the
   data channel(s) SHOULD only be closed application includes no
      channel-specific information" with "... generated by the answerer/offerer after a
   successful SDP answer is sent/received.

      This delayed closure is RECOMMENDED in order RTCweb
      data channel stack includes no channel-specific information".

   o  Move of former section 5 ("Data Channels") to handle cases where
      a successful SDP answer is not received, in which case the state new Appendix A and
      removal of the session SHOULD be kept per the last successful SDP offer/
      answer.

   If a client receives a data channel close indication (due to inband
   SCTP SSN reset or some other reason) without associated SDP offer
   then the client SHOULD generate an SDP offer which excludes JavaScript API specific discussions from this
   closed data channel.

   The application MUST also close any moved
      text (like mentioning of data channel that was negotiated
   via SDP offer/answer, for stack specific states).
      Therefore former section 6 ("SDP Offer/Answer Negotiation") is now
      Section 5.

   o  In Section 5:

      *  Relacement of Section 5's first paragraph "This section defines
         a method of non-DCEP negotiation by which the stream identifiers are not listed
   in an incoming SDP offer.

   A closed two clients can
         negotiate data channel channel-specific and sub-protocol-specific
         parameters, using local close (SCTP SSN reset), without an
   additional the out-of-band SDP offer/answer to close it, may be reused for a new data
   channel. exchange.
         This SDP extension can only be done via new used with the SDP offer/answer, describing offer/answer
         model." with "This section defines an SDP extension by which
         two clients can negotiate data channel-specific and sub-
         protocol-specific parameters without using DCEP
         [I-D.ietf-rtcweb-data-protocol].  This SDP extension only
         defines usage in the context of SDP offer/answer."

      *  Addition of new sub-protocol paragraph: "Appendix A provides information how
         data channels work in general and its attributes, only after especially summarizes some
         key aspects, which should be considered for the corresponding negotiation of
         data channel close acknowledgement channels if DCEP is received from the peer (i.e.
   SCTP SSN reset not used."

   o  In Section 5.1.1 replacement of both incoming and outgoing streams is completed).
   This restriction "The intention of exchanging these
      attributes is to avoid create data channels on both the race conditions between arrival of
   "SDP offer which reuses stream" peers with "SCTP SSN reset which closes
   outgoing stream" at the peer.

6.2.5.  Various SDP Offer/Answer Scenarios and Considerations

      SDP offer has no a=dcmap
      same set of attributes

      *  Initial SDP offer: No data channel is negotiated yet.  The DTLS
         connection and SCTP association is negotiated and, if agreed,
         established as per [I-D.ietf-mmusic-sctp-sdp].

      *  Subsequent SDP offer: All without actually using the SDP offer/answer negotiated data
         channels are expected be closed now.  The DTLS/SCTP association
         remains open for SDP offer/answer or DCEP negotiation
      [I-D.ietf-rtcweb-data-protocol]" with "The intention in exchanging
      these attributes is to create, on two peers, without use of DCEP
      [I-D.ietf-rtcweb-data-protocol], matched pairs of oppositely
      directed data
         channels.

      SDP answer has no a=dcmap attributes

      *  Initial SDP answer: Either the peer does not support dcmap
         attributes or it rejected all channels having the data channels. same set of attributes".

   o  In either
         case the offerer closes all Section 5.1.1.5 replacement of "The 'max-retr' parameter
      indicates the SDP offer/answer negotiated
         data channels that were open at maximal number a user message will be retransmitted"
      with "The 'max-retr' parameter indicates the time maximal number of initial offer.  The
         DTLS connection and SCTP association
      times a user message will still be setup.

      *  Subsequent SDP answer: All the retransmitted".

   o  In Section 5.2.1 replacement of "However, an SDP offer/answer
      exchange MUST NOT be initiated if the associated SCTP stream is
      already negotiated data
         channels are expected via DCEP" with "However, an SCTP stream MUST
      NOT be closed now.  The DTLS/SCTP association
         remains open for future SDP offer/answer referenced in a dcmap or DCEP negotiation dcsa attribute of
         data channels.

      SDP offer has no a=dcsa attributes for a data channel.

      *  This is allowed and indicates there are no sub-protocol
         parameters to convey. an SDP offer/
      answer exchange if the associated SCTP stream has no a=dcsa attributes for a data channel.

      *  This is allowed and indicates there are no sub-protocol
         parameters to convey already been
      negotiated via DCEP".

   o  In the examples in Section 6 addition of the SDP answer.  The number previously missing
      colons to the "a=sctp-port" attribute lines.

10.2.  Changes against 'draft-ietf-mmusic-data-channel-sdpneg-02'

   o  Move of dcsa
         attributes in reference [I-D.ietf-rtcweb-jsep] from the SDP answer does not have list of
      normative references to match the number list of dcsa attributes in informative references.

   o  Addition of [IANA-SDP-Parameters] to the SDP offer.

7.  Examples

   SDP offer:
     m=application 10001 UDP/DTLS/SCTP webrtc-datachannel
     c=IN IP4 10.10.10.1
     a=max-message-size:100000
     a=sctp-port 5000
     a=setup:actpass
     a=connection:new
     a=fingerprint:SHA-1 \
         4A:AD:B9:B1:3F:82:18:3B:54:02:12:DF:3E:5D:49:6B:19:E5:7C:AB
     a=dcmap:0 subprotocol="BFCP";label="BFCP"

   SDP answer:
     m=application 10002 UDP/DTLS/SCTP webrtc-datachannel
     c=IN IP4 10.10.10.2
     a=max-message-size:100000
     a=sctp-port 5002
     a=setup:passive
     a=connection:new
     a=fingerprint:SHA-1 \
         5B:AD:67:B1:3E:82:AC:3B:90:02:B1:DF:12:5D:CA:6B:3F:E5:54:FA

                            Figure 1: Example 1

   In list of informative
      references and addition of following two sentences to the above example first
      paragraph after the ABNF definition: "Note however that not all
      SDP answerer rejected attributes are suitable as "a=dcsa:" parameter.
      [IANA-SDP-Parameters] contains the data channel with
   stream id 0 either for explicit reasons lists of IANA registered
      session and media level or because it does not
   understand the a=dcmap attribute.  As a result the offerer will close media level only SDP attributes."

   o  In the introduction replacement of last sentence "This document
      defines SDP-based out-of-band negotiation procedures to establish
      data channel created channels for transport of well-defined sub-protocols" with the
      "This document defines SDP offer/answer negotiation
   option.  The SCTP association will still be setup over DTLS.  At this
   point the offerer or the answerer may use DCEP negotiation procedures to open
   data channels.

   SDP offer:
     m=application 10001 UDP/DTLS/SCTP webrtc-datachannel
     c=IN IP4 10.10.10.1
     a=max-message-size:100000
     a=sctp-port 5000
     a=setup:actpass
     a=connection:new
     a=fingerprint:SHA-1 \
         4A:AD:B9:B1:3F:82:18:3B:54:02:12:DF:3E:5D:49:6B:19:E5:7C:AB
     a=dcmap:0 subprotocol="BFCP";label="BFCP"
     a=dcmap:2 subprotocol="MSRP";label="MSRP"
     a=dcsa:2 accept-types:message/cpim text/plain text/
     a=dcsa:2 path:msrp://alice.example.com:10001/2s93i93idj;dc

   SDP answer:
     m=application 10002 UDP/DTLS/SCTP webrtc-datachannel
     c=IN IP4 10.10.10.2
     a=max-message-size:100000
     a=sctp-port 5002
     a=setup:passive
     a=connection:new
     a=fingerprint:SHA-1 \
         5B:AD:67:B1:3E:82:AC:3B:90:02:B1:DF:12:5D:CA:6B:3F:E5:54:FA
     a=dcmap:2 subprotocol="MSRP";label="MSRP"
     a=dcsa:2 accept-types:message/cpim text/plain
     a=dcsa:2 path:msrp://bob.example.com:10002/si438dsaodes;dc

                            Figure 2: Example 2

   In the above example the SDP offer contains
      establish data channels for BFCP
   and MSRP sub-protocols.  The SDP answer rejected BFCP transport of well-defined sub-
      protocols, to enable out-of-band negotiation".

   o  Throughout the document replacement of "external negotiation" with
      "SDP offer/answer negotiation" and accepted
   MSRP.  So, removal of term "external
      negotiation" from the offerer should close terminology list in Section 3.

   o  Throughout the data channel for BFCP document replacement of "internal negotiation" with
      "DCEP" and
   both offerer removal of terms "internal negotiation" and answerer may start using "in-band
      negotiation" from the MSRP data channel
   (after SCTP/DTLS association terminology list in Section 3.

   o  Addition of "SCTP Stream Sequence Number (SSN)" to the list of
      terms.

   o  In Section 5.2.1 replacement of sentence "However, a single stream
      is setup).  The data channel managed using one method at a time." with "However, an SDP
      offer/answer exchange MUST NOT be initiated if the associated SCTP
      stream
   id 0 is free already negotiated via DCEP".

   o  In Section 5.2.2 replacement of sentence "By definition max-retr
      and max-time are mutually exclusive, so only one of them can be used for future DCEP or SDP offer/answer
   negotiation.

   Continuing on the earlier example
      present in Figure 1.

   Subsequent SDP offer:
     m=application 10001 UDP/DTLS/SCTP webrtc-datachannel
     c=IN IP4 10.10.10.1
     a=max-message-size:100000
     a=sctp-port 5000
     a=setup:actpass
     a=connection:existing
     a=fingerprint:SHA-1 \
         4A:AD:B9:B1:3F:82:18:3B:54:02:12:DF:3E:5D:49:6B:19:E5:7C:AB
     a=dcmap:4 subprotocol="MSRP";label="MSRP"
     a=dcsa:4 accept-types:message/cpim text/plain
     a=dcsa:4 path:msrp://alice.example.com:10001/2s93i93idj;dc

   Subsequent SDP answer:
     m=application 10002 UDP/DTLS/SCTP webrtc-datachannel
     c=IN IP4 10.10.10.2
     a=max-message-size:100000
     a=sctp-port 5002
     a=setup:passive
     a=connection:existing
     a=fingerprint:SHA-1 \
         5B:AD:67:B1:3E:82:AC:3B:90:02:B1:DF:12:5D:CA:6B:3F:E5:54:FA
     a=dcmap:4 subprotocol="MSRP";label="MSRP"
     a=dcsa:4 accept-types:message/cpim text/plain
     a=dcsa:4 path:msrp://bob.example.com:10002/si438dsaodes;dc

                            Figure 3: Example 3

   The above example is a continuation of the example in Figure 1.  The
   SDP offer now removes the MSRP data channel with stream id 2, but
   opens a new MSRP data channel a=dcmap" with stream id 4.  The answerer accepts
   the entire offer.  As a result the offerer closes the earlier
   negotiated MSRP related data channel "By definition max-retr and both offerer max-time are
      mutually exclusive, so at most one of them MAY be present in
      a=dcmap".

   o  Move of reference [WebRtcAPI] from list of normative references to
      list of informative references.

   o  Removal of almost all text parts, which discussed JavaScript or
      other API specific aspects.  Such API specific aspects were mainly
      discussed in sub-sections of Section 5 and answerer
   may start using Section 5 of draft-
      ietf-mmusic-data-channel-sdpneg-02.

10.3.  Changes against 'draft-ietf-mmusic-data-channel-sdpneg-01'

   o  New Section 4 regarding applicability to SDP offer/answer only.

   o  Addition of new Section 8.1 "Subprotocol identifiers" as
      subsection of the MSRP "IANA Considerations" related data channel. Section 8.  Security Considerations

   No security considerations are envisaged beyond those already
   documented in [RFC4566].

9.  IANA Considerations

9.1.  Subprotocol Identifiers

   Registration  Also
      removal of new subprotocol identifiers is performed using the
   existing IANA table "WebSocket temporary note "To be completed.  As [I-D.ietf-
      rtcweb-data-protocol] this document should refer to IANA's
      WebSocket Subprotocol Name Registry".

   The following text should be added following the title of the table.

   "This table also includes subprotocol identifiers specified for usage
   within a WebRTC data channel."

   The following reference should be added to under Registry defined in [RFC6455]."

   o  In Section 5.2.2:

      *  In the heading
   reference: "RFC XXXX".

   This document assigns no new values to this table.

   NOTE to RFC Editor: Please replace "XXXX" with first paragraph replacement of the number sentence "If an SDP
         offer contains both of this
   RFC.

9.2.  New these parameters then such an SDP Attributes

9.2.1.  dcmap

   [Editor's note: This section still needs to be completed.]

9.2.2.  dcsa

   [Editor's note: This section still needs to offer
         will be completed.]

10.  Acknowledgments

   The authors wish to acknowledge the borrowing of ideas from other
   internet drafts by Salvatore Loreto, Gonzalo Camarillo, Peter Dunkley
   and Gavin Llewellyn, and to thank Roni Even, Christian Groves,
   Christer Holmberg, Paul Kyzivat, Jonathan Lennox, and Uwe
   Rauschenbach for their invaluable comments.

11.  CHANGE LOG

11.1.  Changes against 'draft-ietf-mmusic-data-channel-sdpneg-02'

   o  Move rejected." with "If an SDP offer contains both of reference [I-D.ietf-rtcweb-jsep] from these
         parameters then the list receiver of
      normative references to such an SDP offer MUST reject
         the list of informative references.

   o  Addition of [IANA-SDP-Parameters] to SDP offer."

      *  In the list second paragraph capitalization of informative
      references "shall" and addition of following two "may"
         such that both sentences to now read: "The SDP answer SHALL echo
         the first
      paragraph after same subprotocol, max-retr, max-time, ordered parameters,
         if those were present in the ABNF definition: "Note however that not all
      SDP attributes are suitable as "a=dcsa:" offer, and MAY include a label
         parameter.
      [IANA-SDP-Parameters] contains  They MAY appear in any order, which could be
         different from the lists of IANA registered
      session and media level or media level only SDP attributes."

   o  In offer, in the introduction replacement of last sentence "This document
      defines SDP-based out-of-band negotiation procedures to establish
      data channels for transport of well-defined sub-protocols" with
      "This document defines SDP offer/answer negotiation procedures to
      establish data channels for transport of well-defined sub-
      protocols, to enable out-of-band negotiation".

   o  Throughout answer."

      *  In the document third paragraph replacement of "external negotiation" with
      "SDP offer/answer negotiation" and removal of term "external
      negotiation" from the terminology list sentence "The same
         information MUST be replicated without changes in Section 3.

   o  Throughout any
         subsequent offer or answer, as long as the document replacement data channel is
         still opened at the time of "internal negotiation" offer or answer generation." with
      "DCEP" and removal of terms "internal negotiation"
         "When sending a subsequent offer or an answer, and "in-band
      negotiation" from for as long
         as the terminology list in Section 3.

   o  Addition of "SCTP Stream Sequence Number (SSN)" to data channel is still open, the list of
      terms. sender MUST replicate
         the same information.".

   o  In Section 6.2.1 replacement 5.2.2 the mapping of sentence "However, a single stream
      is managed data channel types defined in
      [I-D.ietf-rtcweb-data-protocol] to the SDP "a=dcmap" attribute
      parameters were illustrated using one method at a time." example "a=dcmap" attribute
      lines.  Replacement of these example "a=dcmap" attribute lines
      with "However, an SDP
      offer/answer exchange MUST NOT be initiated if just the associated SCTP
      stream is already negotiated via DCEP". "a=dcmap" attribute parameters being relevant for
      the channel type.

   o  In Section 6.2.2 replacement of sentence "By definition max-retr
      and max-time are mutually exclusive, so only one 5.2.5 the description of them can be
      present in a=dcmap" with "By definition max-retr and max-time are
      mutually exclusive, so at most one of them MAY be present in
      a=dcmap".

   o  Move of reference [WebRtcAPI] from list of normative references to
      list of informative references.

   o  Removal of almost all text parts, which discussed JavaScript or
      other API specific aspects.  Such API specific aspects were mainly
      discussed in sub-sections bullet point "SDP offer has no
      a=dcmap attributes - Initial SDP offer:" was "Initial SDP offer:
      No data channel negotiated yet."  Replacement of Section 5 this description
      with "Initial SDP offer: No data channel is negotiated yet.  The
      DTLS connection and Section 6.

11.2.  Changes against 'draft-ietf-mmusic-data-channel-sdpneg-01' SCTP association is negotiated and, if agreed,
      established as per [I-D.ietf-mmusic-sctp-sdp]."

   o  New  In Section 4 regarding applicability 5.2.5 in both bullet points related to "Subsequent SDP offer/answer only.

   o  Addition of new Section 9.1 "Subprotocol identifiers" as
      subsection
      offer" and "Subsequent SDP answer" replacement of "All the "IANA Considerations" related Section 9.  Also
      removal of
      externally negotiated data channels must be closed now." with "All
      the temporary note "To externally negotiated data channels are expected be completed.  As [I-D.ietf-
      rtcweb-data-protocol] this document should refer to IANA's
      WebSocket Subprotocol Name Registry defined in [RFC6455]." closed
      now.".

   o  In Section 6.2.2:

      *  In the first Appendix A.2.2's sixth paragraph beginning with "[ASSUMPTION]"
      replacement of the sentence "If an SDP
         offer contains both two occurrences of these parameters then such an SDP offer
         will be rejected." "must" with "If an SDP offer contains both of these
         parameters then the receiver of such an SDP offer MUST reject
         the SDP offer."

      * "MUST".

   o  In Section 5.1.1.1 in the second paragraph capitalization definition of "shall" and "may"
         such that both sentences now read: "The SDP answer SHALL echo
         the same subprotocol, max-retr, max-time, ordered parameters,
         if those were present in the offer, and MAY include ABNF rule "dcmap-opt"
      there was a label
         parameter.  They MAY appear in any order, which could comment saying that "Either only maxretr-opt or
      maxtime-opt is present.  Both MUST not be
         different from present."  Removal of
      the SDP offer, in second normative sentence and instead addition of following
      new paragraph to the SDP answer."

      * end of this section: "Within an 'a=dcmap'
      attribute line's 'dcmap-opt' value either only one 'maxretr-opt'
      parameter or one 'maxtime-opt' parameter is present.  Both MUST
      NOT be present."

   o  In the third paragraph Section 5.1.1.7 replacement of the first sentence "The same
         information MUST be replicated without changes
      'ordered' parameter with value "true" indicates that DATA chunks
      in any
         subsequent offer or answer, as long as the data channel is
         still opened at MUST be dispatched to the time of offer or answer generation." upper layer by the
      receiver while preserving the order." with
         "When sending a subsequent offer or an answer, and for as long
         as "The 'ordered'
      parameter with value "true" indicates that the receiver MUST
      dispatch DATA chunks in the data channel is still open, to the sender MUST replicate upper layer while
      preserving the same information.". order.".

   o  In Section 6.2.2 the mapping 5.2.3's first paragraph replacement of data channel types defined in
      [I-D.ietf-rtcweb-data-protocol] to the SDP "a=dcmap" attribute
      parameters were illustrated using example "a=dcmap" attribute
      lines.  Replacement one
      occurrence of these example "a=dcmap" attribute lines "must" with just the "a=dcmap" attribute parameters being relevant for
      the channel type. "..., it MUST wait until ...".

   o  In Section 6.2.5 5.2.4:

      *  In the description second paragraph replacement of bullet point "SDP offer has no
      a=dcmap attributes - Initial SDP offer:" was "Initial SDP offer:
      No "must" with "... whether
         this closing MUST in addition ..."

      *  In the third paragraph replacement of the sentence "The port
         value for the "m" line SHOULD not be changed (e.g., to zero)
         when closing a data channel negotiated yet."  Replacement of this description ..." with "Initial SDP offer: No "The offerer SHOULD NOT
         change the port value for the "m" line (e.g., to zero) when
         closing a data channel is negotiated yet.  The
      DTLS connection and SCTP association is negotiated and, if agreed,
      established as per [I-D.ietf-mmusic-sctp-sdp]."

   o ...".

      *  In Section 6.2.5 in both bullet points related to "Subsequent SDP
      offer" and "Subsequent SDP answer" the last but two paragraph replacement of "All the
      externally negotiated sentence "...
         then an SDP offer which excludes this closed data channels must channel
         SHOULD be closed now." generated." with "All "... then the externally negotiated data channels are expected be client SHOULD generate
         an SDP offer which excludes this closed
      now.".

   o data channel.".

      *  In Section 5.2.2's sixth the last but one paragraph beginning with "[ASSUMPTION]" replacement of the two occurrences of "must" with "MUST". "The
         application MUST also close...".

   o  In Section 6.1.1.1 in 5.1.2 addition of following note after the formal
      definition of the ABNF rule "dcmap-opt"
      there was a comment saying 'a=dcsa' attribute: "Note that "Either only maxretr-opt or
      maxtime-opt is present.  Both MUST not be present."  Removal of the second normative sentence and instead addition of following
      new paragraph above
      reference to RFC 4566 defines were the end attribute definition can be
      found; it does not provide any limitation on support of attributes
      defined in other documents in accordance with this section: "Within an 'a=dcmap' attribute line's 'dcmap-opt' value either only one 'maxretr-opt'
      parameter or one 'maxtime-opt' parameter is present.  Both MUST
      NOT be present."
      definition."

10.4.  Changes against 'draft-ietf-mmusic-data-channel-sdpneg-00'

   o  In Section 6.1.1.7 replacement 3 "WebRTC data channel" was defined as "A bidirectional
      channel consisting of the first sentence "The
      'ordered' parameter paired SCTP outbound and inbound streams."
      Replacement of this definition with value "true" indicates that DATA chunks
      in the "Data channel: A WebRTC data
      channel MUST be dispatched to the upper layer by the
      receiver while preserving the order." with "The 'ordered'
      parameter with value "true" indicates that the receiver MUST
      dispatch DATA chunks as specified in [I-D.ietf-rtcweb-data-channel]", and
      consistent usage of "data channel" in the data channel to remainder of the upper layer while
      preserving
      document including the order.". document's headline."

   o  In Section 6.2.3's first paragraph replacement of the one
      occurrence 5 removal of "must" with "..., it MUST wait until ...".

   o  In Section 6.2.4:

      * following note: 'OPEN ISSUE: The syntax in
      [I-D.ietf-mmusic-sctp-sdp] may change as that document progresses.
      In the second paragraph replacement particular we expect "webrtc-datachannel" to become a more
      general term.'

   o  Consistent usage of "must" with "... whether
         this closing MUST '"m" line' in addition ..."

      * whole document as per [RFC4566].

   o  In the third paragraph replacement Section 5.1.1 removal of the sentence "The port
         value for the "m" example dcmap attribute line SHOULD
      'a=dcmap:2 subprotocol="BFCP";label="channel 2' as there are
      already four examples right after the ABNF rules in
      Section 5.1.1.1.  Corresponding removal of following related note:
      "Note: This document does not be changed (e.g., provide a complete specification of
      how to zero)
         when closing negotiate the use of a WebRTC data channel ..." with "The offerer SHOULD NOT
         change the port value for to transport
      BFCP.  Procedures specific to each sub-protocol such as BFCP will
      be documented elsewhere.  The use of BFCP is only an example of
      how the "m" line (e.g., generic procedures described herein might apply to zero) when
         closing a data channel ...".

      *
      specific sub-protocol."

   o  In the last but two paragraph replacement Section 5.1.1 removal of following note: "Note: This attribute
      is derived from attribute "webrtc-DataChannel", which was defined
      in old version 03 of the sentence "...
         then an SDP offer following draft, but which excludes this closed data channel
         SHOULD be generated." was removed
      along with "... then the client SHOULD generate
         an any support for SDP offer which excludes this closed data channel.".

      *  In external negotiation in subsequent
      versions: [I-D.ietf-mmusic-sctp-sdp]."

   o  Insertion of following new sentence to the last but one paragraph replacement beginning of "must" with "The
         application MUST also close...".

   o  In
      Section 6.1.2 addition of 5.1.1.1: "dcmap is a media level attribute having
      following note after ABNF syntax:"

   o  Insertion of new Section 5.1.1.2 containing the dcmap-stream-id
      specifying sentence, which previously was placed right before the
      formal
      definition ABNF rules.  Removal of the 'a=dcsa' attribute: "Note that sentence 'Stream is a mandatory
      parameter and is noted directly after the above
      reference to RFC 4566 defines were "a=dcmap:" attribute's
      colon' as this information is part of the attribute definition can be
      found; it does not provide any limitation on support ABNF specification.

   o  In Section 5.1.1.1 modification of attributes
      defined in other documents the 'ordering-value' values
      from "0" or "1" to "true" or "false".  Corresponding text
      modifications in accordance with this attribute
      definition."

11.3.  Changes against 'draft-ietf-mmusic-data-channel-sdpneg-00' Section 5.1.1.7.

   o  In Section 3 "WebRTC data channel" was defined as "A bidirectional
      channel consisting of paired SCTP outbound and inbound streams."
      Replacement of this 5.1.1.1 the ABNF definition of "quoted-string" referred
      to rule name "escaped-char", which was not defined.  Instead a
      rule with "Data channel: A WebRTC data
      channel as specified in [I-D.ietf-rtcweb-data-channel]", and
      consistent usage name "escaped" was defined.  Renamed that rule's name to
      "escaped-char".

   o  Insertion of "data channel" in a dedicated note right after the remainder of "a=dcmap:4"
      attribute example in Section 5.1.1.1 regarding the
      document including non-printable
      "escaped-char" character within the document's headline." "label" value.

   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.
      In particular we expect "webrtc-datachannel" to become a more
      general term.'

   o  Consistent usage 5.1.2's second paragraph replacement of '"m" line' in whole document as per [RFC4566]. "sctp stream
      identifier" with "SCTP stream identifier".

   o  In first paragraph of Section 6.1.1 removal 5.2.1 replacement of first two
      sentences 'For the example dcmap attribute line
      'a=dcmap:2 subprotocol="BFCP";label="channel 2' as there are
      already four examples right after the ABNF rules SDP-based external negotiation described in
      Section 6.1.1.1.  Corresponding removal of following related note:
      "Note:
      this document, the initial offerer based "SCTP over DTLS" owns by
      convention the even stream identifiers whereas the initial
      answerer owns the odd stream identifiers.  This document ownership is
      invariant for the whole lifetime of the signaling session, e.g. it
      does not provide a complete specification of
      how to negotiate change if the use of initial answerer sends a WebRTC data channel to transport
      BFCP.  Procedures specific new offer to each sub-protocol such as BFCP will
      be documented elsewhere.  The use of BFCP is only an example of
      how the generic procedures described herein might apply to
      initial offerer.' with 'If an SDP offer/answer exchange (could be
      the initial or a
      specific sub-protocol."

   o  In Section 6.1.1 removal of following note: "Note: This attribute
      is derived from attribute "webrtc-DataChannel", which was defined subsequent one) results in old version 03 of the following draft, but which was removed
      along with any support for a UDP/DTLS/SCTP or
      TCP/DTLS/SCTP based media description being accepted, and if this
      SDP external negotiation offer/answer exchange results in subsequent
      versions: [I-D.ietf-mmusic-sctp-sdp]."

   o  Insertion of following new sentence to the beginning establishment of
      Section 6.1.1.1: "dcmap is a media level attribute having
      following ABNF syntax:"

   o  Insertion of new Section 6.1.1.2 containing
      SCTP association, then the dcmap-stream-id
      specifying sentence, which previously was placed right before SDP offerer owns the
      formal ABNF rules.  Removal even SCTP stream
      ids of the sentence 'Stream is a mandatory
      parameter this new SCTP association and is noted directly after the "a=dcmap:" attribute's
      colon' as answerer owns the odd
      SCTP stream identifiers.  If this information "m" line is part of removed from the ABNF specification.

   o  In Section 6.1.1.1 modification
      signaling session (its port number set to zero), and if usage of the 'ordering-value' values
      from "0"
      this or "1" to "true" of a new UDP/DTLS/SCTP or "false".  Corresponding text
      modifications in Section 6.1.1.7. TCP/DTLS/SCTP based "m" line is
      renegotiated later on, then the even and odd SCTP stream
      identifier ownership is redetermined as well as described above.'

   o  In Section 6.1.1.1 5.2.3 the ABNF definition first action of "quoted-string" referred
      to rule name "escaped-char", which was not defined.  Instead a
      rule with name "escaped" an SDP answerer, when
      receiving an SDP offer, was defined.  Renamed that rule's name to
      "escaped-char".

   o  Insertion of a dedicated note right after the "a=dcmap:4"
      attribute example in Section 6.1.1.1 regarding the non-printable
      "escaped-char" character within the "label" value.

   o  In Section 6.1.2's second paragraph replacement of "sctp stream
      identifier" with "SCTP stream identifier".

   o  In first paragraph of Section 6.2.1 replacement of first two
      sentences 'For the SDP-based external negotiation described in
      this document, the initial offerer based "SCTP over DTLS" owns by
      convention the even stream identifiers whereas the initial
      answerer owns the odd stream identifiers.  This ownership is
      invariant for the whole lifetime of the signaling session, e.g. it
      does not change if the initial answerer sends a new offer to the
      initial offerer.' with 'If an SDP offer/answer exchange (could be
      the initial or a subsequent one) results in a UDP/DTLS/SCTP or
      TCP/DTLS/SCTP based media description being accepted, and if this
      SDP offer/answer exchange results in the establishment of a new
      SCTP association, then the SDP offerer owns the even SCTP stream
      ids of this new SCTP association and the answerer owns the odd
      SCTP stream identifiers.  If this "m" line is removed from the
      signaling session (its port number set to zero), and if usage of
      this or of a new UDP/DTLS/SCTP or TCP/DTLS/SCTP based "m" line is
      renegotiated later on, then the even and odd SCTP stream
      identifier ownership is redetermined as well as described above.'

   o  In Section 6.2.3 the first action of an SDP answerer, when
      receiving an SDP offer, was described as "Applies the SDP offer.
      Note described as "Applies the SDP offer.
      Note that the browser ignores data channel specific attributes in
      the SDP."  Replacement of these two sentences with "Parses and
      applies the SDP offer.  Note that the typical parser normally
      ignores unknown SDP attributes, which includes data channel
      related attributes."

   o  In Section 6.2.3 5.2.3 the second sentence of the third SDP answerer
      action was "Note that the browser is asked to create data channels
      with stream identifiers not "owned" by the agent.".  Replacement
      of this sentence with "Note that the agent is asked to create data
      channels with SCTP stream identifiers contained in the SDP offer
      if the SDP offer is accepted."

   o  In Section 6.2.4 5.2.4 the third paragraph began with "A data channel
      can be closed by sending a new SDP offer which excludes the dcmap
      and dcsa attribute lines for the data channel.  The port value for
      the m line should not be changed (e.g., to zero) when closing a
      data channel (unless all data channels are being closed and the
      SCTP association is no longer needed), since this would close the
      SCTP association and impact all of the data channels.  If the
      answerer accepts the SDP offer then it MUST also exclude the
      corresponding attribute lines in the answer. ..." Replacement of
      this part with "The intention to close a data channel can be
      signaled by sending a new SDP offer which excludes the "a=dcmap:"
      and "a=dcsa:" attribute lines for the data channel.  The port
      value for the "m" line SHOULD not be changed (e.g., to zero) when
      closing a data channel (unless all data channels are being closed
      and the SCTP association is no longer needed), since this would
      close the SCTP association and impact all of the data channels.
      If the answerer accepts the SDP offer then it MUST close those
      data channels whose "a=dcmap:" and "a=dcsa:" attribute lines were
      excluded from the received SDP offer, unless those data channels
      were already closed, and it MUST also exclude the corresponding
      attribute lines in the answer."

   o  In Section 6.2.4 5.2.4 the hanging text after the third paragraph was
      "This delayed close is to handle cases where a successful SDP
      answer is not received, in which case the state of session should
      be kept per the last successful SDP offer/answer."  Replacement of
      this sentence with "This delayed closure is RECOMMENDED in order
      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
      successful SDP offer/answer."

   o  Although dedicated to "a=dcmap" and "a=dcsa" SDP syntax aspects
      Section 6.1.1 5.1.1 contained already procedural descriptions related to
      data channel reliability negotiation.  Creation of new
      Section 6.2.2 5.2.2 and moval of reliability negotiation related text to
      this new section.

11.4.

10.5.  Changes against 'draft-ejzak-mmusic-data-channel-sdpneg-02'

   o  Removal of note "[ACTION ITEM]" from section "subprotocol
      parameter".  As [I-D.ietf-rtcweb-data-protocol] this document
      should refer to IANA's WebSocket Subprotocol Name Registry defined
      in [RFC6455].

   o  In whole document, replacement of "unreliable" with "partially
      reliable", which is used in [I-D.ietf-rtcweb-data-channel] and in
      [I-D.ietf-rtcweb-data-protocol] in most places.

   o  Clarification of the semantic if the "max-retr" parameter is not
      present in an a=dcmap attribute line.  In section "max-retr
      parameter" the sentence "The max-retr parameter is optional with
      default value unbounded" was replaced with "The max-retr parameter
      is optional.  If the max-retr parameter is not present, then the
      maximal number of retransmissions is determined as per the generic
      SCTP retransmission rules as specified in [RFC4960]".

   o  Clarification of the semantic if the "max-time" parameter is not
      present in an a=dcmap attribute line.  In section "max-time
      parameter" the sentence "The max-time parameter is optional with
      default value unbounded" was replaced with "The max-time parameter
      is optional.  If the max-time parameter is not present, then the
      generic SCTP retransmission timing rules apply as specified in
      [RFC4960]".

   o  In section "label parameter" the sentence "Label is a mandatory
      parameter." was removed and following new sentences (including the
      note) were added: "The 'label' parameter is optional.  If it is
      not present, then its value defaults to the empty string.  Note:
      The empty string may also be explicitly used as 'label' value,
      such that 'label=""' is equivalent to the 'label' parameter not
      being present at all.  [I-D.ietf-rtcweb-data-protocol] allows the
      DATA_CHANNEL_OPEN message's 'Label' value to be an empty string."

   o  In section "subprotocol parameter" the sentence "Subprotocol is a
      mandatory parameter." was replaced with "'Subprotocol' is an
      optional parameter.  If the 'subprotocol' parameter is not
      present, then its value defaults to the empty string."

   o  In the "Examples" section, in the first two SDP offer examples in
      the a=dcmap attribute lines 'label="BGCP"' was replaced with
      'label="BFCP"'.

   o  In all examples, the "m" line proto value "DTLS/SCTP" was replaced
      with "UDP/DTLS/SCTP" and the "a=fmtp" attribute lines were
      replaced with "a=max-message-size" attribute lines, as per draft-
      ietf-mmusic-sctp-sdp-12.

11.5.

10.6.  Changes against '-01'

   o  Formal syntax for dcmap and dcsa attribute lines.

   o  Making subprotocol as an optional parameter in dcmap.

   o  Specifying disallowed parameter combinations for max-time and max-
      retr.

   o  Clarifications on WebRTC data channel close procedures.

11.6.

10.7.  Changes against '-00'

   o  Revisions to identify difference between internal and external
      negotiation and their usage.

   o  Introduction of more generic terminology, e.g. "application"
      instead of "browser".

   o  Clarification of how "max-retr and max-time affect the usage of
      unreliable and reliable WebRTC data channels.

   o  Updates of examples to take into account the SDP syntax changes
      introduced with draft-ietf-mmusic-sctp-sdp-07.

   o  Removal of the SCTP port number from the a=dcmap and a=dcsa
      attributes as this is now contained in the a=sctp-port attribute,
      and as draft-ietf-mmusic-sctp-sdp-07 supports only one SCTP
      association on top of the DTLS connection.

12.

11.  References

12.1.

11.1.  Normative References

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119,
              DOI 10.17487/RFC2119, March 1997,
              <http://www.rfc-editor.org/info/rfc2119>.

   [RFC4566]  Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
              Description Protocol", RFC 4566, DOI 10.17487/RFC4566,
              July 2006, <http://www.rfc-editor.org/info/rfc4566>.

   [RFC3264]  Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model
              with Session Description Protocol (SDP)", RFC 3264,
              DOI 10.17487/RFC3264, June 2002,
              <http://www.rfc-editor.org/info/rfc3264>.

   [RFC5234]  Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
              Specifications: ABNF", STD 68, RFC 5234,
              DOI 10.17487/RFC5234, January 2008,
              <http://www.rfc-editor.org/info/rfc5234>.

   [I-D.ietf-rtcweb-data-channel]
              Jesup, R., Loreto, S., and M. Tuexen, "WebRTC Data
              Channels", draft-ietf-rtcweb-data-channel-13 (work in
              progress), January 2015.

   [I-D.ietf-mmusic-sctp-sdp]
              Holmberg, C., Loreto, S., and G. Camarillo, "Stream
              Control Transmission Protocol (SCTP)-Based Media Transport
              in the Session Description Protocol (SDP)", draft-ietf-
              mmusic-sctp-sdp-14 (work in progress), March 2015.

12.2.

11.2.  Informative References

   [I-D.ietf-rtcweb-data-protocol]
              Jesup, R., Loreto, S., and M. Tuexen, "WebRTC Data Channel
              Establishment Protocol", draft-ietf-rtcweb-data-
              protocol-09 (work in progress), January 2015.

   [RFC4960]  Stewart, R., Ed., "Stream Control Transmission Protocol",
              RFC 4960, DOI 10.17487/RFC4960, September 2007,
              <http://www.rfc-editor.org/info/rfc4960>.

   [RFC4975]  Campbell, B., Ed., Mahy, R., Ed., and C. Jennings, Ed.,
              "The Message Session Relay Protocol (MSRP)", RFC 4975,
              DOI 10.17487/RFC4975, September 2007,
              <http://www.rfc-editor.org/info/rfc4975>.

   [RFC4976]  Jennings, C., Mahy, R., and A. Roach, "Relay Extensions
              for the Message Sessions Relay Protocol (MSRP)", RFC 4976,
              DOI 10.17487/RFC4976, September 2007,
              <http://www.rfc-editor.org/info/rfc4976>.

   [RFC5547]  Garcia-Martin, M., Isomaki, M., Camarillo, G., Loreto, S.,
              and P. Kyzivat, "A Session Description Protocol (SDP)
              Offer/Answer Mechanism to Enable File Transfer", RFC 5547,
              DOI 10.17487/RFC5547, May 2009,
              <http://www.rfc-editor.org/info/rfc5547>.

   [RFC6135]  Holmberg, C. and S. Blau, "An Alternative Connection Model
              for the Message Session Relay Protocol (MSRP)", RFC 6135,
              DOI 10.17487/RFC6135, February 2011,
              <http://www.rfc-editor.org/info/rfc6135>.

   [RFC6455]  Fette, I. and A. Melnikov, "The WebSocket Protocol",
              RFC 6455, DOI 10.17487/RFC6455, December 2011,
              <http://www.rfc-editor.org/info/rfc6455>.

   [RFC6714]  Holmberg, C., Blau, S., and E. Burger, "Connection
              Establishment for Media Anchoring (CEMA) for the Message
              Session Relay Protocol (MSRP)", RFC 6714,
              DOI 10.17487/RFC6714, August 2012,
              <http://www.rfc-editor.org/info/rfc6714>.

   [I-D.ietf-rtcweb-jsep]
              Uberti, J., Jennings, C., and E. Rescorla, "Javascript
              Session Establishment Protocol", draft-ietf-rtcweb-jsep-11
              (work in progress), July 2015.

   [IANA-SDP-Parameters]
              "Session Description Protocol (SDP) Parameters", Internet
              Assigned Numbers Authority Protocol Assignments Session
              Description Protocol (SDP) Parameters,
              <http://www.iana.org/assignments/sdp-parameters/
              sdp-parameters.xhtml>.

   [WebRtcAPI]
              Bergkvist, A., Burnett, D., Jennings, C., and A.
              Narayanan, "WebRTC 1.0: Real-time Communication Between
              Browsers", World Wide Web Consortium WD-webrtc-20150210,
              February 2015,
              <http://www.w3.org/TR/2015/WD-webrtc-20150210/>.

Appendix A.  Generic Data Channel Negotiation Aspects When Not Using
             DCEP

   This appendix summarizes how data channels work in general and
   discusses some key aspects, which should be considered for the out-
   of-band negotiation of data channels if DCEP is not used.

   A WebRTC application creates a data channel by providing a number of
   setup parameters (sub-protocol, label, reliability, order of
   delivery, priority).  The application also specifies if it wants to
   make use of the negotiation using the DCEP
   [I-D.ietf-rtcweb-data-protocol], or if the application intends to
   negotiate data channels using the SDP offer/answer protocol.

   In any case, the SDP offer generated by the application is per
   [I-D.ietf-mmusic-sctp-sdp].  In brief, it contains one "m" line for
   the SCTP association on top of which data channels will run:

   m=application 54111 UDP/DTLS/SCTP webrtc-datachannel
   c=IN IP4 79.97.215.79
   a=max-message-size:100000
   a=sctp-port:5000
   a=setup:actpass
   a=connection:new
   a=fingerprint:SHA-1 \
       4A:AD:B9:B1:3F:82:18:3B:54:02:12:DF:3E:5D:49:6B:19:E5:7C:AB

   Note: A WebRTC application will only use "m" line format "webrtc-
   datachannel", and will not use other formats in the "m" line for
   other protocols such as t38.  [I-D.ietf-mmusic-sctp-sdp] supports
   only one SCTP association to be established on top of a DTLS
   association.

   Note: Above SDP media description does not contain any channel-
   specific information.

A.1.  Stream Identifier Numbering

   Independently from the requested type of negotiation, the application
   creating a data channel can either pass to the data channel stack the
   stream identifier to assign to the data channel or else let the data
   channel stack pick one identifier from the ones unused.

   To avoid glare situations, each endpoint can moreover own an
   exclusive set of stream identifiers, in which case an endpoint can
   only create a data channel with a stream identifier it owns.

   Which set of stream identifiers is owned by which endpoint is
   determined by convention or other means.

      For data channels negotiated with the DCEP, one endpoint owns by
      convention the even stream identifiers, whereas the other owns the
      odd stream identifiers, as defined in
      [I-D.ietf-rtcweb-data-protocol].

      For data channels negotiated via some protocol different from
      DCEP, no convention is defined by default.

A.2.  Generic Data Channel Negotiation Not Using DCEP

A.2.1.  Overview

   DCEP negotiation only provides for negotiation of data channel
   transport parameters and does not provide for negotiation of sub-
   protocol specific parameters.  DCEP-less data channel negotiation can
   be defined to allow negotiation of parameters beyond those handled by
   DCEP, e.g., parameters specific to the sub-protocol instantiated on a
   particular data channel.

   The following procedures are common to all methods of data channel
   negotiation not using DCEP, whether in-band (communicated using
   proprietary means on an already established data channel) or out-of-
   band (using SDP offer/answer or some other protocol associated with
   the signaling channel).

A.2.2.  Opening a Data Channel

   In the case of DCEP-less negotiation, the endpoint application has
   the option to fully control the stream identifier assignments.
   However these assignments have to coexist with the assignments
   controlled by the data channel stack for the DCEP negotiated data
   channels (if any).  It is the responsibility of the application to
   ensure consistent assignment of stream identifiers.

   When the application requests the creation of a new data channel to
   be set up via DCEP-less negotiation, the data channel stack creates
   the data channel locally without sending any DATA_CHANNEL_OPEN
   message in-band.  However, even if the ICE, DTLS and SCTP procedures
   were already successfully completed, the application can't send data
   on this data channel until the negotiation is complete with the peer.
   This is because the peer needs to be aware of and accept the usage of
   this data channel.  The peer, after accepting the data channel offer,
   can start sending data immediately.  This implies that the offerer
   may receive data channel sub-protocol messages before the negotiation
   is complete and the application should be ready to handle it.

   If the peer rejects the data channel part of the offer then it
   doesn't have to do anything as the data channel was not created using
   the stack.  The offerer on the other hand needs to close the data
   channel that was opened by invoking relevant data channel stack API
   procedures.

   It is also worth noting that a data channel stack implementation may
   not provide any API to create and close data channels; instead the
   data channels may be used on the fly as needed just by communicating
   via non-DCEP means or by even having some local configuration/
   assumptions on both the peers.

   The application then negotiates the data channel properties and sub-
   protocol properties with the peer's application using a mechanism
   different from DCEP.

   The peer then symmetrically creates a data channel with these
   negotiated data channel properties.  This is the only way for the
   peer's data channel stack to know which properties to apply when
   transmitting data on this channel.  The data channel stack must allow
   data channel creation with any non-conflicting stream identifier so
   that both peers can create the data channel with the same stream
   identifier.

A.2.3.  Closing a Data Channel

   When the application requests the closing of a data channel
   negotiated without DCEP, the data channel stack always performs an
   SCTP SSN reset for this channel.

   Depending upon the method used for DCEP-less negotiation and the sub-
   protocol associated with the data channel, the closing might in
   addition be signaled to the peer via SDP offer/answer negotiation.

Authors' Addresses

   Keith Drage (editor)
   Alcatel-Lucent
   Quadrant, Stonehill Green, Westlea
   Swindon
   UK

   Email: keith.drage@alcatel-lucent.com

   Maridi R. Makaraju (Raju)
   Alcatel-Lucent
   2000 Lucent Lane
   Naperville, Illinois
   US

   Email: Raju.Makaraju@alcatel-lucent.com

   Juergen Stoetzer-Bradler
   Alcatel-Lucent
   Lorenzstrasse 10
   D-70435 Stuttgart
   Germany

   Email: Juergen.Stoetzer-Bradler@alcatel-lucent.com

   Richard Ejzak
   Unaffiliated

   Email: richard.ejzak@gmail.com

   Jerome Marcon
   Unaffiliated