SDP-based Data Channel Negotiation
draft-ietf-mmusic-data-channel-sdpneg-07
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (mmusic WG)
|
|
Last updated |
|
2015-11-30
|
|
Replaces |
|
draft-ejzak-mmusic-data-channel-sdpneg
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
Proposed Standard
|
|
Formats |
|
pdf
htmlized
bibtex
|
|
Reviews |
|
|
| Stream |
WG state
|
|
In WG Last Call
|
|
Document shepherd |
|
Bo Burman
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
"Bo Burman" <bo.burman@ericsson.com>
|
MMUSIC K. Drage, Ed.
Internet-Draft M. Makaraju
Intended status: Standards Track J. Stoetzer-Bradler
Expires: June 2, 2016 Alcatel-Lucent
R. Ejzak
J. Marcon
Unaffiliated
November 30, 2015
SDP-based Data Channel Negotiation
draft-ietf-mmusic-data-channel-sdpneg-07
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 (Stream Control Transmission Protocol), where each
data channel might be used to transport other protocols, called
subprotocols. 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 (Session
Description Protocol) 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 (which is
defined by the IETF "ControLling mUltiple streams for tElepresence"
working group). 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."
Drage, et al. Expires June 2, 2016 [Page 1]
Internet-Draft SDP-based Data Channel Negotiation November 2015
This Internet-Draft will expire on June 2, 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 . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Applicability Statement . . . . . . . . . . . . . . . . . . . 5
5. SDP Offer/Answer Negotiation . . . . . . . . . . . . . . . . 5
5.1. SDP Syntax . . . . . . . . . . . . . . . . . . . . . . . 5
5.1.1. SDP Attribute for Data Channel Parameter Negotiation 5
5.1.1.1. dcmap Attribute . . . . . . . . . . . . . . . . . 6
5.1.1.2. dcmap Multiplexing Category . . . . . . . . . . . 7
5.1.1.3. dcmap-stream-id Parameter . . . . . . . . . . . . 8
5.1.1.4. label Parameter . . . . . . . . . . . . . . . . . 8
5.1.1.5. subprotocol Parameter . . . . . . . . . . . . . . 8
5.1.1.6. max-retr Parameter . . . . . . . . . . . . . . . 8
5.1.1.7. max-time Parameter . . . . . . . . . . . . . . . 9
5.1.1.8. ordered Parameter . . . . . . . . . . . . . . . . 9
5.1.1.9. priority Parameter . . . . . . . . . . . . . . . 9
5.1.2. Other Media Level Attributes . . . . . . . . . . . . 9
5.1.2.1. dcsa Attribute . . . . . . . . . . . . . . . . . 10
5.1.2.2. dcsa Multiplexing Category . . . . . . . . . . . 11
5.2. Procedures . . . . . . . . . . . . . . . . . . . . . . . 11
5.2.1. Managing Stream Identifiers . . . . . . . . . . . . . 11
5.2.2. Negotiating Data Channel Parameters . . . . . . . . . 12
Show full document text