draft-ietf-rtcweb-use-cases-and-requirements-08.txt   draft-ietf-rtcweb-use-cases-and-requirements-09.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: December 6, 2012 Ericsson Expires: December 29, 2012 Ericsson
June 4, 2012 June 27, 2012
Web Real-Time Communication Use-cases and Requirements Web Real-Time Communication Use-cases and Requirements
draft-ietf-rtcweb-use-cases-and-requirements-08.txt draft-ietf-rtcweb-use-cases-and-requirements-09.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 and data exchange services provided request and control media stream and data exchange services provided
by the browser. by the browser.
Status of this Memo Status of this Memo
skipping to change at page 1, line 35 skipping to change at page 1, line 35
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 6, 2012. This Internet-Draft will expire on December 29, 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
skipping to change at page 2, line 17 skipping to change at page 2, line 17
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Use-cases . . . . . . . . . . . . . . . . . . . . . . . . . . 4 4. Use-cases . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4.1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 4 4.1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 4
4.2. Browser-to-browser use-cases . . . . . . . . . . . . . . . 5 4.2. Browser-to-browser use-cases . . . . . . . . . . . . . . . 5
4.2.1. Simple Video Communication Service . . . . . . . . . . 5 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 . . . . . . . . . . . . . . . . . . . . . . 6 blocks UDP . . . . . . . . . . . . . . . . . . . . . . 6
4.2.3. Simple Video Communication Service, global service 4.2.3. Simple Video Communication Service, FW that only
allows http . . . . . . . . . . . . . . . . . . . . . 6
4.2.4. Simple Video Communication Service, global service
provider . . . . . . . . . . . . . . . . . . . . . . . 6 provider . . . . . . . . . . . . . . . . . . . . . . . 6
4.2.4. Simple Video Communication Service, enterprise 4.2.5. Simple Video Communication Service, enterprise
aspects . . . . . . . . . . . . . . . . . . . . . . . 7 aspects . . . . . . . . . . . . . . . . . . . . . . . 7
4.2.5. Simple Video Communication Service, access change . . 7 4.2.6. Simple Video Communication Service, access change . . 8
4.2.6. Simple Video Communication Service, QoS . . . . . . . 8 4.2.7. Simple Video Communication Service, QoS . . . . . . . 8
4.2.7. Simple Video Communication Service with sharing . . . 8 4.2.8. Simple Video Communication Service with sharing . . . 9
4.2.8. Simple Video Communication Service with file 4.2.9. Simple Video Communication Service with file
exchange . . . . . . . . . . . . . . . . . . . . . . . 9 exchange . . . . . . . . . . . . . . . . . . . . . . . 9
4.2.9. Simple video communication service with 4.2.10. Simple video communication service with
inter-operator calling . . . . . . . . . . . . . . . . 9 inter-operator calling . . . . . . . . . . . . . . . . 9
4.2.10. Hockey Game Viewer . . . . . . . . . . . . . . . . . . 10 4.2.11. Hockey Game Viewer . . . . . . . . . . . . . . . . . . 10
4.2.11. Multiparty video communication . . . . . . . . . . . . 10 4.2.12. Multiparty video communication . . . . . . . . . . . . 11
4.2.12. Multiparty on-line game with voice communication . . . 11 4.2.13. Multiparty on-line game with voice communication . . . 12
4.2.13. Distributed Music Band . . . . . . . . . . . . . . . . 12 4.2.14. Distributed Music Band . . . . . . . . . . . . . . . . 12
4.3. Browser - GW/Server use cases . . . . . . . . . . . . . . 12 4.3. Browser - GW/Server use cases . . . . . . . . . . . . . . 13
4.3.1. Telephony terminal . . . . . . . . . . . . . . . . . . 12 4.3.1. Telephony terminal . . . . . . . . . . . . . . . . . . 13
4.3.2. Fedex Call . . . . . . . . . . . . . . . . . . . . . . 13 4.3.2. Fedex Call . . . . . . . . . . . . . . . . . . . . . . 14
4.3.3. Video conferencing system with central server . . . . 13 4.3.3. Video conferencing system with central server . . . . 14
5. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 15 5. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 15
5.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 15 5.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 15
5.2. Browser requirements . . . . . . . . . . . . . . . . . . . 15 5.2. Browser requirements . . . . . . . . . . . . . . . . . . . 15
5.3. API requirements . . . . . . . . . . . . . . . . . . . . . 18 5.3. API requirements . . . . . . . . . . . . . . . . . . . . . 19
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21
7. Security Considerations . . . . . . . . . . . . . . . . . . . 20 7. Security Considerations . . . . . . . . . . . . . . . . . . . 21
7.1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 21 7.1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 21
7.2. Browser Considerations . . . . . . . . . . . . . . . . . . 21 7.2. Browser Considerations . . . . . . . . . . . . . . . . . . 22
7.3. Web Application Considerations . . . . . . . . . . . . . . 22 7.3. Web Application Considerations . . . . . . . . . . . . . . 22
8. Additional use-cases . . . . . . . . . . . . . . . . . . . . . 22 8. Additional use-cases . . . . . . . . . . . . . . . . . . . . . 22
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 23 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 23
10. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 23 10. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 24
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 26 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 27
11.1. Normative References . . . . . . . . . . . . . . . . . . . 26 11.1. Normative References . . . . . . . . . . . . . . . . . . . 27
11.2. Informative References . . . . . . . . . . . . . . . . . . 26 11.2. Informative References . . . . . . . . . . . . . . . . . . 27
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 27
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
skipping to change at page 5, line 32 skipping to change at page 5, line 32
reject the session. 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 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 wiretapped
[RFC2804].
The users are provided wiht means that allow them to (through a The users are provided wiht means that allow them to (through a
separate, trusted communication channel) verify that the media separate, trusted communication channel) verify that the media
origins from the other user and has not been manipulated. origins from the other user and has not been manipulated.
The user's browsers will reject all incoming media that has been 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 created, injected or in any way modified by any entity not trusted by
the service provider. the service provider.
The application gives the users the opportunity to stop it from The application gives the users the opportunity to stop it from
skipping to change at page 6, line 7 skipping to change at page 6, line 8
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).
The web service monitors the quality of the service (focus on quality
of audio and video) the end-users experience.
4.2.1.2. Derived Requirements 4.2.1.2. Derived Requirements
F1, F2, F3, F4, F5, F6, F8, F9, F10, F20, F25, F28, F35, F36 F1, F2, F3, F4, F5, F6, F8, F9, F10, F20, F25, F28, F35, F36, F38
A1, A2, A3, A4, A5, A6, A7, A8, A9, A10, A11, A12, A25 A1, A2, A3, A4, A5, A6, A7, A8, A9, A10, A11, A12, A25, A26
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
F1, F2, F3, F4, F5, F6, F8, F9, F10, F20, F25, F28, F29 F1, F2, F3, F4, F5, F6, F8, F9, F10, F20, F25, F28, F29
A1, A2, A3, A4, A5, A6, A7, A8, A9, A10, A11, A12 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, FW that only allows http
4.2.3.1. Description 4.2.3.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
users is behind a FW that only allows http traffic.
Note: What about WS? Could it be a viable back-off mechanism?
4.2.3.2. Derived Requirements
F1, F2, F3, F4, F5, F6, F8, F9, F10, F20, F25, F28, F37
A1, A2, A3, A4, A5, A6, A7, A8, A9, A10, A11, A12
4.2.4. Simple Video Communication Service, global service provider
4.2.4.1. Description
This use-case is almost identical to the Simple Video Communication
Service use-case (Section 4.2.1). Service use-case (Section 4.2.1).
What is added is that the service provider is operating over large What is added is that the service provider is operating over large
geographical areas (or even globally). geographical areas (or even globally).
Assuming that ICE will be used, this means that the service provider 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 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 app) to the browser; selection of which one(s) to use is part of
the ICE processing. Other reasons for wanting to provide several the ICE processing. Other reasons for wanting to provide several
STUN and TURN servers include support for IPv4 and IPv6, load STUN and TURN servers include support for IPv4 and IPv6, load
balancing and redundancy. balancing and redundancy.
4.2.3.2. Derived Requirements 4.2.4.2. Derived Requirements
F1, F2, F3, F4, F5, F6, F8, F9, F10, F20, F25, F28, F31 F1, F2, F3, F4, F5, F6, F8, F9, F10, F20, F25, F28, F31
A1, A2, A3, A4, A5, A6, A7, A8, A9, A10, A11, A12, A22 A1, A2, A3, A4, A5, A6, A7, A8, A9, A10, A11, A12, A22
4.2.4. Simple Video Communication Service, enterprise aspects 4.2.5. Simple Video Communication Service, enterprise aspects
4.2.4.1. Description 4.2.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 4.2.1). use-case (Section 4.2.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 RTCWEB based web application for
communication desires to audit all RTCWEB based application session communication desires to audit all RTCWEB based application session
used from inside the company towards any external peer. To be able used from inside the company towards any external peer. To be able
skipping to change at page 7, line 36 skipping to change at page 8, line 8
TURN server, thus they deploy a STUN server allowing the RTCWEB TURN server, thus they deploy a STUN server allowing the RTCWEB
client to determine its server reflexive address on the internal client to determine its server reflexive address on the internal
side. Thus enabling cases where peers are both on the internal side side. Thus enabling cases where peers are both on the internal side
to connect without the traffic leaving the internal network. It must to connect without the traffic leaving the internal network. It must
be possibele to configure the browsers used in the enterprise with be possibele 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 autoconfiguration methods. The RTCWEB functionality will achieve by autoconfiguration methods. The RTCWEB 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.
4.2.4.2. Derived Requirements 4.2.5.2. Derived Requirements
F1, F2, F3, F4, F5, F6, F8, F9, F10, F20, F25, F28, F32 F1, F2, F3, F4, F5, F6, F8, F9, F10, F20, F25, F28, F32
A1, A2, A3, A4, A5, A6, A7, A8, A9, A10, A11, A12 A1, A2, A3, A4, A5, A6, A7, A8, A9, A10, A11, A12
4.2.5. Simple Video Communication Service, access change 4.2.6. Simple Video Communication Service, access change
4.2.5.1. Description 4.2.6.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 the user Service use-case (Section 4.2.1).The difference is that the user
changes network access during the session: changes network access during the session:
The communication device used by one of the users have several The communication device used by one of the users have several
network adapters (Ethernet, WiFi, Cellular). The communication network adapters (Ethernet, WiFi, Cellular). The communication
device is accessing the Internet using Ethernet, but the user has to device is accessing the Internet using Ethernet, but the user has to
start a trip during the session. The communication device start a trip during the session. The communication device
automatically changes to use WiFi when the Ethernet cable is removed automatically changes to use WiFi when the Ethernet cable is removed
and then moves to cellular access to the Internet when moving out of and then moves to cellular access to the Internet when moving out of
WiFi coverage. The session continues even though the access method WiFi coverage. The session continues even though the access method
changes. changes.
4.2.5.2. Derived Requirements 4.2.6.2. Derived Requirements
F1, F2, F3, F4, F5, F6, F8, F9, F10, F20, F25, F26, F28 F1, F2, F3, F4, F5, F6, F8, F9, F10, F20, F25, F26, F28
A1, A2, A3, A4, A5, A6, A7, A8, A9, A10, A11, A12 A1, A2, A3, A4, A5, A6, A7, A8, A9, A10, A11, A12
4.2.6. Simple Video Communication Service, QoS 4.2.7. Simple Video Communication Service, QoS
4.2.6.1. Description 4.2.7.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, access change use-case (Section 4.2.5). The use of Quality Service, access change use-case (Section 4.2.6). The use of Quality
of Service (QoS) capabilities is added: of Service (QoS) capabilities is 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 prioritization of traffic. common residential router that supports prioritization 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.
4.2.6.2. Derived Requirements 4.2.7.2. Derived Requirements
F1, F2, F3, F4, F5, F6, F8, F9, F10, F20, F24, F25, F26, F28 F1, F2, F3, F4, F5, F6, F8, F9, F10, F20, F24, F25, F26, F28
A1, A2, A3, A4, A5, A6, A7, A8, A9, A10, A11, A12 A1, A2, A3, A4, A5, A6, A7, A8, A9, A10, A11, A12
4.2.7. Simple Video Communication Service with sharing 4.2.8. Simple Video Communication Service with sharing
4.2.7.1. Description 4.2.8.1. Description
This use-case has the audio and video communication of the Simple This use-case has the audio and video communication of the Simple
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.8.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 file exchange 4.2.9. Simple Video Communication Service with file exchange
4.2.8.1. Description 4.2.9.1. Description
This use-case has the audio and video communication of the Simple This use-case has the audio and video communication of the Simple
Video Communication Service use-case (Section 4.2.1). Video Communication Service use-case (Section 4.2.1).
But in addition to this, the users can send and receive files stored But in addition to this, the users can send and receive files stored
in the file system of the device used. in the file system of the device used.
4.2.8.2. Derived Requirements 4.2.9.2. Derived Requirements
F1, F2, F3, F4, F5, F6, F8, F9, F10, F20, F25, F28, F30, F33 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 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.10. Simple video communication service with inter-operator calling
4.2.9.1. Description 4.2.10.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.9.2. Derived requirements 4.2.10.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.10. Hockey Game Viewer 4.2.11. Hockey Game Viewer
4.2.10.1. Description 4.2.11.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 10, line 38 skipping to change at page 11, line 10
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. As the most important stream in this phase
is the video showing the game, the application used in the talent is the video showing the game, the application used in the talent
scout's mobile sets higher priority for that stream. 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 wiretapped
[RFC2804].
4.2.10.2. Derived Requirements 4.2.11.2. Derived Requirements
F1, F2, F3, F4, F5, F6, F8, F9, F10, F17, F20, F34 F1, F2, F3, F4, F5, F6, F8, F9, F10, F17, F20, F34
A1, A2, A3, A4, A5, A7, A8, A9, A10, A11, A12, A17, A23 A1, A2, A3, A4, A5, A7, A8, A9, A10, A11, A12, A17, A23
4.2.11. Multiparty video communication 4.2.12. Multiparty video communication
4.2.11.1. Description 4.2.12.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 11, line 21 skipping to change at page 11, line 43
different participants are placed in the (virtual) room. In addition different participants are placed in the (virtual) room. In addition
the levels in the audio signals are adjusted before mixing. the levels in the audio signals are adjusted before mixing.
Another feature intended to enhance the use experience is that the Another feature intended to enhance the use experience is that the
video window that displays the video of the currently speaking peer video window that displays the video of the currently speaking peer
is highlighted. is highlighted.
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.
It is essential that the communication cannot be eavesdropped. It is essential that the communication cannot be wiretapped
[RFC2804].
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.11.2. Derived Requirements 4.2.12.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.12. Multiparty on-line game with voice communication 4.2.13. Multiparty on-line game with voice communication
4.2.12.1. Description 4.2.13.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, and have higher priority Quick updates of the game state is required, and have higher priority
than the voice. than the voice.
It is essential that the communication cannot be eavesdropped. It is essential that the communication cannot be wiretapped
[RFC2804].
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.12.2. Derived Requirements 4.2.13.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, F34 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, A23 A17, A18, A23
4.2.13. Distributed Music Band 4.2.14. Distributed Music Band
4.2.13.1. Description 4.2.14.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.13.2. Derived Requirements 4.2.14.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
4.3.1.1. Description 4.3.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.
It is essential that the communication cannot be eavesdropped. It is essential that the communication cannot be wiretapped
[RFC2804].
Note: With "place and receive calls in the same way as when using a Note: With "place and receive calls in the same way as when using a
normal mobile phone" it is meant that you can dial a number, and that normal mobile phone" it is meant that you can dial a number, and that
your mobile telephony operator has made available your phone contacts your mobile telephony operator has made available your phone contacts
on line, so they are available and can be clicked to call, and be 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 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. And for people receiving calls made from
the web browser the usual identity (i.e. the phone number of the the web browser the usual identity (i.e. the phone number of the
skipping to change at page 14, line 25 skipping to change at page 14, line 51
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 delay
from when a video stream is selected for display until the video can from when a video stream is selected for display until the video can
be displayed is short. be displayed is short.
The organization has an internal network set up with an aggressive The organization has an internal network set up with an aggressive
firewall handling access to the Internet. If users cannot physically firewall handling access to the Internet. If users cannot physically
access the internal network, they can establish a Virtual Private access the internal network, they can establish a Virtual Private
Network (VPN). Network (VPN).
It is essential that the communication cannot be eavesdropped. It is essential that the communication cannot be wiretapped
[RFC2804].
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 e-mail
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 F7, on encryption of media and on ability to traverse very switches F7, on encryption of media and on ability to traverse very
restrictive FWs. There exist several solutions that enable the restrictive FWs. There exist several solutions that enable the
skipping to change at page 15, line 25 skipping to change at page 15, line 49
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 F2 The browser MUST be able to send streams and
to a peer in the presence of NATs. data to a peer in the presence of NATs.
---------------------------------------------------------------- ----------------------------------------------------------------
F3 Transmitted streams MUST be rate controlled. F3 Transmitted streams and data 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 and data ("render" does not
apply for data) 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
levels of jitter and packet losses. reasonable levels of jitter and packet losses.
TBD: What is a reasonable level? TBD: What is a reasonable level?
---------------------------------------------------------------- ----------------------------------------------------------------
F6 The browser MUST be able to handle high loss and F6 The browser MUST be able to handle high loss and
jitter levels in a graceful way. jitter levels in a graceful way.
---------------------------------------------------------------- ----------------------------------------------------------------
F7 The browser MUST support fast stream switches. F7 The browser MUST support fast stream switches.
---------------------------------------------------------------- ----------------------------------------------------------------
F8 The browser MUST detect when a stream from a F8 The browser MUST detect when a stream from a
peer is not received anymore peer is not received anymore
---------------------------------------------------------------- ----------------------------------------------------------------
F9 When there are both incoming and outgoing audio F9 When there are both incoming and outgoing audio
streams, echo cancellation MUST be made available to streams, echo cancellation MUST be made
avoid disturbing echo during conversation. available to avoid disturbing echo during
conversation.
QUESTION: How much control should be left to the QUESTION: How much control should be left to the
web application? web application?
---------------------------------------------------------------- ----------------------------------------------------------------
F10 The browser MUST support synchronization of F10 The browser MUST support synchronization of
audio and video. audio and video.
QUESTION: How much control should be left to the QUESTION: How much control should be left to the
web application? web application?
---------------------------------------------------------------- ----------------------------------------------------------------
F11 The browser MUST be able to transmit streams to F11 The browser MUST be able to transmit streams and
several peers concurrently. data to several peers concurrently.
---------------------------------------------------------------- ----------------------------------------------------------------
F12 The browser MUST be able to receive streams from F12 The browser MUST be able to receive streams and
multiple peers concurrently. data from multiple peers concurrently.
---------------------------------------------------------------- ----------------------------------------------------------------
F13 The browser MUST be able to apply spatialization F13 The browser MUST be able to apply spatialization
effects to audio streams. effects to audio streams.
---------------------------------------------------------------- ----------------------------------------------------------------
F14 The browser MUST be able to measure the level F14 The browser MUST be able to measure the level
in audio streams. in audio streams.
---------------------------------------------------------------- ----------------------------------------------------------------
F15 The browser MUST be able to change the level F15 The browser MUST be able to change the level
in audio streams. in audio streams.
---------------------------------------------------------------- ----------------------------------------------------------------
F16 The browser MUST be able to render several F16 The browser MUST be able to render several
concurrent video streams concurrent video streams
---------------------------------------------------------------- ----------------------------------------------------------------
F17 The browser MUST be able to mix several F17 The browser MUST be able to mix several
audio streams. audio streams.
---------------------------------------------------------------- ----------------------------------------------------------------
skipping to change at page 16, line 34 skipping to change at page 17, line 16
F15 The browser MUST be able to change the level F15 The browser MUST be able to change the level
in audio streams. in audio streams.
---------------------------------------------------------------- ----------------------------------------------------------------
F16 The browser MUST be able to render several F16 The browser MUST be able to render several
concurrent video streams concurrent video streams
---------------------------------------------------------------- ----------------------------------------------------------------
F17 The browser MUST be able to mix several F17 The browser MUST be able to mix several
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
source than the established media stream(s) with the another source than the established media
peer(s) with audio streams. stream(s) with the peer(s) with audio streams.
---------------------------------------------------------------- ----------------------------------------------------------------
F19 Streams MUST be able to pass through restrictive F19 Streams and data MUST be able to pass through
firewalls. restrictive firewalls.
---------------------------------------------------------------- ----------------------------------------------------------------
F20 It MUST be possible to protect streams F20 It MUST be possible to protect streams and data
from eavesdropping. from wiretapping.
---------------------------------------------------------------- ----------------------------------------------------------------
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
a DTMF based IVR a DTMF based IVR
---------------------------------------------------------------- ----------------------------------------------------------------
F23 The browser must be able to send short F23 The browser must be able to send short
latency unreliable datagram traffic to a latency unreliable datagram traffic to a
peer browser. 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 SHOULD be able to take advantage
capabilities (supplied by network nodes) to of available capabilities (supplied by network
prioritize voice, video and data appropriately. nodes) to 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
media session where the data needed for establishment accept a media session where the data needed
can be carried in SIP. for establishment can be carried in SIP.
---------------------------------------------------------------- ----------------------------------------------------------------
F28 The browser MUST support a baseline audio and F28 The browser MUST support a baseline audio and
video codec video codec
---------------------------------------------------------------- ----------------------------------------------------------------
F29 The browser MUST be able to send streams to a F29 The browser MUST be able to send streams and
peer in the presence of NATs that block UDP traffic. data to a peer in the presence of NATs that
block UDP traffic.
---------------------------------------------------------------- ----------------------------------------------------------------
F30 The browser MUST be able to use the screen (or F30 The browser MUST be able to use the screen (or
a specific area of the screen) or what a certain a specific area of the screen) or what a certain
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
the service provided (i.e. the network provider) than the service provided (i.e. the network
provider).
---------------------------------------------------------------- ----------------------------------------------------------------
F33 The browser must be able to send reliable F33 The browser must be able to send reliable
data traffic to a peer browser. 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 F34 The browser MUST support priortization of
streams and data. streams and data.
---------------------------------------------------------------- ----------------------------------------------------------------
F35 The browser MUST enable verification, given the right F35 The browser MUST enable verification, given
circumstances and by use of other trusted communication, the right circumstances and by use of other
of that streams and data recevived have not been trusted communication, of that streams and
manipulated by any party data received have not been manipulated by
any party.
---------------------------------------------------------------- ----------------------------------------------------------------
F36 The browser MUST reject incoming media and data, either F36 The browser MUST reject incoming media and
modified, created or injected, by any entity not trusted data, either modified, created or injected,
by the site. by any entity not trusted by the site.
----------------------------------------------------------------
F37 The browser MUST be able to send streams and
data to a peer in the presence of FWs that only
allows http(s) traffic.
----------------------------------------------------------------
F38 The browser MUST be able to collect statistics,
related to the transport of audio and video
between peers, needed to estimate quality of
service.
---------------------------------------------------------------- ----------------------------------------------------------------
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.
---------------------------------------------------------------- ----------------------------------------------------------------
skipping to change at page 19, line 48 skipping to change at page 20, line 33
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 For each stream generated, the Web API MUST provide A17 For each stream generated, the Web API MUST
an identifier that is accessible by the application. provide an identifier that is accessible by the
The identifier MUST be accessible also for a peer application. The identifier MUST be accessible
receiving that stream and MUST be unique relative also for a peer receiving that stream and MUST
to all other stream identifiers in use by either party. be unique relative to all other stream
identifiers in use by either party.
---------------------------------------------------------------- ----------------------------------------------------------------
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 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
for when setting up a connection (audio, video, streams for when setting up a connection (audio,
other). The types of media he's willing to accept video, other). The types of media he's willing
can be a subset of the types of media the browser to accept can be a subset of the types of media
is able to accept. the browser 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 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 refrain from A25 It must be possible for the application to
exposing the IP address refrain from exposing the IP address
----------------------------------------------------------------
A26 The Web API MUST provide means for the
application to obtain the statistics (related
to transport, and collected by the browser)
needed to estimate quality of service.
---------------------------------------------------------------- ----------------------------------------------------------------
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 22, line 48 skipping to change at page 23, line 39
rtcweb/current/msg00530.html rtcweb/current/msg00530.html
9. Call center http://www.ietf.org/mail-archive/web/rtcweb/current/ 9. Call center http://www.ietf.org/mail-archive/web/rtcweb/current/
msg04203.html msg04203.html
10. Enterprise policies http://www.ietf.org/mail-archive/web/rtcweb/ 10. Enterprise policies http://www.ietf.org/mail-archive/web/rtcweb/
current/msg04271.html current/msg04271.html
11. Low-complex multiparty central node http://www.ietf.org/ 11. Low-complex multiparty central node http://www.ietf.org/
mail-archive/web/rtcweb/current/msg04430.html mail-archive/web/rtcweb/current/msg04430.html
12. Multiparty central node that is not allowed to decipher http:// 12. Multiparty central node that is not allowed to decipher http://
www.ietf.org/mail-archive/web/rtcweb/current/msg04457.html www.ietf.org/mail-archive/web/rtcweb/current/msg04457.html
13. Enable company coop without being able to decipher http:// 13. Enable company coop without being able to decipher http://
www.ietf.org/mail-archive/web/rtcweb/current/msg04464.html www.ietf.org/mail-archive/web/rtcweb/current/msg04461.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 23, line 26 skipping to change at page 24, line 15
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-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 FW 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 Changes from draft-ietf-rtcweb-use-cases-and-requirements-07
o Added "and data exchange" to 1. Introduction. o Added "and data exchange" to 1. Introduction.
o Removed cone and symmetric NAT from 4.1 Introduction, refers to o Removed cone and symmetric NAT from 4.1 Introduction, refers to
RFC4787 instead. RFC4787 instead.
o Added text on enabling verifyication of that the media has not o Added text on enabling verifyication of that the media has not
been manipulated by anyone to use-case "Simple Video Communication been manipulated by anyone to use-case "Simple Video Communication
Service", derived req. F35 Service", derived req. F35
o Added text on that the browser should reject media (data) that has o Added text on that the browser should reject media (data) that has
been created/injected/modified by non-trusted party, derived req. been created/injected/modified by non-trusted party, derived req.
skipping to change at page 26, line 25 skipping to change at page 27, line 25
by a browser (Ted Hardie, 080311) by a browser (Ted Hardie, 080311)
o - Editorial corrections and clarifications o - Editorial corrections and clarifications
11. References 11. References
11.1. Normative References 11.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
11.2. Informative References [RFC2804] IAB and IESG, "IETF Policy on Wiretapping", RFC 2804,
May 2000.
[webrtc_reqs] 11.2. Informative References
"Webrt requirements,
http://dev.w3.org/2011/webrtc/editor/webrtc_reqs.html".
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
 End of changes. 83 change blocks. 
132 lines changed or deleted 187 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/