--- 1/draft-ietf-rtcweb-use-cases-and-requirements-09.txt 2012-12-19 14:45:05.756043038 +0100 +++ 2/draft-ietf-rtcweb-use-cases-and-requirements-10.txt 2012-12-19 14:45:05.804040937 +0100 @@ -1,19 +1,19 @@ RTCWEB Working Group C. Holmberg Internet-Draft S. Hakansson Intended status: Informational G. Eriksson -Expires: December 29, 2012 Ericsson - June 27, 2012 +Expires: June 22, 2013 Ericsson + December 19, 2012 Web Real-Time Communication Use-cases and Requirements - draft-ietf-rtcweb-use-cases-and-requirements-09.txt + draft-ietf-rtcweb-use-cases-and-requirements-10.txt Abstract This document describes web based real-time communication use-cases. Based on the use-cases, the document also derives requirements related to the browser, and the API used by web applications to request and control media stream and data exchange services provided by the browser. Status of this Memo @@ -24,21 +24,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on December 29, 2012. + This Internet-Draft will expire on June 22, 2013. Copyright Notice Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -149,23 +149,23 @@ 4.2.1. Simple Video Communication Service 4.2.1.1. Description Two or more users have loaded a video communication web application into their browsers, provided by the same service provider, and logged into the service it provides. The web service publishes information about user login status by pushing updates to the web application in the browsers. When one online user selects a peer - online user, a 1-1 video communication session between the browsers - of the two peers is initiated. The invited user might accept or - reject the session. + online user, a 1-1 audiovisual communication session between the + browsers of the two peers is initiated. The invited user might + accept or reject the session. During session establishment a self-view is displayed, and once the session has been established the video sent from the remote peer is 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 desired. Each user can also change the sizes of his/her two video displays during the session. Each user can also pause sending of media (audio, video, or both) and mute incoming media It is essential that the communication cannot be wiretapped @@ -402,26 +402,27 @@ An ice-hockey club uses an application that enables talent scouts to, in real-time, show and discuss games and players with the club manager. The talent scouts use a mobile phone with two cameras, one front facing and one rear facing. The club manager uses a desktop, equipped with one camera, for viewing the game and discussing with the talent scout. Before the game starts, and during game breaks, the talent scout and - the manager have a 1-1 video communication. Only the rear facing - camera of the mobile phone is used. On the display of the mobile - phone, the video of the club manager is shown with a picture-in- - picture thumbnail of the rear facing camera (self-view). On the - display of the desktop, the video of the talent scout is shown with a - picture-in-picture thumbnail of the desktop camera (self-view). + the manager have a 1-1 audiovisual communication session. Only the + rear facing camera of the mobile phone is used. On the display of + the mobile phone, the video of the club manager is shown with a + picture-in-picture thumbnail of the rear facing camera (self-view). + On the display of the desktop, the video of the talent scout is shown + with a picture-in-picture thumbnail of the desktop camera (self- + view). 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 stream from the rear facing camera continues to be sent all the time). The video stream captured by the front facing camera (that is capturing the game) of the mobile phone is shown in a big window on the desktop screen, with picture-in-picture thumbnails of the rear facing camera and the desktop camera (self-view). On the display of the mobile phone the game is shown (front facing camera) with picture-in-picture thumbnails of the rear facing camera (self-view) @@ -1047,20 +1048,25 @@ Harald Alvestrand and Cullen Jennings have provided additional use- cases. Thank You to everyone in the RTCWEB community that have provided comments, feedback and improvement proposals on the draft content. 10. Change Log [RFC EDITOR NOTE: Please remove this section when publishing] + Changes from draft-ietf-rtcweb-use-cases-and-requirements-09 + + o Changed "video communication session" to "audiovisual + communication session. + Changes from draft-ietf-rtcweb-use-cases-and-requirements-08 o Changed "eavesdropping" to "wiretapping" and referenced RFC2804. o Removed informal ref webrtc_req; that document has been abandoned by the W3C webrtc WG. o Added use-case where one user is behind a 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