RTCWeb Datagram Connection
draft-ietf-rtcweb-data-channel-01

The information below is for an old version of the document
Document Type Active Internet-Draft (rtcweb WG)
Last updated 2012-09-07
Stream IETF
Intended RFC status (None)
Formats pdf htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
RTCWeb Working Group                                            R. Jesup
Internet-Draft                                                   Mozilla
Intended status: Informational                                 S. Loreto
Expires: March 11, 2013                                         Ericsson
                                                               M. Tuexen
                                        Muenster Univ. of Appl. Sciences
                                                       September 7, 2012

                       RTCWeb Datagram Connection
                 draft-ietf-rtcweb-data-channel-01.txt

Abstract

   The Web Real-Time Communication (WebRTC) working group is charged to
   provide protocol support for direct interactive rich communication
   using audio, video, and data between two peers' web-browsers.  This
   document describes the non-media data transport aspects of the WebRTC
   framework.  It provides an architectural overview of how the Stream
   Control Transmission Protocol (SCTP) is used in the WebRTC context as
   a generic transport service allowing Web Browser to exchange generic
   data from peer to peer.

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 March 11, 2013.

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

Jesup, et al.            Expires March 11, 2013                 [Page 1]
Internet-Draft             data P2P in RTCWEB             September 2012

   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.  Requirements . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Use Cases  . . . . . . . . . . . . . . . . . . . . . . . . . .  5
     3.1.  Use Cases for Unreliable Datagram Based Channels . . . . .  5
     3.2.  Use Cases for Reliable Channels (Datagram or Stream
           Based) . . . . . . . . . . . . . . . . . . . . . . . . . .  5
   4.  Datagrams over SCTP over DTLS over UDP . . . . . . . . . . . .  6
   5.  The Envisioned Usage of SCTP in the RTCWeb Context . . . . . .  8
     5.1.  Association Setup  . . . . . . . . . . . . . . . . . . . .  8
     5.2.  SCTP Streams . . . . . . . . . . . . . . . . . . . . . . .  9
     5.3.  Channel Definition . . . . . . . . . . . . . . . . . . . .  9
     5.4.  Usage of Payload Protocol Identifier . . . . . . . . . . .  9
   6.  Minor Protocol and Message Format  . . . . . . . . . . . . . . 10
   7.  Security Considerations  . . . . . . . . . . . . . . . . . . . 10
   8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 10
   9.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 10
   10. Informative References . . . . . . . . . . . . . . . . . . . . 10
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11

Jesup, et al.            Expires March 11, 2013                 [Page 2]
Internet-Draft             data P2P in RTCWEB             September 2012

1.  Introduction

   The issue of how best to handle non-media data types in the context
   of RTCWEB has reached a general consensus on the usage of SCTP
   [RFC4960] encapsulated on DTLS [RFC6347]:

                                +----------+
                                |   SCTP   |
                                +----------+
                                |   DTLS   |
                                +----------+
                                | ICE/UDP  |
                                +----------+

                       Figure 1: Basic stack diagram

   The encapsulation of SCTP over DTLS over ICE/UDP provides a NAT
   traversal solution together with confidentiality, source
Show full document text