draft-ietf-rtcweb-overview-14.txt   draft-ietf-rtcweb-overview-15.txt 
Network Working Group H. Alvestrand Network Working Group H. Alvestrand
Internet-Draft Google Internet-Draft Google
Intended status: Standards Track June 16, 2015 Intended status: Standards Track January 21, 2016
Expires: December 18, 2015 Expires: July 24, 2016
Overview: Real Time Protocols for Browser-based Applications Overview: Real Time Protocols for Browser-based Applications
draft-ietf-rtcweb-overview-14 draft-ietf-rtcweb-overview-15
Abstract Abstract
This document gives an overview and context of a protocol suite This document gives an overview and context of a protocol suite
intended for use with real-time applications that can be deployed in intended for use with real-time applications that can be deployed in
browsers - "real time communication on the Web". browsers - "real time communication on the Web".
It intends to serve as a starting and coordination point to make sure 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 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 that the parts that belong in the Internet protocol suite are fully
skipping to change at page 1, line 43 skipping to change at page 1, line 43
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 December 18, 2015. This Internet-Draft will expire on July 24, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2016 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 3, line 9 skipping to change at page 3, line 9
A.9. Changes from -04 to -05 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.10. Changes from -05 to -06 . . . . . . . . . . . . . . . . . 20
A.11. Changes from -06 to -07 . . . . . . . . . . . . . . . . . 21 A.11. Changes from -06 to -07 . . . . . . . . . . . . . . . . . 21
A.12. Changes from -07 to -08 . . . . . . . . . . . . . . . . . 21 A.12. Changes from -07 to -08 . . . . . . . . . . . . . . . . . 21
A.13. Changes from -08 to -09 . . . . . . . . . . . . . . . . . 21 A.13. Changes from -08 to -09 . . . . . . . . . . . . . . . . . 21
A.14. Changes from -09 to -10 . . . . . . . . . . . . . . . . . 21 A.14. Changes from -09 to -10 . . . . . . . . . . . . . . . . . 21
A.15. Changes from -10 to -11 . . . . . . . . . . . . . . . . . 21 A.15. Changes from -10 to -11 . . . . . . . . . . . . . . . . . 21
A.16. Changes from -11 to -12 . . . . . . . . . . . . . . . . . 22 A.16. Changes from -11 to -12 . . . . . . . . . . . . . . . . . 22
A.17. Changes from -12 to -13 . . . . . . . . . . . . . . . . . 22 A.17. Changes from -12 to -13 . . . . . . . . . . . . . . . . . 22
A.18. Changes from -13 to -14 . . . . . . . . . . . . . . . . . 22 A.18. Changes from -13 to -14 . . . . . . . . . . . . . . . . . 22
A.19. Changes from -14 to -15 . . . . . . . . . . . . . . . . . 22
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 22 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 22
1. Introduction 1. Introduction
The Internet was, from very early in its lifetime, considered a The Internet was, from very early in its lifetime, considered a
possible vehicle for the deployment of real-time, interactive possible vehicle for the deployment of real-time, interactive
applications - with the most easily imaginable being audio applications - with the most easily imaginable being audio
conversations (aka "Internet telephony") and video conferencing. conversations (aka "Internet telephony") and video conferencing.
The first attempts to build this were dependent on special networks, The first attempts to build this were dependent on special networks,
skipping to change at page 6, line 15 skipping to change at page 6, line 15
A WebRTC non-browser may be capable of hosting applications in a A WebRTC non-browser may be capable of hosting applications in a
similar way to the way in which a browser can host Javascript similar way to the way in which a browser can host Javascript
applications, typically by offering APIs in other languages. For applications, typically by offering APIs in other languages. For
instance it may be implemented as a library that offers a C++ API instance it may be implemented as a library that offers a C++ API
intended to be loaded into applications. In this case, similar intended to be loaded into applications. In this case, similar
security considerations as for Javascript may be needed; however, security considerations as for Javascript may be needed; however,
since such APIs are not defined or referenced here, this document since such APIs are not defined or referenced here, this document
cannot give any specific rules for those interfaces. cannot give any specific rules for those interfaces.
WebRTC gateways are described in a separate document, WebRTC gateways are described in a separate document,
[I-D.alvestrand-rtcweb-gateways]. [I-D.ietf-rtcweb-gateways].
2.3. On interoperability and innovation 2.3. On interoperability and innovation
The "Mission statement of the IETF" [RFC3935] states that "The The "Mission statement of the IETF" [RFC3935] states that "The
benefit of a standard to the Internet is in interoperability - that benefit of a standard to the Internet is in interoperability - that
multiple products implementing a standard are able to work together multiple products implementing a standard are able to work together
in order to deliver valuable functions to the Internet's users." in order to deliver valuable functions to the Internet's users."
Communication on the Internet frequently occurs in two phases: Communication on the Internet frequently occurs in two phases:
skipping to change at page 16, line 35 skipping to change at page 16, line 35
Thanks to Bjoern Hoehrmann, Colin Perkins, Colton Shields, Eric Thanks to Bjoern Hoehrmann, Colin Perkins, Colton Shields, Eric
Rescorla, Heath Matlock, Henry Sinnreich, Justin Uberti, Keith Drage Rescorla, Heath Matlock, Henry Sinnreich, Justin Uberti, Keith Drage
and Simon Leinen for document review. and Simon Leinen for document review.
13. References 13. References
13.1. Normative References 13.1. Normative References
[I-D.ietf-rtcweb-audio] [I-D.ietf-rtcweb-audio]
Valin, J. and C. Bran, "WebRTC Audio Codec and Processing Valin, J. and C. Bran, "WebRTC Audio Codec and Processing
Requirements", draft-ietf-rtcweb-audio-08 (work in Requirements", draft-ietf-rtcweb-audio-05 (work in
progress), April 2015. progress), February 2014.
[I-D.ietf-rtcweb-data-channel] [I-D.ietf-rtcweb-data-channel]
Jesup, R., Loreto, S., and M. Tuexen, "WebRTC Data Jesup, R., Loreto, S., and M. Tuexen, "WebRTC Data
Channels", draft-ietf-rtcweb-data-channel-13 (work in Channels", draft-ietf-rtcweb-data-channel-11 (work in
progress), January 2015. progress), July 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-09 (work in progress), January 2015. protocol-07 (work in progress), July 2014.
[I-D.ietf-rtcweb-jsep] [I-D.ietf-rtcweb-jsep]
Uberti, J., Jennings, C., and E. Rescorla, "Javascript Uberti, J., Jennings, C., and E. Rescorla, "Javascript
Session Establishment Protocol", draft-ietf-rtcweb-jsep-10 Session Establishment Protocol", draft-ietf-rtcweb-jsep-07
(work in progress), June 2015. (work in progress), July 2014.
[I-D.ietf-rtcweb-rtp-usage] [I-D.ietf-rtcweb-rtp-usage]
Perkins, C., Westerlund, M., and J. Ott, "Web Real-Time Perkins, C., Westerlund, M., and J. Ott, "Web Real-Time
Communication (WebRTC): Media Transport and Use of RTP", Communication (WebRTC): Media Transport and Use of RTP",
draft-ietf-rtcweb-rtp-usage-22 (work in progress), draft-ietf-rtcweb-rtp-usage-16 (work in progress), July
February 2015. 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-08 (work in progress), February 2015. ietf-rtcweb-security-07 (work in progress), July 2014.
[I-D.ietf-rtcweb-security-arch] [I-D.ietf-rtcweb-security-arch]
Rescorla, E., "WebRTC Security Architecture", draft-ietf- Rescorla, E., "WebRTC Security Architecture", draft-ietf-
rtcweb-security-arch-11 (work in progress), March 2015. rtcweb-security-arch-10 (work in progress), July 2014.
[I-D.ietf-rtcweb-transports] [I-D.ietf-rtcweb-transports]
Alvestrand, H., "Transports for WebRTC", draft-ietf- Alvestrand, H., "Transports for WebRTC", draft-ietf-
rtcweb-transports-08 (work in progress), February 2015. rtcweb-transports-06 (work in progress), August 2014.
[I-D.ietf-rtcweb-video] [I-D.ietf-rtcweb-video]
Roach, A., "WebRTC Video Processing and Codec Roach, A., "WebRTC Video Processing and Codec
Requirements", draft-ietf-rtcweb-video-06 (work in Requirements", draft-ietf-rtcweb-video-00 (work in
progress), June 2015. progress), July 2014.
[RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model [RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model
with Session Description Protocol (SDP)", RFC 3264, June with Session Description Protocol (SDP)", RFC 3264, June
2002. 2002.
[RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V.
Jacobson, "RTP: A Transport Protocol for Real-Time Jacobson, "RTP: A Transport Protocol for Real-Time
Applications", STD 64, RFC 3550, July 2003. Applications", STD 64, RFC 3550, July 2003.
[RFC3711] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K. [RFC3711] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K.
Norrman, "The Secure Real-time Transport Protocol (SRTP)", Norrman, "The Secure Real-time Transport Protocol (SRTP)",
RFC 3711, March 2004. RFC 3711, March 2004.
[RFC5245] Rosenberg, J., "Interactive Connectivity Establishment [RFC5245] Rosenberg, J., "Interactive Connectivity Establishment
(ICE): A Protocol for Network Address Translator (NAT) (ICE): A Protocol for Network Address Translator (NAT)
Traversal for Offer/Answer Protocols", RFC 5245, April Traversal for Offer/Answer Protocols", RFC 5245, April
2010. 2010.
[W3C.WD-mediacapture-streams-20120628] [W3C.WD-mediacapture-streams-20120628]
Burnett, D. and A. Narayanan, "Media Capture and Streams", Burnett, D. and A. Narayanan, "Media Capture and Streams",
World Wide Web Consortium WD WD-mediacapture- World Wide Web Consortium WD WD-mediacapture-streams-
streams-20120628, June 2012, <http://www.w3.org/TR/2012/ 20120628, June 2012, <http://www.w3.org/TR/2012/
WD-mediacapture-streams-20120628>. WD-mediacapture-streams-20120628>.
[W3C.WD-webrtc-20120209] [W3C.WD-webrtc-20120209]
Bergkvist, A., Burnett, D., Jennings, C., and A. Bergkvist, A., Burnett, D., Jennings, C., and A.
Narayanan, "WebRTC 1.0: Real-time Communication Between Narayanan, "WebRTC 1.0: Real-time Communication Between
Browsers", World Wide Web Consortium WD WD- Browsers", World Wide Web Consortium WD WD-webrtc-
webrtc-20120209, February 2012, 20120209, February 2012,
<http://www.w3.org/TR/2012/WD-webrtc-20120209>. <http://www.w3.org/TR/2012/WD-webrtc-20120209>.
13.2. Informative References 13.2. Informative References
[I-D.alvestrand-rtcweb-gateways] [I-D.ietf-rtcweb-gateways]
Alvestrand, H. and U. Rauschenbach, "WebRTC Gateways", Alvestrand, H. and U. Rauschenbach, "WebRTC Gateways",
draft-alvestrand-rtcweb-gateways-02 (work in progress), draft-ietf-rtcweb-gateways-01 (work in progress), July
March 2015. 2015.
[I-D.ietf-rtcweb-use-cases-and-requirements] [I-D.ietf-rtcweb-use-cases-and-requirements]
Holmberg, C., Hakansson, S., and G. Eriksson, "Web Real- Holmberg, C., Hakansson, S., and G. Eriksson, "Web Real-
Time Communication Use-cases and Requirements", draft- Time Communication Use-cases and Requirements", draft-
ietf-rtcweb-use-cases-and-requirements-16 (work in ietf-rtcweb-use-cases-and-requirements-14 (work in
progress), January 2015. progress), February 2014.
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
A., Peterson, J., Sparks, R., Handley, M., and E. A., Peterson, J., Sparks, R., Handley, M., and E.
Schooler, "SIP: Session Initiation Protocol", RFC 3261, Schooler, "SIP: Session Initiation Protocol", RFC 3261,
June 2002. June 2002.
[RFC3935] Alvestrand, H., "A Mission Statement for the IETF", BCP [RFC3935] Alvestrand, H., "A Mission Statement for the IETF", BCP
95, RFC 3935, October 2004. 95, RFC 3935, October 2004.
[RFC6120] Saint-Andre, P., "Extensible Messaging and Presence [RFC6120] Saint-Andre, P., "Extensible Messaging and Presence
skipping to change at page 22, line 28 skipping to change at page 22, line 28
document. document.
Added words about WebRTC APIs in languages other than Javascript. Added words about WebRTC APIs in languages other than Javascript.
Referenced draft-ietf-rtcweb-video for video codecs to support. Referenced draft-ietf-rtcweb-video for video codecs to support.
A.18. Changes from -13 to -14 A.18. Changes from -13 to -14
None. This is a "keepalive" update. None. This is a "keepalive" update.
A.19. Changes from -14 to -15
Changed "gateways" reference to point to the WG document.
Author's Address Author's Address
Harald T. Alvestrand Harald T. Alvestrand
Google Google
Kungsbron 2 Kungsbron 2
Stockholm 11122 Stockholm 11122
Sweden Sweden
Email: harald@alvestrand.no Email: harald@alvestrand.no
 End of changes. 21 change blocks. 
29 lines changed or deleted 34 lines changed or added

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