Re: [rtcweb] Use cases - recording and voicemail

Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com> Fri, 19 August 2011 13:20 UTC

Return-Path: <stefan.lk.hakansson@ericsson.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 EE99121F8B03 for <rtcweb@ietfa.amsl.com>; Fri, 19 Aug 2011 06:20:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.26
X-Spam-Level:
X-Spam-Status: No, score=-6.26 tagged_above=-999 required=5 tests=[AWL=0.039, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 jVk0qf3sF4hH for <rtcweb@ietfa.amsl.com>; Fri, 19 Aug 2011 06:20:34 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id 3862721F8AFD for <rtcweb@ietf.org>; Fri, 19 Aug 2011 06:20:34 -0700 (PDT)
X-AuditID: c1b4fb39-b7bfdae000005125-e5-4e4e635a0dd0
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 12.AE.20773.A536E4E4; Fri, 19 Aug 2011 15:21:30 +0200 (CEST)
Received: from ESESSCMS0362.eemea.ericsson.se ([169.254.1.110]) by esessmw0256.eemea.ericsson.se ([10.2.3.125]) with mapi; Fri, 19 Aug 2011 15:21:30 +0200
From: =?iso-8859-1?Q?Stefan_H=E5kansson_LK?= <stefan.lk.hakansson@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Date: Fri, 19 Aug 2011 15:21:30 +0200
Thread-Topic: [rtcweb] Use cases - recording and voicemail
Thread-Index: AcxecQV39GlpikzGRLWQuTfNXGLADQAASGDk
Message-ID: <BBF498F2D030E84AB1179E24D1AC41D616C389F248@ESESSCMS0362.eemea.ericsson.se>
References: <BBF498F2D030E84AB1179E24D1AC41D616C389F16D@ESESSCMS0362.eemea.ericsson.se> <4E3AB4D4.4070308@jesup.org>, <A444A0F8084434499206E78C106220CA09BDB6A238@MCHP058A.global-ad.net> <BBF498F2D030E84AB1179E24D1AC41D616C389F242@ESESSCMS0362.eemea.ericsson.se>, <4E4E6025.7010403@alum.mit.edu>
In-Reply-To: <4E4E6025.7010403@alum.mit.edu>
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
X-Brightmail-Tracker: AAAAAA==
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: Fri, 19 Aug 2011 13:20:35 -0000

>> I'm less sure about that the recorded media should also be an RTP source - couldn't you just as well send the file over and then play it at the remote end?
>
>I think discussing this in terms of a "file" is an over simplification.
>While it could be a file, it could also be synthesized, or assembled
>from pieces, interactively as a result of received media or signaling.
>In such cases you can't just "send the file".
Maybe it was an over simplification, but synthesizing/assembling etc. sound a bit overly complex to me, at least in a first version. Just my personal opinion. In any case we would have to specify more precisely what should be possible.