WebRTC Data Channel Protocol
draft-jesup-rtcweb-data-protocol-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2012-06-09
Replaced by draft-ietf-rtcweb-data-protocol
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)
RTCWeb Working Group                                            R. Jesup
Internet-Draft                                                   Mozilla
Intended status: Standards Track                               S. Loreto
Expires: December 11, 2012                                      Ericsson
                                                               M. Tuexen
                                        Muenster Univ. of Appl. Sciences
                                                            June 9, 2012

                      WebRTC Data Channel Protocol
                draft-jesup-rtcweb-data-protocol-01.txt

Abstract

   The Web Real-Time Communication (WebRTC) working group is charged to
   provide protocols to support for direct interactive rich
   communication using audio, video, and data between two peers' web-
   browsers.  This document specifies an actual (minor) protocol for how
   the JS-layer dataChannel objects provide the data channels between
   the peers.

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 December 11, 2012.

Copyright Notice

   Copyright (c) 2012 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

Jesup, et al.           Expires December 11, 2012               [Page 1]
Internet-Draft        WebRTC Data Channel Protocol             June 2012

   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.  Opening Handshake . . . . . . . . . . . . . . . . . . . . . . . 3
   5.  Control Messages  . . . . . . . . . . . . . . . . . . . . . . . 4
     5.1.  DATA_CHANNEL_OPEN_REQUEST Message . . . . . . . . . . . . . 4
     5.2.  DATA_CHANNEL_OPEN_RESPONSE Message  . . . . . . . . . . . . 5
     5.3.  DATA_CHANNEL_ACK Message  . . . . . . . . . . . . . . . . . 6
   6.  Procedures  . . . . . . . . . . . . . . . . . . . . . . . . . . 6
     6.1.  Adding a Channel  . . . . . . . . . . . . . . . . . . . . . 6
     6.2.  Closing a Channel . . . . . . . . . . . . . . . . . . . . . 7
     6.3.  Sending and Receiving Data  . . . . . . . . . . . . . . . . 7
   7.  Security Considerations . . . . . . . . . . . . . . . . . . . . 7
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 8
   9.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 8
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . . . 8
     10.1. Normative References  . . . . . . . . . . . . . . . . . . . 8
     10.2. Informational References  . . . . . . . . . . . . . . . . . 9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 9

Jesup, et al.           Expires December 11, 2012               [Page 2]
Internet-Draft        WebRTC Data Channel Protocol             June 2012

1.  Introduction

   The Data Channel Protocol is designed to provide, in the WebRTC
   context [I-D.ietf-rtcweb-overview], a generic transport service
   allowing Web Browser to exchange generic data in a bidirectional peer
   to peer fashion.  As discussed in [I-D.ietf-rtcweb-data-channel] the
   protocol uses Stream Control Transmission Protocol (SCTP) [RFC4960]
   encapsulated on Datagram Transport Layer Security (DTLS) [RFC6347] as
   described in [I-D.tuexen-tsvwg-sctp-dtls-encaps] to benefit from
   their already standardized transport and security features.

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:
Show full document text