draft-ietf-rtcweb-security-03.txt		draft-ietf-rtcweb-security-04.txt
	RTC-Web E. Rescorla		RTC-Web E. Rescorla
	Internet-Draft RTFM, Inc.		Internet-Draft RTFM, Inc.
	Intended status: Standards Track June 05, 2012		Intended status: Standards Track January 22, 2013
	Expires: December 7, 2012		Expires: July 26, 2013
	Security Considerations for RTC-Web		Security Considerations for RTC-Web
	draft-ietf-rtcweb-security-03		draft-ietf-rtcweb-security-04
	Abstract		Abstract
	The Real-Time Communications on the Web (RTC-Web) working group is		The Real-Time Communications on the Web (RTC-Web) working group is
	tasked with standardizing protocols for real-time communications		tasked with standardizing protocols for real-time communications
	between Web browsers. The major use cases for RTC-Web technology are		between Web browsers. The major use cases for RTC-Web technology are
	real-time audio and/or video calls, Web conferencing, and direct data		real-time audio and/or video calls, Web conferencing, and direct data
	transfer. Unlike most conventional real-time systems (e.g., SIP-		transfer. Unlike most conventional real-time systems (e.g., SIP-
	based soft phones) RTC-Web communications are directly controlled by		based soft phones) RTC-Web communications are directly controlled by
	some Web server, which poses new security challenges. For instance,		some Web server, which poses new security challenges. For instance,
	skipping to change at page 2, line 7		skipping to change at page 2, line 7
	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 7, 2012.		This Internet-Draft will expire on July 26, 2013.
	Copyright Notice		Copyright Notice
	Copyright (c) 2012 IETF Trust and the persons identified as the		Copyright (c) 2013 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 20, line 37		skipping to change at page 20, line 37
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	7.2. Informative References		7.2. Informative References
	[CORS] van Kesteren, A., "Cross-Origin Resource Sharing".		[CORS] van Kesteren, A., "Cross-Origin Resource Sharing".
	[I-D.ietf-rtcweb-security-arch]		[I-D.ietf-rtcweb-security-arch]
	Rescorla, E., "RTCWEB Security Architecture",		Rescorla, E., "RTCWEB Security Architecture",
	draft-ietf-rtcweb-security-arch-01 (work in progress),		draft-ietf-rtcweb-security-arch-05 (work in progress),
	March 2012.		October 2012.
	[I-D.kaufman-rtcweb-security-ui]		[I-D.kaufman-rtcweb-security-ui]
	Kaufman, M., "Client Security User Interface Requirements		Kaufman, M., "Client Security User Interface Requirements
	for RTCWEB", draft-kaufman-rtcweb-security-ui-00 (work in		for RTCWEB", draft-kaufman-rtcweb-security-ui-00 (work in
	progress), June 2011.		progress), June 2011.
	[I-D.rescorla-rtcweb-generic-idp]		[I-D.rescorla-rtcweb-generic-idp]
	Rescorla, E., "RTCWEB Generic Identity Provider		Rescorla, E., "RTCWEB Generic Identity Provider
	Interface", draft-rescorla-rtcweb-generic-idp-01 (work in		Interface", draft-rescorla-rtcweb-generic-idp-01 (work in
	progress), March 2012.		progress), March 2012.
End of changes. 5 change blocks.
	7 lines changed or deleted		7 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/