--- 1/draft-ietf-rtcweb-overview-08.txt 2014-02-14 15:14:39.637665873 -0800 +++ 2/draft-ietf-rtcweb-overview-09.txt 2014-02-14 15:14:39.677666848 -0800 @@ -1,102 +1,108 @@ Network Working Group H. Alvestrand Internet-Draft Google -Intended status: Standards Track September 3, 2013 -Expires: March 7, 2014 +Intended status: Standards Track February 14, 2014 +Expires: August 18, 2014 Overview: Real Time Protocols for Brower-based Applications - draft-ietf-rtcweb-overview-08 + draft-ietf-rtcweb-overview-09 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 specified and on the right publication track. + The document will be publishd as an Applicability Statement - it does + not itself specify any protocol, but specifies which other + specifications RTCWEB compliant implementations are supposed to + follow. + This document is a work item of the RTCWEB working group. 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 7, 2014. + This Internet-Draft will expire on August 18, 2014. Copyright Notice - Copyright (c) 2013 IETF Trust and the persons identified as the + 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 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. Principles and Terminology . . . . . . . . . . . . . . . . . . 4 - 2.1. Goals of this document . . . . . . . . . . . . . . . . . . 4 - 2.2. Relationship between API and protocol . . . . . . . . . . 4 - 2.3. On interoperability and innovation . . . . . . . . . . . . 5 - 2.4. Terminology . . . . . . . . . . . . . . . . . . . . . . . 6 - 3. Architecture and Functionality groups . . . . . . . . . . . . 7 - 4. Data transport . . . . . . . . . . . . . . . . . . . . . . . . 11 - 5. Data framing and securing . . . . . . . . . . . . . . . . . . 11 - 6. Data formats . . . . . . . . . . . . . . . . . . . . . . . . . 12 - 7. Connection management . . . . . . . . . . . . . . . . . . . . 12 - 8. Presentation and control . . . . . . . . . . . . . . . . . . . 13 - 9. Local system support functions . . . . . . . . . . . . . . . . 13 - 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 - 11. Security Considerations . . . . . . . . . . . . . . . . . . . 14 - 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15 - 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15 - 13.1. Normative References . . . . . . . . . . . . . . . . . . . 15 - 13.2. Informative References . . . . . . . . . . . . . . . . . . 16 - Appendix A. Change log . . . . . . . . . . . . . . . . . . . . . 17 + 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 + 2. Principles and Terminology . . . . . . . . . . . . . . . . . . 5 + 2.1. Goals of this document . . . . . . . . . . . . . . . . . . 5 + 2.2. Relationship between API and protocol . . . . . . . . . . 5 + 2.3. On interoperability and innovation . . . . . . . . . . . . 6 + 2.4. Terminology . . . . . . . . . . . . . . . . . . . . . . . 7 + 3. Architecture and Functionality groups . . . . . . . . . . . . 8 + 4. Data transport . . . . . . . . . . . . . . . . . . . . . . . . 12 + 5. Data framing and securing . . . . . . . . . . . . . . . . . . 12 + 6. Data formats . . . . . . . . . . . . . . . . . . . . . . . . . 13 + 7. Connection management . . . . . . . . . . . . . . . . . . . . 13 + 8. Presentation and control . . . . . . . . . . . . . . . . . . . 14 + 9. Local system support functions . . . . . . . . . . . . . . . . 14 + 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 + 11. Security Considerations . . . . . . . . . . . . . . . . . . . 15 + 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 16 + 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16 + 13.1. Normative References . . . . . . . . . . . . . . . . . . . 16 + 13.2. Informative References . . . . . . . . . . . . . . . . . . 17 + Appendix A. Change log . . . . . . . . . . . . . . . . . . . . . 18 A.1. Changes from - draft-alvestrand-dispatch-rtcweb-datagram-00 to -01 . . . 17 + draft-alvestrand-dispatch-rtcweb-datagram-00 to -01 . . . 18 A.2. Changes from draft-alvestrand-dispatch-01 to - draft-alvestrand-rtcweb-overview-00 . . . . . . . . . . . 18 - A.3. Changes from draft-alvestrand-rtcweb-00 to -01 . . . . . . 18 + draft-alvestrand-rtcweb-overview-00 . . . . . . . . . . . 19 + A.3. Changes from draft-alvestrand-rtcweb-00 to -01 . . . . . . 19 A.4. Changes from draft-alvestrand-rtcweb-overview-01 to - draft-ietf-rtcweb-overview-00 . . . . . . . . . . . . . . 18 - A.5. Changes from -00 to -01 of draft-ietf-rtcweb-overview . . 18 - A.6. Changes from -01 to -02 of draft-ietf-rtcweb-overview . . 18 - A.7. Changes from -02 to -03 of draft-ietf-rtcweb-overview . . 19 - A.8. Changes from -03 to -04 of draft-ietf-rtcweb-overview . . 19 - A.9. Changes from -04 to -05 of draft-ietf-rtcweb-overview . . 19 - A.10. Changes from -05 to -06 . . . . . . . . . . . . . . . . . 19 - A.11. Changes from -06 to -07 . . . . . . . . . . . . . . . . . 19 - A.12. Changes from -07 to -08 . . . . . . . . . . . . . . . . . 20 - Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 20 + draft-ietf-rtcweb-overview-00 . . . . . . . . . . . . . . 19 + A.5. Changes from -00 to -01 of draft-ietf-rtcweb-overview . . 19 + A.6. Changes from -01 to -02 of draft-ietf-rtcweb-overview . . 19 + A.7. Changes from -02 to -03 of draft-ietf-rtcweb-overview . . 20 + A.8. Changes from -03 to -04 of draft-ietf-rtcweb-overview . . 20 + A.9. Changes from -04 to -05 of draft-ietf-rtcweb-overview . . 20 + A.10. Changes from -05 to -06 . . . . . . . . . . . . . . . . . 20 + A.11. Changes from -06 to -07 . . . . . . . . . . . . . . . . . 20 + A.12. Changes from -07 to -08 . . . . . . . . . . . . . . . . . 21 + A.13. Changes from -08 to -09 . . . . . . . . . . . . . . . . . 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, special hardware and custom-built software, often at very high prices @@ -652,43 +658,43 @@ Requirements", draft-ietf-rtcweb-audio-02 (work in progress), August 2013. [I-D.ietf-rtcweb-data-channel] Jesup, R., Loreto, S., and M. Tuexen, "RTCWeb Data Channels", draft-ietf-rtcweb-data-channel-05 (work in progress), July 2013. [I-D.ietf-rtcweb-jsep] Uberti, J. and C. Jennings, "Javascript Session - Establishment Protocol", draft-ietf-rtcweb-jsep-03 (work - in progress), February 2013. + Establishment Protocol", draft-ietf-rtcweb-jsep-04 (work + in progress), September 2013. [I-D.ietf-rtcweb-rtp-usage] Perkins, C., Westerlund, M., and J. Ott, "Web Real-Time Communication (WebRTC): Media Transport and Use of RTP", - draft-ietf-rtcweb-rtp-usage-07 (work in progress), - July 2013. + draft-ietf-rtcweb-rtp-usage-09 (work in progress), + September 2013. [I-D.ietf-rtcweb-security] Rescorla, E., "Security Considerations for WebRTC", draft-ietf-rtcweb-security-05 (work in progress), July 2013. [I-D.ietf-rtcweb-security-arch] Rescorla, E., "WebRTC Security Architecture", draft-ietf-rtcweb-security-arch-07 (work in progress), July 2013. [I-D.ietf-rtcweb-transports] Alvestrand, H., "Transports for RTCWEB", - draft-ietf-rtcweb-transports-00 (work in progress), - August 2013. + draft-ietf-rtcweb-transports-01 (work in progress), + September 2013. [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. @@ -864,19 +870,24 @@ references. Otherwise, it's a "keepalive" draft. A.12. Changes from -07 to -08 Removed the appendix that detailed transports, and replaced it with a reference to draft-ietf-rtcweb-transports. Removed now-unused references. +A.13. Changes from -08 to -09 + + Added text to the Abstract indicating that the intended status is an + Applicability Statement. + Author's Address Harald T. Alvestrand Google Kungsbron 2 Stockholm, 11122 Sweden Email: harald@alvestrand.no