draft-ietf-rtcweb-data-channel-09.txt   draft-ietf-rtcweb-data-channel-10.txt 
Network Working Group R. Jesup Network Working Group R. Jesup
Internet-Draft Mozilla Internet-Draft Mozilla
Intended status: Standards Track S. Loreto Intended status: Standards Track S. Loreto
Expires: November 16, 2014 Ericsson Expires: December 11, 2014 Ericsson
M. Tuexen M. Tuexen
Muenster Univ. of Appl. Sciences Muenster Univ. of Appl. Sciences
May 15, 2014 June 9, 2014
WebRTC Data Channels WebRTC Data Channels
draft-ietf-rtcweb-data-channel-09.txt draft-ietf-rtcweb-data-channel-10.txt
Abstract Abstract
The Real-Time Communication in WEB-browsers working group is charged The Real-Time Communication in WEB-browsers working group is charged
to provide protocol support for direct interactive rich communication to provide protocol support for direct interactive rich communication
using audio, video, and data between two peers' web-browsers. This using audio, video, and data between two peers' web-browsers. This
document specifies the non-SRTP media data transport aspects of the document specifies the non-SRTP media data transport aspects of the
WebRTC framework. It provides an architectural overview of how the WebRTC framework. It provides an architectural overview of how the
Stream Control Transmission Protocol (SCTP) is used in the WebRTC Stream Control Transmission Protocol (SCTP) is used in the WebRTC
context as a generic transport service allowing WEB-browsers to context as a generic transport service allowing WEB-browsers to
skipping to change at page 1, line 40 skipping to change at page 1, line 40
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on November 16, 2014. This Internet-Draft will expire on December 11, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 29 skipping to change at page 2, line 29
5. SCTP over DTLS over UDP Considerations . . . . . . . . . . . 5 5. SCTP over DTLS over UDP Considerations . . . . . . . . . . . 5
6. The Usage of SCTP for Data Channels . . . . . . . . . . . . . 8 6. The Usage of SCTP for Data Channels . . . . . . . . . . . . . 8
6.1. SCTP Protocol Considerations . . . . . . . . . . . . . . 8 6.1. SCTP Protocol Considerations . . . . . . . . . . . . . . 8
6.2. Association Setup . . . . . . . . . . . . . . . . . . . . 9 6.2. Association Setup . . . . . . . . . . . . . . . . . . . . 9
6.3. SCTP Streams . . . . . . . . . . . . . . . . . . . . . . 9 6.3. SCTP Streams . . . . . . . . . . . . . . . . . . . . . . 9
6.4. Channel Definition . . . . . . . . . . . . . . . . . . . 9 6.4. Channel Definition . . . . . . . . . . . . . . . . . . . 9
6.5. Opening a Channel . . . . . . . . . . . . . . . . . . . . 10 6.5. Opening a Channel . . . . . . . . . . . . . . . . . . . . 10
6.6. Transferring User Data on a Channel . . . . . . . . . . . 10 6.6. Transferring User Data on a Channel . . . . . . . . . . . 10
6.7. Closing a Channel . . . . . . . . . . . . . . . . . . . . 11 6.7. Closing a Channel . . . . . . . . . . . . . . . . . . . . 11
7. Security Considerations . . . . . . . . . . . . . . . . . . . 11 7. Security Considerations . . . . . . . . . . . . . . . . . . . 11
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
10.1. Normative References . . . . . . . . . . . . . . . . . . 12 10.1. Normative References . . . . . . . . . . . . . . . . . . 12
10.2. Informative References . . . . . . . . . . . . . . . . . 14 10.2. Informative References . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14
1. Introduction 1. Introduction
Non-SRTP media data types in the context of WebRTC are handled by Non-SRTP media data types in the context of WebRTC are handled by
using SCTP [RFC4960] encapsulated in DTLS [RFC6347]. using SCTP [RFC4960] encapsulated in DTLS [RFC6347].
skipping to change at page 9, line 46 skipping to change at page 9, line 46
6.4. Channel Definition 6.4. Channel Definition
The W3C has consensus on defining the application API for WebRTC The W3C has consensus on defining the application API for WebRTC
DataChannels to be bidirectional. They also consider the notions of DataChannels to be bidirectional. They also consider the notions of
in-sequence, out-of-sequence, reliable and unreliable as properties in-sequence, out-of-sequence, reliable and unreliable as properties
of Channels. One strong wish is for the application-level API to be of Channels. One strong wish is for the application-level API to be
close to the API for WebSockets, which implies bidirectional streams close to the API for WebSockets, which implies bidirectional streams
of data and waiting for onopen to fire before sending, a textual of data and waiting for onopen to fire before sending, a textual
label used to identify the meaning of the stream, among other things. label used to identify the meaning of the stream, among other things.
Each data channel also has a priority. These priorities MUST NOT be
strict priorities. Each data channel also has a priority, which is an 2 byte unsigned
integer value. These priorities MUST be interpreted as weighted-
fair-queuing scheduling priorities per the definition of the
corresponding stream scheduler supporting interleaving in
[I-D.ietf-tsvwg-sctp-ndata]. For use in WebRTC, the values used
SHOULD be one of 128 ("below normal"), 256 ("normal"), 512 ("high")
or 1024 ("extra high").
The realization of a bidirectional Data Channel is a pair of one The realization of a bidirectional Data Channel is a pair of one
incoming stream and one outgoing SCTP stream having the same stream incoming stream and one outgoing SCTP stream having the same stream
SCTP identifier. SCTP identifier.
How stream values are selected is protocol and implementation How stream values are selected is protocol and implementation
dependent. dependent.
6.5. Opening a Channel 6.5. Opening a Channel
skipping to change at page 13, line 31 skipping to change at page 13, line 37
[I-D.ietf-tsvwg-sctp-ndata] [I-D.ietf-tsvwg-sctp-ndata]
Stewart, R., Tuexen, M., Loreto, S., and R. Seggelmann, "A Stewart, R., Tuexen, M., Loreto, S., and R. Seggelmann, "A
New Data Chunk for Stream Control Transmission Protocol", New Data Chunk for Stream Control Transmission Protocol",
draft-ietf-tsvwg-sctp-ndata-00 (work in progress), draft-ietf-tsvwg-sctp-ndata-00 (work in progress),
February 2014. February 2014.
[I-D.ietf-rtcweb-data-protocol] [I-D.ietf-rtcweb-data-protocol]
Jesup, R., Loreto, S., and M. Tuexen, "WebRTC Data Channel Jesup, R., Loreto, S., and M. Tuexen, "WebRTC Data Channel
Establishment Protocol", draft-ietf-rtcweb-data- Establishment Protocol", draft-ietf-rtcweb-data-
protocol-04 (work in progress), April 2014. protocol-05 (work in progress), May 2014.
[I-D.ietf-tsvwg-sctp-dtls-encaps] [I-D.ietf-tsvwg-sctp-dtls-encaps]
Tuexen, M., Stewart, R., Jesup, R., and S. Loreto, "DTLS Tuexen, M., Stewart, R., Jesup, R., and S. Loreto, "DTLS
Encapsulation of SCTP Packets", draft-ietf-tsvwg-sctp- Encapsulation of SCTP Packets", draft-ietf-tsvwg-sctp-
dtls-encaps-04 (work in progress), May 2014. dtls-encaps-04 (work in progress), May 2014.
[I-D.ietf-rtcweb-security] [I-D.ietf-rtcweb-security]
Rescorla, E., "Security Considerations for WebRTC", draft- Rescorla, E., "Security Considerations for WebRTC", draft-
ietf-rtcweb-security-06 (work in progress), January 2014. ietf-rtcweb-security-06 (work in progress), January 2014.
skipping to change at page 14, line 9 skipping to change at page 14, line 14
[I-D.ietf-rtcweb-jsep] [I-D.ietf-rtcweb-jsep]
Uberti, J. and C. Jennings, "Javascript Session Uberti, J. and C. Jennings, "Javascript Session
Establishment Protocol", draft-ietf-rtcweb-jsep-06 (work Establishment Protocol", draft-ietf-rtcweb-jsep-06 (work
in progress), February 2014. in progress), February 2014.
[I-D.ietf-tsvwg-sctp-prpolicies] [I-D.ietf-tsvwg-sctp-prpolicies]
Tuexen, M., Seggelmann, R., Stewart, R., and S. Loreto, Tuexen, M., Seggelmann, R., Stewart, R., and S. Loreto,
"Additional Policies for the Partial Reliability Extension "Additional Policies for the Partial Reliability Extension
of the Stream Control Transmission Protocol", draft-ietf- of the Stream Control Transmission Protocol", draft-ietf-
tsvwg-sctp-prpolicies-02 (work in progress), April 2014. tsvwg-sctp-prpolicies-03 (work in progress), May 2014.
[I-D.ietf-mmusic-sctp-sdp] [I-D.ietf-mmusic-sctp-sdp]
Loreto, S. and G. Camarillo, "Stream Control Transmission Loreto, S. and G. Camarillo, "Stream Control Transmission
Protocol (SCTP)-Based Media Transport in the Session Protocol (SCTP)-Based Media Transport in the Session
Description Protocol (SDP)", draft-ietf-mmusic-sctp-sdp-06 Description Protocol (SDP)", draft-ietf-mmusic-sctp-sdp-06
(work in progress), February 2014. (work in progress), February 2014.
10.2. Informative References 10.2. Informative References
[RFC5764] McGrew, D. and E. Rescorla, "Datagram Transport Layer [RFC5764] McGrew, D. and E. Rescorla, "Datagram Transport Layer
 End of changes. 8 change blocks. 
9 lines changed or deleted 15 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/