Re: [rtcweb] Plan for MTI video codec?

Alexandre GOUAILLARD <agouaillard@gmail.com> Sat, 18 October 2014 21:08 UTC

Return-Path: <agouaillard@gmail.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 6D0F81A1A70 for <rtcweb@ietfa.amsl.com>; Sat, 18 Oct 2014 14:08:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 kIQHYC_nRIAj for <rtcweb@ietfa.amsl.com>; Sat, 18 Oct 2014 14:08:04 -0700 (PDT)
Received: from mail-ob0-x22c.google.com (mail-ob0-x22c.google.com [IPv6:2607:f8b0:4003:c01::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E445B1A1A6E for <rtcweb@ietf.org>; Sat, 18 Oct 2014 14:08:03 -0700 (PDT)
Received: by mail-ob0-f172.google.com with SMTP id vb8so2188610obc.17 for <rtcweb@ietf.org>; Sat, 18 Oct 2014 14:08:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=JV8ryEV4SIkxCXmighrXGv5Jx1wTMytj1T3SL7sbTMA=; b=ubWlEg3iOA2v0Vx9HBV7BRftlHdPHjJkAxE0sQoOS2Od9anEa3d2v8skXjLFUAWWGI npZyN2Muua+OnueLaPMqZ1bmpc+aBfwRnYt0ZRDHAbUoB1ZShdJpdFroWBvJ26B2l58l WpExyxa1yL0JmU7WLP0uKRrhy2+U9VYlIieUWE1oY/es6z4RA/Gmz0aZJO/M0gbYjH6M T7OpoNi4JX6bOQnmcDo22FdaXDc7eSxIICzzIBUYzuyBvMeHS4+/jDBoK9dahFlEeKV4 0FTGIuxNQPBeDDY9LXZ0cu9ZJL8NP+KedxajRfPxW3f+kfxrr2TRLCCQWeqqius3ZvRb 0rlA==
MIME-Version: 1.0
X-Received: by 10.202.206.144 with SMTP id e138mr3257009oig.64.1413666483270; Sat, 18 Oct 2014 14:08:03 -0700 (PDT)
Received: by 10.202.66.5 with HTTP; Sat, 18 Oct 2014 14:08:03 -0700 (PDT)
In-Reply-To: <544117FB.6050706@alvestrand.no>
References: <CAGTXFp-HVJDwd86207PNM2QVYO4Z_K4WF-KarnRs1fb7nvy4zA@mail.gmail.com> <CA+9kkMDfES8gpi0-PTXpCnQHjFYUSF2r44TNzH5B4UfDGo8PtA@mail.gmail.com> <CAGTXFp8O-7ACksk3v3f=KjCkcDb4e8G=t-e=EJ1503vt7TkpCQ@mail.gmail.com> <CAGTXFp867AMUZ_fEKxG9uAoR1H1AirVHi3-ayJ=KTQk9L+C7+g@mail.gmail.com> <CA+9kkMAZufR7gUrwkS7Tf5GOfg+ZtsZWGcn-8YLCvnmYnTgfFw@mail.gmail.com> <544035DE.8000606@matthew.at> <CABkgnnUNgWaauS6-nZ5fcExjsMPy4ZGPXaahduzA39=iqh9+fQ@mail.gmail.com> <D5D11F2B-9E32-4932-A601-F1D7FD50C706@gmail.com> <544117FB.6050706@alvestrand.no>
Date: Sun, 19 Oct 2014 05:08:03 +0800
Message-ID: <CAHgZEq6GTk5ei+LLpWPM5povpieompD66VU9F+u7--WJVgapaQ@mail.gmail.com>
From: Alexandre GOUAILLARD <agouaillard@gmail.com>
To: Harald Alvestrand <harald@alvestrand.no>
Content-Type: multipart/alternative; boundary=001a113ad9f090fbc80505b8e028
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/fhm4bBh6gkhrpl8yvpkp4XkchwY
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Plan for MTI video 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: Sat, 18 Oct 2014 21:08:06 -0000

+1 to not having MTI codec discussion unless some progress has been made on
VP8 at MPEG. Any news on that? I'm sharing harald's  feeling that there was
no change on the members position.

On Fri, Oct 17, 2014 at 9:22 PM, Harald Alvestrand <harald@alvestrand.no>
wrote:

> On 10/17/2014 12:02 AM, Bernard Aboba wrote:
>
>> One thing we could do instead of wasting time on MTI is to actually make
>> progress on Sections 4.2 - 4.4 of draft-IETF-RTCWEB-video, so we could
>> actually interoperate regardless of the codec.
>>
>
> The big argument for an MTI is actually the one stated in -overview: It
> guards against interoperability failure.
>
> I would like to have an ecosystem where one can field a box, connect it to
> everything else, and run well for *some* level of "well" - and I would
> prefer that ecosystem to be one where it's possible to field the box
> without making prior arrangements with anyone about licenses.
>
> This argument hasn't changed one whit since last time we discussed it. And
> I don't see much movement on the specifics of the proposals either.
>
> We'll have to interoperate well with the codecs we field. So using some
> time to discuss draft-ietf-rtcweb-video seems to make sense. (And 4.1 isn't
> finished either. There's one sentence that needs to be removed.)
>
> I wouldn't say I'd be happy to not discuss this in Honolulu. But I'd
> prefer to re-discuss based on the knowledge that some significant players
> have actually changed their minds.
>
> At the moment, I don't see signs that any of the poll respondents have
> said "I have changed my mind".
>
> Harald
>
>
>
>
>>
>>
>>  On Oct 16, 2014, at 2:28 PM, Martin Thomson <martin.thomson@gmail.com>
>>> wrote:
>>>
>>>  On 16 October 2014 14:17, Matthew Kaufman <matthew@matthew.at> wrote:
>>>> And that's because something substantive has changed, or simply because
>>>> wasting the WG time on this again is more entertaining than actually
>>>> finishing a specification that can be independently implemented by all
>>>> browser vendors? (A specification that we are nowhere near having, as
>>>> far as
>>>> I can tell)
>>>>
>>> Personally, I've found the reprieve from this fight refreshing.  And
>>> it would appear that we've made some real progress as a result.  I'd
>>> suggest that if we don't have new information, we continue to spend
>>> our time productively.  If we can't find topics to occupy our meeting
>>> agenda time, then maybe we can free an agenda slot.
>>>
>>> _______________________________________________
>>> 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
>>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>



-- 
Alex. Gouaillard, PhD, PhD, MBA
------------------------------------------------------------------------------------
CTO - Temasys Communications, S'pore / Mountain View
President - CoSMo Software, Cambridge, MA
------------------------------------------------------------------------------------
sg.linkedin.com/agouaillard

   -