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

Justin Uberti <juberti@google.com> Mon, 06 August 2012 20:20 UTC

Return-Path: <juberti@google.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 2698A11E80A6 for <rtcweb@ietfa.amsl.com>; Mon, 6 Aug 2012 13:20:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.719
X-Spam-Level:
X-Spam-Status: No, score=-102.719 tagged_above=-999 required=5 tests=[AWL=0.257, 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 uffN2i+S1BCr for <rtcweb@ietfa.amsl.com>; Mon, 6 Aug 2012 13:20:05 -0700 (PDT)
Received: from mail-qc0-f172.google.com (mail-qc0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id C61A511E80A5 for <rtcweb@ietf.org>; Mon, 6 Aug 2012 13:20:04 -0700 (PDT)
Received: by qcac10 with SMTP id c10so2321476qca.31 for <rtcweb@ietf.org>; Mon, 06 Aug 2012 13:20:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-system-of-record; bh=6IKShilgXVHsg85VVpt/k/4z0kqhCDiGFqljo5/jzhw=; b=eK2a5CfGyhZIQ8OYKNcGqQufdH7rH9A20to+fLZH99V0TqR5M19F9U2y9dxEs5+b/t yMrr1qtusymwwk7HnYlpiVcZ1pj5b0oj0K5h4wlrrgg0c4+dRvs5VwoN2XCKMeDrjNWU vfP7qvDPPxzQ4JhsAkQ5jPmQ4k9IMs5Au+pvAov4lPP9lqMwon4f7w0kzieshy0O8HU+ Fc7yfWZX1+HISFRXGsZ0Xsf3+ofjoLedMsXre0cSX5dCtPuLEHbIjmHRRvhF3VPDA8Pb aX9e6rAM0wjLH0oJIxqltN6YPowESuA33uJ2SB+BhhldFZy9uz9dx4JZyM2gXuWaPcHf u97g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-system-of-record:x-gm-message-state; bh=6IKShilgXVHsg85VVpt/k/4z0kqhCDiGFqljo5/jzhw=; b=nZCbMhRQG+SkXBA656h/JzV6+KJpCJfYmV75hdNVKOZEVtfkK16WSuDrHi1gDBeM0u Cc1p5Y66iZDMhcUN+mIjeM7v3kqOAllNLYzHrL+s30Z8sROik92nCYeLV/ZOFW0153Ph y5xTwXnuxf4TRvCL7M2HVa4xRuQ2buKakQZOSYSRBMQVzjiEHWCsGy+9X28h9EKHBGDC OO/I5raPCfIdyVsSNIBk/zoSfbmDs2C/TmTinakHmaUdSG9MWYfEcD4q1lz5sO2trzbp qPclpqAmQsiP/xAvYS+GjYrBgk3EAzFN91+eF/xHVDDRt44HYH2lkwmtIFP6fazeWvHi SD5Q==
Received: by 10.224.180.146 with SMTP id bu18mr20066044qab.10.1344284404230; Mon, 06 Aug 2012 13:20:04 -0700 (PDT)
Received: by 10.224.180.146 with SMTP id bu18mr20066031qab.10.1344284404113; Mon, 06 Aug 2012 13:20:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.218.80 with HTTP; Mon, 6 Aug 2012 13:19:43 -0700 (PDT)
In-Reply-To: <AEF5DA45-0307-4170-A8B4-BAE6B25248C8@cisco.com>
References: <53223349-A31F-4381-899F-82E29B0A0B6C@cisco.com> <CACHLvecT1AgJRo=xM5AH-fGZn+iYrtHqWk7Eym8QJn9U7YGcsg@mail.gmail.com> <CAPk5xQv_ZNqo66LfApshWtRrvXuBMscnp3+kY_GMiibgD1BCqw@mail.gmail.com> <AEF5DA45-0307-4170-A8B4-BAE6B25248C8@cisco.com>
From: Justin Uberti <juberti@google.com>
Date: Mon, 6 Aug 2012 22:19:43 +0200
Message-ID: <CAOJ7v-093zyfumK_z5dGhr8msNatfBABk6wD=g80GH2LG4055Q@mail.gmail.com>
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Content-Type: multipart/alternative; boundary=485b397dcfcd6260fc04c69e9aed
X-System-Of-Record: true
X-Gm-Message-State: ALoCoQn5b3E8W0hgpmYSk0CYFQkeYteV8vUoFgKzCzTGrYPKZsUGxI6RxNAMDs0Ydxaqltu9/dHHAtRRJ4zr3XeVIMRS+Khz6DXl5isGQaHDUlu6BE14dhXpSu1dJJeqJsEqw+nYDOHB9J9h91OGt/j4wl7pnjUrzUCqR7e/BtJrMTM6SqrKr/fExX4Nsdgkc8SaKBBMW+8z
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>
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 20:20:06 -0000

Note also that pre- and post-processing of media are not covered by this
proposal, those concepts are in the domain of MediaStream (and
post-processing is possible today through various methods).

In fact, I think the primary novel features of this proposal are:
- SessionDescriptions are true objects, instead of wrappers around SDP
- Additional control over the ICE Agent

However, no use cases have yet been outlined that require this
functionality.


On Mon, Aug 6, 2012 at 10:00 PM, Cullen Jennings (fluffy)
<fluffy@cisco.com>wrote;wrote:

>
> On Aug 6, 2012, at 1: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.
>
> and every proposal from any company or individual that I can recall being
> sent to theses WGs has had exactly that property. So it is sort of
> disappointing to see Microsoft present it as if their proposal was somehow
> different in this regards.
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>