draft-ietf-rtcweb-use-cases-and-requirements-16.txt		rfc7478.txt
	RTCWEB Working Group C. Holmberg		Internet Engineering Task Force (IETF) C. Holmberg
	Internet-Draft S. Hakansson		Request for Comments: 7478 S. Hakansson
	Intended status: Informational G. Eriksson		Category: Informational G. Eriksson
	Expires: July 27, 2015 Ericsson		ISSN: 2070-1721 Ericsson
	January 23, 2015		March 2015
	Web Real-Time Communication Use-cases and Requirements		Web Real-Time Communication Use Cases and Requirements
	draft-ietf-rtcweb-use-cases-and-requirements-16.txt
	Abstract		Abstract
	This document describes web based real-time communication use-cases.		This document describes web-based real-time communication use cases.
	Requirements on the browser functionality are derived from the use-		Requirements on the browser functionality are derived from the use
	cases.		cases.
	This document was developed in an initial phase of the work with		This document was developed in an initial phase of the work with
	rather minor updates at later stages. It has not really served as a		rather minor updates at later stages. It has not really served as a
	tool in deciding features or scope for the WGs efforts so far. It is		tool in deciding features or scope for the WG's efforts so far. It
	being published to record the early conclusions of the working group.		is being published to record the early conclusions of the WG. It
	It will not be used as a set of rigid guidelines that specifications		will not be used as a set of rigid guidelines that specifications and
	and implementations will be held to in the future.		implementations will be held to in the future.
	Status of This Memo		Status of This Memo
	This Internet-Draft is submitted in full conformance with the		This document is not an Internet Standards Track specification; it is
	provisions of BCP 78 and BCP 79.		published for informational purposes.
	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		This document is a product of the Internet Engineering Task Force
	and may be updated, replaced, or obsoleted by other documents at any		(IETF). It represents the consensus of the IETF community. It has
	time. It is inappropriate to use Internet-Drafts as reference		received public review and has been approved for publication by the
	material or to cite them other than as "work in progress."		Internet Engineering Steering Group (IESG). Not all documents
			approved by the IESG are a candidate for any level of Internet
			Standard; see Section 2 of RFC 5741.
	This Internet-Draft will expire on July 27, 2015.		Information about the current status of this document, any errata,
			and how to provide feedback on it may be obtained at
			http://www.rfc-editor.org/info/rfc7478.
	Copyright Notice		Copyright Notice
	Copyright (c) 2015 IETF Trust and the persons identified as the		Copyright (c) 2015 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
	described in the Simplified BSD License.		described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction ....................................................4
	2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3		2. Use Cases .......................................................4
	3. Use-cases . . . . . . . . . . . . . . . . . . . . . . . . . . 3		2.1. Introduction ...............................................4
	3.1. Introduction . . . . . . . . . . . . . . . . . . . . . . 4		2.2. Common Requirements ........................................5
	3.2. Common requirements . . . . . . . . . . . . . . . . . . . 4		2.3. Browser-to-Browser Use Cases ...............................5
	3.3. Browser-to-browser use-cases . . . . . . . . . . . . . . 4		2.3.1. Simple Video Communication Service ..................5
	3.3.1. Simple Video Communication Service . . . . . . . . . 4		2.3.2. Simple Video Communication Service:
	3.3.2. Simple Video Communication Service, NAT/Firewall that		NAT/Firewall That Blocks UDP ........................8
	blocks UDP . . . . . . . . . . . . . . . . . . . . . 7		2.3.3. Simple Video Communication Service: Firewall
	3.3.3. Simple Video Communication Service, Firewall that		That Only Allows Traffic via an HTTP Proxy ..........8
	only allows traffic via a HTTP Proxy . . . . . . . . 7		2.3.4. Simple Video Communication Service: Global
	3.3.4. Simple Video Communication Service, global service		Service Provider ....................................8
	provider . . . . . . . . . . . . . . . . . . . . . . 7		2.3.5. Simple Video Communication Service:
	3.3.5. Simple Video Communication Service, enterprise		Enterprise Aspects ..................................9
	aspects . . . . . . . . . . . . . . . . . . . . . . . 8		2.3.6. Simple Video Communication Service: Access Change ..10
	3.3.6. Simple Video Communication Service, access change . . 9		2.3.7. Simple Video Communication Service: QoS ............11
	3.3.7. Simple Video Communication Service, QoS . . . . . . . 10		2.3.8. Simple Video Communication Service with
	3.3.8. Simple Video Communication Service with screen		Screen Sharing .....................................11
	sharing . . . . . . . . . . . . . . . . . . . . . . . 10		2.3.9. Simple Video Communication Service with
	3.3.9. Simple Video Communication Service with file exchange 11		File Exchange ......................................12
	3.3.10. Hockey Game Viewer . . . . . . . . . . . . . . . . . 11		2.3.10. Hockey Game Viewer ................................12
	3.3.11. Multiparty video communication . . . . . . . . . . . 12		2.3.11. Multiparty Video Communication ....................14
	3.3.12. Multiparty on-line game with voice communication . . 14		2.3.12. Multiparty Online Game with Voice Communication ...15
	3.4. Browser - GW/Server use cases . . . . . . . . . . . . . . 15		2.4. Browser - GW/Server Use Cases .............................17
	3.4.1. Telephony terminal . . . . . . . . . . . . . . . . . 15		2.4.1. Telephony Terminal .................................17
	3.4.2. Fedex Call . . . . . . . . . . . . . . . . . . . . . 16		2.4.2. FedEx Call .........................................17
	3.4.3. Video conferencing system with central server . . . . 17		2.4.3. Video Conferencing System with Central Server ......18
	4. Requirements summary . . . . . . . . . . . . . . . . . . . . 18		3. Requirements Summary ...........................................19
	4.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 18		3.1. General ...................................................19
	4.2. Browser requirements . . . . . . . . . . . . . . . . . . 18		3.2. Browser Requirements ......................................19
	5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22		4. Security Considerations ........................................23
	6. Security Considerations . . . . . . . . . . . . . . . . . . . 22		4.1. Introduction ..............................................23
	6.1. Introduction . . . . . . . . . . . . . . . . . . . . . . 22		4.2. Browser Considerations ....................................24
	6.2. Browser Considerations . . . . . . . . . . . . . . . . . 22		4.3. Web Application Considerations ............................24
	6.3. Web Application Considerations . . . . . . . . . . . . . 23		5. Normative References ...........................................25
	7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 23		Appendix A. API Requirements ......................................26
	8. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 23		Acknowledgements ..................................................29
	9. Normative References . . . . . . . . . . . . . . . . . . . . 30		Authors' Addresses ................................................29
	Appendix A. API requirements . . . . . . . . . . . . . . . . . . 30
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 33
	1. Introduction		1. Introduction
	This document presents a few use-cases of web applications that are		This document presents a few use cases of web applications that are
	executed in a browser and use real-time communication capabilities.		executed in a browser and use real-time communication capabilities.
	In most of the use-cases all end-user clients are web applications,		In most of the use cases, all end-user clients are web applications,
	but there are some use-cases where at least one of the end-user		but there are some use cases where at least one of the end-user
	clients is of another type (e.g. a mobile phone or a SIP User Agent		clients is of another type (e.g., a mobile phone or a SIP User Agent
	(UA)).		(UA)).
	Based on the use-cases, the document derives requirements related to		Based on the use cases, the document derives requirements related to
	browser functionality. These requirements are named "Fn", where n is		browser functionality. These requirements are named "Fn", where n is
	an integer, and are listed in conjunction with the use-cases. A		an integer, and are listed in conjunction with the use cases. A
	summary is provided in Section 4.2.		summary is provided in Section 3.2.
	This document was developed in an initial phase of the work with		This document was developed in an initial phase of the work with
	rather minor updates at later stages. It has not really served as a		rather minor updates at later stages. It has not really served as a
	tool in deciding features or scope for the WGs efforts so far. It is		tool in deciding features or scope for the WG's efforts so far. It
	proposed to be used in a later phase to evaluate the protocols and		is proposed to be used in a later phase to evaluate the protocols and
	solutions developed by the WG.		solutions developed by the WG.
	This document also lists requirements related to the API to be used		This document also lists requirements related to the API to be used
	by web applications as an appendix. The reason is that the W3C		by web applications as an appendix. The reason is that the W3C
	WebRTC WG has decided to not develop its own use-case/requirement		WebRTC WG has decided to not develop its own use-case or requirement
	document, but instead use this document. These requirements are		document, but instead will use this document. These requirements are
	named "An", where n is an integer, and are described in Appendix A.		named "An", where n is an integer, and are described in Appendix A.
	This document was developed in an initial phase of the work with		This document was developed in an initial phase of the work with
	rather minor updates at later stages. It has not really served as a		rather minor updates at later stages. It has not really served as a
	tool in deciding features or scope for the WGs efforts so far. It is		tool in deciding features or scope for the WG's efforts so far. It
	being published to record the early conclusions of the working group.		is being published to record the early conclusions of the WG. It
	It will not be used as a set of rigid guidelines that specifications		will not be used as a set of rigid guidelines that specifications and
	and implementations will be held to in the future.		implementations will be held to in the future.
	2. Conventions
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		2. Use Cases
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	document are to be interpreted as described in BCP 14, RFC 2119
	[RFC2119].
	3. Use-cases		2.1. Introduction
	3.1. Introduction
	This section describes web based real-time communication use-cases,		This section describes web-based real-time communication use cases,
	from which requirements are derived.		from which requirements are derived.
	The following considerations are applicable to all use cases:		The following considerations are applicable to all use cases:
	o Clients can be on IPv4-only		o Clients can be on IPv4-only
	o Clients can be on IPv6-only		o Clients can be on IPv6-only
	o Clients can be on dual-stack		o Clients can be on dual-stack
	o Clients can be connected to networks with different throughput		o Clients can be connected to networks with different throughput
	capabilities		capabilities
	o Clients can be on variable-media-quality networks (wireless)		o Clients can be on variable-media-quality networks (wireless)
	o Clients can be on congested networks		o Clients can be on congested networks
	o Clients can be on firewalled networks with no UDP allowed		o Clients can be on firewalled networks with no UDP allowed
	o Clients can be on networks with a NAT or IPv4-IPv6 translation		o Clients can be on networks with a NAT or IPv4-IPv6 translation
	skipping to change at page 4, line 28		skipping to change at page 5, line 15
	capabilities		capabilities
	o Clients can be on variable-media-quality networks (wireless)		o Clients can be on variable-media-quality networks (wireless)
	o Clients can be on congested networks		o Clients can be on congested networks
	o Clients can be on firewalled networks with no UDP allowed		o Clients can be on firewalled networks with no UDP allowed
	o Clients can be on networks with a NAT or IPv4-IPv6 translation		o Clients can be on networks with a NAT or IPv4-IPv6 translation
	devices using any type of Mapping and Filtering behaviors (as		devices using any type of Mapping and Filtering behaviors (as
	described in RFC4787).		described in RFC 4787).
	3.2. Common requirements		2.2. Common Requirements
	The requirements retrived from the Simple Video Communication Service		The requirements retrieved from the
	use-case (Section 3.3.1) by default apply to all other use-cases, and		Simple Video Communication Service use case (Section 2.3.1) by
	are considred common. For each individual use-case, only the		default apply to all other use cases and are considered common. For
	additional requirements are listed.		each use case, only the additional requirements are listed.
	3.3. Browser-to-browser use-cases		2.3. Browser-to-Browser Use Cases
	3.3.1. Simple Video Communication Service		2.3.1. Simple Video Communication Service
	3.3.1.1. Description		2.3.1.1. Description
	Two or more users have loaded a video communication web application		Two or more users have loaded a video communication web application
	into their browsers, provided by the same service provider, and		into their browsers, provided by the same service provider, and
	logged into the service it provides. The web service publishes		logged into the service it provides. The web service publishes
	information about user login status by pushing updates to the web		information about user login status by pushing updates to the web
	application in the browsers. When one online user selects a peer		application in the browsers. When one online user selects a peer
	online user, a 1-1 audiovisual communication session between the		online user, a 1:1 audiovisual communication session between the
	browsers of the two peers is initiated. The invited user might		browsers of the two peers is initiated. The invited user might
	accept or reject the session.		accept or reject the session.
	During session establishment a self-view is displayed, and once the		During session establishment, a self view is displayed, and once the
	session has been established the video sent from the remote peer is		session has been established the video sent from the remote peer is
	displayed in addition to the self-view. During the session, each		displayed in addition to the self view. During the session, each
	user can select to remove and re-insert the self-view as often as		user can:
	desired. Each user can also change the sizes of his/her two video
	displays during the session. Each user can also pause sending of
	media (audio, video, or both) and mute incoming media.
	It is essential that media and data be encrypted, authenticated and		o select to remove and reinsert the self-view as often as desired,
	integrity protected on a per IP packet basis and that media and data
			o change the sizes of his/her two video displays during the session,
			and
			o pause the sending of media (audio, video, or both) and mute
			incoming media.
			It is essential that media and data be encrypted, authenticated, and
			integrity protected on a per-IP-packet basis and that media and data
	packets failing the integrity check not be delivered to the		packets failing the integrity check not be delivered to the
	application.		application.
	The application gives the users the opportunity to stop it from		The application gives the users the opportunity to stop it from
	exposing the host IP address to the application of the other user.		exposing the host IP address to the application of the other user.
	Any session participant can end the session at any time.		Any session participant can end the session at any time.
	The two users may be using communication devices with different		The two users may be using communication devices with different
	operating systems and browsers from different vendors.		operating systems and browsers from different vendors.
	The web service monitors the quality of the service (focus on quality		The web service monitors the quality of the service (focus on quality
	of audio and video) the end-users experience.		of audio and video) that the end users experience.
	3.3.1.2. Common Requirements		2.3.1.2. Common Requirements
	----------------------------------------------------------------		----------------------------------------------------------------
	REQ-ID DESCRIPTION		REQ-ID DESCRIPTION
	----------------------------------------------------------------		----------------------------------------------------------------
	F1 The browser must be able to use microphones and		F1 The browser must be able to use microphones and
	cameras as input devices to generate streams.		cameras as input devices to generate streams.
	----------------------------------------------------------------		----------------------------------------------------------------
	F2 The browser must be able to send streams and		F2 The browser must be able to send streams and
	data to a peer in the presence of NATs.		data to a peer in the presence of NATs.
	----------------------------------------------------------------		----------------------------------------------------------------
	F3 Transmitted streams and data must be rate		F3 Transmitted streams and data must be rate
	controlled (meaning that the browser must, regardless		controlled (meaning that the browser must, regardless
	of application behavior, reduce send rate when		of application behavior, reduce send rate when
	there is congestion).		there is congestion).
	----------------------------------------------------------------		----------------------------------------------------------------
	F4 The browser must be able to receive, process and		F4 The browser must be able to receive, process, and
	render streams and data ("render" does not		render streams and data ("render" does not
	apply for data) from peers.		apply for data) from peers.
	----------------------------------------------------------------		----------------------------------------------------------------
	F5 The browser should be able to render good quality		F5 The browser should be able to render good quality
	audio and video even in the presence of		audio and video even in the presence of
	reasonable levels of jitter and packet losses.		reasonable levels of jitter and packet losses.
	----------------------------------------------------------------		----------------------------------------------------------------
	F6 The browser must detect when a stream from a		F6 The browser must detect when a stream from a
	peer is not received anymore.		peer is not received anymore.
	----------------------------------------------------------------		----------------------------------------------------------------
	F7 When there are both incoming and outgoing audio		F7 When there are both incoming and outgoing audio
	streams, echo cancellation must be made		streams, echo cancellation must be made
	available to avoid disturbing echo during		available to avoid disturbing echo during
	conversation.		conversation.
	----------------------------------------------------------------		----------------------------------------------------------------
	F8 The browser must support synchronization of		F8 The browser must support synchronization of
	audio and video.		audio and video.
	----------------------------------------------------------------		----------------------------------------------------------------
	F9 The browser should use encoding of streams		F9 The browser should use encoding of streams
	suitable for the current rendering (e.g.		suitable for the current rendering (e.g.,
	video display size) and should change parameters		video display size) and should change parameters
	if the rendering changes during the session.		if the rendering changes during the session.
	----------------------------------------------------------------		----------------------------------------------------------------
	F10 The browser must support a baseline audio and		F10 The browser must support a baseline audio and
	video codec.		video codec.
	----------------------------------------------------------------		----------------------------------------------------------------
	F11 It must be possible to protect streams and data		F11 It must be possible to protect streams and data
	from wiretapping [RFC2804][RFC7258].		from wiretapping [RFC2804] [RFC7258].
	----------------------------------------------------------------		----------------------------------------------------------------
	F12 The browser must enable verification, given		F12 The browser must enable verification, given
	the right circumstances and by use of other		the right circumstances and by use of other
	trusted communication, that streams and		trusted communication, that streams and
	data received have not been manipulated by		data received have not been manipulated by
	any party.		any party.
	----------------------------------------------------------------		----------------------------------------------------------------
	F13 The browser must encrypt, authenticate and		F13 The browser must encrypt, authenticate, and
	integrity protect media and data on a		integrity protect media and data on a
	per IP packet basis, and must drop incoming media		per-IP-packet basis, and it must drop incoming media
	and data packets that fail the per IP packet		and data packets that fail the per-IP-packet
	integrity check. In addition, the browser		integrity check. In addition, the browser
	must support a mechanism for cryptographically		must support a mechanism for cryptographically
	binding media and data security keys to the		binding media and data security keys to the
	user identity (see R-ID-BINDING in [RFC5479]).		user identity (see R-ID-BINDING in [RFC5479]).
	----------------------------------------------------------------		----------------------------------------------------------------
	F14 The browser must make it possible to set up a		F14 The browser must make it possible to set up a
	call between two parties without one party		call between two parties without one party
	learning the other party's host IP address.		learning the other party's host IP address.
	----------------------------------------------------------------		----------------------------------------------------------------
	F15 The browser must be able to collect statistics,		F15 The browser must be able to collect statistics,
	related to the transport of audio and video		related to the transport of audio and video
	between peers, needed to estimate quality of		between peers, needed to estimate quality of
	experience.		experience.
	----------------------------------------------------------------		----------------------------------------------------------------
	A1, A2, A3, A4, A5, A6, A7, A8, A9, A10, A11, A12, A25, A26		A1, A2, A3, A4, A5, A6, A7, A8, A9, A10, A11, A12, A25, A26
	3.3.2. Simple Video Communication Service, NAT/Firewall that blocks UDP		2.3.2. Simple Video Communication Service: NAT/Firewall That Blocks UDP
	3.3.2.1. Description		2.3.2.1. Description
	This use-case is almost identical to the		This use case is almost identical to the
	Simple Video Communication Service use-case (Section 3.3.1). The		Simple Video Communication Service use case (Section 2.3.1). The
	difference is that one of the users is behind a NAT/Firewall that		difference is that one of the users is behind a NAT/firewall that
	blocks UDP traffic.		blocks UDP traffic.
	3.3.2.2. Additional Requirements		2.3.2.2. Additional Requirements
	----------------------------------------------------------------		----------------------------------------------------------------
	REQ-ID DESCRIPTION		REQ-ID DESCRIPTION
	----------------------------------------------------------------		----------------------------------------------------------------
	F18 The browser must be able to send streams and		F18 The browser must be able to send streams and
	data to a peer in the presence of NATs and		data to a peer in the presence of NATs and
	Firewalls that block UDP traffic.		firewalls that block UDP traffic.
	----------------------------------------------------------------		----------------------------------------------------------------
	3.3.3. Simple Video Communication Service, Firewall that only allows		2.3.3. Simple Video Communication Service: Firewall That Only Allows
	traffic via a HTTP Proxy		Traffic via an HTTP Proxy
	3.3.3.1. Description		2.3.3.1. Description
	This use-case is almost identical to the		This use case is almost identical to the
	Simple Video Communication Service use-case (Section 3.3.1). The		Simple Video Communication Service use case (Section 2.3.1). The
	difference is that one of the users is behind a Firewall that only		difference is that one of the users is behind a firewall that only
	allows traffic via a HTTP Proxy.		allows traffic via an HTTP Proxy.
	3.3.3.2. Additional Requirements		2.3.3.2. Additional Requirements
	----------------------------------------------------------------		----------------------------------------------------------------
	REQ-ID DESCRIPTION		REQ-ID DESCRIPTION
	----------------------------------------------------------------		----------------------------------------------------------------
	F21 The browser must be able to send streams and		F21 The browser must be able to send streams and
	data to a peer in the presence of Firewalls that only		data to a peer in the presence of firewalls that only
	allows traffic via a HTTP Proxy, when Firewall policy		allow traffic via an HTTP Proxy, when firewall policy
	allows WebRTC traffic.		allows WebRTC traffic.
	----------------------------------------------------------------		----------------------------------------------------------------
	3.3.4. Simple Video Communication Service, global service provider		2.3.4. Simple Video Communication Service: Global Service Provider
	3.3.4.1. Description
	This use-case is almost identical to the		2.3.4.1. Description
	Simple Video Communication Service use-case (Section 3.3.1).
	What is added is that the service provider is operating over large		This use case is almost identical to the
			Simple Video Communication Service use case (Section 2.3.1). What is
			added is that the service provider is operating over large
	geographical areas (or even globally).		geographical areas (or even globally).
	Assuming that the Interactive Connectivity Establishment (ICE)		Assuming that the Interactive Connectivity Establishment (ICE)
	mechanism [RFC5245] will be used, this means that the service		mechanism [RFC5245] will be used, this means that the service
	provider would like to be able to provide several STUN and TURN		provider would like to be able to provide several Session Traversal
	servers (via the app) to the browser; selection of which one(s) to		Utilities for NAT (STUN) and Traversal Using Relay NAT (TURN) servers
	use is part of the ICE processing. Other reasons for wanting to		(via the app) to the browser; selection of which one(s) to use is
	provide several STUN and TURN servers include support for IPv4 and		part of the ICE processing. Other reasons for wanting to provide
	IPv6, load balancing and redundancy.		several STUN and TURN servers include support for IPv4 and IPv6, load
			balancing, and redundancy.
	Note that ICE support being mandatory does not preclude a WebRTC		Note that ICE support being mandatory does not preclude a WebRTC
	endpoint from supporting more traversal mechanisms than ICE using		endpoint from supporting more traversal mechanisms than ICE using
	STUN and TURN.		STUN and TURN.
	3.3.4.2. Additional Requirements		2.3.4.2. Additional Requirements
	----------------------------------------------------------------		----------------------------------------------------------------
	REQ-ID DESCRIPTION		REQ-ID DESCRIPTION
	----------------------------------------------------------------		----------------------------------------------------------------
	F19 The browser must be able to use several STUN		F19 The browser must be able to use several STUN
	and TURN servers		and TURN servers.
	----------------------------------------------------------------		----------------------------------------------------------------
	A22		A22
	3.3.5. Simple Video Communication Service, enterprise aspects		2.3.5. Simple Video Communication Service: Enterprise Aspects
	3.3.5.1. Description		2.3.5.1. Description
	This use-case is similar to the Simple Video Communication Service		This use case is similar to the Simple Video Communication Service
	use-case (Section 3.3.1).		use case (Section 2.3.1).
	What is added is aspects when using the service in enterprises. ICE		What is added is aspects when using the service in enterprises. ICE
	is assumed in the further description of this use-case.		is assumed in the further description of this use case.
	An enterprise that uses a RTCWEB based web application for		An enterprise that uses a WebRTC-based web application for
	communication desires to audit all RTCWEB based application sessions		communication desires to audit all WebRTC-based application sessions
	used from inside the company towards any external peer. To be able		used from inside the company towards any external peer. To be able
	to do this they deploy a TURN server that straddles the boundary		to do this, they deploy a TURN server that straddles the boundary
	between the internal and the external network.		between the internal and the external network.
	The firewall will block all attempts to use STUN with an external		The firewall will block all attempts to use STUN with an external
	destination unless they go to the enterprise auditing TURN server.		destination unless they go to the enterprise auditing TURN server.
	In cases where employees are using RTCWEB applications provided by an		In cases where employees are using WebRTC applications provided by an
	external service provider they still want the traffic to stay inside		external service provider, they still want the traffic to stay inside
	their internal network and in addition not load the straddling TURN		their internal network and in addition not load the straddling TURN
	server, thus they deploy a STUN server allowing the RTCWEB client to		server; thus, they deploy a STUN server allowing the WebRTC client to
	determine its server reflexive address on the internal side. Thus		determine its server reflexive address on the internal side. Thus,
	enabling cases where peers are both on the internal side to connect		enabling cases where peers are both on the internal side to connect
	without the traffic leaving the internal network. It must be		without the traffic leaving the internal network. It must be
	possible to configure the browsers used in the enterprise with		possible to configure the browsers used in the enterprise with
	network specific STUN and TURN servers. This should be possible to		network specific STUN and TURN servers. This should be possible to
	achieve by auto-configuration methods. The RTCWEB functionality will		achieve by autoconfiguration methods. The WebRTC functionality will
	need to utilize both network specific STUN and TURN resources and		need to utilize both network specific STUN and TURN resources and
	STUN and TURN servers provisioned by the web application.		STUN and TURN servers provisioned by the web application.
	3.3.5.2. Additional Requirements		2.3.5.2. Additional Requirements
	----------------------------------------------------------------		----------------------------------------------------------------
	REQ-ID DESCRIPTION		REQ-ID DESCRIPTION
	----------------------------------------------------------------		----------------------------------------------------------------
	F20 The browser must support the use of STUN and TURN		F20 The browser must support the use of STUN and TURN
	servers that are supplied by entities other than		servers that are supplied by entities other than
	the web application (i.e. the network provider).		the web application (i.e., the network provider).
	----------------------------------------------------------------		----------------------------------------------------------------
	3.3.6. Simple Video Communication Service, access change		2.3.6. Simple Video Communication Service: Access Change
	3.3.6.1. Description		2.3.6.1. Description
	This use-case is almost identical to the		This use case is almost identical to the
	Simple Video Communication Service use-case (Section 3.3.1). The		Simple Video Communication Service use case (Section 2.3.1). The
	difference is that the user changes network access during the		difference is that the user changes network access during the
	session.		session.
	The communication device used by one of the users has several network		The communication device used by one of the users has several network
	adapters (Ethernet, WiFi, Cellular). The communication device is		adapters (Ethernet, Wi-Fi, Cellular). The communication device is
	accessing the Internet using Ethernet, but the user has to start a		accessing the Internet using Ethernet, but the user has to start a
	trip during the session. The communication device automatically		trip during the session. The communication device automatically
	changes to use WiFi when the Ethernet cable is removed and then moves		changes to use Wi-Fi when the Ethernet cable is removed and then
	to cellular access to the Internet when moving out of WiFi coverage.		moves to cellular access to the Internet when moving out of Wi-Fi
	The session continues even though the access method changes.		coverage. The session continues even though the access method
			changes.
	3.3.6.2. Additional Requirements		2.3.6.2. Additional Requirements
	----------------------------------------------------------------		----------------------------------------------------------------
	REQ-ID DESCRIPTION		REQ-ID DESCRIPTION
	----------------------------------------------------------------		----------------------------------------------------------------
	F17 The communication session must survive across a		F17 The communication session must survive across a
	change of the network interface used by the		change of the network interface used by the
	session		session.
	----------------------------------------------------------------		----------------------------------------------------------------
	3.3.7. Simple Video Communication Service, QoS		2.3.7. Simple Video Communication Service: QoS
	3.3.7.1. Description		2.3.7.1. Description
	This use-case is almost identical to the		This use case is almost identical to the
	Simple Video Communication Service, access change use-case		Simple Video Communication Service: Access Change use case
	(Section 3.3.6). The use of Quality of Service (QoS) capabilities is		(Section 2.3.6). The use of Quality of Service (QoS) capabilities is
	added:		added:
	The user in the previous use case that starts a trip is behind a		The user in the previous use case that starts a trip is behind a
	common residential router that supports differentiation of traffic.		common residential router that supports differentiation of traffic.
	In addition, the user's provider of cellular access has QoS support		In addition, the user's provider of cellular access has QoS support
	enabled. The user is able to take advantage of the QoS support both		enabled. The user is able to take advantage of the QoS support both
	when accessing via the residential router and when using cellular.		when accessing via the residential router and when using cellular.
	3.3.7.2. Additional Requirements		2.3.7.2. Additional Requirements
	----------------------------------------------------------------		----------------------------------------------------------------
	REQ-ID DESCRIPTION		REQ-ID DESCRIPTION
	----------------------------------------------------------------		----------------------------------------------------------------
	F17 The communication session must survive across a		F17 The communication session must survive across a
	change of the network interface used by the		change of the network interface used by the
	session		session.
	----------------------------------------------------------------		----------------------------------------------------------------
	F22 The browser should be able to take advantage		F22 The browser should be able to take advantage
	of available capabilities (supplied by network		of available capabilities (supplied by network
	nodes) to differentiate voice, video and data		nodes) to differentiate voice, video, and data
	appropriately.		appropriately.
	----------------------------------------------------------------		----------------------------------------------------------------
	3.3.8. Simple Video Communication Service with screen sharing		2.3.8. Simple Video Communication Service with Screen Sharing
	3.3.8.1. Description		2.3.8.1. Description
	This use-case has the audio and video communication of the		This use case has the audio and video communication of the
	Simple Video Communication Service use-case (Section 3.3.1).		Simple Video Communication Service use case (Section 2.3.1).
	But in addition to this, one of the users can share what is being		However, in addition to this, one of the users can share what is
	displayed on her/his screen with a peer. The user can choose to		being displayed on her/his screen with a peer. The user can choose
	share the entire screen, part of the screen (part selected by the		to share the entire screen, part of the screen (part selected by the
	user) or what a selected application displays with the peer.		user), or what a selected application displays with the peer.
			2.3.8.2. Additional Requirements
	3.3.8.2. Additional Requirements
	----------------------------------------------------------------		----------------------------------------------------------------
	REQ-ID DESCRIPTION		REQ-ID DESCRIPTION
	----------------------------------------------------------------		----------------------------------------------------------------
	F36 The browser must be able to generate streams		F36 The browser must be able to generate streams
	using the entire user display, a specific area		using the entire user display, a specific area
	of the user's display or the information being		of the user display, or the information being
	displayed by a specific application.		displayed by a specific application.
	----------------------------------------------------------------		----------------------------------------------------------------
	A21		A21
	3.3.9. Simple Video Communication Service with file exchange		2.3.9. Simple Video Communication Service with File Exchange
	3.3.9.1. Description		2.3.9.1. Description
	This use-case has the audio and video communication of the		This use case has the audio and video communication of the
	Simple Video Communication Service use-case (Section 3.3.1).		Simple Video Communication Service use case (Section 3.3.1).
	But in addition to this, the users can send and receive files stored		However, in addition to this, the users can send and receive files
	in the file system of the device used.		stored in the file system of the device used.
	3.3.9.2. Additional Requirements		2.3.9.2. Additional Requirements
	----------------------------------------------------------------		----------------------------------------------------------------
	REQ-ID DESCRIPTION		REQ-ID DESCRIPTION
	----------------------------------------------------------------		----------------------------------------------------------------
	F35 The browser must be able to send reliable		F35 The browser must be able to send reliable
	data traffic to a peer browser.		data traffic to a peer browser.
	----------------------------------------------------------------		----------------------------------------------------------------
	A21, A24		A21, A24
	3.3.10. Hockey Game Viewer		2.3.10. Hockey Game Viewer
	3.3.10.1. Description		2.3.10.1. Description
	An ice-hockey club uses an application that enables talent scouts to,		An ice-hockey club uses an application that enables talent scouts to,
	in real-time, show and discuss games and players with the club		in real-time, show and discuss games and players with the club
	manager. The talent scouts use a mobile phone with two cameras, one		manager. The talent scouts use a mobile phone with two cameras: one
	front facing and one rear facing.		front facing and one rear facing.
	The club manager uses a desktop, equipped with one camera, for		The club manager uses a desktop, equipped with one camera, for
	viewing the game and discussing with the talent scout.		viewing the game and discussing with the talent scout.
	Before the game starts, and during game breaks, the talent scout and		Before the game starts, and during game breaks, the talent scout and
	the manager have a 1-1 audiovisual communication session. On the		the manager have a 1:1 audiovisual communication session. On the
	mobile phone, only the camera facing the talent scout is used. On		mobile phone, only the camera facing the talent scout is used. On
	the user display of the mobile phone, the video of the club manager		the user display of the mobile phone, the video of the club manager
	is shown with a picture-in-picture thumbnail of the rear facing		is shown with a picture-in-picture thumbnail of the rear-facing
	camera (self-view). On the display of the desktop, the video of the		camera (self view). On the display of the desktop, the video of the
	talent scout is shown with a picture-in-picture thumbnail of the		talent scout is shown with a picture-in-picture thumbnail of the
	desktop camera (self-view).		desktop camera (self view).
	When the game is on-going, the talent scout activates the use of the		When the game is ongoing, the talent scout activates the use of the
	front facing camera, and that stream is sent to the desktop (the		front-facing camera, and that stream is sent to the desktop (the
	stream from the rear facing camera continues to be sent all the		stream from the rear-facing camera continues to be sent all the
	time). The video stream captured by the front facing camera (that is		time). The video stream captured by the front-facing camera (that is
	capturing the game) of the mobile phone is shown in a big window on		capturing the game) of the mobile phone is shown in a big window on
	the desktop screen, with picture-in-picture thumbnails of the rear		the desktop screen, with picture-in-picture thumbnails of the rear-
	facing camera and the desktop camera (self-view). On the display of		facing camera and the desktop camera (self view). On the display of
	the mobile phone the game is shown (front facing camera) with		the mobile phone the game is shown (front-facing camera) with
	picture-in-picture thumbnails of the rear facing camera (self-view)		picture-in-picture thumbnails of the rear-facing camera (self view)
	and the desktop camera. As the most important stream in this phase		and the desktop camera. Because the most important stream in this
	is the video showing the game, the application used in the talent		phase is the video showing the game, the application used in the
	scout's mobile sets higher priority for that stream.		talent scout's mobile phone sets higher priority for that stream.
	3.3.10.2. Additional Requirements		2.3.10.2. Additional Requirements
	----------------------------------------------------------------		----------------------------------------------------------------
	REQ-ID DESCRIPTION		REQ-ID DESCRIPTION
	----------------------------------------------------------------		----------------------------------------------------------------
	F22 The browser should be able to take advantage		F22 The browser should be able to take advantage
	of available capabilities (supplied by network		of available capabilities (supplied by network
	nodes) to differentiate voice, video and data		nodes) to differentiate voice, video, and data
	appropriately.		appropriately.
	----------------------------------------------------------------		----------------------------------------------------------------
	F25 The browser must be able to render several		F25 The browser must be able to render several
	concurrent audio and video streams.		concurrent audio and video streams.
	----------------------------------------------------------------		----------------------------------------------------------------
	A17, A23		A17, A23
	3.3.11. Multiparty video communication		2.3.11. Multiparty Video Communication
	3.3.11.1. Description		2.3.11.1. Description
	In this use-case, the Simple Video Communication Service use-case		In this use case, the Simple Video Communication Service use case
	(Section 3.3.1) is extended by allowing multiparty sessions. No		(Section 2.3.1) is extended by allowing multiparty sessions. No
	central server is involved - the browser of each participant sends		central server is involved -- the browser of each participant sends
	and receives streams to and from all other session participants. The		and receives streams to and from all other session participants. The
	web application in the browser of each user is responsible for		web application in the browser of each user is responsible for
	setting up streams to all receivers.		setting up streams to all receivers.
	In order to enhance the user experience, the web application renders		In order to enhance the user experience, the web application renders
	the audio coming from different participants so that it is		the audio coming from different participants so that it is
	experienced to come from different spatial locations. This is done		experienced to come from different spatial locations. This is done
	automatically, but users can change how the different participants		automatically, but users can change how the different participants
	are placed in the (virtual) room. In addition the levels in the		are placed in the (virtual) room. In addition, the levels in the
	audio signals are adjusted before mixing.		audio signals are adjusted before mixing.
	Another feature intended to enhance the use experience is that the		Another feature intended to enhance the user experience is the
	video window that displays the video of the currently speaking peer		highlighting of the video window that displays the video of the
	is highlighted.		currently speaking peer.
	Each video stream received is by default displayed in a thumbnail		Each video stream received is, by default, displayed in a thumbnail
	frame within the browser, but users can change the display size.		frame within the browser, but users can change the display size.
	Note: What this use-case adds in terms of requirements is		Note: What this use case adds in terms of requirements are
	capabilities to send streams to and receive streams from several		capabilities to send streams to and receive streams from several
	peers concurrently, as well as the capabilities to render the video		peers concurrently as well as the capabilities to render the video
	from all received streams and be able to spatialize, level adjust and		from all received streams and be able to spatialize, level adjust,
	mix the audio from all received streams locally in the browser. It		and mix the audio from all received streams locally in the browser.
	also adds the capability to measure the audio level/activity.		It also adds the capability to measure the audio level/activity.
	3.3.11.2. Additional Requirements		2.3.11.2. Additional Requirements
	----------------------------------------------------------------		----------------------------------------------------------------
	REQ-ID DESCRIPTION		REQ-ID DESCRIPTION
	----------------------------------------------------------------		----------------------------------------------------------------
	F23 The browser must be able to transmit streams and		F23 The browser must be able to transmit streams and
	data to several peers concurrently.		data to several peers concurrently.
	----------------------------------------------------------------		----------------------------------------------------------------
	F24 The browser must be able to receive streams and		F24 The browser must be able to receive streams and
	data from multiple peers concurrently.		data from multiple peers concurrently.
	----------------------------------------------------------------		----------------------------------------------------------------
	F25 The browser must be able to render several		F25 The browser must be able to render several
	concurrent audio and video streams.		concurrent audio and video streams.
	----------------------------------------------------------------		----------------------------------------------------------------
	F26 The browser must be able to mix several		F26 The browser must be able to mix several
	audio streams.		audio streams.
	----------------------------------------------------------------		----------------------------------------------------------------
	F27 The browser must be able to apply spatialization		F27 The browser must be able to apply spatialization
	effects to audio streams.		effects to audio streams.
	----------------------------------------------------------------		----------------------------------------------------------------
	F28 The browser must be able to measure the		F28 The browser must be able to measure the
	voice activity level in audio streams.		voice activity level in audio streams.
	----------------------------------------------------------------		----------------------------------------------------------------
	F29 The browser must be able to change the		F29 The browser must be able to change the
	voice activity level in audio streams.		voice activity level in audio streams.
	----------------------------------------------------------------		----------------------------------------------------------------
	A13, A14, A15, A16		A13, A14, A15, A16
	3.3.12. Multiparty on-line game with voice communication		2.3.12. Multiparty Online Game with Voice Communication
	3.3.12.1. Description		2.3.12.1. Description
	This use case is based on the previous one. In this use-case, the		This use case is based on the previous one. In this use case, the
	voice part of the multiparty video communication use case is used in		voice part of the multiparty video communication use case is used in
	the context of an on-line game. The received voice audio media is		the context of an online game. The received voice audio media is
	rendered together with game sound objects. For example, the sound of		rendered together with game sound objects. For example, the sound of
	a tank moving from left to right over the screen must be rendered and		a tank moving from left to right over the screen must be rendered and
	played to the user together with the voice media.		played to the user together with the voice media.
	Quick updates of the game state is required, and have higher priority		Quick updates of the game state are required, and they have higher
	than the voice.		priority than the voice.
	Note: the difference regarding local audio processing compared to the		Note: the difference regarding local audio processing compared to the
	"Multiparty video communication" use-case is that other sound objects		"Multiparty Video Communication" use case is that other sound objects
	than the streams must be possible to be included in the		than the streams must be possible to be included in the
	spatialization and mixing. "Other sound objects" could for example		spatialization and mixing. "Other sound objects" could for example
	be a file with the sound of the tank; that file could be stored		be a file with the sound of the tank; that file could be stored
	locally or remotely.		locally or remotely.
	3.3.12.2. Additional Requirements		2.3.12.2. Additional Requirements
	----------------------------------------------------------------		----------------------------------------------------------------
	REQ-ID DESCRIPTION		REQ-ID DESCRIPTION
	----------------------------------------------------------------		----------------------------------------------------------------
	F22 The browser should be able to take advantage		F22 The browser should be able to take advantage
	of available capabilities (supplied by network		of available capabilities (supplied by network
	nodes) to differentiate voice, video and data		nodes) to differentiate voice, video, and data
	appropriately.		appropriately.
	----------------------------------------------------------------		----------------------------------------------------------------
	F23 The browser must be able to transmit streams and		F23 The browser must be able to transmit streams and
	data to several peers concurrently.		data to several peers concurrently.
	----------------------------------------------------------------		----------------------------------------------------------------
	F24 The browser must be able to receive streams and		F24 The browser must be able to receive streams and
	data from multiple peers concurrently.		data from multiple peers concurrently.
	----------------------------------------------------------------		----------------------------------------------------------------
	F25 The browser must be able to render several		F25 The browser must be able to render several
	concurrent audio and video streams.		concurrent audio and video streams.
	----------------------------------------------------------------		----------------------------------------------------------------
	F26 The browser must be able to mix several		F26 The browser must be able to mix several
	audio streams.		audio streams.
	----------------------------------------------------------------		----------------------------------------------------------------
	F27 The browser must be able to apply spatialization		F27 The browser must be able to apply spatialization
	effects when playing audio streams.		effects when playing audio streams.
	----------------------------------------------------------------		----------------------------------------------------------------
	F28 The browser must be able to measure the		F28 The browser must be able to measure the
	voice activity level in audio streams.		voice activity level in audio streams.
	----------------------------------------------------------------		----------------------------------------------------------------
	F29 The browser must be able to change the		F29 The browser must be able to change the
	voice activity level in audio streams.		voice activity level in audio streams.
	----------------------------------------------------------------		----------------------------------------------------------------
	F30 The browser must be able to process and mix		F30 The browser must be able to process and mix
	sound objects (media that is retrieved from		sound objects (media that is retrieved from
	another source than the established media		another source than the established media
	stream(s) with the peer(s) with audio streams.		stream(s) with the peer(s) with audio streams).
	----------------------------------------------------------------		----------------------------------------------------------------
	F34 The browser must be able to send short		F34 The browser must be able to send short
	latency unreliable datagram traffic to a		latency unreliable datagram traffic to a
	peer browser [RFC5405].		peer browser [RFC5405].
	----------------------------------------------------------------		----------------------------------------------------------------
	A13, A14, A15, A16, A17, A18, A23		A13, A14, A15, A16, A17, A18, A23
	3.4. Browser - GW/Server use cases		2.4. Browser - GW/Server Use Cases
	3.4.1. Telephony terminal		2.4.1. Telephony Terminal
	3.4.1.1. Description
			2.4.1.1. Description
	A mobile telephony operator allows its customers to use a web browser		A mobile telephony operator allows its customers to use a web browser
	to access their services. After a simple log in the user can place		to access their services. After a simple log in, the user can place
	and receive calls in the same way as when using a normal mobile		and receive calls in the same way as when using a normal mobile
	phone. When a call is received or placed, the identity is shown in		phone. When a call is received or placed, the identity is shown in
	the same manner as when a mobile phone is used.		the same manner as when a mobile phone is used.
	Note: With "place and receive calls in the same way as when using a		Note: "place and receive calls in the same way as when using a normal
	normal mobile phone" it is meant that you can dial a number, and that		mobile phone" means that you can dial a number and your mobile
	your mobile telephony operator has made available your phone contacts		telephony operator has made available your phone contacts online so
	on line, so they are available and can be clicked to call, and be		that they are available and can be clicked to call and they can be
	used to present the identity of an incoming call. If the callee is		used to present the identity of an incoming call. If the callee is
	not in your phone contacts the number is displayed. Furthermore,		not in your phone contacts, the number is displayed. Furthermore,
	your call logs are available, and updated with the calls made/		your call logs are available, and updated with the calls made/
	received from the browser. And for people receiving calls made from		received from the browser. For people receiving calls made from the
	the web browser the usual identity (i.e. the phone number of the		web browser, the usual identity (i.e., the phone number of the mobile
	mobile phone) will be presented.		phone) will be presented.
	3.4.1.2. Additional Requirements		2.4.1.2. Additional Requirements
	----------------------------------------------------------------		----------------------------------------------------------------
	REQ-ID DESCRIPTION		REQ-ID DESCRIPTION
	----------------------------------------------------------------		----------------------------------------------------------------
	F31 The browser must support an audio media format		F31 The browser must support an audio media format
	(codec) that is commonly supported by existing		(codec) that is commonly supported by existing
	telephony services.		telephony services.
	----------------------------------------------------------------		----------------------------------------------------------------
	F33 The browser must be able to initiate and		F33 The browser must be able to initiate and
	accept a media session where the data needed		accept a media session where the data needed
	for establishment can be carried in SIP.		for establishment can be carried in SIP.
	----------------------------------------------------------------		----------------------------------------------------------------
	3.4.2. Fedex Call		2.4.2. FedEx Call
	3.4.2.1. Description		2.4.2.1. Description
	Alice uses her web browser with a service that allows her to call		Alice uses her web browser with a service that allows her to call
	PSTN numbers. Alice calls 1-800-gofedex. Alice should be able to		Public Switched Telephone Network (PSTN) numbers. Alice calls
	hear the initial prompts from the fedex Interactive Voice Responder		1-800-123-4567. Alice should be able to hear the initial prompts
	(IVR) and when the IVR says press 1, there should be a way for Alice		from the FedEx Interactive Voice Responder (IVR), and when the IVR
	to navigate the IVR.		says press 1, there should be a way for Alice to navigate the IVR.
			2.4.2.2. Additional Requirements
	3.4.2.2. Additional Requirements
	----------------------------------------------------------------		----------------------------------------------------------------
	REQ-ID DESCRIPTION		REQ-ID DESCRIPTION
	----------------------------------------------------------------		----------------------------------------------------------------
	F31 The browser must support an audio media format		F31 The browser must support an audio media format
	(codec) that is commonly supported by existing		(codec) that is commonly supported by existing
	telephony services.		telephony services.
	----------------------------------------------------------------		----------------------------------------------------------------
	F32 There should be a way to navigate		F32 There should be a way to navigate
	a Dual-tone multi-frequency signaling (DTMF)		a dual-tone multi-frequency signaling (DTMF)
	based Interactive voice response (IVR) System		based Interactive Voice Response (IVR) system.
	----------------------------------------------------------------		----------------------------------------------------------------
	3.4.3. Video conferencing system with central server		2.4.3. Video Conferencing System with Central Server
	3.4.3.1. Description		2.4.3.1. Description
	An organization uses a video communication system that supports the		An organization uses a video communication system that supports the
	establishment of multiparty video sessions using a central conference		establishment of multiparty video sessions using a central conference
	server.		server.
	The browser of each participant sends an audio stream (type in terms		The browser of each participant sends an audio stream (type in terms
	of mono, stereo, 5.1, ... depending on the equipment of the		of mono, stereo, 5.1 -- depending on the equipment of the
	participant) to the central server. The central server mixes the		participant) to the central server. The central server mixes the
	audio streams (and can in the mixing process naturally add effects		audio streams (and can in the mixing process naturally add effects
	such as spatialization) and sends towards each participant a mixed		such as spatialization) and sends towards each participant a mixed
	audio stream which is played to the user.		audio stream that is played to the user.
	The browser of each participant sends video towards the server. For		The browser of each participant sends video towards the server. For
	each participant one high resolution video is displayed in a large		each participant, one high-resolution video is displayed in a large
	window, while a number of low resolution videos are displayed in		window, while a number of low-resolution videos are displayed in
	smaller windows. The server selects what video streams to be		smaller windows. The server selects what video streams to be
	forwarded as main- and thumbnail videos respectively, based on speech		forwarded as main and thumbnail videos, respectively, based on speech
	activity. As the video streams to display can change quite		activity. As the video streams to display can change quite
	frequently (as the conversation flows) it is important that the delay		frequently (as the conversation flows), it is important that the
	from when a video stream is selected for display until the video can		delay from when a video stream is selected for display until the
	be displayed is short.		video can be displayed is short.
	All participants are authenticated by the central server, and		All participants are authenticated by the central server and
	authorized to connect to the central server. The participants are		authorized to connect to the central server. The participants are
	identified to each other by the central server, and the participants		identified to each other by the central server, and the participants
	do not have access to each others' credentials such as e-mail		do not have access to each others' credentials such as email
	addresses or login IDs.		addresses or login IDs.
	Note: This use-case adds requirements on support for fast stream		Note: This use case adds requirements on support for fast stream
	switches F16. There exist several solutions that enable the server		switches (F16). There exist several solutions that enable the server
	to forward one high resolution and several low resolution video		to forward one high-resolution and several low-resolution video
	streams: a) each browser could send a high resolution, but scalable		streams: a) each browser could send a high-resolution, but scalable
	stream, and the server could send just the base layer for the low		stream, and the server could send just the base layer for the low-
	resolution streams, b) each browser could in a simulcast fashion send		resolution streams, b) each browser could in a simulcast fashion send
	one high resolution and one low resolution stream, and the server		one high-resolution and one low-resolution stream, and the server
	just selects or c) each browser sends just a high resolution stream,		just selects, or c) each browser sends just a high-resolution stream,
	the server transcodes into low resolution streams as required.		the server transcodes into low-resolution streams as required.
	3.4.3.2. Additional Requirements		2.4.3.2. Additional Requirements
	----------------------------------------------------------------		----------------------------------------------------------------
	REQ-ID DESCRIPTION		REQ-ID DESCRIPTION
	----------------------------------------------------------------		----------------------------------------------------------------
	F16 The browser must support insertion of reference frames		F16 The browser must support insertion of reference frames
	in outgoing media streams when requested by a peer.		in outgoing media streams when requested by a peer.
	----------------------------------------------------------------		----------------------------------------------------------------
	F25 The browser must be able to render several		F25 The browser must be able to render several
	concurrent audio and video streams.		concurrent audio and video streams.
	----------------------------------------------------------------		----------------------------------------------------------------
	4. Requirements summary		3. Requirements Summary
	4.1. General		3.1. General
	This section contains the requirements on the browser derived from		This section contains the requirements on the browser derived from
	the use-cases in Section 3.		the use cases in Section 2.
	NOTE: It is assumed that the user applications are executed on a		Note: It is assumed that the user applications are executed on a
	browser. Whether the capabilities to implement specific browser		browser. Whether the capabilities to implement specific browser
	requirements are implemented by the browser application, or are		requirements are implemented by the browser application, or are
	provided to the browser application by the underlying operating		provided to the browser application by the underlying operating
	system, is outside the scope of this document.		system, is outside the scope of this document.
	4.2. Browser requirements		3.2. Browser Requirements
	----------------------------------------------------------------
	Common, basic requirements
	----------------------------------------------------------------
	REQ-ID DESCRIPTION
	----------------------------------------------------------------
	F1 The browser must be able to use microphones and
	cameras as input devices to generate streams.
	----------------------------------------------------------------
	F2 The browser must be able to send streams and
	data to a peer in the presence of NATs.
	----------------------------------------------------------------
	F3 Transmitted streams and data must be rate
	controlled (meaning that the browser must, regardless
	of application behavior, reduce send rate when
	there is congestion).
	----------------------------------------------------------------		----------------------------------------------------------------
	F4 The browser must be able to receive, process and		Common, basic requirements
	render streams and data ("render" does not		----------------------------------------------------------------
	apply for data) from peers.		REQ-ID DESCRIPTION
	----------------------------------------------------------------		----------------------------------------------------------------
	F5 The browser should be able to render good quality		F1 The browser must be able to use microphones and
	audio and video even in the presence of		cameras as input devices to generate streams.
	reasonable levels of jitter and packet losses.		----------------------------------------------------------------
	----------------------------------------------------------------		F2 The browser must be able to send streams and
	F6 The browser must detect when a stream from a		data to a peer in the presence of NATs.
	peer is not received anymore
	----------------------------------------------------------------
	F7 When there are both incoming and outgoing audio
	streams, echo cancellation must be made
	available to avoid disturbing echo during
	conversation.
	----------------------------------------------------------------
	F8 The browser must support synchronization of
	audio and video.
	----------------------------------------------------------------
	F9 The browser should use encoding of streams
	suitable for the current rendering (e.g.
	video display size) and should change parameters
	if the rendering changes during the session
	----------------------------------------------------------------
	F10 The browser must support a baseline audio and
	video codec
	----------------------------------------------------------------
	F11 It must be possible to protect streams and data
	from wiretapping [RFC2804][RFC7258].
	----------------------------------------------------------------
	F12 The browser must enable verification, given
	the right circumstances and by use of other
	trusted communication, that streams and
	data received have not been manipulated by
	any party.
	----------------------------------------------------------------
	F13 The browser must encrypt, authenticate and
	integrity protect media and data on a
	per-packet basis, and must drop incoming media
	and data packets that fail the per-packet
	integrity check. In addition, the browser
	must support a mechanism for cryptographically
	binding media and data security keys to the
	user identity (see R-ID-BINDING in [RFC5479]).
	----------------------------------------------------------------
	F14 The browser must make it possible to set up a
	call between two parties without one party
	learning the other party's host IP address.
	----------------------------------------------------------------
	F15 The browser must be able to collect statistics,
	related to the transport of audio and video
	between peers, needed to estimate quality of
	experience.
	----------------------------------------------------------------
	Requirements related to network and topology
	----------------------------------------------------------------
	REQ-ID DESCRIPTION
	----------------------------------------------------------------
	F16 The browser must support insertion of reference frames
	in outgoing media streams when requested by a peer.
	----------------------------------------------------------------
	F17 The communication session must survive across a
	change of the network interface used by the
	session
	----------------------------------------------------------------
	F18 The browser must be able to send streams and
	data to a peer in the presence of NATs and
	Firewalls that block UDP traffic.
	----------------------------------------------------------------
	F19 The browser must be able to use several STUN
	and TURN servers
	----------------------------------------------------------------
	F20 The browser must support the use of STUN and TURN
	servers that are supplied by entities other than
	the web application (i.e. the network provider).
	----------------------------------------------------------------
	F21 The browser must be able to send streams and
	data to a peer in the presence of Firewalls that only
	allows traffic via a HTTP Proxy, when Firewall policy
	allows WebRTC traffic.
	----------------------------------------------------------------
	F22 The browser should be able to take advantage
	of available capabilities (supplied by network
	nodes) to differentiate voice, video and data
	appropriately.
	----------------------------------------------------------------
	Requirements related to multiple peers and streams
	----------------------------------------------------------------
	REQ-ID DESCRIPTION
	----------------------------------------------------------------
	F23 The browser must be able to transmit streams and
	data to several peers concurrently.
	----------------------------------------------------------------
	F24 The browser must be able to receive streams and
	data from multiple peers concurrently.
	----------------------------------------------------------------		----------------------------------------------------------------
	F25 The browser must be able to render several		F3 Transmitted streams and data must be rate
	concurrent audio and video streams.		controlled (meaning that the browser must, regardless
	----------------------------------------------------------------		of application behavior, reduce send rate when
	F26 The browser must be able to mix several		there is congestion).
	audio streams.		----------------------------------------------------------------
	----------------------------------------------------------------		F4 The browser must be able to receive, process, and
	Requirements related to audio processing		render streams and data ("render" does not
	----------------------------------------------------------------		apply for data) from peers.
	REQ-ID DESCRIPTION		----------------------------------------------------------------
	----------------------------------------------------------------		F5 The browser should be able to render good quality
	F27 The browser must be able to apply spatialization		audio and video even in the presence of
	effects when playing audio streams.		reasonable levels of jitter and packet losses.
	----------------------------------------------------------------		----------------------------------------------------------------
	F28 The browser must be able to measure the		F6 The browser must detect when a stream from a
	voice activity level in audio streams.		peer is not received anymore.
	----------------------------------------------------------------		----------------------------------------------------------------
	F29 The browser must be able to change the		F7 When there are both incoming and outgoing audio
	voice activity level in audio streams.		streams, echo cancellation must be made
	----------------------------------------------------------------		available to avoid disturbing echo during
	F30 The browser must be able to process and mix		conversation.
	sound objects (media that is retrieved from		----------------------------------------------------------------
	another source than the established media		F8 The browser must support synchronization of
	stream(s) with the peer(s) with audio streams.		audio and video.
	----------------------------------------------------------------		----------------------------------------------------------------
	Requirements related to legacy interop		F9 The browser should use encoding of streams
	----------------------------------------------------------------		suitable for the current rendering (e.g.,
	REQ-ID DESCRIPTION		video display size) and should change parameters
	----------------------------------------------------------------		if the rendering changes during the session
	F31 The browser must support an audio media format		----------------------------------------------------------------
	(codec) that is commonly supported by existing		F10 The browser must support a baseline audio and
	telephony services.		video codec.
	----------------------------------------------------------------		----------------------------------------------------------------
	F32 There should be a way to navigate		F11 It must be possible to protect streams and data
	a Dual-tone multi-frequency signaling (DTMF)		from wiretapping [RFC2804] [RFC7258].
	based Interactive voice response (IVR) System		----------------------------------------------------------------
	----------------------------------------------------------------		F12 The browser must enable verification, given
	F33 The browser must be able to initiate and		the right circumstances and by use of other
	accept a media session where the data needed		trusted communication, that streams and
	for establishment can be carried in SIP.		data received have not been manipulated by
	----------------------------------------------------------------		any party.
	Other requirements
	----------------------------------------------------------------
	REQ-ID DESCRIPTION
	----------------------------------------------------------------
	F34 The browser must be able to send short
	latency unreliable datagram traffic to a
	peer browser [RFC5405].
	----------------------------------------------------------------		----------------------------------------------------------------
	F35 The browser must be able to send reliable		F13 The browser must encrypt, authenticate, and
	data traffic to a peer browser.		integrity protect media and data on a
	----------------------------------------------------------------		per-IP-packet basis, and it must drop incoming media
	F36 The browser must be able to generate streams		and data packets that fail the per-IP-packet
	using the entire user display, a specific area		integrity check. In addition, the browser
	of the user's display or the information being		must support a mechanism for cryptographically
	displayed by a specific application.		binding media and data security keys to the
	----------------------------------------------------------------		user identity (see R-ID-BINDING in [RFC5479]).
			----------------------------------------------------------------
			F14 The browser must make it possible to set up a
			call between two parties without one party
			learning the other party's host IP address.
			----------------------------------------------------------------
			F15 The browser must be able to collect statistics,
			related to the transport of audio and video
			between peers, needed to estimate quality of
			experience.
			----------------------------------------------------------------
			Requirements related to network and topology
			----------------------------------------------------------------
			REQ-ID DESCRIPTION
			----------------------------------------------------------------
			F16 The browser must support insertion of reference frames
			in outgoing media streams when requested by a peer.
			----------------------------------------------------------------
			F17 The communication session must survive across a
			change of the network interface used by the
			session.
			----------------------------------------------------------------
			F18 The browser must be able to send streams and
			data to a peer in the presence of NATs and
			firewalls that block UDP traffic.
			----------------------------------------------------------------
			F19 The browser must be able to use several STUN
			and TURN servers.
			----------------------------------------------------------------
			F20 The browser must support the use of STUN and TURN
			servers that are supplied by entities other than
			the web application (i.e., the network provider).
			----------------------------------------------------------------
			F21 The browser must be able to send streams and
			data to a peer in the presence of firewalls that only
			allow traffic via an HTTP Proxy, when firewall policy
			allows WebRTC traffic.
	5. IANA Considerations		----------------------------------------------------------------
			F22 The browser should be able to take advantage
			of available capabilities (supplied by network
			nodes) to differentiate voice, video, and data
			appropriately.
			----------------------------------------------------------------
			Requirements related to multiple peers and streams
			----------------------------------------------------------------
			REQ-ID DESCRIPTION
			----------------------------------------------------------------
			F23 The browser must be able to transmit streams and
			data to several peers concurrently.
			----------------------------------------------------------------
			F24 The browser must be able to receive streams and
			data from multiple peers concurrently.
			----------------------------------------------------------------
			F25 The browser must be able to render several
			concurrent audio and video streams.
			----------------------------------------------------------------
			F26 The browser must be able to mix several
			audio streams.
			----------------------------------------------------------------
			Requirements related to audio processing
			----------------------------------------------------------------
			REQ-ID DESCRIPTION
			----------------------------------------------------------------
			F27 The browser must be able to apply spatialization
			effects when playing audio streams.
			----------------------------------------------------------------
			F28 The browser must be able to measure the
			voice activity level in audio streams.
			----------------------------------------------------------------
			F29 The browser must be able to change the
			voice activity level in audio streams.
			----------------------------------------------------------------
			F30 The browser must be able to process and mix
			sound objects (media that is retrieved from
			another source than the established media
			stream(s) with the peer(s) with audio streams).
			----------------------------------------------------------------
			Requirements related to legacy interop
			----------------------------------------------------------------
			REQ-ID DESCRIPTION
			----------------------------------------------------------------
			F31 The browser must support an audio media format
			(codec) that is commonly supported by existing
			telephony services.
	There are no IANA actions in this document.		----------------------------------------------------------------
			F32 There should be a way to navigate
			a dual-tone multi-frequency signaling (DTMF)
			based Interactive Voice Response (IVR) system.
			----------------------------------------------------------------
			F33 The browser must be able to initiate and
			accept a media session where the data needed
			for establishment can be carried in SIP.
			----------------------------------------------------------------
			Other requirements
			----------------------------------------------------------------
			REQ-ID DESCRIPTION
			----------------------------------------------------------------
			F34 The browser must be able to send short
			latency unreliable datagram traffic to a
			peer browser [RFC5405].
			----------------------------------------------------------------
			F35 The browser must be able to send reliable
			data traffic to a peer browser.
			----------------------------------------------------------------
			F36 The browser must be able to generate streams
			using the entire user display, a specific area
			of the user display or the information being
			displayed by a specific application.
			----------------------------------------------------------------
	6. Security Considerations		4. Security Considerations
	6.1. Introduction		4.1. Introduction
	A malicious web application might use the browser to perform Denial		A malicious web application might use the browser to perform Denial-
	Of Service (DOS) attacks on NAT infrastructure, or on peer devices.		of-Service (DoS) attacks on NAT infrastructure, or on peer devices.
	Also, a malicious web application might silently establish outgoing,		For example, a malicious web application might leak TURN credentials
	and accept incoming, streams on an already established connection.		to unauthorized parties, allowing them to consume the TURN server's
			bandwidth. To address this risk, web applications should be prepared
			to revoke TURN credentials and issue new ones. Also, a malicious web
			application might silently establish outgoing, and accept incoming,
			streams on an already established connection.
	Based on the identified security risks, this section will describe		Based on the identified security risks, this section will describe
	security considerations for the browser and web application.		security considerations for the browser and web application.
	6.2. Browser Considerations		4.2. Browser Considerations
	The browser is expected to provide mechanisms for getting user		The browser is expected to provide mechanisms for getting user
	consent to use device resources such as camera and microphone.		consent to use device resources such as camera and microphone.
	The browser is expected to provide mechanisms for informing the user		The browser is expected to provide mechanisms for informing the user
	that device resources such as camera and microphone are in use		that device resources such as camera and microphone are in use
	("hot").		("hot").
	The browser must provide mechanisms for users to revise and even		The browser must provide mechanisms for users to revise and even
	completely revoke consent to use device resources such as camera and		completely revoke consent to use device resources such as camera and
	microphone.		microphone.
	The browser is expected to provide mechanisms for getting user		The browser is expected to provide mechanisms for getting user
	consent to use the screen (or a certain part of it) or what a certain		consent to use the screen (or a certain part of it) or what a certain
	application displays on the screen as source for streams.		application displays on the screen as source for streams.
	The browser is expected to provide mechanisms for informing the user		The browser is expected to provide mechanisms for informing the user
	that the screen, part thereof or an application is serving as a		that the screen, part thereof, or an application is serving as a
	stream source ("hot").		stream source ("hot").
	The browser must provide mechanisms for users to revise and even		The browser must provide mechanisms for users to revise and even
	completely revoke consent to use the screen, part thereof or an		completely revoke consent to use the screen, part thereof, or an
	application is serving as a stream source.		application as a stream source.
	The browser is expected to provide mechanisms in order to assure that		The browser is expected to provide mechanisms in order to assure that
	streams are the ones the recipient intended to receive.		streams are the ones the recipient intended to receive.
	The browser is expected to provide mechanisms that allows the users		The browser is expected to provide mechanisms that allow the users to
	to verify that the streams received have not be manipulated (F12).		verify that the streams received have not be manipulated (F12).
	The browser needs to ensure that media is not sent, and that received		The browser needs to ensure that media is not sent, and that received
	media is not rendered, until the associated stream establishment and		media is not rendered, until the associated stream establishment and
	handshake procedures with the remote peer have been successfully		handshake procedures with the remote peer have been successfully
	finished.		finished.
	The browser needs to ensure that the stream negotiation procedures		The browser needs to ensure that the stream negotiation procedures
	are not seen as Denial Of Service (DOS) by other entities.		are not seen as DoS by other entities.
	6.3. Web Application Considerations		4.3. Web Application Considerations
	The web application is expected to ensure user consent in sending and		The web application is expected to ensure user consent in sending and
	receiving media streams.		receiving media streams.
	7. Acknowledgements		5. Normative References
	The authors wish to thank Bernard Aboba, Gunnar Hellstrom, Martin
	Thomson, Lars Eggert, Matthew Kaufman, Emil Ivov, Eric Rescorla, Eric
	Burger, John Leslie, Dan Wing, Richard Barnes, Barry Dingle, Dale
	Worley, Ted hardie, Mary Barnes, Dan Burnett, Stephan Wenger, Harald
	Alvestrand, Cullen Jennings, Andrew Hutton and everyone else in the
	RTCWEB community that have provided comments, feedback, text and
	improvement proposals on the document. A big thank you to everyone
	that provided comments as part of the IESG evaluation, and to
	everyone else that provided comments and input in order to improve
	the document.
	8. Change Log
	[RFC EDITOR NOTE: Please remove this section when publishing]
	Changes from draft-ietf-rtcweb-use-cases-and-requirements-15
	o Changes based on comment from Stephen Farrell:
	o - A1 modified, to also cover access to the local file stystem.
	o Changes based on comments from Benoit Claise:
	o - RFC 5245 added to references.
	o - Note added to Annex A, indicating that the API requirements are
	not normative.
	o Changes based on comments from Brian Carpenter:
	o - RFC 7258 added to references.
	o - Terminology fixes:
	o -- 'prioritize' -> 'differentiate'.
	o -- 'prioritization' -> 'differentiation'.
	Changes from draft-ietf-rtcweb-use-cases-and-requirements-14
	o Changes based on comments from the ops-dir:
	o - Editorial fixes.
	o - F13: 'per-packet basis' -> 'per IP packet basis'.
	o - F22: Text corrected in one occurance.
	o - F25: 'audio' added.
	o Changes based on comments from IESG
	o - Editorial fixes.
	o - Disclaimer text suggested by Alissa Cooper added.
	o - F11: Reference to RFC 7258 added.
	o - F27: 'when playing' removed.
	Changes from draft-ietf-rtcweb-use-cases-and-requirements-10
	o Described that the API requirements are really from a W3C
	perspective and are supplied as an appendix in the introduction.
	Moved API requirements to an Appendix.
	o Removed the "Conventions" section with the key-words and reference
	to RFC2119. Also changed uppercase MUST's/SHOULD's to lowercase.
	o Added a note on the proposed use of the document to the
	introduction.
	o Removed the note talking about WS from the "Firewall that only
	allows http" use-case.
	o Removed the word "Skype" that was used as example in one of the
	use-cases.
	o Clarified F3 (the req saying the everything the browser sends must
	be rate controlled).
	o Removed the TBD saying we need to define reasonable levels from
	the requirement saying that quality must be good even in presence
	of packet losses (F5), and changed "must" to "should" (Based on a
	list discussion involving Bernard).
	o Removed F6 ("The browser must be able to handle high loss and
	jitter levels in a graceful way."), also after a list discussion.
	o Clarified F7 (used to say that the browser must support fast
	stream switches, now says that reference frames must be inserted
	when requested).
	o Removed the questions from F9 (echo cancellation), F10
	(synchronization), F21 (telephony codec).
	o Exchanged "restrictive firewalls" for "limited middleboxes" in F19
	(as proposed by Martin).
	o Expanded DTMF and IVR in F22 (proposed by Martin)
	o Added ref to RFC5405 in F23 (proposed by Lars Eggert).
	o Exchanged "service provided" for "web application" in F32.
	o Changed the text in 3.2.1 that motivates F36 (new text "It is
	essential that media and data be encrypted, authenticated ...
	bound to the user identity."); and rewrote F36, included a ref to
	RFC5479.
	o Changed "quality of service" to "quality of experience" in F38.
	o Added F39.
	o Used new formulation of A17 (proposed by Martin).
	o Updated A20.
	o Updated A25.
	Changes from draft-ietf-rtcweb-use-cases-and-requirements-09
	o Changed "video communication session" to "audiovisual
	communication session.
	Changes from draft-ietf-rtcweb-use-cases-and-requirements-08
	o Changed "eavesdropping" to "wiretapping" and referenced RFC2804.
	o Removed informal ref webrtc_req; that document has been abandoned
	by the W3C webrtc WG.
	o Added use-case where one user is behind a Firewall that only
	allows http; derived req. F37.
	o Changed F24 slightly; MUST-> SHOULD, inserted "available".
	o Added a clause to "Simple video communication service" saying that
	the service provider monitors the quality of service, and derived
	reqs F38 and A26.
	Changes from draft-ietf-rtcweb-use-cases-and-requirements-07
	o Added "and data exchange" to 1. Introduction.
	o Removed cone and symmetric NAT from 4.1 Introduction, refers to
	RFC4787 instead.
	o Added text on enabling verification of that the media has not been
	manipulated by anyone to use-case "Simple Video Communication
	Service", derived req. F35
	o Added text on that the browser should reject media (data) that has
	been created/injected/modified by non-trusted party, derived req.
	F36
	o Added text on enabling the app to refrain from revealing IP
	address to use-case "Simple Video Communication Service", derived
	req. A25
	o Added use-case "Simple Video Communication Service with file
	exchange", derived reqs F33 and A24
	o Added priority of video streams to "Hockey game viewer" use case,
	added priority of data to "on-line game use-case", derived reqs
	F34 and A23
	o In F22, "the IVR" -> "a DTMF based IVR".
	o Updated req F23 to clarify that requirements such as NAT
	traversal, protection from eavesdropping, rate control applies
	also to datagram.
	Changes from draft-ietf-rtcweb-use-cases-and-requirements-06
	o Renaming of requirements (FaI1 -> F31), (FaI2 -> F32) and (AaI1 ->
	A22)
	Changes from draft-ietf-rtcweb-use-cases-and-requirements-05
	o Added use-case "global service provider", derived reqs associated
	with several STUN/TURN servers
	o Added use-case "enterprise aspects", derived req associated with
	enabling the network provider to supply STUN and TURN servers
	o The requirements from the above are ICE specific and labeled
	accordingly
	o Separated the requirements phrased like "processing such as pan,
	mix and render" for audio to be specific reqs on spatialization,
	level measurement, level adjustment and mixing (discussed on the
	lists in http://www.ietf.org/mail-archive/web/rtcweb/current/
	msg01648.html and http://lists.w3.org/Archives/Public/public-
	webrtc/2011Sep/0102.html)
	o Added use-case on sharing as decided in http://www.ietf.org/mail-
	archive/web/rtcweb/current/msg01700.html, derived reqs F30 and A21
	o Added the list of common considerations proposed in mail
	http://www.ietf.org/mail-archive/web/rtcweb/current/msg01562.html
	to the Introduction of the use-case section
	Changes from draft-ietf-rtcweb-use-cases-and-requirements-04
	o Most changes based on the input from Dan Burnett
	http://www.ietf.org/mail-archive/web/rtcweb/current/msg00948.html
	o Many editorial changes
	o 4.2.1.1 Clarified
	o Some clarification added to 4.3.1.1 as a note
	o F-requirements updated (see reply to Dan's mail).
	o Almost all A-requirements updated to start "The Web API MUST
	provide ..."
	o A8 removed, A9 rephrased to cover A8 and old A9
	o A15 rephrased
	o For more details, and discussion, look at the response to Dan's
	mail http://www.ietf.org/mail-archive/web/rtcweb/current/
	msg01177.html
	Changes from draft-ietf-rtcweb-use-cases-and-requirements-03
	o Editorials
	o Changed when the self-view is displayed in 4.2.1.1, and added
	words about allowing users to remove and re-insert it.
	o Clarified 4.2.6.1
	o Removed the "mono" stuff from 4.2.7.1
	o Added that communication should not be possible to eavesdrop to
	most use cases - and req. F17
	o Re-phrased 4.3.3.1 to not describe the technical solution so much,
	and removed "stereo" stuff. Solution possibilities are now in a
	note.
	o Re-inserted API requirements after discussion in the W3C webrtc
	WG. (Re-phrased A15 and added A18 compared to version -02).
	Changes from draft-ietf-rtcweb-use-cases-and-requirements-02
	o Removed description/list of API requirements, instead
	o Reference to W3C webrtc_reqs document for API requirements
	Changes from draft-ietf-rtcweb-ucreqs-01
	o Changed Intended status to Information
	o Changed "Ipr" to "trust200902"
	o Added use case "Simple video communication service, NAT/Firewall
	that blocks UDP", and derived new req F26
	o Added use case "Distributed Music Band" and derived new req A17
	o Added F24 as requirement derived from use case "Simple video
	communication service with inter-operator calling"
	o Added section "Additional use cases"
	o Added text about ID handling to multiparty with central server use
	case
	o Re-phrased A1 slightly
	Changes from draft-ietf-rtcweb-ucreqs-00
	o - Reshuffled: Just two main groups of use cases (b2b and b2GW/
	Server); removed some specific use cases and added them instead as
	flavors to the base use case (Simple video communication)
	o - Changed the formulation of F19
	o - Removed the requirement on an API for DTMF
	o - Removed "FX3: There SHOULD be a mapping of the minimum needed
	data for setting up connections into SIP, so that the restriction
	to SIP-carriable data can be verified. Not a rew on the browser
	but rather on a document"
	o - (see http://www.ietf.org/mail-archive/web/rtcweb/current/
	msg00227.html for more details)
	o -Added text on informing user of that mic/cam is being used and
	that it must be possible to revoce permission to use them in
	section 7.
	Changes from draft-holmberg-rtcweb-ucreqs-01
	o - Draft name changed to draft-ietf-rtcweb-ucreqs
	o - Use-case grouping introduced
	o - Additional use-cases added
	o - Additional reqs added (derived from use cases): F19-F25, A16-A17
	Changes from draft-holmberg-rtcweb-ucreqs-00
	o - Mapping between use-cases and requirements added (Harald
	Alvestrand, 090311)
	o - Additional security considerations text (Harald Alvestrand,
	090311)
	o - Clarification that user applications are assumed to be executed
	by a browser (Ted Hardie, 080311)
	o - Editorial corrections and clarifications
	9. Normative References
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, March 1997.
	[RFC2804] IAB and IESG, "IETF Policy on Wiretapping", RFC 2804, May		[RFC2804] IAB and , "IETF Policy on Wiretapping", RFC 2804, May
	2000.		2000, <http://www.rfc-editor.org/info/rfc2804>.
	[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, <http://www.rfc-editor.org/info/rfc5245>.
	[RFC5405] Eggert, L. and G. Fairhurst, "Unicast UDP Usage Guidelines		[RFC5405] Eggert, L. and G. Fairhurst, "Unicast UDP Usage Guidelines
	for Application Designers", BCP 145, RFC 5405, November		for Application Designers", BCP 145, RFC 5405, November
	2008.		2008, <http://www.rfc-editor.org/info/rfc5405>.
	[RFC5479] Wing, D., Fries, S., Tschofenig, H., and F. Audet,		[RFC5479] Wing, D., Ed., Fries, S., Tschofenig, H., and F. Audet,
	"Requirements and Analysis of Media Security Management		"Requirements and Analysis of Media Security Management
	Protocols", RFC 5479, April 2009.		Protocols", RFC 5479, April 2009,
			<http://www.rfc-editor.org/info/rfc5479>.
	[RFC7258] Farrell, S. and H. Tschofenig, "Pervasive Monitoring Is an		[RFC7258] Farrell, S. and H. Tschofenig, "Pervasive Monitoring Is an
	Attack", BCP 188, RFC 7258, May 2014.		Attack", BCP 188, RFC 7258, May 2014,
			<http://www.rfc-editor.org/info/rfc7258>.
	Appendix A. API requirements		Appendix A. API Requirements
	This section contains the requirements on the API derived from the		This section contains the requirements on the API derived from the
	use-cases in Section 3.		use cases in Section 2.
	NOTE: As W3C is responsible for the API, the API requirements in this		Note: As the W3C is responsible for the API, the API requirements in
	specification are not normative.		this specification are not normative.
	REQ-ID DESCRIPTION		REQ-ID DESCRIPTION
	----------------------------------------------------------------		----------------------------------------------------------------
	A1 The Web API must provide means for the		A1 The web API must provide means for the
	application to ask the browser for permission		application to ask the browser for permission
	to use cameras and microphones as input devices,		to use cameras and microphones as input devices
	and to have access to the local file system.		and to have access to the local file system.
	----------------------------------------------------------------		----------------------------------------------------------------
	A2 The Web API must provide means for the web		A2 The web API must provide means for the web
	application to control how streams generated		application to control how streams generated
	by input devices are used.		by input devices are used.
	----------------------------------------------------------------		----------------------------------------------------------------
	A3 The Web API must provide means for the web		A3 The web API must provide means for the web
	application to control the local rendering of		application to control the local rendering of
	streams (locally generated streams and streams		streams (locally generated streams and streams
	received from a peer).		received from a peer).
	----------------------------------------------------------------		----------------------------------------------------------------
	A4 The Web API must provide means for the web		A4 The web API must provide means for the web
	application to initiate sending of		application to initiate the sending of a
	stream/stream components to a peer.		stream / stream components to a peer.
	----------------------------------------------------------------		----------------------------------------------------------------
	A5 The Web API must provide means for the web		A5 The web API must provide means for the web
	application to control the media format (codec)		application to control the media format (codec)
	to be used for the streams sent to a peer.		to be used for the streams sent to a peer.
	NOTE: The level of control depends on whether		Note: The level of control depends on whether
	the codec negotiation is handled by the browser		the codec negotiation is handled by the browser
	or the web application.		or the web application.
	----------------------------------------------------------------		----------------------------------------------------------------
	A6 The Web API must provide means for the web		A6 The web API must provide means for the web
	application to modify the media format for		application to modify the media format for
	streams sent to a peer after a media stream		streams sent to a peer after a media stream
	has been established.		has been established.
	----------------------------------------------------------------		----------------------------------------------------------------
	A7 The Web API must provide means for		A7 The web API must provide means for
	informing the web application of whether the		informing the web application of whether or not
	establishment of a stream with a peer was		the establishment of a stream with a peer was
	successful or not.		successful.
	----------------------------------------------------------------		----------------------------------------------------------------
	A8 The Web API must provide means for the web		A8 The web API must provide means for the web
	application to mute/unmute a stream or stream		application to mute/unmute a stream or stream
	component(s). When a stream is sent to a peer		component(s). When a stream is sent to a peer,
	mute status must be preserved in the stream		mute status must be preserved in the stream
	received by the peer.		received by the peer.
	----------------------------------------------------------------		----------------------------------------------------------------
	A9 The Web API must provide means for the web		A9 The web API must provide means for the web
	application to cease the sending of a stream		application to cease the sending of a stream
	to a peer.		to a peer.
	----------------------------------------------------------------		----------------------------------------------------------------
	A10 The Web API must provide means for the web		A10 The web API must provide means for the web
	application to cease processing and rendering		application to cease the processing and rendering
	of a stream received from a peer.		of a stream received from a peer.
	----------------------------------------------------------------		----------------------------------------------------------------
	A11 The Web API must provide means for		A11 The web API must provide means for
	informing the web application when a		informing the web application when a
	stream from a peer is no longer received.		stream from a peer is no longer received.
	----------------------------------------------------------------		----------------------------------------------------------------
	A12 The Web API must provide means for		A12 The web API must provide means for
	informing the web application when high		informing the web application when high
	loss rates occur.		loss rates occur.
	----------------------------------------------------------------		----------------------------------------------------------------
	A13 The Web API must provide means for the web		A13 The web API must provide means for the web
	application to apply spatialization effects to		application to apply spatialization effects to
	audio streams.		audio streams.
	----------------------------------------------------------------		----------------------------------------------------------------
	A14 The Web API must provide means for the web		A14 The web API must provide means for the web
	application to detect the level in audio		application to detect the level in audio
	streams.		streams.
	----------------------------------------------------------------		----------------------------------------------------------------
	A15 The Web API must provide means for the web		A15 The web API must provide means for the web
	application to adjust the level in audio		application to adjust the level in audio
	streams.		streams.
	----------------------------------------------------------------		----------------------------------------------------------------
	A16 The Web API must provide means for the web		A16 The web API must provide means for the web
	application to mix audio streams.		application to mix audio streams.
	----------------------------------------------------------------		----------------------------------------------------------------
	A17 The Web API must provide a way to identify		A17 The web API must provide a way to identify
	streams such that an application is able to		streams such that an application is able to
	match streams on a sending peer with the same		match streams on a sending peer with the same
	stream on all receiving peers.		stream on all receiving peers.
	----------------------------------------------------------------		----------------------------------------------------------------
	A18 The Web API must provide a mechanism for sending		A18 The web API must provide a mechanism for sending
	and receiving isolated discrete chunks of data.		and receiving isolated discrete chunks of data.
	----------------------------------------------------------------		----------------------------------------------------------------
	A19 The Web API must provide means for the web		A19 The web API must provide means for the web
	application to indicate the type of audio signal		application to indicate the type of audio signal
	(speech, audio) for audio stream(s)/stream		(speech, audio) for audio stream(s) / stream
	component(s).		component(s).
	----------------------------------------------------------------		----------------------------------------------------------------
	A20 It must be possible for an initiator or a		A20 It must be possible for an initiator or a
	responder web application to indicate the types		responder web application to indicate the types
	of media it is willing to accept incoming		of media it is willing to accept incoming
	streams for when setting up a connection (audio,		streams for when setting up a connection (audio,
	video, other). The types of media to be accepted		video, other). The types of media to be accepted
	can be a subset of the types of media the browser		can be a subset of the types of media the browser
	is able to accept.		is able to accept.
	----------------------------------------------------------------		----------------------------------------------------------------
	A21 The Web API must provide means for the		A21 The web API must provide means for the
	application to ask the browser for permission		application to ask the browser for permission
	to the screen, a certain area on the screen		to use the screen, a certain area on the screen,
	or what a certain application displays on the		or what a certain application displays on the
	screen as input to streams.		screen as input to streams.
	----------------------------------------------------------------		----------------------------------------------------------------
	A22 The Web API must provide means for the		A22 The web API must provide means for the
	application to specify several STUN and/or		application to specify several STUN and/or
	TURN servers to use.		TURN servers to use.
	----------------------------------------------------------------		----------------------------------------------------------------
	A23 The Web API must provide means for the		A23 The web API must provide means for the
	application to specify the priority to		application to specify the priority to
	apply for outgoing streams and data.		apply for outgoing streams and data.
	----------------------------------------------------------------		----------------------------------------------------------------
	A24 The Web API must provide a mechanism for sending		A24 The web API must provide a mechanism for sending
	and receiving files.		and receiving files.
	----------------------------------------------------------------		----------------------------------------------------------------
	A25 It must be possible for the application to		A25 It must be possible for the application to
	instruct the browser to refrain from exposing		instruct the browser to refrain from exposing
	the host IP address to the application		the host IP address to the application.
	----------------------------------------------------------------		----------------------------------------------------------------
	A26 The Web API must provide means for the		A26 The web API must provide means for the
	application to obtain the statistics (related		application to obtain the statistics (related
	to transport, and collected by the browser)		to transport, and collected by the browser)
	needed to estimate quality of service.		needed to estimate the quality of service.
	----------------------------------------------------------------		----------------------------------------------------------------
			Acknowledgements
			The authors wish to thank Bernard Aboba, Gunnar Hellstrom, Martin
			Thomson, Lars Eggert, Matthew Kaufman, Emil Ivov, Eric Rescorla, Eric
			Burger, John Leslie, Dan Wing, Richard Barnes, Barry Dingle, Dale
			Worley, Ted Hardie, Mary Barnes, Dan Burnett, Stephan Wenger, Harald
			Alvestrand, Cullen Jennings, Andrew Hutton and everyone else in the
			RTCWEB community that have provided comments, feedback, text and
			improvement proposals on the document. A big thank you to everyone
			that provided comments as part of the IESG evaluation and to everyone
			else that provided comments and input in order to improve the
			document.
	Authors' Addresses		Authors' Addresses
	Christer Holmberg		Christer Holmberg
	Ericsson		Ericsson
	Hirsalantie 11		Hirsalantie 11
	Jorvas 02420		Jorvas 02420
	Finland		Finland
	Email: christer.holmberg@ericsson.com		EMail: christer.holmberg@ericsson.com
	Stefan Hakansson		Stefan Hakansson
	Ericsson		Ericsson
	Laboratoriegrand 11		Laboratoriegrand 11
	Lulea 97128		Lulea 97128
	Sweden		Sweden
	Email: stefan.lk.hakansson@ericsson.com		EMail: stefan.lk.hakansson@ericsson.com
	Goran AP Eriksson		Goran AP Eriksson
	Ericsson		Ericsson
	Farogatan 6		Farogatan 6
	Stockholm 16480		Stockholm 16480
	Sweden		Sweden
	Email: goran.ap.eriksson@ericsson.com		EMail: goran.ap.eriksson@ericsson.com
End of changes. 245 change blocks.
	1043 lines changed or deleted		740 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/