Re: [rtcweb] Proposed text - remote recording use case

Matthew Kaufman <matthew.kaufman@skype.net> Mon, 12 September 2011 08:32 UTC

Return-Path: <matthew.kaufman@skype.net>
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 9D40621F86A6 for <rtcweb@ietfa.amsl.com>; Mon, 12 Sep 2011 01:32:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 GTsvBFvJHkyP for <rtcweb@ietfa.amsl.com>; Mon, 12 Sep 2011 01:32:23 -0700 (PDT)
Received: from mx.skype.net (mx.skype.net [78.141.177.88]) by ietfa.amsl.com (Postfix) with ESMTP id 16FF921F8567 for <rtcweb@ietf.org>; Mon, 12 Sep 2011 01:32:23 -0700 (PDT)
Received: from mx.skype.net (localhost [127.0.0.1]) by mx.skype.net (Postfix) with ESMTP id 8650E170F; Mon, 12 Sep 2011 10:34:25 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=skype.net; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=mx; bh=RUNdFdR6Y6pN4s b8ftq45aWUjN4=; b=FFDY3DTpsTOWz8FZgWHoR1omEw1AG1yZ/sac2TwU70ofP+ NIZ9T4s1aw9Wtm/QvFEHLMAqU3Oig7WlAqG7dFUNXjO4RMdMsIQyhJRNS4BhGMk6 xzIGcb48AKzrMfmfOr7s3aXVQt4373J8qP8W9KNWtXbnLZkW3lpvcRw+9Qd+s=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=skype.net; h=message-id:date:from :mime-version:to:cc:subject:references:in-reply-to:content-type: content-transfer-encoding; q=dns; s=mx; b=vi/vtkWx+A8fywASHx/8ZV MiK+XI9UuTFtv/+ZVm0GeKndjtHVqiMmMXB1se8BbWi8ci+19rORFpl/CkDyK2V8 x+qQmZ99sRs/rjc3Ok8Z3ojZ92EHfxWTURKPNmZu9Qsr2YaG91wFvtCF6f1/df34 frCrFaeX1nSVl33ed8lWk=
Received: from zimbra.skype.net (zimbra.skype.net [78.141.177.82]) by mx.skype.net (Postfix) with ESMTP id 841FC7F6; Mon, 12 Sep 2011 10:34:25 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by zimbra.skype.net (Postfix) with ESMTP id 43DA01672683; Mon, 12 Sep 2011 10:34:25 +0200 (CEST)
X-Virus-Scanned: amavisd-new at lu2-zimbra.skype.net
Received: from zimbra.skype.net ([127.0.0.1]) by localhost (zimbra.skype.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XHsXHc+dFs4w; Mon, 12 Sep 2011 10:34:24 +0200 (CEST)
Received: from Matthew-Kaufman-Air.local (c-217-115-41-36.cust.bredband2.com [217.115.41.36]) by zimbra.skype.net (Postfix) with ESMTPSA id 39E5D1672681; Mon, 12 Sep 2011 10:34:24 +0200 (CEST)
Message-ID: <4E6DC40F.3080504@skype.net>
Date: Mon, 12 Sep 2011 10:34:23 +0200
From: Matthew Kaufman <matthew.kaufman@skype.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0.2) Gecko/20110902 Thunderbird/6.0.2
MIME-Version: 1.0
To: Ravindran Parthasarathi <pravindran@sonusnet.com>
References: <A444A0F8084434499206E78C106220CA0B04921B16@MCHP058A.global-ad.net> <2E239D6FCD033C4BAF15F386A979BF510F09ED@sonusinmail02.sonusnet.com>
In-Reply-To: <2E239D6FCD033C4BAF15F386A979BF510F09ED@sonusinmail02.sonusnet.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Proposed text - remote recording use case
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, 12 Sep 2011 08:32:23 -0000

On 9/11/11 10:29 PM, Ravindran Parthasarathi wrote:
> John,
>
> Please let me know whether the updated text works for you:
>
> New requirements:
> Fyy1: The browser MUST be able to send in real-time to an another
> browser/session recording server(SRS) that are being transmitted to and
> received from remote browser.
>
> Ayy1: The web application MUST be able to ask the browser to transmit in
> real-time to another browser/session recording server(SRS) that are
> being transmitted to and received from remote browser.

I still maintain that adding these requirements opens a huge can of 
security and resource utilization worms.

I really think these need to be addressed early before we make this one 
of the mandatory-to-support cases.

Matthew Kaufman