Re: [rtcweb] Review request for RTCWeb standard signaling protocol

Ted Hardie <ted.ietf@gmail.com> Tue, 18 October 2011 23:40 UTC

Return-Path: <ted.ietf@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 DB2D421F8B10 for <rtcweb@ietfa.amsl.com>; Tue, 18 Oct 2011 16:40:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.159
X-Spam-Level:
X-Spam-Status: No, score=-3.159 tagged_above=-999 required=5 tests=[AWL=0.439, BAYES_00=-2.599, 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 z4xmitMr6Kh4 for <rtcweb@ietfa.amsl.com>; Tue, 18 Oct 2011 16:40:39 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 07DD921F8B0B for <rtcweb@ietf.org>; Tue, 18 Oct 2011 16:40:38 -0700 (PDT)
Received: by ggnv1 with SMTP id v1so1349034ggn.31 for <rtcweb@ietf.org>; Tue, 18 Oct 2011 16:40:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=GMNBz/3SnoodR3rXlpUaHE9VRZ2DjKmJHtmfmH+YoEs=; b=rUgOx15getEgR4Z7W1i5wpD2aeZU5GH3egxpDgsBjEpsTZd6BrPlIQc7FKgHKUEVT3 /ox7wvYJZkgYdcGeQe260FxBgpczRCCpzb9WuD8bU/eBJnERKulyTVWJQK4aSS4ObjUI 0y2POtNLkDxuBB+oxLwwcQSGw5UQT/+8qRsiM=
MIME-Version: 1.0
Received: by 10.236.131.40 with SMTP id l28mr6918616yhi.6.1318981238584; Tue, 18 Oct 2011 16:40:38 -0700 (PDT)
Received: by 10.236.105.169 with HTTP; Tue, 18 Oct 2011 16:40:38 -0700 (PDT)
In-Reply-To: <37796D08-7A24-478B-8157-052FFB2E3945@acmepacket.com>
References: <2E239D6FCD033C4BAF15F386A979BF510F1367@sonusinmail02.sonusnet.com> <4E8AC222.4050308@alvestrand.no> <2E239D6FCD033C4BAF15F386A979BF510F14CE@sonusinmail02.sonusnet.com> <CALiegf=ejF2kUC1m=74o9eprF1M8wYtgE-Crwa1x14rzDOf+gQ@mail.gmail.com> <2E239D6FCD033C4BAF15F386A979BF510F14FD@sonusinmail02.sonusnet.com> <393F1888-F834-4DAE-B6B1-1C5D35EE3292@phonefromhere.com> <CAOg=WDcC9t2KhQUg0gDJ60gO_2mNyMv9HKt=otCdPDfj4TnoTg@mail.gmail.com> <2E239D6FCD033C4BAF15F386A979BF510F152B@sonusinmail02.sonusnet.com> <CABRok6mM7TfbLgGhoQvdRh1Kwoi5BhRweLcqWg7VZOFnaa8VOw@mail.gmail.com> <2E239D6FCD033C4BAF15F386A979BF510F1532@sonusinmail02.sonusnet.com> <CABRok6n33QK0Si1Y0kT7+U0zgAWsJ4d5GENK_KL-JPx5a4erYg@mail.gmail.com> <2E239D6FCD033C4BAF15F386A979BF511598EE@sonusinmail02.sonusnet.com> <665A16AB-AAD8-42B3-AC17-7E629EA2DE35@phonefromhere.com> <2E239D6FCD033C4BAF15F386A979BF5115992E@sonusinmail02.sonusnet.com> <CALiegfmrncjsLVSiWk0tEgzwB00YaBGiqj0SDf9JTm9p1ZNoVA@mail.gmail.com> <0950F0E1-6E4B-407F-9563-654AFE79F64B@ag-projects.com> <2E239D6FCD033C4BAF15F386A979BF51159994@sonusinmail02.sonusnet.com> <1F2A2C70609D9E41844A2126145FC09804004302@HKGMBOXPRD22.polycom.com> <033458F56EC2A64E8D2D7B759FA3E7E703DBF614@sonusmail04.sonusnet.com> <8486C8728176924BAF5BDB2F7D7EEDDF3E091D13@ucolhp4d.easf.csd.disa.mil> <2E239D6FCD033C4BAF15F386A979BF511599F3@sonusinmail02.sonusnet.com> <CALiegfnyfrBHATQ3WThT7F_fpXePN8PFYW_MJMwK-6QUjzkknA@mail.gmail.com> <CA+9kkMBa7RNzT3y_s+PgHZr9DTz-49WC8aEqmmZLt-eEYkBFnQ@mail.gmail.com> <37796D08-7A24-478B-8157-052FFB2E3945@acmepacket.com>
Date: Tue, 18 Oct 2011 16:40:38 -0700
Message-ID: <CA+9kkMATLaKpZzbNQeS8XMbqkViyeY=w6qx4S-txJr5A=D9s=w@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
To: Hadriel Kaplan <HKaplan@acmepacket.com>
Content-Type: multipart/alternative; boundary=20cf301afabb30f5dd04af9b400e
Cc: "<rtcweb@ietf.org>" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Review request for RTCWeb standard signaling protocol
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: Tue, 18 Oct 2011 23:40:40 -0000

On Tue, Oct 18, 2011 at 1:43 PM, Hadriel Kaplan <HKaplan@acmepacket.com>wrote:

>
>
> You make this sound like you believe this to be an advantage.
>
>
>
>  It *is* an advantage.  It puts the power in the hands of the app
> developer, not the browser developer.
>
>
>
As Peter Parker's uncle Ben tells, us, with great power comes great
responsibility.  Yes, it gives them a choice, but it also makes them
responsible for something that is, bluntly, infrastructure plumbing that
most of them would rather just worked.

>  Having seen the bit-rot in quite a few libraries,
>
>
>  Have you ever used Internet Explorer??
>
>

Not lately; it doesn't run on any of my current platforms.


> (and I'm not slamming IE because I think their developers are bad - they
> have a very tough job of keeping compatibility with numerous Windows OS
> versions, drivers, etc. - I just think they'll focus on doing that rather
> dealing with signaling protocol changes/bug-fixes for RTCWeb in any timely
> manner)
>
>   It's certainly less efficient and, given the majority of users now
> accessing the Internet via mobile devices which are power and bandwidth
> constrained, that sort of wastefulness should not be trivially dismissed.
>
>
>  If a mobile platform is so constrained of power and bandwidth that
> downloading a JS library is difficult, it's unlikely it would be able to
> handle RTP/RTCP media regardless.
>
>
You don't get to be rich by making a lot of money, you get to be rich by
keeping it.  The same is true with energy in mobile systems.  Pay attention
to it all the time, and there's a fair chance you will never run out.  Pay
attention to it only when you're low, and you're likely paying attention to
late.

regards,

Ted



>  -hadriel
>
>