Re: [rtcweb] Remote recording - RTC-Web client acting as SIPREC session recording client

"Robert O'Callahan" <robert@ocallahan.org> Fri, 26 August 2011 05:24 UTC

Return-Path: <rocallahan@gmail.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 9500121F8ACC for <rtcweb@ietfa.amsl.com>; Thu, 25 Aug 2011 22:24:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level:
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 uI2KHSjabc8S for <rtcweb@ietfa.amsl.com>; Thu, 25 Aug 2011 22:24:29 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 0285A21F8ABC for <rtcweb@ietf.org>; Thu, 25 Aug 2011 22:24:28 -0700 (PDT)
Received: by ywe9 with SMTP id 9so2859676ywe.31 for <rtcweb@ietf.org>; Thu, 25 Aug 2011 22:25:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:reply-to:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=cBR7uMMBgxCAVkHj/K0RG1pcEgipNg0UJkl433AlBnI=; b=uKCYasA43Fyw8CNHtoM0fUzmXAzBy42sn31+SZKNddUEfjR8IJKhq1XcosQHmJnush Kkw12jkkuzk5+hrJmhKQhrbkd6W2A3g99bv5Vzc8oNj047zH+BRbDpibCdZPSgyyy9o3 V6jHR7+X4tW37Jqi5OVuj4F65w3DhEMiLp2Aw=
MIME-Version: 1.0
Received: by 10.42.28.130 with SMTP id n2mr650602icc.28.1314336343923; Thu, 25 Aug 2011 22:25:43 -0700 (PDT)
Sender: rocallahan@gmail.com
Received: by 10.231.169.198 with HTTP; Thu, 25 Aug 2011 22:25:43 -0700 (PDT)
In-Reply-To: <4E56BC1A.8070803@skype.net>
References: <A444A0F8084434499206E78C106220CA0B00FDB08B@MCHP058A.global-ad.net> <89177AB2-F721-47E4-8471-2180EDA10615@voxeo.com> <A444A0F8084434499206E78C106220CA0B00FDB34D@MCHP058A.global-ad.net> <496EE152-41F2-49AB-A136-05735FE5A9F9@voxeo.com> <101C6067BEC68246B0C3F6843BCCC1E31018BF6BE2@MCHP058A.global-ad.net> <4E54AB9B.9090600@jesup.org> <A444A0F8084434499206E78C106220CA0B00FDB534@MCHP058A.global-ad.net> <101C6067BEC68246B0C3F6843BCCC1E31018BF6DF6@MCHP058A.global-ad.net> <4E554BCE.2040403@alum.mit.edu> <4E56399E.2020902@alvestrand.no> <A444A0F8084434499206E78C106220CA0B011C8D3B@MCHP058A.global-ad.net> <4E5682DD.5020204@skype.net> <4E568FA7.9060805@gmail.com> <2E239D6FCD033C4BAF15F386A979BF51064370@sonusinmail02.sonusnet.com> <4E56BC1A.8070803@skype.net>
Date: Fri, 26 Aug 2011 17:25:43 +1200
X-Google-Sender-Auth: iLzyeSFlx8r7Ev4JpgPNwyuLpb8
Message-ID: <CAOp6jLbStpSEn1zaYJRhuPiNvJfRgXm3xpWdzsg6HH3u+nMX_g@mail.gmail.com>
From: Robert O'Callahan <robert@ocallahan.org>
To: Matthew Kaufman <matthew.kaufman@skype.net>
Content-Type: multipart/alternative; boundary="20cf30427260e51c5504ab61c63e"
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Remote recording - RTC-Web client acting as SIPREC session recording client
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@ocallahan.org
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, 26 Aug 2011 05:25:09 -0000

On Fri, Aug 26, 2011 at 9:18 AM, Matthew Kaufman
<matthew.kaufman@skype.net>wrote:

> Getting ubiquitous deployment will require complying with norms about what
> a browser does and doesn't do. Right now one of the things it *doesn't* do
> is relay media unexpectedly.


Browsers *do* consume arbitrary quantities of downstream bandwidth, and
sometimes upstream bandwidth too. Opera even built BitTorrent into their
browser. Most "browsers don't do X" norms have already fallen by the
wayside. "Browsers don't act as relays" will too.

Given browsers are general-purpose application platforms, it makes more
sense to ban specific Web sites than browsers if you're worried about
excessive bandwidth usage.

Rob
-- 
"If we claim to be without sin, we deceive ourselves and the truth is not in
us. If we confess our sins, he is faithful and just and will forgive us our
sins and purify us from all unrighteousness. If we claim we have not sinned,
we make him out to be a liar and his word is not in us." [1 John 1:8-10]