Re: [rtcweb] confirming sense of the room: mti codec

Justin Uberti <juberti@google.com> Tue, 09 December 2014 00:21 UTC

Return-Path: <juberti@google.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 8CC841A028A for <rtcweb@ietfa.amsl.com>; Mon, 8 Dec 2014 16:21:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level:
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 4eMAM4ey-bij for <rtcweb@ietfa.amsl.com>; Mon, 8 Dec 2014 16:21:16 -0800 (PST)
Received: from mail-vc0-x22e.google.com (mail-vc0-x22e.google.com [IPv6:2607:f8b0:400c:c03::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7DB781A0079 for <rtcweb@ietf.org>; Mon, 8 Dec 2014 16:21:16 -0800 (PST)
Received: by mail-vc0-f174.google.com with SMTP id id10so2693179vcb.19 for <rtcweb@ietf.org>; Mon, 08 Dec 2014 16:21:15 -0800 (PST)
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; bh=e8Djgr1kKS6INWF3VOWFBS6kWcuO8X+/Gans8OnKLkM=; b=WdLq5mNf1wBXLKexfHYw/QX0yEEc38f+vxZAWNTQ7Ozpjj4r4w+CAUwExogJgmzSrz r0E8Q33kbW4N/m0RW1uynPCwv2qFKe0Nt5CxFObrwHTKTmK355UfdkKJi4WRflUU+Lyy f3YU7fOtggPPIleNMpa3Crmy5C+xxyzxViNLaF7oMrnojR/7GEgc4HyXg1scGu4Nqc+r cZsh8ojQGOI5Eps1fCv18Pj9fVx9F7RVqUFGgaShuJsqp8bTKyDgicjNi5zKQsPC8kbN 2o4k6kje7PdI4neLnO2aZoAKZOSovcZseCIshIjO58zIZZuaV87poFop0IQnbeTRL8I2 lGMg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=e8Djgr1kKS6INWF3VOWFBS6kWcuO8X+/Gans8OnKLkM=; b=hVFOuImz54MWIVfXyO7GSn0gxKpJ/nKaz0Cg4ZbDEUZogpcwAobWS1E9ylSSqwvqGm uEWqvXmdyLIf/4W1heAfmXe3jfOFBt/aIJfx0lI2U17ocucLIxMjg5QGIJ230ibjjV5U iBV+3TBVcMq81W4efwDDsct4ZjBK4RR2NrCBb3OvlWCPRUsXkWqye3t8NTEaaERiJy3N tu7ONBQfTS/f7Fuy99glWh4dRx7gRPvpRlZxs6nrpM2ZxaWBaykyewozF+10UdQW8Q6v oeMFmPZWRctQBN3L58Ry5JrFPEQJnL18kPLluc1QYmqK/6YEj/JE1jXDyx3nhK2/I9c3 mXxw==
X-Gm-Message-State: ALoCoQlNDrqafDZyBAHdxTIkszahLIiGYgONNZdnXUZHzmIYf8eZu2EPo/Y5MnbxbeqsLKJGnHzB
X-Received: by 10.52.27.237 with SMTP id w13mr65499vdg.68.1418084475528; Mon, 08 Dec 2014 16:21:15 -0800 (PST)
MIME-Version: 1.0
Received: by 10.52.237.130 with HTTP; Mon, 8 Dec 2014 16:20:55 -0800 (PST)
In-Reply-To: <BBF5DDFE515C3946BC18D733B20DAD233998AC05@XMB122CNC.rim.net>
References: <E3FA0C72-48C5-465E-AE15-EB19D8D563A7@ieca.com> <54820E74.90201@mozilla.com> <54861AD6.8090603@reavy.org> <BBF5DDFE515C3946BC18D733B20DAD233998AC05@XMB122CNC.rim.net>
From: Justin Uberti <juberti@google.com>
Date: Mon, 8 Dec 2014 16:20:55 -0800
Message-ID: <CAOJ7v-2pKjpvFnTtsGCZk24xqgSf9Vd_AdOgv9LkDfyQ+qTGYA@mail.gmail.com>
To: Andrew Allen <aallen@blackberry.com>
Content-Type: multipart/alternative; boundary=20cf307abed56d06840509bd85dc
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/H0w6O5QeOWPYPDNsS5wiemmtVT0
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] confirming sense of the room: mti codec
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: Tue, 09 Dec 2014 00:21:18 -0000

On Mon, Dec 8, 2014 at 3:28 PM, Andrew Allen <aallen@blackberry.com> wrote:

> We are not re-opening this discussion. This list discussion is the
> decision making process.
>
> What took place in Honolulu was only a consensus hum of those present in
> the room.
>
> In IETF all decisions are made on the list and it was clearly stated by
> the chair in Honolulu that the decision would need to be endorsed on the
> list.
>
> On 1) We have committed to an MTI video codec
>
> I note the small word "an".


> If we decide on two MTI video codecs then we have clearly failed to meet
> this commitment.
>

Goodness. If you're going to descend to this level of pedantry, at least
look at the charter:

*"6. Define a set of media formats that must or should be supported by a
client to improve interoperability."*

Clearly this compromise is entirely satisfactory in this regard.

>
> On 3) This is the only proposal that gets support from both camps
>
> As David pointed out we are not in two monolithic camps (this isn't the
> cold war here). Different companies and different individuals have
> different positions for different reasons. The fact that some people who
> might have been perceived as being in "one camp" have found a way to agree
> to a "compromise" based upon a definition that doesn't force them in their
> product to implement what they don't agree to implement does not mean that
> the fundamental reason behind the difficulty in reaching consensus on MTI
> video codecs by those whose products would be forced to implement both
> codecs has changed.
>
> It's very easy to agree to someone else to have to do something that you
> are not willing to do yourself.
>
> Andrew
>
> -----Original Message-----
> From: rtcweb [mailto:rtcweb-bounces@ietf.org] On Behalf Of Maire Reavy
> Sent: Monday, December 08, 2014 4:41 PM
> To: rtcweb@ietf.org
> Subject: Re: [rtcweb] confirming sense of the room: mti codec
>
> On 12/5/2014 2:58 PM, Jean-Marc Valin wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Considering that:
> > 1) We have committed to an MTI video codec
> > 2) All consensus calls on "VP8 only" and "H.264 only" have failed
> > 3) This is the only proposal that gets support from both camps I
> > strongly support this MTI proposal.
> > Please, let's close this debate once and for all. This compromise is
> > by no means great, but it's much better than anything else we're going
> > to get otherwise (i.e. more wasted time and still no MTI).
> A big +1
>
> We have spent *so* many hours already considering, discussing, & debating
> what to do about the MTI video codec.  One could argue an "insane amount"
> of time relative to the other issues we need to resolve.  We did this
> because most of us realized that "no MTI" could be horrific for the
> standard.  We should embrace consensus around anything less than horrific,
> and most of us agree that this compromise is less than horrific (not great,
> but less than horrific).
>
> Right now I fear we're on the verge of shooting ourselves in the foot or
> head (I'm not sure which) by reopening this discussion even though we're in
> sight of the end.  I ask that the working group and the chairs put the
> proverbially safety back on the gun, declare consensus on this
> less-than-horrific proposal, and finish our work on "v1.0" of the spec.
>
> Please.
>
> -Maire
> -------------------------
> Maire Reavy
> mdr@reavy.org
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>