Re: [rtcweb] Plan for MTI video codec?

Jonathan Rosenberg <jdrosen@jdrosen.net> Sun, 19 October 2014 15:15 UTC

Return-Path: <jdrosen@jdrosen.net>
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 5B9FD1A1AF1 for <rtcweb@ietfa.amsl.com>; Sun, 19 Oct 2014 08:15:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level:
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001] 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 fkpGA7PVUFnn for <rtcweb@ietfa.amsl.com>; Sun, 19 Oct 2014 08:14:59 -0700 (PDT)
Received: from ecbiz71.inmotionhosting.com (ecbiz71.inmotionhosting.com [70.39.232.100]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 235721A1AE1 for <rtcweb@ietf.org>; Sun, 19 Oct 2014 08:14:59 -0700 (PDT)
Received: from mail-wg0-f43.google.com ([74.125.82.43]:39667) by ecbiz71.inmotionhosting.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.82) (envelope-from <jdrosen@jdrosen.net>) id 1XfsBv-0003pm-JX for rtcweb@ietf.org; Sun, 19 Oct 2014 11:14:55 -0400
Received: by mail-wg0-f43.google.com with SMTP id m15so3824909wgh.14 for <rtcweb@ietf.org>; Sun, 19 Oct 2014 08:14:42 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.194.2.129 with SMTP id 1mr26600812wju.12.1413731682293; Sun, 19 Oct 2014 08:14:42 -0700 (PDT)
Received: by 10.194.120.66 with HTTP; Sun, 19 Oct 2014 08:14:42 -0700 (PDT)
In-Reply-To: <CAHgZEq6GTk5ei+LLpWPM5povpieompD66VU9F+u7--WJVgapaQ@mail.gmail.com>
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> <CAHgZEq6GTk5ei+LLpWPM5povpieompD66VU9F+u7--WJVgapaQ@mail.gmail.com>
Date: Sun, 19 Oct 2014 11:14:42 -0400
Message-ID: <CA+23+fGWnWd0QEeCmZ=6BmJkPrUVW6cZ0jwmXA+fM88=_+_NWw@mail.gmail.com>
From: Jonathan Rosenberg <jdrosen@jdrosen.net>
To: Alexandre GOUAILLARD <agouaillard@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b343d30bb22180505c80eab
X-OutGoing-Spam-Status: No, score=-2.9
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - ecbiz71.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jdrosen.net
X-Get-Message-Sender-Via: ecbiz71.inmotionhosting.com: authenticated_id: jdrosen+jdrosen.net/only user confirmed/virtual account not confirmed
X-Source:
X-Source-Args:
X-Source-Dir:
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/GyZU3aJMTrtorMhzTEEG-JNQ4ok
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: Sun, 19 Oct 2014 15:15:01 -0000

I'm in favor of taking another run at this.

The working group has repeatedly said that an MTI codec is something we
need to produce. And its one of the issues holding up wider adoption of the
technology (not the only one for sure).

And things have changed since the last meeting, a year ago now (November in
Vancouver). Cisco's open264 plugin shipped and now just recently is
integrated into Firefox. iOS8 shipped with APIs for H264. There are other
things worth noting. Will this change the minds of everyone? Surely not.
Will it sway enough for us to achieve rough consensus? Maybe. IMHO - worth
finding out.

On Sat, Oct 18, 2014 at 5:08 PM, Alexandre GOUAILLARD <agouaillard@gmail.com
> wrote:

> +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
>
>    -
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>
>


-- 
Jonathan Rosenberg, Ph.D.
jdrosen@jdrosen.net
http://www.jdrosen.net