IETF Logo Mail Archive

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

Neil Stratford <neils@belltower.co.uk> Wed, 19 October 2011 11:33 UTC

Return-Path: <neils@vipadia.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 EC7AD21F8B91 for <rtcweb@ietfa.amsl.com>; Wed, 19 Oct 2011 04:33:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.959
X-Spam-Level:
X-Spam-Status: No, score=-2.959 tagged_above=-999 required=5 tests=[AWL=0.017, 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 EnHK6lJIw0QQ for <rtcweb@ietfa.amsl.com>; Wed, 19 Oct 2011 04:33:29 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6C7AF21F8B77 for <rtcweb@ietf.org>; Wed, 19 Oct 2011 04:33:29 -0700 (PDT)
Received: by gyh20 with SMTP id 20so1923887gyh.31 for <rtcweb@ietf.org>; Wed, 19 Oct 2011 04:33:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.42.161.70 with SMTP id s6mr12030098icx.40.1319024009002; Wed, 19 Oct 2011 04:33:29 -0700 (PDT)
Sender: neils@vipadia.com
Received: by 10.231.199.4 with HTTP; Wed, 19 Oct 2011 04:33:28 -0700 (PDT)
In-Reply-To: <CA+9kkMATLaKpZzbNQeS8XMbqkViyeY=w6qx4S-txJr5A=D9s=w@mail.gmail.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> <CA+9kkMATLaKpZzbNQeS8XMbqkViyeY=w6qx4S-txJr5A=D9s=w@mail.gmail.com>
Date: Wed, 19 Oct 2011 12:33:28 +0100
X-Google-Sender-Auth: uiNtVa5T5NFmrU96XYZEnkQp7tM
Message-ID: <CABRok6=ZyFkNCEXQFMMBe5EZ6Si66-qQGqftgc_4wK5r4E6ztw@mail.gmail.com>
From: Neil Stratford <neils@belltower.co.uk>
To: Ted Hardie <ted.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="90e6ba2123e581c07204afa5359e"
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: Wed, 19 Oct 2011 11:33:30 -0000

On Wed, Oct 19, 2011 at 12:40 AM, Ted Hardie <ted.ietf@gmail.com> wrote:

>
> 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.
>

The low energy example is a great reason why we wouldn't want a single
standard protocol. In the low energy case you want to move all the smarts
out of the handset and into the server, which requires a different protocol
to the one you'd use for a high power desktop application.

Forcing a handset to implement a protocol that is expressive enough for all
the possible uses on the desktop seems like a bad idea.

Neil

v2.23.0 | Report a Bug | By Email