Re: [rtcweb] Microsoft tells W3C and IETF what we are doing no signs of offering real world interoperability

Harald Alvestrand <harald@alvestrand.no> Mon, 06 August 2012 19:43 UTC

Return-Path: <harald@alvestrand.no>
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 2B6A421F8470 for <rtcweb@ietfa.amsl.com>; Mon, 6 Aug 2012 12:43:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, 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 vqUYhJWnV0DW for <rtcweb@ietfa.amsl.com>; Mon, 6 Aug 2012 12:43:50 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 7F4C021F846F for <rtcweb@ietf.org>; Mon, 6 Aug 2012 12:43:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 1C8E639E0FA for <rtcweb@ietf.org>; Mon, 6 Aug 2012 21:43:48 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iukSn-qotTBa for <rtcweb@ietf.org>; Mon, 6 Aug 2012 21:43:45 +0200 (CEST)
Received: from [192.168.1.107] (unknown [188.113.88.47]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id C99D739E062 for <rtcweb@ietf.org>; Mon, 6 Aug 2012 21:43:45 +0200 (CEST)
Message-ID: <50201E78.3060602@alvestrand.no>
Date: Mon, 06 Aug 2012 21:43:52 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <53223349-A31F-4381-899F-82E29B0A0B6C@cisco.com> <CACHLvecT1AgJRo=xM5AH-fGZn+iYrtHqWk7Eym8QJn9U7YGcsg@mail.gmail.com> <CAPk5xQv_ZNqo66LfApshWtRrvXuBMscnp3+kY_GMiibgD1BCqw@mail.gmail.com>
In-Reply-To: <CAPk5xQv_ZNqo66LfApshWtRrvXuBMscnp3+kY_GMiibgD1BCqw@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------070203080905090407040901"
Subject: Re: [rtcweb] Microsoft tells W3C and IETF what we are doing no signs of offering real world interoperability
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: Mon, 06 Aug 2012 19:43:52 -0000

On 08/06/2012 09:27 PM, Rohit Puri wrote:
> Based on our experiences at TenHands Inc. where we are trying to build 
> a RT video-centric collaboration service, the goal cited in MSFT 
> proposal (http://html5labs.com/cu-rtc-web/cu-rtc-web.htm), namely:
>
> "*Flexibility in its support of popular media formats and codecs as 
> well as openness to future innovation*---A successful standard cannot 
> be tied to individual codecs, data formats or scenarios. They may soon 
> be supplanted by newer versions, which would make such a tightly 
> coupled standard obsolete just as quickly. The right approach is 
> instead to to support multiple media formats and to bring the bulk of 
> the logic to the application layer, enabling developers to innovate. "
>
> sounds like a great idea.
The WG agrees with you that multiple codecs should be supported, but the 
WG long ago came to consensus that there needs to be a 
mandatory-to-implement codec to prevent interoperability failure.
That consensus has been rough at times, but I believe it is still the 
consensus.

See section 2.3 of draft-ietf-rtcweb-overview.