Re: [rtcweb] RTCWeb default signaling protocol [was RE: About defining a signaling protocol for WebRTC (or not)]

Eric Rescorla <ekr@rtfm.com> Tue, 04 October 2011 15:30 UTC

Return-Path: <ekr@rtfm.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 963BE21F8CF8 for <rtcweb@ietfa.amsl.com>; Tue, 4 Oct 2011 08:30:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level:
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 8CANOiWzXefq for <rtcweb@ietfa.amsl.com>; Tue, 4 Oct 2011 08:30:09 -0700 (PDT)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id 920E521F8CF7 for <rtcweb@ietf.org>; Tue, 4 Oct 2011 08:30:09 -0700 (PDT)
Received: by eye4 with SMTP id 4so679524eye.31 for <rtcweb@ietf.org>; Tue, 04 Oct 2011 08:33:14 -0700 (PDT)
Received: by 10.213.33.136 with SMTP id h8mr764427ebd.21.1317742394263; Tue, 04 Oct 2011 08:33:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.213.22.211 with HTTP; Tue, 4 Oct 2011 08:32:34 -0700 (PDT)
In-Reply-To: <4E8B1B86.2080805@jesup.org>
References: <CALiegfnOCxyTo9ffQ272+ncdu5UdgrtDT-dn10BWGTZMEjZoCg@mail.gmail.com> <2E239D6FCD033C4BAF15F386A979BF510F0C0A@sonusinmail02.sonusnet.com> <05CAC192-E462-421F-B1E5-B78DC8F60306@ag-projects.com> <2E239D6FCD033C4BAF15F386A979BF510F0C93@sonusinmail02.sonusnet.com> <16880306-5B3A-4EFD-ADE4-1201138D9182@acmepacket.com> <2E239D6FCD033C4BAF15F386A979BF510F137B@sonusinmail02.sonusnet.com> <226C9800-9791-465A-B519-40935E2D135F@phonefromhere.com> <4E8B1B86.2080805@jesup.org>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 4 Oct 2011 08:32:34 -0700
Message-ID: <CABcZeBPjwC_ux1EuqANgFMLPneabSNyeewFGhrVfso3gMdN0Cg@mail.gmail.com>
To: Randell Jesup <randell-ietf@jesup.org>
Content-Type: multipart/alternative; boundary=000e0cd1380250cab404ae7acf9c
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] RTCWeb default signaling protocol [was RE: About defining a signaling protocol for WebRTC (or not)]
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, 04 Oct 2011 15:30:10 -0000

On Tue, Oct 4, 2011 at 7:43 AM, Randell Jesup <randell-ietf@jesup.org>wrote:
>
> 3) Inaki's (sorry about the cedilla) point about "website-based libraries
> can be updated more often than ones baked into a browser" is valid, but it
> has a flip-side - the swarm of smaller users of webrtc are likely to
> download a version of jSIP.js (or whatever) and are not likely to actively
> track updates.  My understanding is that this is rife in the use of things
> like jquery - upgrading is time-consuming and risks breakage, and requires
> QA.  People grab one version and never change it - while Firefox for example
> updates every 6 weeks.  (He may have a better argument with IE users,
> especially in business, but my point still holds.)


This is my understanding as well, and it's something that is encouraged by
the way that these
libraries are distributed, namely that the obvious behavior if you go to the
JQuery site is to
just download one of the canned versions, which of course is specific. Even
if you use one
of the CDN versions (see:
http://docs.jquery.com/Downloading_jQuery#CDN_Hosted_jQuery),
the links are all to specific versions. So, the consequence is that people
en up nailed to
one version.

This doesn't necessarily mean that client libraries will upgrade more slowly
than the browsers,
but as far as I know it's not a decided question either way.

Best,
-Ekr