draft-ietf-mmusic-data-channel-sdpneg-27.txt   draft-ietf-mmusic-data-channel-sdpneg-28.txt 
MMUSIC K. Drage MMUSIC K. Drage
Internet-Draft Unaffiliated Internet-Draft Unaffiliated
Intended status: Standards Track M. Makaraju Intended status: Standards Track M. Makaraju
Expires: October 31, 2019 Nokia Expires: November 12, 2019 Nokia
R. Ejzak R. Ejzak
J. Marcon J. Marcon
Unaffiliated Unaffiliated
R. Even, Ed. R. Even, Ed.
Huawei Huawei
April 29, 2019 May 11, 2019
SDP-based Data Channel Negotiation SDP-based Data Channel Negotiation
draft-ietf-mmusic-data-channel-sdpneg-27 draft-ietf-mmusic-data-channel-sdpneg-28
Abstract Abstract
Data channel setup can be done using either the in-band Data Channel Data channel setup can be done using either the in-band Data Channel
Establishment Protocol (DCEP) or using some out-of-band non-DCEP Establishment Protocol (DCEP) or using some out-of-band non-DCEP
protocol. This document specifies how the SDP (Session Description protocol. This document specifies how the SDP (Session Description
Protocol) offer/answer exchange can be used to achieve an out-of-band Protocol) offer/answer exchange can be used to achieve an out-of-band
non-DCEP negotiation for establishing a data channel. non-DCEP negotiation for establishing a data channel.
Status of This Memo Status of This Memo
skipping to change at page 1, line 40 skipping to change at page 1, line 40
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 31, 2019. This Internet-Draft will expire on November 12, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Applicability Statement . . . . . . . . . . . . . . . . . . . 5 4. Applicability Statement . . . . . . . . . . . . . . . . . . . 6
5. SDP Data Channel Attributes . . . . . . . . . . . . . . . . . 6 5. SDP Data Channel Attributes . . . . . . . . . . . . . . . . . 6
5.1. SDP DCMAP Attribute . . . . . . . . . . . . . . . . . . . 6 5.1. SDP DCMAP Attribute . . . . . . . . . . . . . . . . . . . 6
5.1.1. DCMAP Attribute Syntax . . . . . . . . . . . . . . . 6 5.1.1. DCMAP Attribute Syntax . . . . . . . . . . . . . . . 6
5.1.2. Dcmap-stream-id Parameter . . . . . . . . . . . . . . 8 5.1.2. Dcmap-stream-id Parameter . . . . . . . . . . . . . . 8
5.1.3. Label Parameter . . . . . . . . . . . . . . . . . . . 8 5.1.3. Label Parameter . . . . . . . . . . . . . . . . . . . 8
5.1.4. Subprotocol Parameter . . . . . . . . . . . . . . . . 8 5.1.4. Subprotocol Parameter . . . . . . . . . . . . . . . . 8
5.1.5. Max-retr Parameter . . . . . . . . . . . . . . . . . 9 5.1.5. Max-retr Parameter . . . . . . . . . . . . . . . . . 9
5.1.6. Max-time Parameter . . . . . . . . . . . . . . . . . 9 5.1.6. Max-time Parameter . . . . . . . . . . . . . . . . . 9
5.1.7. Ordered Parameter . . . . . . . . . . . . . . . . . . 9 5.1.7. Ordered Parameter . . . . . . . . . . . . . . . . . . 9
5.1.8. Priority Parameter . . . . . . . . . . . . . . . . . 9 5.1.8. Priority Parameter . . . . . . . . . . . . . . . . . 10
5.1.9. DCMAP Multiplexing Category . . . . . . . . . . . . . 10 5.1.9. DCMAP Multiplexing Category . . . . . . . . . . . . . 10
5.2. SDP DCSA Attribute . . . . . . . . . . . . . . . . . . . 10 5.2. SDP DCSA Attribute . . . . . . . . . . . . . . . . . . . 10
5.2.1. DCSA Syntax . . . . . . . . . . . . . . . . . . . . . 11 5.2.1. DCSA Syntax . . . . . . . . . . . . . . . . . . . . . 11
5.2.2. DCSA Multiplexing Category . . . . . . . . . . . . . 12 5.2.2. DCSA Multiplexing Category . . . . . . . . . . . . . 12
6. SDP Offer/Answer Procedures . . . . . . . . . . . . . . . . . 12 6. SDP Offer/Answer Procedures . . . . . . . . . . . . . . . . . 13
6.1. Managing Stream Identifiers . . . . . . . . . . . . . . . 13 6.1. Managing Stream Identifiers . . . . . . . . . . . . . . . 13
6.2. Negotiating Data Channel Parameters . . . . . . . . . . . 13 6.2. Negotiating Data Channel Parameters . . . . . . . . . . . 13
6.3. Generating the Initial Offer for A Data Channel . . . . . 14 6.3. Generating the Initial Offer for A Data Channel . . . . . 14
6.4. Generating SDP Answer . . . . . . . . . . . . . . . . . . 14 6.4. Generating SDP Answer . . . . . . . . . . . . . . . . . . 14
6.5. Offerer Processing of the SDP Answer . . . . . . . . . . 15 6.5. Offerer Processing of the SDP Answer . . . . . . . . . . 15
6.6. Modifying the Session . . . . . . . . . . . . . . . . . . 15 6.6. Modifying the Session . . . . . . . . . . . . . . . . . . 15
6.6.1. Closing a Data Channel . . . . . . . . . . . . . . . 16 6.6.1. Closing a Data Channel . . . . . . . . . . . . . . . 16
6.7. Various SDP Offer/Answer Considerations . . . . . . . . . 16 6.7. Various SDP Offer/Answer Considerations . . . . . . . . . 16
7. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 17 7. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 17
8. Security Considerations . . . . . . . . . . . . . . . . . . . 19 8. Security Considerations . . . . . . . . . . . . . . . . . . . 19
skipping to change at page 4, line 44 skipping to change at page 4, line 44
negotiate the use of a data channel to transport MSRP. Procedures negotiate the use of a data channel to transport MSRP. Procedures
specific to each subprotocol would have to be documented elsewhere. specific to each subprotocol would have to be documented elsewhere.
For MSRP they are documented in For MSRP they are documented in
[I-D.ietf-mmusic-msrp-usage-data-channel] . The use of MSRP in some [I-D.ietf-mmusic-msrp-usage-data-channel] . The use of MSRP in some
examples is only to show how the generic procedures described herein examples is only to show how the generic procedures described herein
might apply to a specific subprotocol. might apply to a specific subprotocol.
2. Conventions 2. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED","MAY", and
document are to be interpreted as described in [RFC2119] [RFC8174] "OPTIONAL" in this document are to be interpreted as described in
BCP14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
3. Terminology 3. Terminology
This document uses the following terms: This document uses the following terms:
Data channel: A WebRTC data channel as specified in Data channel: A WebRTC data channel as specified in
[I-D.ietf-rtcweb-data-channel]. [I-D.ietf-rtcweb-data-channel].
Data channel stack: An entity which, upon application request, Data channel stack: An entity which, upon application request,
runs the data channel protocol to keep track of states, sending runs the data channel protocol to keep track of states, sending
 End of changes. 8 change blocks. 
10 lines changed or deleted 12 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/