Network Working Group R. Jesup
Internet-Draft Mozilla
Intended status: Standards Track S. Loreto
Expires: August 29, 2013 Ericsson
M. Tuexen
Muenster Univ. of Appl. Sciences
February 25, 2013
RTCWeb Data Channels
draft-ietf-rtcweb-data-channel-04.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 specifies 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 August 29, 2013.
Copyright Notice
Copyright (c) 2013 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 August 29, 2013 [Page 1]
Internet-Draft RTCWeb Data Channels February 2013
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. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Use Cases for Unreliable Data Channels . . . . . . . . . . 4
3.2. Use Cases for Reliable Data Channels . . . . . . . . . . . 4
4. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 4
5. SCTP over DTLS over UDP Considerations . . . . . . . . . . . . 6
6. The Usage of SCTP in the RTCWeb Context . . . . . . . . . . . 9
6.1. Association Setup . . . . . . . . . . . . . . . . . . . . 9
6.2. SCTP Streams . . . . . . . . . . . . . . . . . . . . . . . 9
6.3. Channel Definition . . . . . . . . . . . . . . . . . . . . 9
6.4. Usage of Payload Protocol Identifier . . . . . . . . . . . 10
7. Security Considerations . . . . . . . . . . . . . . . . . . . 10
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10
10.1. Normative References . . . . . . . . . . . . . . . . . . . 10
10.2. Informative References . . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12
Jesup, et al. Expires August 29, 2013 [Page 2]
Internet-Draft RTCWeb Data Channels February 2013
1. Introduction
Non-media data types in the context of RTCWeb are handled by using
SCTP [RFC4960] encapsulated in DTLS [RFC6347].
+----------+
| SCTP |
+----------+
| DTLS |
+----------+
| ICE/UDP |
+----------+
Figure 1: Basic stack diagram
datatracker.ietf.org