--- 1/draft-ietf-rtcweb-data-channel-09.txt 2014-06-09 23:14:27.323629056 -0700 +++ 2/draft-ietf-rtcweb-data-channel-10.txt 2014-06-09 23:14:27.355629864 -0700 @@ -1,21 +1,21 @@ Network Working Group R. Jesup Internet-Draft Mozilla Intended status: Standards Track S. Loreto -Expires: November 16, 2014 Ericsson +Expires: December 11, 2014 Ericsson M. Tuexen Muenster Univ. of Appl. Sciences - May 15, 2014 + June 9, 2014 WebRTC Data Channels - draft-ietf-rtcweb-data-channel-09.txt + draft-ietf-rtcweb-data-channel-10.txt Abstract The Real-Time Communication in WEB-browsers 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-SRTP 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-browsers to @@ -29,21 +29,21 @@ 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 November 16, 2014. + This Internet-Draft will expire on December 11, 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 @@ -64,21 +64,21 @@ 5. SCTP over DTLS over UDP Considerations . . . . . . . . . . . 5 6. The Usage of SCTP for Data Channels . . . . . . . . . . . . . 8 6.1. SCTP Protocol Considerations . . . . . . . . . . . . . . 8 6.2. Association Setup . . . . . . . . . . . . . . . . . . . . 9 6.3. SCTP Streams . . . . . . . . . . . . . . . . . . . . . . 9 6.4. Channel Definition . . . . . . . . . . . . . . . . . . . 9 6.5. Opening a Channel . . . . . . . . . . . . . . . . . . . . 10 6.6. Transferring User Data on a Channel . . . . . . . . . . . 10 6.7. Closing a Channel . . . . . . . . . . . . . . . . . . . . 11 7. Security Considerations . . . . . . . . . . . . . . . . . . . 11 - 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 + 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 10.1. Normative References . . . . . . . . . . . . . . . . . . 12 10.2. Informative References . . . . . . . . . . . . . . . . . 14 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 1. Introduction Non-SRTP media data types in the context of WebRTC are handled by using SCTP [RFC4960] encapsulated in DTLS [RFC6347]. @@ -409,22 +409,28 @@ 6.4. Channel Definition The W3C has consensus on defining the application API for WebRTC DataChannels to be bidirectional. They also consider the notions of in-sequence, out-of-sequence, reliable and unreliable as properties of Channels. One strong wish is for the application-level API to be close to the API for WebSockets, which implies bidirectional streams of data and waiting for onopen to fire before sending, a textual 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 incoming stream and one outgoing SCTP stream having the same stream SCTP identifier. How stream values are selected is protocol and implementation dependent. 6.5. Opening a Channel @@ -585,21 +591,21 @@ [I-D.ietf-tsvwg-sctp-ndata] Stewart, R., Tuexen, M., Loreto, S., and R. Seggelmann, "A New Data Chunk for Stream Control Transmission Protocol", draft-ietf-tsvwg-sctp-ndata-00 (work in progress), February 2014. [I-D.ietf-rtcweb-data-protocol] Jesup, R., Loreto, S., and M. Tuexen, "WebRTC Data Channel 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] Tuexen, M., Stewart, R., Jesup, R., and S. Loreto, "DTLS Encapsulation of SCTP Packets", draft-ietf-tsvwg-sctp- dtls-encaps-04 (work in progress), May 2014. [I-D.ietf-rtcweb-security] Rescorla, E., "Security Considerations for WebRTC", draft- ietf-rtcweb-security-06 (work in progress), January 2014. @@ -609,21 +615,21 @@ [I-D.ietf-rtcweb-jsep] Uberti, J. and C. Jennings, "Javascript Session Establishment Protocol", draft-ietf-rtcweb-jsep-06 (work in progress), February 2014. [I-D.ietf-tsvwg-sctp-prpolicies] Tuexen, M., Seggelmann, R., Stewart, R., and S. Loreto, "Additional Policies for the Partial Reliability Extension 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] Loreto, S. and G. Camarillo, "Stream Control Transmission Protocol (SCTP)-Based Media Transport in the Session Description Protocol (SDP)", draft-ietf-mmusic-sctp-sdp-06 (work in progress), February 2014. 10.2. Informative References [RFC5764] McGrew, D. and E. Rescorla, "Datagram Transport Layer