draft-ietf-rtcweb-use-cases-and-requirements-07.txt   draft-ietf-rtcweb-use-cases-and-requirements-08.txt 
RTCWEB Working Group C. Holmberg RTCWEB Working Group C. Holmberg
Internet-Draft S. Hakansson Internet-Draft S. Hakansson
Intended status: Informational G. Eriksson Intended status: Informational G. Eriksson
Expires: October 4, 2012 Ericsson Expires: December 6, 2012 Ericsson
April 2, 2012 June 4, 2012
Web Real-Time Communication Use-cases and Requirements Web Real-Time Communication Use-cases and Requirements
draft-ietf-rtcweb-use-cases-and-requirements-07.txt draft-ietf-rtcweb-use-cases-and-requirements-08.txt
Abstract Abstract
This document describes web based real-time communication use-cases. This document describes web based real-time communication use-cases.
Based on the use-cases, the document also derives requirements Based on the use-cases, the document also derives requirements
related to the browser, and the API used by web applications to related to the browser, and the API used by web applications to
request and control media stream services provided by the browser. request and control media stream and data exchange services provided
by the browser.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 4, 2012. This Internet-Draft will expire on December 6, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 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. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Use-cases . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Use-cases . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4.1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 3 4.1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 4
4.2. Browser-to-browser use-cases . . . . . . . . . . . . . . . 4 4.2. Browser-to-browser use-cases . . . . . . . . . . . . . . . 5
4.2.1. Simple Video Communication Service . . . . . . . . . . 4 4.2.1. Simple Video Communication Service . . . . . . . . . . 5
4.2.2. Simple Video Communication Service, NAT/FW that 4.2.2. Simple Video Communication Service, NAT/FW that
blocks UDP . . . . . . . . . . . . . . . . . . . . . . 5 blocks UDP . . . . . . . . . . . . . . . . . . . . . . 6
4.2.3. Simple Video Communication Service, global service 4.2.3. Simple Video Communication Service, global service
provider . . . . . . . . . . . . . . . . . . . . . . . 5 provider . . . . . . . . . . . . . . . . . . . . . . . 6
4.2.4. Simple Video Communication Service, enterprise 4.2.4. Simple Video Communication Service, enterprise
aspects . . . . . . . . . . . . . . . . . . . . . . . 5 aspects . . . . . . . . . . . . . . . . . . . . . . . 7
4.2.5. Simple Video Communication Service, access change . . 6 4.2.5. Simple Video Communication Service, access change . . 7
4.2.6. Simple Video Communication Service, QoS . . . . . . . 7 4.2.6. Simple Video Communication Service, QoS . . . . . . . 8
4.2.7. Simple Video Communication Service with sharing . . . 7 4.2.7. Simple Video Communication Service with sharing . . . 8
4.2.8. Simple video communication service with 4.2.8. Simple Video Communication Service with file
inter-operator calling . . . . . . . . . . . . . . . . 7 exchange . . . . . . . . . . . . . . . . . . . . . . . 9
4.2.9. Hockey Game Viewer . . . . . . . . . . . . . . . . . . 8 4.2.9. Simple video communication service with
4.2.10. Multiparty video communication . . . . . . . . . . . . 9 inter-operator calling . . . . . . . . . . . . . . . . 9
4.2.11. Multiparty on-line game with voice communication . . . 10 4.2.10. Hockey Game Viewer . . . . . . . . . . . . . . . . . . 10
4.2.12. Distributed Music Band . . . . . . . . . . . . . . . . 10 4.2.11. Multiparty video communication . . . . . . . . . . . . 10
4.3. Browser - GW/Server use cases . . . . . . . . . . . . . . 11 4.2.12. Multiparty on-line game with voice communication . . . 11
4.3.1. Telephony terminal . . . . . . . . . . . . . . . . . . 11 4.2.13. Distributed Music Band . . . . . . . . . . . . . . . . 12
4.3.2. Fedex Call . . . . . . . . . . . . . . . . . . . . . . 11 4.3. Browser - GW/Server use cases . . . . . . . . . . . . . . 12
4.3.3. Video conferencing system with central server . . . . 12 4.3.1. Telephony terminal . . . . . . . . . . . . . . . . . . 12
5. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 13 4.3.2. Fedex Call . . . . . . . . . . . . . . . . . . . . . . 13
5.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 13 4.3.3. Video conferencing system with central server . . . . 13
5.2. Browser requirements . . . . . . . . . . . . . . . . . . . 13 5. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 15
5.3. API requirements . . . . . . . . . . . . . . . . . . . . . 16 5.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 15
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 5.2. Browser requirements . . . . . . . . . . . . . . . . . . . 15
7. Security Considerations . . . . . . . . . . . . . . . . . . . 18 5.3. API requirements . . . . . . . . . . . . . . . . . . . . . 18
7.1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 18 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20
7.2. Browser Considerations . . . . . . . . . . . . . . . . . . 18 7. Security Considerations . . . . . . . . . . . . . . . . . . . 20
7.3. Web Application Considerations . . . . . . . . . . . . . . 19 7.1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 21
8. Additional use-cases . . . . . . . . . . . . . . . . . . . . . 19 7.2. Browser Considerations . . . . . . . . . . . . . . . . . . 21
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 20 7.3. Web Application Considerations . . . . . . . . . . . . . . 22
10. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 20 8. Additional use-cases . . . . . . . . . . . . . . . . . . . . . 22
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 23 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 23
11.1. Normative References . . . . . . . . . . . . . . . . . . . 23 10. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 23
11.2. Informative References . . . . . . . . . . . . . . . . . . 23 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 23 11.1. Normative References . . . . . . . . . . . . . . . . . . . 26
11.2. Informative References . . . . . . . . . . . . . . . . . . 26
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 26
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.
Based on the use-cases, the document derives requirements related to Based on the use-cases, the document derives requirements related to
the browser and the API used by web applications in the browser. the browser and the API used by web applications in the browser.
The requirements related to the browser are named "Fn" and are The requirements related to the browser are named "Fn" and are
described in Section 5.2 described in Section 5.2
The requirements related to the API are named "An" and are described The requirements related to the API are named "An" and are described
in Section 5.3 in Section 5.3
The document focuses on requirements related to real-time media The document focuses on requirements related to real-time media
streams. Requirements related to privacy, signalling between the streams and data exchange. Requirements related to privacy,
browser and web server etc. are currently not considered. signalling between the browser and web server etc. are currently not
considered.
2. Conventions 2. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in BCP 14, RFC 2119 document are to be interpreted as described in BCP 14, RFC 2119
[RFC2119]. [RFC2119].
3. Definitions 3. Definitions
skipping to change at page 4, line 5 skipping to change at page 5, line 6
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 on wideband (10s of Mbits/sec) 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 narrowband (10s to 100s of Kbits/sec)
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 cone NAT o Clients can be on networks with any type (as described in RFC4787)
o Clients can be on networks with symmetric NAT of NAT.
4.2. Browser-to-browser use-cases 4.2. Browser-to-browser use-cases
4.2.1. Simple Video Communication Service 4.2.1. Simple Video Communication Service
4.2.1.1. Description 4.2.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
skipping to change at page 4, line 33 skipping to change at page 5, line 34
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 select to remove and re-insert the self-view as often as
desired. Each user can also change the sizes of his/her two video desired. Each user can also change the sizes of his/her two video
displays during the session. Each user can also pause sending of displays during the session. Each user can also pause sending of
media (audio, video, or both) and mute incoming media media (audio, video, or both) and mute incoming media
It is essential that the communication cannot be eavesdropped. It is essential that the communication cannot be eavesdropped.
The users are provided wiht means that allow them to (through a
separate, trusted communication channel) verify that the media
origins from the other user and has not been manipulated.
The user's browsers will reject all incoming media that has been
created, injected or in any way modified by any entity not trusted by
the service provider.
The application gives the users the opportunity to stop it from
exposing the 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 of different makes, The two users may be using communication devices of different makes,
with different operating systems and browsers from different vendors. with different operating systems and browsers from different vendors.
One user has an unreliable Internet connection. It sometimes loses One user has an unreliable Internet connection. It sometimes loses
packets, and sometimes goes down completely. packets, and sometimes goes down completely.
One user is located behind a Network Address Translator (NAT). One user is located behind a Network Address Translator (NAT).
4.2.1.2. Derived Requirements 4.2.1.2. Derived Requirements
F1, F2, F3, F4, F5, F6, F8, F9, F10, F20, F25, F28 F1, F2, F3, F4, F5, F6, F8, F9, F10, F20, F25, F28, F35, F36
A1, A2, A3, A4, A5, A6, A7, A8, A9, A10, A11, A12 A1, A2, A3, A4, A5, A6, A7, A8, A9, A10, A11, A12, A25
4.2.2. Simple Video Communication Service, NAT/FW that blocks UDP 4.2.2. Simple Video Communication Service, NAT/FW that blocks UDP
4.2.2.1. Description 4.2.2.1. Description
This use-case is almost identical to the Simple Video Communication 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 Service use-case (Section 4.2.1). The difference is that one of the
users is behind a NAT that blocks UDP traffic. users is behind a NAT that blocks UDP traffic.
4.2.2.2. Derived Requirements 4.2.2.2. Derived Requirements
skipping to change at page 7, line 40 skipping to change at page 9, line 4
Video Communication Service use-case (Section 4.2.1). Video Communication Service use-case (Section 4.2.1).
But in addition to this, one of the users can share what is being 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 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 share the entire screen, part of the screen (part selected by the
user) or what a selected applicaton displays with the peer. user) or what a selected applicaton displays with the peer.
4.2.7.2. Derived Requirements 4.2.7.2. Derived Requirements
F1, F2, F3, F4, F5, F6, F8, F9, F10, F20, F25, F28, F30 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 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. Simple Video Communication Service with file exchange
4.2.8.1. Description 4.2.8.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, the users can send and receive files stored
in the file system of the device used.
4.2.8.2. Derived Requirements
F1, F2, F3, F4, F5, F6, F8, F9, F10, F20, F25, F28, F30, F33
A1, A2, A3, A4, A5, A6, A7, A8, A9, A10, A11, A12, A21, A24
4.2.9. Simple video communication service with inter-operator calling
4.2.9.1. Description
Two users have logged into two different web applications, provided Two users have logged into two different web applications, provided
by different service providers. by different service providers.
The service providers are interconnected by some means, but exchange The service providers are interconnected by some means, but exchange
no more information about the users than what can be carried using no more information about the users than what can be carried using
SIP. SIP.
NOTE: More profiling of what this means may be needed. NOTE: More profiling of what this means may be needed.
For each user Alice who has authorized another user Bob to receive For each user Alice who has authorized another user Bob to receive
login status information, Alice's service publishes Alice's login login status information, Alice's service publishes Alice's login
status information to Bob. How this authorization is defined and status information to Bob. How this authorization is defined and
established is out of scope. established is out of scope.
The same functionality as in the the Simple Video Communication The same functionality as in the the Simple Video Communication
Service use-case (Section 4.2.1) is available. Service use-case (Section 4.2.1) is available.
The same issues with connectivity apply. The same issues with connectivity apply.
4.2.8.2. Derived requirements 4.2.9.2. Derived requirements
F1, F2, F3, F4, F5, F6, F8, F9, F10, F20, F25, F27, F28 F1, F2, F3, F4, F5, F6, F8, F9, F10, F20, F25, F27, F28
A1, A2, A3, A4, A5, A6, A7, A8, A9, A10, A11, A12, A20 A1, A2, A3, A4, A5, A6, A7, A8, A9, A10, A11, A12, A20
4.2.9. Hockey Game Viewer 4.2.10. Hockey Game Viewer
4.2.9.1. Description 4.2.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
skipping to change at page 8, line 52 skipping to change at page 10, line 34
When the game is on-going, the talent scout activates the use of the When the game is on-going, 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. and the desktop camera. As the most important stream in this phase
is the video showing the game, the application used in the talent
scout's mobile sets higher priority for that stream.
It is essential that the communication cannot be eavesdropped. It is essential that the communication cannot be eavesdropped.
4.2.9.2. Derived Requirements 4.2.10.2. Derived Requirements
F1, F2, F3, F4, F5, F6, F8, F9, F10, F17, F20 F1, F2, F3, F4, F5, F6, F8, F9, F10, F17, F20, F34
A1, A2, A3, A4, A5, A7, A8, A9, A10, A11, A12, A17 A1, A2, A3, A4, A5, A7, A8, A9, A10, A11, A12, A17, A23
4.2.10. Multiparty video communication 4.2.11. Multiparty video communication
4.2.10.1. Description 4.2.11.1. Description
In this use-case is the Simple Video Communication Service use-case In this use-case is the Simple Video Communication Service use-case
(Section 4.2.1) is extended by allowing multiparty sessions. No (Section 4.2.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 intelligibility, the web application pans the In order to enhance intelligibility, the web application pans the
audio from different participants differently when rendering the audio from different participants differently when rendering the
skipping to change at page 9, line 46 skipping to change at page 11, line 30
It is essential that the communication cannot be eavesdropped. It is essential that the communication cannot be eavesdropped.
Note: What this use-case adds in terms of requirements is Note: What this use-case adds in terms of requirements is
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 recevied streams and be able to spatialize, level adjust and from all recevied streams and be able to spatialize, level adjust and
mix the audio from all received streams locally in the browser. It mix the audio from all received streams locally in the browser. It
also adds the capability to measure the audio level/activity. also adds the capability to measure the audio level/activity.
4.2.10.2. Derived Requirements 4.2.11.2. Derived Requirements
F1, F2, F3, F4, F5, F6, F8, F9, F10, F11, F12, F13, F14, F15, F16, F1, F2, F3, F4, F5, F6, F8, F9, F10, F11, F12, F13, F14, F15, F16,
F17, F20, F25 F17, F20, F25
A1, A2, A3, A4, A5, A6, A7, A8, A9, A10, A11, A12, A13, A14, A15, A1, A2, A3, A4, A5, A6, A7, A8, A9, A10, A11, A12, A13, A14, A15,
A16, A17 A16, A17
4.2.11. Multiparty on-line game with voice communication 4.2.12. Multiparty on-line game with voice communication
4.2.11.1. Description 4.2.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 on-line 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. Quick updates of the game state is required, and have higher priority
than the voice.
It is essential that the communication cannot be eavesdropped. It is essential that the communication cannot be eavesdropped.
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.
4.2.11.2. Derived Requirements 4.2.12.2. Derived Requirements
F1, F2, F3, F4, F5, F6, F8, F9, F11, F12, F13, F14, F15, F16, F18, F1, F2, F3, F4, F5, F6, F8, F9, F11, F12, F13, F14, F15, F16, F18,
F20, F23 F20, F23, F34
A1, A2, A3, A4, A5, A7, A8, 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 A17, A18, A23
4.2.12. Distributed Music Band 4.2.13. Distributed Music Band
4.2.12.1. Description 4.2.13.1. Description
In this use-case, a music band is playing music while the members are In this use-case, a music band is playing music while the members are
at different physical locations. No central server is used, instead at different physical locations. No central server is used, instead
all streams are set up in a mesh fashion. all streams are set up in a mesh fashion.
Discussion: This use-case was briefly discussed at the Quebec webrtc Discussion: This use-case was briefly discussed at the Quebec webrtc
meeting and it got support. So far the only concrete requirement meeting and it got support. So far the only concrete requirement
(A17) derived is that the application must be able to ask the browser (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, to treat the audio signal as audio (in contrast to speech). However,
the use case should be further analysed to determine other the use case should be further analysed to determine other
requirements (could be e.g. on delay mic->speaker, level control of requirements (could be e.g. on delay mic->speaker, level control of
audio signals, etc.). audio signals, etc.).
4.2.12.2. Derived Requirements 4.2.13.2. Derived Requirements
F1, F2, F3, F4, F5, F6, F8, F9, F11, F12, F13, F14, F15, F16 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, A1, A2, A3, A4, A5, A7, A8, A9, A10, A11, A12, A13, A14, A15, A16,
A19 A19
4.3. Browser - GW/Server use cases 4.3. Browser - GW/Server use cases
4.3.1. Telephony terminal 4.3.1. Telephony terminal
skipping to change at page 13, line 38 skipping to change at page 15, line 25
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.
5.2. Browser requirements 5.2. Browser 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 to a F2 The browser MUST be able to send streams
peer in the presence of NATs. to a peer in the presence of NATs.
---------------------------------------------------------------- ----------------------------------------------------------------
F3 Transmitted streams MUST be rate controlled. F3 Transmitted streams MUST be rate controlled.
---------------------------------------------------------------- ----------------------------------------------------------------
F4 The browser MUST be able to receive, process and F4 The browser MUST be able to receive, process and
render streams from peers. render streams from peers.
---------------------------------------------------------------- ----------------------------------------------------------------
F5 The browser MUST be able to render good quality F5 The browser MUST be able to render good quality
audio and video even in the presence of reasonable audio and video even in the presence of reasonable
levels of jitter and packet losses. levels of jitter and packet losses.
skipping to change at page 15, line 9 skipping to change at page 16, line 41
audio streams. audio streams.
---------------------------------------------------------------- ----------------------------------------------------------------
F18 The browser MUST be able to process and mix F18 The browser MUST be able to process and mix
sound objects (media that is retrieved from another sound objects (media that is retrieved from another
source than the established media stream(s) with the source than the established media stream(s) with the
peer(s) with audio streams. peer(s) with audio streams.
---------------------------------------------------------------- ----------------------------------------------------------------
F19 Streams MUST be able to pass through restrictive F19 Streams MUST be able to pass through restrictive
firewalls. firewalls.
---------------------------------------------------------------- ----------------------------------------------------------------
F20 It MUST be possible to protect streams from F20 It MUST be possible to protect streams
eavesdropping. from eavesdropping.
---------------------------------------------------------------- ----------------------------------------------------------------
F21 The browser MUST support an audio media format F21 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.
QUESTION: G.711? QUESTION: G.711?
---------------------------------------------------------------- ----------------------------------------------------------------
F22 There should be a way to navigate F22 There should be a way to navigate
the IVR a DTMF based IVR
---------------------------------------------------------------- ----------------------------------------------------------------
F23 The browser must be able to send short F23 The browser must be able to send short
latency datagram traffic to a peer browser latency unreliable datagram traffic to a
peer browser.
Requirements F2, F3, F4 (except the render
part), F11, F12, F19, F20 apply to datagram
traffic (exchange "stream" for "datagram")
---------------------------------------------------------------- ----------------------------------------------------------------
F24 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 capabilities (supplied by network nodes) to
appropriately. prioritize voice, video and data appropriately.
---------------------------------------------------------------- ----------------------------------------------------------------
F25 The browser SHOULD use encoding of streams F25 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
---------------------------------------------------------------- ----------------------------------------------------------------
F26 It MUST be possible to move from one network F26 It MUST be possible to move from one network
interface to another one interface to another one
---------------------------------------------------------------- ----------------------------------------------------------------
F27 The browser MUST be able to initiate and accept a F27 The browser MUST be able to initiate and accept a
skipping to change at page 16, line 10 skipping to change at page 17, line 47
application displays on the screen to generate application displays on the screen to generate
streams. streams.
---------------------------------------------------------------- ----------------------------------------------------------------
F31 The browser MUST be able to use several STUN F31 The browser MUST be able to use several STUN
and TURN servers and TURN servers
---------------------------------------------------------------- ----------------------------------------------------------------
F32 There browser MUST support that STUN and TURN F32 There browser MUST support that STUN and TURN
servers to use are supplied by other entities than servers to use are supplied by other entities than
the service provided (i.e. the network provider) the service provided (i.e. the network provider)
---------------------------------------------------------------- ----------------------------------------------------------------
F33 The browser must be able to send reliable
data traffic to a peer browser.
Requirements F2, F3, F4 (except the render
part), F11, F12, F19, F20 apply to data
traffic (exchange "stream" for "data")
----------------------------------------------------------------
F34 The browser MUST support priortization of
streams and data.
----------------------------------------------------------------
F35 The browser MUST enable verification, given the right
circumstances and by use of other trusted communication,
of that streams and data recevived have not been
manipulated by any party
----------------------------------------------------------------
F36 The browser MUST reject incoming media and data, either
modified, created or injected, by any entity not trusted
by the site.
----------------------------------------------------------------
5.3. API requirements 5.3. API requirements
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.
---------------------------------------------------------------- ----------------------------------------------------------------
A2 The Web API MUST provide means for the web A2 The Web API MUST provide means for the web
skipping to change at page 17, line 45 skipping to change at page 20, line 4
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 For each stream generated, the Web API MUST provide A17 For each stream generated, the Web API MUST provide
an identifier that is accessible by the application. an identifier that is accessible by the application.
The identifier MUST be accessible also for a peer The identifier MUST be accessible also for a peer
receiving that stream and MUST be unique relative receiving that stream and MUST be unique relative
to all other stream identifiers in use by either party. to all other stream identifiers in use by either party.
---------------------------------------------------------------- ----------------------------------------------------------------
A18 In addition to the streams listed elsewhere, A18 The Web API MUST provide a mechanism for sending
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 indicate the type of audio signal application indicate the type of audio signal
(speech, audio)for audio stream(s)/stream component(s). (speech, audio)for audio stream(s)/stream 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 he's willing to accept incoming streams of media he's willing to accept incoming streams
for when setting up a connection (audio, video, for when setting up a connection (audio, video,
skipping to change at page 18, line 24 skipping to change at page 20, line 31
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 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
application to specify the priority to
apply for outgoing streams and data.
----------------------------------------------------------------
A24 The Web API MUST provide a mechanism for sending
and receiving files.
----------------------------------------------------------------
A25 It must be possible for the application to refrain from
exposing the IP address
----------------------------------------------------------------
6. IANA Considerations 6. IANA Considerations
TBD TBD
7. Security Considerations 7. Security Considerations
7.1. Introduction 7.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, Also, a malicious web application might silently establish outgoing,
and accept incoming, streams on an already established connection. 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.
skipping to change at page 19, line 24 skipping to change at page 21, line 42
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 is expected to provide mechanisms for users to revise and The browser is expected to provide mechanisms for users to revise and
even completely revoke consent to use the screen, part thereof or an even completely revoke consent to use the screen, part thereof or an
application is serving as a stream source. application is serving 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
to verify that the streams received have not be manipulated (F35).
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 Denial Of Service (DOS) by other entities.
7.3. Web Application Considerations 7.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.
8. Additional use-cases 8. Additional use-cases
Several additional use-cases have been discussed. At this point Several additional use-cases have been discussed. At this point
these use-cases are not included as requirement deriving use-cases these use-cases are not included as requirement deriving use-cases
for different reasons (lack of documentation, overlap with existing for different reasons (lack of documentation, overlap with existing
use-cases, lack of consensus). For completeness these additional use-cases, lack of consensus). For completeness these additional
use-cases are listed below: use-cases are listed below:
1. Use-cases regarding different situations when being invited to a 1. Use-cases regarding different situations when being invited to a
"session", e.g. browser open, browser open but another tab "session", e.g. browser open, browser open but another tab
active, browser open but active in session, browser closed, .... active, browser open but active in session, browser closed, ....
(Matthew Kaufman); discussed at webrtc meeting (Matthew Kaufman); discussed at webrtc meeting
2. E911 (Paul Beaumont) http://www.ietf.org/mail-archive/web/rtcweb/ 2. E911 (Paul Beaumont) http://www.ietf.org/mail-archive/web/
current/msg00525.html, followed up by Stephan Wenger rtcweb/current/msg00525.html, followed up by Stephan Wenger
3. Local Recording and Remote recording (John): Discussed a _lot_
3. Local Recording and Remote recording (John): Discussed a _lot_ on on the mail lists (rtcweb as well as public-webrtc) lAugust and
the mail lists (rtcweb as well as public-webrtc) lAugust and September 2011. Concrete proposal: http://www.ietf.org/
September 2011. Concrete proposal: mail-archive/web/rtcweb/current/msg01006.html (remote) and http:
http://www.ietf.org/mail-archive/web/rtcweb/current/msg01006.html //www.ietf.org/mail-archive/web/rtcweb/current/msg00734.html
(remote) and (local)
http://www.ietf.org/mail-archive/web/rtcweb/current/msg00734.html 4. Emergency access for disabled (Bernard Aboba) http://
(local) www.ietf.org/mail-archive/web/rtcweb/current/msg00478.html
4. Emergency access for disabled (Bernard Aboba) 5. Clue use-cases (Roni Even) http://tools.ietf.org/html/
http://www.ietf.org/mail-archive/web/rtcweb/current/msg00478.html draft-ietf-clue-telepresence-use-cases-01
5. Clue use-cases (Roni Even) http://tools.ietf.org/html/ 6. Rohan red cross (Cullen Jennings); http://www.ietf.org/
draft-ietf-clue-telepresence-use-cases-01 mail-archive/web/rtcweb/current/msg00323.html
6. Rohan red cross (Cullen Jennings); 7. Security camera/baby monitor usage http://www.ietf.org/
http://www.ietf.org/mail-archive/web/rtcweb/current/msg00323.html mail-archive/web/rtcweb/current/msg00543.html
7. Security camera/baby monitor usage 8. Large multiparty session http://www.ietf.org/mail-archive/web/
http://www.ietf.org/mail-archive/web/rtcweb/current/msg00543.html rtcweb/current/msg00530.html
8. Large multiparty session 9. Call center http://www.ietf.org/mail-archive/web/rtcweb/current/
http://www.ietf.org/mail-archive/web/rtcweb/current/msg00530.html msg04203.html
10. Enterprise policies http://www.ietf.org/mail-archive/web/rtcweb/
current/msg04271.html
11. Low-complex multiparty central node http://www.ietf.org/
mail-archive/web/rtcweb/current/msg04430.html
12. Multiparty central node that is not allowed to decipher http://
www.ietf.org/mail-archive/web/rtcweb/current/msg04457.html
13. Enable company coop without being able to decipher http://
www.ietf.org/mail-archive/web/rtcweb/current/msg04464.html
9. Acknowledgements 9. Acknowledgements
Dan Burnett has reviewed and proposed a lot of things that enhances Dan Burnett has reviewed and proposed a lot of things that enhances
the document. Most of this has been incorporated in rev -05. the document. Most of this has been incorporated in rev -05.
Stephan Wenger has provided a lot of useful input and feedback, as Stephan Wenger has provided a lot of useful input and feedback, as
well as editorial comments. well as editorial comments.
Harald Alvestrand and Ted Hardie have provided comments and feedback Harald Alvestrand and Ted Hardie have provided comments and feedback
skipping to change at page 20, line 44 skipping to change at page 23, line 26
Harald Alvestrand and Cullen Jennings have provided additional use- Harald Alvestrand and Cullen Jennings have provided additional use-
cases. cases.
Thank You to everyone in the RTCWEB community that have provided Thank You to everyone in the RTCWEB community that have provided
comments, feedback and improvement proposals on the draft content. comments, feedback and improvement proposals on the draft content.
10. Change Log 10. Change Log
[RFC EDITOR NOTE: Please remove this section when publishing] [RFC EDITOR NOTE: Please remove this section when publishing]
Changes from draft-ietf-rtcweb-use-cases-and-requirements-06 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 verifyication 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, prtoection 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 -> o Renaming of requirements (FaI1 -> F31), (FaI2 -> F32) and (AaI1 ->
A22) A22)
Changes from draft-ietf-rtcweb-use-cases-and-requirements-05 Changes from draft-ietf-rtcweb-use-cases-and-requirements-05
o Added use-case "global service provider", derived reqs associated o Added use-case "global service provider", derived reqs associated
with several STUN/TURN servers with several STUN/TURN servers
o Added use-case "enterprise aspects", derived req associated with o Added use-case "enterprise aspects", derived req associated with
enabling the network provider to supply STUN and TURN servers enabling the network provider to supply STUN and TURN servers
o The requirements from the above are ICE specific and labeled o The requirements from the above are ICE specific and labeled
accordingly accordingly
o Separated the requirements phrased like "processing such as pan, o Separated the requirements phrased like "processing such as pan,
mix and render" for audio to be specific reqs on spatialization, mix and render" for audio to be specific reqs on spatialization,
level measurement, level adjustment and mixing (discussed on the level measurement, level adjustment and mixing (discussed on the
lists in lists in
 End of changes. 50 change blocks. 
107 lines changed or deleted 208 lines changed or added

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