--- 1/draft-ietf-rtcweb-use-cases-and-requirements-05.txt 2011-10-04 15:14:09.778548990 +0200 +++ 2/draft-ietf-rtcweb-use-cases-and-requirements-06.txt 2011-10-04 15:14:09.822548466 +0200 @@ -1,19 +1,19 @@ RTCWEB Working Group C. Holmberg Internet-Draft S. Hakansson Intended status: Informational G. Eriksson -Expires: March 18, 2012 Ericsson - September 15, 2011 +Expires: April 6, 2012 Ericsson + October 4, 2011 Web Real-Time Communication Use-cases and Requirements - draft-ietf-rtcweb-use-cases-and-requirements-05.txt + draft-ietf-rtcweb-use-cases-and-requirements-06.txt Abstract This document describes web based real-time communication use-cases. Based on the use-cases, the document also derives requirements related to the browser, and the API used by web applications to request and control media stream services provided by the browser. Status of this Memo @@ -23,21 +23,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on March 18, 2012. + This Internet-Draft will expire on April 6, 2012. Copyright Notice Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -47,52 +47,57 @@ the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Use-cases . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4.1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 3 - 4.2. Browser-to-browser use-cases . . . . . . . . . . . . . . . 3 - 4.2.1. Simple Video Communication Service . . . . . . . . . . 3 + 4.2. Browser-to-browser use-cases . . . . . . . . . . . . . . . 4 + 4.2.1. Simple Video Communication Service . . . . . . . . . . 4 4.2.2. Simple Video Communication Service, NAT/FW that - blocks UDP . . . . . . . . . . . . . . . . . . . . . . 4 - 4.2.3. Simple Video Communication Service, access change . . 4 - 4.2.4. Simple Video Communication Service, QoS . . . . . . . 5 - 4.2.5. Simple video communication service with - inter-operator calling . . . . . . . . . . . . . . . . 5 - 4.2.6. Hockey Game Viewer . . . . . . . . . . . . . . . . . . 6 - 4.2.7. Multiparty video communication . . . . . . . . . . . . 7 - 4.2.8. Multiparty on-line game with voice communication . . . 8 - 4.2.9. Distributed Music Band . . . . . . . . . . . . . . . . 8 - 4.3. Browser - GW/Server use cases . . . . . . . . . . . . . . 9 - 4.3.1. Telephony terminal . . . . . . . . . . . . . . . . . . 9 - 4.3.2. Fedex Call . . . . . . . . . . . . . . . . . . . . . . 9 - 4.3.3. Video conferencing system with central server . . . . 10 - 5. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 11 - 5.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 11 - 5.2. Browser requirements . . . . . . . . . . . . . . . . . . . 11 - 5.3. API requirements . . . . . . . . . . . . . . . . . . . . . 13 - 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 - 7. Security Considerations . . . . . . . . . . . . . . . . . . . 15 - 7.1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 15 - 7.2. Browser Considerations . . . . . . . . . . . . . . . . . . 15 - 7.3. Web Application Considerations . . . . . . . . . . . . . . 16 - 8. Additional use-cases . . . . . . . . . . . . . . . . . . . . . 16 - 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 17 - 10. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 17 - 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19 - 11.1. Normative References . . . . . . . . . . . . . . . . . . . 19 - 11.2. Informative References . . . . . . . . . . . . . . . . . . 19 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19 + blocks UDP . . . . . . . . . . . . . . . . . . . . . . 5 + 4.2.3. Simple Video Communication Service, global service + provider . . . . . . . . . . . . . . . . . . . . . . . 5 + 4.2.4. Simple Video Communication Service, enterprise + aspects . . . . . . . . . . . . . . . . . . . . . . . 5 + 4.2.5. Simple Video Communication Service, access change . . 6 + 4.2.6. Simple Video Communication Service, QoS . . . . . . . 7 + 4.2.7. Simple Video Communication Service with sharing . . . 7 + 4.2.8. Simple video communication service with + inter-operator calling . . . . . . . . . . . . . . . . 8 + 4.2.9. Hockey Game Viewer . . . . . . . . . . . . . . . . . . 8 + 4.2.10. Multiparty video communication . . . . . . . . . . . . 9 + 4.2.11. Multiparty on-line game with voice communication . . . 10 + 4.2.12. Distributed Music Band . . . . . . . . . . . . . . . . 11 + 4.3. Browser - GW/Server use cases . . . . . . . . . . . . . . 11 + 4.3.1. Telephony terminal . . . . . . . . . . . . . . . . . . 11 + 4.3.2. Fedex Call . . . . . . . . . . . . . . . . . . . . . . 12 + 4.3.3. Video conferencing system with central server . . . . 12 + 5. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 13 + 5.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 13 + 5.2. Browser requirements . . . . . . . . . . . . . . . . . . . 13 + 5.3. API requirements . . . . . . . . . . . . . . . . . . . . . 16 + 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 + 7. Security Considerations . . . . . . . . . . . . . . . . . . . 18 + 7.1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 18 + 7.2. Browser Considerations . . . . . . . . . . . . . . . . . . 19 + 7.3. Web Application Considerations . . . . . . . . . . . . . . 19 + 8. Additional use-cases . . . . . . . . . . . . . . . . . . . . . 20 + 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 20 + 10. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 21 + 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 23 + 11.1. Normative References . . . . . . . . . . . . . . . . . . . 23 + 11.2. Informative References . . . . . . . . . . . . . . . . . . 23 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 23 1. Introduction This document presents a few use-cases of web applications that are executed in a browser and use real-time communication capabilities. Based on the use-cases, the document derives requirements related to the browser and the API used by web applications in the browser. The requirements related to the browser are named "Fn" and are described in Section 5.2 @@ -115,20 +120,32 @@ TBD 4. Use-cases 4.1. Introduction This section describes web based real-time communication use-cases, from which requirements are derived. + The following considerations are applicable to all use cases: + o Clients can be on IPv4-only + o Clients can be on IPv6-only + o Clients can be on dual-stack + o Clients can be on wideband (10s of Mbits/sec) + o Clients can be on narrowband (10s to 100s of Kbits/sec) + o Clients can be on variable-media-quality networks (wireless) + o Clients can be on congested networks + o Clients can be on firewalled networks with no UDP allowed + o Clients can be on networks with cone NAT + o Clients can be on networks with symmetric NAT + 4.2. Browser-to-browser use-cases 4.2.1. Simple Video Communication Service 4.2.1.1. Description Two or more users have loaded a video communication web application into their browsers, provided by the same service provider, and logged into the service it provides. The web service publishes information about user login status by pushing updates to the web @@ -152,110 +169,202 @@ The two users may be using communication devices of different makes, with different operating systems and browsers from different vendors. One user has an unreliable Internet connection. It sometimes loses packets, and sometimes goes down completely. One user is located behind a Network Address Translator (NAT). 4.2.1.2. Derived Requirements - F1, F2, F3, F4, F5, F6, F8, F9, F10, F17, F22, F25 + F1, F2, F3, F4, F5, F6, F8, F9, F10, F20, F25, F28 - A1, A2, A3, A4, A5, A6, A7, A9, A10, A11, A12, A13 + A1, A2, A3, A4, A5, A6, A7, A8, A9, A10, A11, A12 4.2.2. Simple Video Communication Service, NAT/FW that blocks UDP 4.2.2.1. Description - This use-case is almost identical to the previos one. The difference - is that one of the users is behind a NAT that blocks UDP traffic. + This use-case is almost identical to the Simple Video Communication + Service use-case (Section 4.2.1). The difference is that one of the + users is behind a NAT that blocks UDP traffic. 4.2.2.2. Derived Requirements - F1, F2, F3, F4, F5, F6, F8, F9, F10, F17, F22, F23, F25, F26 + F1, F2, F3, F4, F5, F6, F8, F9, F10, F20, F25, F28, F29 - A1, A2, A3, A4, A5, A6, A7, A9, A10, A11, A12, A13 + A1, A2, A3, A4, A5, A6, A7, A8, A9, A10, A11, A12 + +4.2.3. Simple Video Communication Service, global service provider -4.2.3. Simple Video Communication Service, access change 4.2.3.1. Description - This use-case is almost identical to "4.2.1 Simple Video - Communication Service". The difference is that the user changes - network access during the session: + This use-case is almost identical to the Simple Video Communication + Service use-case (Section 4.2.1). + + What is added is that the service provider is operating over large + geographical areas (or even globally). + + Assuming that ICE will be used, this means that the service provider + would like to be able to provide several STUN and TURN servers (via + the app) to the browser; selection of which one(s) to use is part of + the ICE processing. Other reasons for wanting to provide several + STUN and TURN servers include support for IPv4 and IPv6, load + balancing and redundancy. + + Note that the additional requirements derived are termed FaI/AaI + where aI means "assuming ICE". + +4.2.3.2. Derived Requirements + + F1, F2, F3, F4, F5, F6, F8, F9, F10, F20, F25, F28 + + FaI1 + + A1, A2, A3, A4, A5, A6, A7, A8, A9, A10, A11, A12 + + AaI1 + +4.2.4. Simple Video Communication Service, enterprise aspects +4.2.4.1. Description + + This use-case is similar to the Simple Video Communication Service + use-case (Section 4.2.1). + + What is added is aspects when using the service in enterprises. ICE + is assumed in the further description of this use-case. + + An enterprise that uses a RTCWEB based web application for + communication desires to audit all RTCWEB based application session + used from inside the company towards any external peer. To be able + to do this they deploy a TURN server that straddle the boundary + between the internal network and the external. + + The firewall will block all attempts to use STUN with an external + destination unless they go to the enterprise auditing TURN server. + In cases where employees are using RTCWEB applications provided by an + external service provider they still want to have the traffic to stay + inside their internal network and in addition not load the straddling + TURN server, thus they deploy a STUN server allowing the RTCWEB + client to determine its server reflexive address on the internal + side. Thus enabling cases where peers are both on the internal side + to connect without the traffic leaving the internal network. It must + be possibele to configure the browsers used in the enterprise with + network specific STUN and TURN servers. This should be possible to + achieve by autoconfiguration methods. The RTCWEB functionality will + need to utilize both network specific STUN and TURN resources and + STUN and TURN servers provisioned by the web application. + + Note that the additional requirements derived are termed FaI/AaI + where aI means "assuming ICE". + +4.2.4.2. Derived Requirements + + F1, F2, F3, F4, F5, F6, F8, F9, F10, F20, F25, F28 + + FaI2 + + A1, A2, A3, A4, A5, A6, A7, A8, A9, A10, A11, A12 + +4.2.5. Simple Video Communication Service, access change + +4.2.5.1. Description + + This use-case is almost identical to the Simple Video Communication + Service use-case (Section 4.2.1).The difference is that the user + changes network access during the session: The communication device used by one of the users have several network adapters (Ethernet, WiFi, Cellular). The communication device is accessing the Internet using Ethernet, but the user has to start a trip during the session. The communication device automatically changes to use WiFi when the Ethernet cable is removed and then moves to cellular access to the Internet when moving out of WiFi coverage. The session continues even though the access method changes. -4.2.3.2. Derived Requirements +4.2.5.2. Derived Requirements - F1, F2, F3, F4, F5, F6, F8, F9, F10, F17, F22, F23, F25 + F1, F2, F3, F4, F5, F6, F8, F9, F10, F20, F25, F26, F28 - A1, A2, A3, A4, A5, A6, A7, A9, A10, A11, A12, A13 + A1, A2, A3, A4, A5, A6, A7, A8, A9, A10, A11, A12 -4.2.4. Simple Video Communication Service, QoS +4.2.6. Simple Video Communication Service, QoS -4.2.4.1. Description +4.2.6.1. Description - This use-case is almost identical to the previous one. The use of - Quality of Service (QoS) capabilities is added: + This use-case is almost identical to the Simple Video Communication + Service, access change use-case (Section 4.2.5). The use of Quality + of Service (QoS) capabilities is added: The user in the previous use case that starts a trip is behind a common residential router that supports prioritization of traffic. 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 when accessing via the residential router and when using cellular. -4.2.4.2. Derived Requirements +4.2.6.2. Derived Requirements - F1, F2, F3, F4, F5, F6, F8, F9, F10, F17, F21, F22, F23, F25 + F1, F2, F3, F4, F5, F6, F8, F9, F10, F20, F24, F25, F26, F28 - A1, A2, A3, A4, A5, A6, A7, A9, A10, A11, A12, A13 + A1, A2, A3, A4, A5, A6, A7, A8, A9, A10, A11, A12 -4.2.5. Simple video communication service with inter-operator calling +4.2.7. Simple Video Communication Service with sharing -4.2.5.1. Description +4.2.7.1. Description + + This use-case has the audio and video communication of the Simple + Video Communication Service use-case (Section 4.2.1). + + But in addition to this, one of the users can share what is being + displayed on her/his screen with a peer. The user can choose to + share the entire screen, part of the screen (part selected by the + user) or what a selected applicaton displays with the peer. + +4.2.7.2. Derived Requirements + + F1, F2, F3, F4, F5, F6, F8, F9, F10, F20, F25, F28, F30 + + A1, A2, A3, A4, A5, A6, A7, A8, A9, A10, A11, A12, A21 + +4.2.8. Simple video communication service with inter-operator calling + +4.2.8.1. Description Two users have logged into two different web applications, provided by different service providers. The service providers are interconnected by some means, but exchange no more information about the users than what can be carried using SIP. NOTE: More profiling of what this means may be needed. For each user Alice who has authorized another user Bob to receive login status information, Alice's service publishes Alice's login status information to Bob. How this authorization is defined and established is out of scope. - The same functionality as in the "4.2.1 Simple Video Communication - Service" is available. + The same functionality as in the the Simple Video Communication + Service use-case (Section 4.2.1) is available. The same issues with connectivity apply. -4.2.5.2. Derived requirements +4.2.8.2. Derived requirements - F1, F2, F3, F4, F5, F6, F8, F9, F10, F17, F22, F24, F25 + F1, F2, F3, F4, F5, F6, F8, F9, F10, F20, F25, F27, F28 - A1, A2, A3, A4, A5, A6, A7, A9, A10, A11, A12, A13 + A1, A2, A3, A4, A5, A6, A7, A8, A9, A10, A11, A12, A20 -4.2.6. Hockey Game Viewer +4.2.9. Hockey Game Viewer -4.2.6.1. Description +4.2.9.1. Description An ice-hockey club uses an application that enables talent scouts to, in real-time, show and discuss games and players with the club manager. The talent scouts use a mobile phone with two cameras, one front facing and one rear facing. The club manager uses a desktop, equipped with one camera, for viewing the game and discussing with the talent scout. Before the game starts, and during game breaks, the talent scout and @@ -272,107 +381,119 @@ 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 the desktop screen, with picture-in-picture thumbnails of the rear facing camera and the desktop camera (self-view). On the display of the mobile phone the game is shown (front facing camera) with picture-in-picture thumbnails of the rear facing camera (self-view) and the desktop camera. It is essential that the communication cannot be eavesdropped. -4.2.6.2. Derived Requirements +4.2.9.2. Derived Requirements - F1, F2, F3, F4, F5, F6, F8, F9, F10, F14, F17 + F1, F2, F3, F4, F5, F6, F8, F9, F10, F17, F20 - A1, A2, A3, A4, A5, A7, A9, A10, A11, A12, A13, A15 + A1, A2, A3, A4, A5, A7, A8, A9, A10, A11, A12, A17 -4.2.7. Multiparty video communication +4.2.10. Multiparty video communication -4.2.7.1. Description +4.2.10.1. Description - In this use-case the simple video communication service - Section 4.2.1is extended by allowing multiparty sessions. No central - server is involved - the browser of each participant sends and - receives streams to and from all other session participants. The web - application in the browser of each user is responsible for setting up - streams to all receivers. + In this use-case is the Simple Video Communication Service use-case + (Section 4.2.1) is extended by allowing multiparty sessions. No + central server is involved - the browser of each participant sends + and receives streams to and from all other session participants. The + web application in the browser of each user is responsible for + setting up streams to all receivers. In order to enhance intelligibility, the web application pans the audio from different participants differently when rendering the audio. This is done automatically, but users can change how the - different participants are placed in the (virtual) room. + different participants are placed in the (virtual) room. In addition + the levels in the audio signals are adjusted before mixing. + + Another feature intended to enhance the use experience is that the + video window that displays the video of the currently speaking peer + is highlighted. Each video stream received is by default displayed in a thumbnail frame within the browser, but users can change the display size. It is essential that the communication cannot be eavesdropped. Note: What this use-case adds in terms of requirements is capabilities to send streams to and receive streams from several peers concurrently, as well as the capabilities to render the video - from all recevied streams and be able to spatialize and mix the audio - from all received streams locally in the browser. + from all recevied streams and be able to spatialize, level adjust and + mix the audio from all received streams locally in the browser. It + also adds the capability to measure the audio level/activity. -4.2.7.2. Derived Requirements +4.2.10.2. Derived Requirements - F1, F2, F3, F4, F5, F6, F8, F9, F10, F11, F12, F13, F14, F17, F22 + F1, F2, F3, F4, F5, F6, F8, F9, F10, F11, F12, F13, F14, F15, F16, + F17, F20, F25 - A1, A2, A3, A4, A5, A6, A7, A9, A10, A11, A12, A13, A14, A15 + A1, A2, A3, A4, A5, A6, A7, A8, A9, A10, A11, A12, A13, A14, A15, + A16, A17 -4.2.8. Multiparty on-line game with voice communication +4.2.11. Multiparty on-line game with voice communication -4.2.8.1. Description +4.2.11.1. Description 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 the context of an on-line game. The received voice audio media is 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 played to the user together with the voice media. Quick updates of the game state is required. It is essential that the communication cannot be eavesdropped. Note: the difference regarding local audio processing compared to the "Multiparty video communication" use-case is that other sound objects than the streams must be possible to be included in the spatialization and mixing. "Other sound objects" could for example be a file with the sound of the tank; that file could be stored locally or remotely. -4.2.8.2. Derived Requirements +4.2.11.2. Derived Requirements - F1, F2, F3, F4, F5, F6, F8, F9, F11, F12, F13, F15, F17, F20 + F1, F2, F3, F4, F5, F6, F8, F9, F11, F12, F13, F14, F15, F16, F18, + F20, F23 - A1, A2, A3, A4, A5, A7, A9, A10, A11, A12, A13, A14, A15, A16 + A1, A2, A3, A4, A5, A7, A8, A9, A10, A11, A12, A13, A14, A15, A16, + A17, A18 -4.2.9. Distributed Music Band +4.2.12. Distributed Music Band -4.2.9.1. Description +4.2.12.1. Description In this use-case, a music band is playing music while the members are at different physical locations. No central server is used, instead all streams are set up in a mesh fashion. Discussion: This use-case was briefly discussed at the Quebec webrtc meeting and it got support. So far the only concrete requirement (A17) derived is that the application must be able to ask the browser to treat the audio signal as audio (in contrast to speech). However, the use case should be further analysed to determine other requirements (could be e.g. on delay mic->speaker, level control of audio signals, etc.). -4.2.9.2. Derived Requirements +4.2.12.2. Derived Requirements - F1, F2, F3, F4, F5, F6, F8, F9, F11, F12, F13 - A1, A2, A3, A4, A5, A7, A9, A10, A11, A12, A13, A14, A15, A17 + F1, F2, F3, F4, F5, F6, F8, F9, F11, F12, F13, F14, F15, F16 + + A1, A2, A3, A4, A5, A7, A8, A9, A10, A11, A12, A13, A14, A15, A16, + A19 4.3. Browser - GW/Server use cases 4.3.1. Telephony terminal 4.3.1.1. Description 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 and receive calls in the same way as when using a normal mobile @@ -387,39 +508,39 @@ on line, so they are available and can be clicked to call, and be used to present the identity of an incoming call. If the callee is not in your phone contacts the number is displayed. Furthermore, your call logs are available, and updated with the calls made/ received from the browser. And for people receiving calls made from the web browser the usual identity (i.e. the phone number of the mobile phone) will be presented. 4.3.1.2. Derived Requirements - F1, F2, F3, F4, F5, F6, F8, F9, F10, F17, F18 + F1, F2, F3, F4, F5, F6, F8, F9, F10, F20, F21 - A1, A2, A3, A4, A7, A9, A10, A11, A12, A13 + A1, A2, A3, A4, A7, A8, A9, A10, A11, A12 4.3.2. Fedex Call 4.3.2.1. Description Alice uses her web browser with a service something like Skype to be able to phone PSTN numbers. Alice calls 1-800-gofedex. Alice should be able to hear the initial prompts from the fedex IVR and when the IVR says press 1, there should be a way for Alice to navigate the IVR. 4.3.2.2. Derived Requirements - F1, F2, F3, F4, F5, F6, F8, F9, F10, F18, F19 + F1, F2, F3, F4, F5, F6, F8, F9, F10, F21, F22 - A1, A2, A3, A4, A7, A9, A10, A11, A12, A13 + A1, A2, A3, A4, A7, A8, A9, A10, A11, A12 4.3.3. Video conferencing system with central server 4.3.3.1. Description An organization uses a video communication system that supports the establishment of multiparty video sessions using a central conference server. The browser of each participant send an audio stream (type in terms @@ -459,23 +580,23 @@ video streams: a) each browser could send a high resolution, but scalable stream, and the server could send just the base layer for the low resolution streams, b) each browser could in a simulcast fashion send one high resolution and one low resolution stream, and the server just selects or c) each browser sends just a high resolution stream, the server transcodes into low resolution streams as required. 4.3.3.2. Derived Requirements - F1, F2, F3, F4, F5, F6, F7, F8, F9, F10, F14, F16, F17 + F1, F2, F3, F4, F5, F6, F7, F8, F9, F10, F17, F19, F20 - A1, A2, A3, A4, A5, A7, A9, A10, A11, A12, A13, A15 + A1, A2, A3, A4, A5, A7, A8, A9, A10, A11, A12, A17 5. Requirements 5.1. General This section contains the requirements derived from the use-cases in section 4. NOTE: It is assumed that the user applications are executed on a browser. Whether the capabilities to implement specific browser @@ -525,71 +645,93 @@ QUESTION: How much control should be left to the web application? ---------------------------------------------------------------- F11 The browser MUST be able to transmit streams to several peers concurrently. ---------------------------------------------------------------- F12 The browser MUST be able to receive streams from multiple peers concurrently. ---------------------------------------------------------------- - F13 The browser MUST be able to pan, mix and render - several concurrent audio streams. + F13 The browser MUST be able to apply spatialization + effects to audio streams. + ---------------------------------------------------------------- - F14 The browser MUST be able to render several + F14 The browser MUST be able to measure the level + in audio streams. + ---------------------------------------------------------------- + F15 The browser MUST be able to change the level + in audio streams. + ---------------------------------------------------------------- + F16 The browser MUST be able to render several concurrent video streams ---------------------------------------------------------------- - F15 The browser MUST be able to process and mix + F17 The browser MUST be able to mix several + audio streams. + ---------------------------------------------------------------- + F18 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). + peer(s) with audio streams. ---------------------------------------------------------------- - F16 Streams MUST be able to pass through restrictive + F19 Streams MUST be able to pass through restrictive firewalls. ---------------------------------------------------------------- - F17 It MUST be possible to protect streams from + F20 It MUST be possible to protect streams from eavesdropping. ---------------------------------------------------------------- - F18 The browser MUST support an audio media format + F21 The browser MUST support an audio media format (codec) that is commonly supported by existing telephony services. QUESTION: G.711? ---------------------------------------------------------------- - F19 There should be a way to navigate + F22 There should be a way to navigate the IVR ---------------------------------------------------------------- - F20 The browser must be able to send short + F23 The browser must be able to send short latency datagram traffic to a peer browser ---------------------------------------------------------------- - F21 The browser MUST be able to take advantage of + F24 The browser MUST be able to take advantage of capabilities to prioritize voice and video appropriately. ---------------------------------------------------------------- - F22 The browser SHOULD use encoding of streams + F25 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 ---------------------------------------------------------------- - F23 It MUST be possible to move from one network + F26 It MUST be possible to move from one network interface to another one ---------------------------------------------------------------- - F24 The browser MUST be able to initiate and accept a + F27 The browser MUST be able to initiate and accept a media session where the data needed for establishment can be carried in SIP. ---------------------------------------------------------------- - F25 The browser MUST support a baseline audio and + F28 The browser MUST support a baseline audio and video codec ---------------------------------------------------------------- - F26 The browser MUST be able to send streams to a + F29 The browser MUST be able to send streams to a peer in the presence of NATs that block UDP traffic. ---------------------------------------------------------------- + F30 The browser MUST be able to use the screen (or + a specific area of the screen) or what a certain + application displays on the screen to generate + streams. + ---------------------------------------------------------------- + FaI1 The browser MUST be able to use several STUN + and TURN servers + ---------------------------------------------------------------- + FaI2 There browser MUST support that STUN and TURN + servers to use are supplied by other entities than + the service provided (i.e. the network provider) + ---------------------------------------------------------------- 5.3. API requirements REQ-ID DESCRIPTION ---------------------------------------------------------------- A1 The Web API MUST provide means for the application to ask the browser for permission to use cameras and microphones as input devices. ---------------------------------------------------------------- A2 The Web API MUST provide means for the web @@ -616,70 +758,89 @@ A6 The Web API MUST provide means for the web application to modify the media format for streams sent to a peer after a media stream has been established. ---------------------------------------------------------------- A7 The Web API MUST provide means for informing the web application of whether the establishment of a stream with a peer was successful or not. ---------------------------------------------------------------- - A8 Removed. - ---------------------------------------------------------------- - A9 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 component(s). When a stream is sent to a peer mute status must be preserved in the stream received by the peer. ---------------------------------------------------------------- - A10 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 to a peer. ---------------------------------------------------------------- - A11 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 of a stream received from a peer. ---------------------------------------------------------------- - A12 The Web API MUST provide means for + A11 The Web API MUST provide means for informing the web application when a stream from a peer is no longer received. ---------------------------------------------------------------- - A13 The Web API MUST provide means for + A12 The Web API MUST provide means for informing the web application when high loss rates occur. ---------------------------------------------------------------- + A13 The Web API MUST provide means for the web + application to apply spatialization effects to + audio streams. + ---------------------------------------------------------------- A14 The Web API MUST provide means for the web - application to control panning, mixing and - other processing for streams. + application to detect the level in audio + streams. ---------------------------------------------------------------- - A15 For each stream generated, the Web API MUST provide + A15 The Web API MUST provide means for the web + application to adjust the level in audio + streams. + ---------------------------------------------------------------- + A16 The Web API MUST provide means for the web + application to mix audio streams. + ---------------------------------------------------------------- + A17 For each stream generated, the Web API MUST provide an identifier that is accessible by the application. The identifier MUST be accessible also for a peer receiving that stream and MUST be unique relative to all other stream identifiers in use by either party. ---------------------------------------------------------------- - A16 In addition to the streams listed elsewhere, + A18 In addition to the streams listed elsewhere, the Web API MUST provide a mechanism for sending and receiving isolated discrete chunks of data. ---------------------------------------------------------------- - A17 The Web API MUST provide means for the web + A19 The Web API MUST provide means for the web application indicate the type of audio signal (speech, audio)for audio stream(s)/stream component(s). ---------------------------------------------------------------- - A18 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 of media he's willing to accept incoming streams for when setting up a connection (audio, video, other). The types of media he's willing to accept can be a subset of the types of media the browser is able to accept. ---------------------------------------------------------------- + A21 The Web API MUST provide means for the + application to ask the browser for permission + to the screen, a certain area on the screen + or what a certain application displays on the + screen as input to streams. + ---------------------------------------------------------------- + AaI1 The Web API MUST provide means for the + application to specify several STUN and/or + TURN servers to use. + ---------------------------------------------------------------- 6. IANA Considerations TBD 7. Security Considerations 7.1. Introduction A malicious web application might use the browser to perform Denial @@ -696,20 +858,32 @@ consent to use device resources such as camera and microphone. The browser is expected to provide mechanisms for informing the user that device resources such as camera and microphone are in use ("hot"). The browser is expected to provide mechanisms for users to revise and even completely revoke consent to use device resources such as camera and microphone. + 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 + application displays on the screen as source for streams. + + The browser is expected to provide mechanisms for informing the user + that the screen, part thereof or an application is serving as a + stream source ("hot"). + + The browser is expected to provide mechanisms for users to revise and + even completely revoke consent to use the screen, part thereof or an + application is serving as a stream source. + The browser is expected to provide mechanisms in order to assure that streams are the ones the recipient intended to receive. The browser needs to ensure that media is not sent, and that received media is not rendered, until the associated stream establishment and handshake procedures with the remote peer have been successfully finished. The browser needs to ensure that the stream negotiation procedures are not seen as Denial Of Service (DOS) by other entities. @@ -723,46 +897,39 @@ Several additional use-cases have been discussed. At this point these use-cases are not included as requirement deriving use-cases for different reasons (lack of documentation, overlap with existing use-cases, lack of consensus). For completeness these additional use-cases are listed below: 1. Use-cases regarding different situations when being invited to a "session", e.g. browser open, browser open but another tab active, browser open but active in session, browser closed, .... (Matthew Kaufman); discussed at webrtc meeting - 2. Different TURN provider scenarios (Cullen Jennings); discussed - at the webrtc meeting. Proposed text in http://lists.w3.org/ - Archives/Public/public-webrtc/2011Aug/0133.html - 3. E911 (Paul Beaumont) http://www.ietf.org/mail-archive/web/ - rtcweb/current/msg00525.html, followed up by Stephan Wenger - 4. Local Recording and Remote recording (John): Discussed a _lot_ - on the mail lists (rtcweb as well as public-webrtc) lAugust and - September 2011. Concrete proposal: http://www.ietf.org/ - mail-archive/web/rtcweb/current/msg01006.html (remote) and http: - //www.ietf.org/mail-archive/web/rtcweb/current/msg00734.html + 2. E911 (Paul Beaumont) http://www.ietf.org/mail-archive/web/rtcweb/ + current/msg00525.html, followed up by Stephan Wenger + 3. Local Recording and Remote recording (John): Discussed a _lot_ on + the mail lists (rtcweb as well as public-webrtc) lAugust and + September 2011. Concrete proposal: + http://www.ietf.org/mail-archive/web/rtcweb/current/msg01006.html + (remote) and + http://www.ietf.org/mail-archive/web/rtcweb/current/msg00734.html (local) - 5. Emergency access for disabled (Bernard Aboba) http:// - www.ietf.org/mail-archive/web/rtcweb/current/msg00478.html - - 6. Clue use-cases (Roni Even) http://tools.ietf.org/html/ + 4. Emergency access for disabled (Bernard Aboba) + http://www.ietf.org/mail-archive/web/rtcweb/current/msg00478.html + 5. Clue use-cases (Roni Even) http://tools.ietf.org/html/ draft-ietf-clue-telepresence-use-cases-01 - 7. Rohan red cross (Cullen Jennings); http://www.ietf.org/ - mail-archive/web/rtcweb/current/msg00323.html - 8. Remote assistance (ala VNC or RDP) - User is helping another - user on their computer with either view-only or view-with- - control, either of just the browser of the the entire screen. ht - tp://www.ietf.org/mail-archive/web/rtcweb/current/msg00543.html - 9. Security camera/baby monitor usage http://www.ietf.org/ - mail-archive/web/rtcweb/current/msg00543.html - 10. Large multiparty session http://www.ietf.org/mail-archive/web/ - rtcweb/current/msg00530.html + 6. Rohan red cross (Cullen Jennings); + http://www.ietf.org/mail-archive/web/rtcweb/current/msg00323.html + 7. Security camera/baby monitor usage + http://www.ietf.org/mail-archive/web/rtcweb/current/msg00543.html + 8. Large multiparty session + http://www.ietf.org/mail-archive/web/rtcweb/current/msg00530.html 9. Acknowledgements Dan Burnett has reviewed and proposed a lot of things that enhances the document. Most of this has been incorporated in rev -05. Stephan Wenger has provided a lot of useful input and feedback, as well as editorial comments. Harald Alvestrand and Ted Hardie have provided comments and feedback @@ -771,20 +938,42 @@ Harald Alvestrand and Cullen Jennings have provided additional use- cases. Thank You to everyone in the RTCWEB community that have provided comments, feedback and improvement proposals on the draft content. 10. Change Log [RFC EDITOR NOTE: Please remove this section when publishing] + 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 ..."