SDP-based "SCTP over DTLS" data channel negotiation
draft-ejzak-mmusic-data-channel-sdpneg-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2014-10-20
Replaces draft-ejzak-dispatch-webrtc-data-channel-sdpneg
Replaced by draft-ietf-mmusic-data-channel-sdpneg
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
MMUSIC                                                     K. Drage, Ed.
Internet-Draft                                               M. Makaraju
Intended status: Standards Track                          Alcatel-Lucent
Expires: April 23, 2015                                         R. Ejzak
                                                               J. Marcon
                                                            Unaffiliated
                                                        October 20, 2014

          SDP-based "SCTP over DTLS" data channel negotiation
               draft-ejzak-mmusic-data-channel-sdpneg-01

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 internal in-band band (also referred to
   as 'internal' for the rest of the document) WebRTC Data Channel
   Establishment Protocol or some external out-of-band simply referred
   to as 'external negotiation' in the rest of the document . This
   document specifies how the SDP offer/answer exchange can be used to
   achieve such an external 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 April 23, 2015.

Drage, et al.            Expires April 23, 2015                 [Page 1]
Internet-Draft     SDP-based data channel negotiation       October 2014

Copyright Notice

   Copyright (c) 2014 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
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Data Channels . . . . . . . . . . . . . . . . . . . . . . . .   4
     4.1.  Stream identifier numbering . . . . . . . . . . . . . . .   5
     4.2.  Generic external negotiation  . . . . . . . . . . . . . .   5
       4.2.1.  Overview  . . . . . . . . . . . . . . . . . . . . . .   6
       4.2.2.  Opening a data channel  . . . . . . . . . . . . . . .   6
       4.2.3.  Closing a data channel  . . . . . . . . . . . . . . .   7
   5.  SDP-based external negotiation  . . . . . . . . . . . . . . .   7
     5.1.  SDP syntax  . . . . . . . . . . . . . . . . . . . . . . .   8
       5.1.1.  SDP attribute for data channel parameter negotiation    8
         5.1.1.1.  dcmap attribute . . . . . . . . . . . . . . . . .   9
         5.1.1.2.  label parameter . . . . . . . . . . . . . . . . .  10
         5.1.1.3.  subprotocol parameter . . . . . . . . . . . . . .  10
         5.1.1.4.  max_retr parameter  . . . . . . . . . . . . . . .  10
         5.1.1.5.  max_time parameter  . . . . . . . . . . . . . . .  10
         5.1.1.6.  unordered parameter . . . . . . . . . . . . . . .  11
       5.1.2.  Sub-protocol specific attributes  . . . . . . . . . .  11
     5.2.  Procedures  . . . . . . . . . . . . . . . . . . . . . . .  12
       5.2.1.  Managing stream identifiers . . . . . . . . . . . . .  12
       5.2.2.  Opening a data channel  . . . . . . . . . . . . . . .  12
Show full document text