Re: [rtcweb] Use cases - recording and voicemail

"Elwell, John" <john.elwell@siemens-enterprise.com> Mon, 22 August 2011 14:40 UTC

Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5194421F863A for <rtcweb@ietfa.amsl.com>; Mon, 22 Aug 2011 07:40:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.119
X-Spam-Level:
X-Spam-Status: No, score=-103.119 tagged_above=-999 required=5 tests=[AWL=-0.820, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WcKxxFaDtkJ8 for <rtcweb@ietfa.amsl.com>; Mon, 22 Aug 2011 07:40:18 -0700 (PDT)
Received: from senmx11-mx.siemens-enterprise.com (senmx11-mx.siemens-enterprise.com [62.134.46.9]) by ietfa.amsl.com (Postfix) with ESMTP id 6793321F8591 for <rtcweb@ietf.org>; Mon, 22 Aug 2011 07:40:18 -0700 (PDT)
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx11-mx.siemens-enterprise.com (Server) with ESMTP id BDE371EB846C; Mon, 22 Aug 2011 16:41:22 +0200 (CEST)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Mon, 22 Aug 2011 16:41:22 +0200
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Harald Alvestrand <harald@alvestrand.no>, =?iso-8859-1?Q?Stefan_H=E5kansson_LK?= <stefan.lk.hakansson@ericsson.com>
Date: Mon, 22 Aug 2011 16:41:20 +0200
Thread-Topic: [rtcweb] Use cases - recording and voicemail
Thread-Index: Acxg1SWBKFO59e/TTriCOSPCA287pAAAZMag
Message-ID: <A444A0F8084434499206E78C106220CA0B00FDAE68@MCHP058A.global-ad.net>
References: <BBF498F2D030E84AB1179E24D1AC41D616C389F16D@ESESSCMS0362.eemea.ericsson.se><4E3AB4D4.4070308@jesup.org>, <A444A0F8084434499206E78C106220CA09BDB6A238@MCHP058A.global-ad.net><BBF498F2D030E84AB1179E24D1AC41D616C389F242@ESESSCMS0362.eemea.ericsson.se>, <A444A0F8084434499206E78C106220CA09BDB6A34F@MCHP058A.global-ad.net><BBF498F2D030E84AB1179E24D1AC41D616C389F245@ESESSCMS0362.eemea.ericsson.se>, <A444A0F8084434499206E78C106220CA09BDB6A397@MCHP058A.global-ad.net><BBF498F2D030E84AB1179E24D1AC41D616C389F24A@ESESSCMS0362.eemea.ericsson.se><2E239D6FCD033C4BAF15F386A979BF510640D0@sonusinmail02.sonusnet.com><A444A0F8084434499206E78C106220CA0B00FDABAD@MCHP058A.global-ad.net> <2E239D6FCD033C4BAF15F386A979BF51064106@sonusinmail02.sonusnet.com> <1F2A2C70609D9E41844A2126145FC09801F1550D@HKGMBOXPRD22.polycom.com> <2E239D6FCD033C4BAF15F386A979BF51064117@sonusinmail02.sonusnet.com> <4E523B4B.4070905@ericsson.com> <4E526327.7050807@alvestrand.no>
In-Reply-To: <4E526327.7050807@alvestrand.no>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Subject: Re: [rtcweb] Use cases - recording and voicemail
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2011 14:40:19 -0000

 

> -----Original Message-----
> From: Harald Alvestrand [mailto:harald@alvestrand.no] 
> Sent: 22 August 2011 15:10
> To: Stefan Håkansson LK
> Cc: Ravindran Parthasarathi; Avasarala, Ranjit; Elwell, John; 
> rtcweb@ietf.org; public-webrtc@w3.org
> Subject: Re: [rtcweb] Use cases - recording and voicemail
> 
> On 08/22/11 13:19, Stefan Håkansson LK wrote:
> > On 2011-08-22 10:16, Ravindran Parthasarathi wrote:
> >
> >> ... Currently, let us have common understanding whether recording 
> >> usecase has to be added in RTCWeb or not.
> > Agree. And also _which_ recording use case(s) in that case. I think 
> > this is what John was looking for when starting the thread.
> >
> > My $0.02 says that we need to take some care before adding more and 
> > more usages and reqs - after all the schedules for the WGs 
> are quite 
> > aggressive.
> Indeed. When thinking about the recording use cases, I could come up 
> with a few interpretations:
> 
> - Record one media stream, as it arrives (the "voice mailbox" concept)
[JRE] This was not what I originally proposed, but emerged during discussion. From my point of view a mailbox is more likely to be centralized, not on a user's device, so the web application can divert calls to a mailbox using signalling means, without any impact on the browser. Some people might want to support a local mailbox, in which case browser support would be needed, but that is second priority, from my perspective.

> - Record a conversation: Outgoing and incoming audio and video in an 
> 1-on-1 or 1-on-N context (typically as permanent records of a 
> meeting or 
> conversation)
[JRE] This was what I was originally asking about. Seems to be important to have this capability from day 1, or at least an architecture that can be extended to do this at day 2.


> - Record the application screen as presented to the user, 
> together with 
> the audio tracks as presented to the user's audio device, but don't 
> bother with incoming audio from the user at all (game recording, for 
> instance - the "WoW movie" kind)
[JRE] Not high priority from my perspective.

> 
> In each instance, recording technology might include recording:
> 
>    - As one track, somehow mixed, ready for playback
>    - As multiple tracks recorded separately within a container that 
> requires special playback devices
[JRE] I think the container here is what is known as metadata, from a session recording point of view. That container can be a matter for the web application.

>    - As multiple tracks, recorded separately to separate objects
[JRE] Yes, although the possibility of mixing (e.g., the two directions of an audio stream) would be good to have.

>    - As streams sent to some remote recording entity, that may choose 
> one of the options above
[JRE] Yes, this is my primary concern, coupled with the "record a conversation" above.

> 
> I'd be happier about discussing which ones of these people find it 
> critical to support before we dive into figuring out how to 
> support them.
> 
> Send text!
[JRE] I was just about to - look out for separate postings for local and remote recording (I will leave others to proposed text for mailbox, if they require it).

John


John Elwell
Tel: +44 1908 817801 (office and mobile)
Email: john.elwell@siemens-enterprise.com
http://www.siemens-enterprise.com/uk/

Siemens Enterprise Communications Limited.
Registered office: Brickhill Street, Willen Lake, Milton Keynes, MK15 0DJ.
Registered No: 5903714, England.

Siemens Enterprise Communications Limited is a Trademark Licensee of Siemens AG.


> 
>                        Harald
> 
>