IETF Logo Mail Archive

Re: [rtcweb] Interoperability - what have we learned?

Bernard Aboba <bernard_aboba@hotmail.com> Sat, 21 December 2013 23:25 UTC

Return-Path: <bernard_aboba@hotmail.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BBAC1AE0DF for <rtcweb@ietfa.amsl.com>; Sat, 21 Dec 2013 15:25:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level:
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4dtMl4lPWv_3 for <rtcweb@ietfa.amsl.com>; Sat, 21 Dec 2013 15:25:14 -0800 (PST)
Received: from blu0-omc3-s25.blu0.hotmail.com (blu0-omc3-s25.blu0.hotmail.com [65.55.116.100]) by ietfa.amsl.com (Postfix) with ESMTP id E482F1AE0CE for <rtcweb@ietf.org>; Sat, 21 Dec 2013 15:25:13 -0800 (PST)
Received: from BLU405-EAS316 ([65.55.116.72]) by blu0-omc3-s25.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Sat, 21 Dec 2013 15:25:11 -0800
X-TMN: [/MydbzHS5L7zpt19XVmXBvJRsyr41syP]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU405-EAS3161C2664A35035737B2A0093C70@phx.gbl>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
From: Bernard Aboba <bernard_aboba@hotmail.com>
MIME-Version: 1.0 (1.0)
Date: Sat, 21 Dec 2013 18:25:08 -0500
References: <52AE759C.7020209@bbs.darktech.org> <CABcZeBMjTGs41t7y=xvaLdn4i63HxC2YQUkrd-itq=VkuKvpTA@mail.gmail.com> <52AE9129.8090702@bbs.darktech.org> <CABcZeBPOxqa2YQxOrTp9sVF-tQrpg-Kn=CbazBXOx_9dajhUZA@mail.gmail.com> <52AE9E0C.9060707@bbs.darktech.org> <20131216170820.GD82971@verdi> <20131220113631.GA70585@verdi> <52B47196.6060400@bbs.darktech.org> <D5B39658-5766-4C5B-9090-8E8EDC4BCFA6@apple.com> <BLU403-EAS179850B162A879E8A7BC47793C70@phx.gbl> <20131221231651.GX3245@audi.shelbyville.oz>
To: Ron <ron@debian.org>
In-Reply-To: <20131221231651.GX3245@audi.shelbyville.oz>
X-OriginalArrivalTime: 21 Dec 2013 23:25:11.0006 (UTC) FILETIME=[E4AE0FE0:01CEFEA3]
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Interoperability - what have we learned?
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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: Sat, 21 Dec 2013 23:25:15 -0000

On Dec 21, 2013, at 6:17 PM, "Ron" <ron@debian.org> wrote:
> 
> It ...  didn't?  SIP has so many ways to be completely non-interoperable
> that as a global standard it's been completely stillborn.  Codecs are
> the least of the many interoperability problems that ruined it by design.

[BA] Indeed. And let me suggest that we are in great danger of repeating this in RTCWEB, which today is not sufficiently specified to enable widespread interop - but could be if we were to spend our efforts more wisely.

v2.23.0 | Report a Bug | By Email