--- 1/draft-ietf-rtcweb-overview-06.txt 2013-08-14 07:14:23.087299266 -0700 +++ 2/draft-ietf-rtcweb-overview-07.txt 2013-08-14 07:14:23.131300386 -0700 @@ -1,18 +1,18 @@ Network Working Group H. Alvestrand Internet-Draft Google -Intended status: Standards Track February 20, 2013 -Expires: August 24, 2013 +Intended status: Standards Track August 14, 2013 +Expires: February 15, 2014 Overview: Real Time Protocols for Brower-based Applications - draft-ietf-rtcweb-overview-06 + draft-ietf-rtcweb-overview-07 Abstract This document gives an overview and context of a protocol suite intended for use with real-time applications that can be deployed in browsers - "real time communication on the Web". It intends to serve as a starting and coordination point to make sure all the parts that are needed to achieve this goal are findable, and that the parts that belong in the Internet protocol suite are fully @@ -28,21 +28,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 August 24, 2013. + This Internet-Draft will expire on February 15, 2014. 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 publication of this document. Please review these documents @@ -75,29 +75,30 @@ 13.2. Informative References . . . . . . . . . . . . . . . . . . 17 Appendix A. Transport and Middlebox specification . . . . . . . . 18 A.1. System-provided interfaces . . . . . . . . . . . . . . . . 18 A.2. Middle box related functions . . . . . . . . . . . . . . . 18 A.3. Transport protocols implemented . . . . . . . . . . . . . 19 Appendix B. Change log . . . . . . . . . . . . . . . . . . . . . 19 B.1. Changes from draft-alvestrand-dispatch-rtcweb-datagram-00 to -01 . . . 19 B.2. Changes from draft-alvestrand-dispatch-01 to draft-alvestrand-rtcweb-overview-00 . . . . . . . . . . . 19 - B.3. Changes from draft-alvestrand-rtcweb-00 to -01 . . . . . . 19 + B.3. Changes from draft-alvestrand-rtcweb-00 to -01 . . . . . . 20 B.4. Changes from draft-alvestrand-rtcweb-overview-01 to draft-ietf-rtcweb-overview-00 . . . . . . . . . . . . . . 20 B.5. Changes from -00 to -01 of draft-ietf-rtcweb-overview . . 20 B.6. Changes from -01 to -02 of draft-ietf-rtcweb-overview . . 20 B.7. Changes from -02 to -03 of draft-ietf-rtcweb-overview . . 20 B.8. Changes from -03 to -04 of draft-ietf-rtcweb-overview . . 21 B.9. Changes from -04 to -05 of draft-ietf-rtcweb-overview . . 21 B.10. Changes from -05 to -06 . . . . . . . . . . . . . . . . . 21 + B.11. Changes from -06 to -07 . . . . . . . . . . . . . . . . . 21 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 21 1. Introduction The Internet was, from very early in its lifetime, considered a possible vehicle for the deployment of real-time, interactive applications - with the most easily imaginable being audio conversations (aka "Internet telephony") and video conferencing. The first attempts to build this were dependent on special networks, @@ -469,21 +470,22 @@ Data transport refers to the sending and receiving of data over the network interfaces, the choice of network-layer addresses at each end of the communication, and the interaction with any intermediate entities that handle the data, but do not modify it (such as TURN relays). It includes necessary functions for congestion control: When not to send data. - T are described in . + The data transport protocols used by RTCWEB are described in . ICE is required for all media paths that use UDP; in addition to the ability to pass NAT boxes, ICE fulfills the need for guaranteeing that the media path is going to a UDP port that is willing to receive the data. The data transport protocols used by RTCWEB, as well as the details of interactions with intermediate boxes, such as firewalls, relays and NAT boxes, are intended to be described in a separate document; for now, notes are gathered in Appendix A. @@ -544,21 +546,22 @@ required for it to be possible to use that in the web browsers. Adding new codecs which might have new SDP parameters should not change the APIs between the browser and Javascript application. As soon as the browsers support the new codecs, old applications written before the codecs were specified should automatically be able to use the new codecs where appropriate with no changes to the JS applications. The particular choices made for RTCWEB, and their implications for the API offered by a browser implementing RTCWEB, are described in - [I-D.ietf-rtcweb-jsep] + [I-D.ietf-rtcweb-jsep]. This document in turn implements the + solutions described in [I-D.roach-mmusic-unified-plan]. 8. Presentation and control The most important part of control is the user's control over the browser's interaction with input/output devices and communications channels. It is important that the user have some way of figuring out where his audio, video or texting is being sent, for what purported reason, and what guarantees are made by the parties that form part of this control channel. This is largely a local function between the browser, the underlying operating system and the user @@ -686,31 +689,37 @@ [I-D.ietf-rtcweb-security] Rescorla, E., "Security Considerations for RTC-Web", draft-ietf-rtcweb-security-04 (work in progress), January 2013. [I-D.ietf-rtcweb-security-arch] Rescorla, E., "RTCWEB Security Architecture", draft-ietf-rtcweb-security-arch-06 (work in progress), January 2013. + [I-D.ietf-tsvwg-sctp-dtls-encaps] + Jesup, R., Loreto, S., Stewart, R., and M. Tuexen, "DTLS + Encapsulation of SCTP Packets for RTCWEB", + draft-ietf-tsvwg-sctp-dtls-encaps-00 (work in progress), + February 2013. + [I-D.nandakumar-rtcweb-stun-uri] Nandakumar, S., Salgueiro, G., Jones, P., and M. Petit- Huguenin, "URI Scheme for Session Traversal Utilities for NAT (STUN) Protocol", draft-nandakumar-rtcweb-stun-uri-03 (work in progress), January 2013. - [I-D.tuexen-tsvwg-sctp-dtls-encaps] - Jesup, R., Loreto, S., Stewart, R., and M. Tuexen, "DTLS - Encapsulation of SCTP Packets for RTCWEB", - draft-tuexen-tsvwg-sctp-dtls-encaps-01 (work in progress), - July 2012. + [I-D.roach-mmusic-unified-plan] + Roach, A., Uberti, J., and M. Thomson, "A Unified Plan for + Using SDP with Large Numbers of Media Flows", + draft-roach-mmusic-unified-plan-00 (work in progress), + July 2013. [RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model with Session Description Protocol (SDP)", RFC 3264, June 2002. [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. Jacobson, "RTP: A Transport Protocol for Real-Time Applications", RFC 3550, July 2003. [RFC3711] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K. @@ -815,21 +824,21 @@ o TURN, including TURN over TCP [[QUESTION: and TURN over TLS]], [RFC5766]. For referring to STUN and TURN servers, this specification depends on the STUN URI, [I-D.nandakumar-rtcweb-stun-uri]. A.3. Transport protocols implemented For data transport, RTCWEB implementations support SCTP over DTLS - over ICE. This is specified in [I-D.tuexen-tsvwg-sctp-dtls-encaps]. + over ICE. This is specified in [I-D.ietf-tsvwg-sctp-dtls-encaps]. Negotiation of this transport in SCTP is defined in [I-D.ietf-mmusic-sctp-sdp]. Appendix B. Change log This section may be deleted by the RFC Editor when preparing for publication. B.1. Changes from draft-alvestrand-dispatch-rtcweb-datagram-00 to -01 @@ -927,19 +935,26 @@ B.9. Changes from -04 to -05 of draft-ietf-rtcweb-overview Minor grammatical fixes. This is mainly a "keepalive" refresh. B.10. Changes from -05 to -06 Clarifications in response to Last Call review comments. Inserted reference to draft-ietf-rtcweb-audio. +B.11. Changes from -06 to -07 + + Added a refereence to the "unified plan" draft, and updated some + references. + + Otherwise, it's a "keepalive" draft. + Author's Address Harald T. Alvestrand Google Kungsbron 2 Stockholm, 11122 Sweden Email: harald@alvestrand.no