Re: [rtcweb] Plan for MTI video codec?
"Jeremy Laurenson (jlaurens)" <jlaurens@cisco.com> Sun, 19 October 2014 18:00 UTC
Return-Path: <jlaurens@cisco.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 34E791A1A71 for <rtcweb@ietfa.amsl.com>; Sun, 19 Oct 2014 11:00:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 PhGzcHzfID_T for <rtcweb@ietfa.amsl.com>; Sun, 19 Oct 2014 11:00:00 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B9171A19FE for <rtcweb@ietf.org>; Sun, 19 Oct 2014 11:00:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=14013; q=dns/txt; s=iport; t=1413741601; x=1414951201; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=W5RZnFd7nzhvaO5ZDkaVT1e4OgxlawJQI2pbYldDOAw=; b=EJVl2vr/E3u8LkLILIjm8zZ7RDN3SB4ZCoyCk3s7r2IXI+5pO27dGpmB elvaLqEY2n2j4gFmuzExxKxWJ705yK6dnF/is7YAcqzRTBhkRznHxF5oB 0zbr9IDQ3kbsgzSZKk7DmPbbi8aaS04A0zQCYgFx9HkdXQ6dh0JpJdOkP A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmwFAFH6Q1StJV2P/2dsb2JhbABbgkVGU1jKJ4FmAQmGelQCgQ4WAXILhAMBAQQBAQFSGRsCAQg/ByEGCxQRAgQTGogRAxENuRMNhjEBAQEBAQEBAQEBAQEBAQEBAQEBAQEXjh2CMAuDLYEeBYYti1OERoUCghGPSIZagV2CGmyCSwEBAQ
X-IronPort-AV: E=Sophos;i="5.04,749,1406592000"; d="scan'208,217";a="364582417"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by rcdn-iport-8.cisco.com with ESMTP; 19 Oct 2014 18:00:00 +0000
Received: from xhc-aln-x05.cisco.com (xhc-aln-x05.cisco.com [173.36.12.79]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id s9JHxxqr020140 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <rtcweb@ietf.org>; Sun, 19 Oct 2014 17:59:59 GMT
Received: from xmb-rcd-x03.cisco.com ([169.254.7.63]) by xhc-aln-x05.cisco.com ([173.36.12.79]) with mapi id 14.03.0195.001; Sun, 19 Oct 2014 12:59:59 -0500
From: "Jeremy Laurenson (jlaurens)" <jlaurens@cisco.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] Plan for MTI video codec?
Thread-Index: AQHP669o0YA0VVXvZkG/wkm6G20Ux5w3tZ/C
Date: Sun, 19 Oct 2014 17:59:58 +0000
Message-ID: <16C290A2-EB7C-4D77-8871-C7E82B374C48@cisco.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>, <CA+23+fGWnWd0QEeCmZ=6BmJkPrUVW6cZ0jwmXA+fM88=_+_NWw@mail.gmail.com>
In-Reply-To: <CA+23+fGWnWd0QEeCmZ=6BmJkPrUVW6cZ0jwmXA+fM88=_+_NWw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_16C290A2EB7C4D778871C7E82B374C48ciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/ejCFdFcVuxWAOgVI5iBOepw62YE
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 18:00:03 -0000
I am hearing a lot of folks outside this group losing faith and beginning to talk about writing off WebRTC for lack of consensus (including analysts). I am therefore in favor of a very finite amount of "new-news" discussion and another attempt at consensus. We either do or don't have it. On Oct 19, 2014, at 11:15 AM, Jonathan Rosenberg <jdrosen@jdrosen.net<mailto:jdrosen@jdrosen.net>> wrote: 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<mailto: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<mailto: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<mailto:martin.thomson@gmail.com>> wrote: On 16 October 2014 14:17, Matthew Kaufman <matthew@matthew.at<mailto: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<mailto:rtcweb@ietf.org> https://www.ietf.org/mailman/listinfo/rtcweb _______________________________________________ rtcweb mailing list rtcweb@ietf.org<mailto:rtcweb@ietf.org> https://www.ietf.org/mailman/listinfo/rtcweb _______________________________________________ rtcweb mailing list rtcweb@ietf.org<mailto: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<http://sg.linkedin.com/agouaillard> * _______________________________________________ rtcweb mailing list rtcweb@ietf.org<mailto:rtcweb@ietf.org> https://www.ietf.org/mailman/listinfo/rtcweb -- Jonathan Rosenberg, Ph.D. jdrosen@jdrosen.net<mailto:jdrosen@jdrosen.net> http://www.jdrosen.net _______________________________________________ rtcweb mailing list rtcweb@ietf.org<mailto:rtcweb@ietf.org> https://www.ietf.org/mailman/listinfo/rtcweb
- [rtcweb] Plan for MTI video codec? Victor Pascual Avila
- Re: [rtcweb] Plan for MTI video codec? Victor Pascual Avila
- Re: [rtcweb] Plan for MTI video codec? Ted Hardie
- Re: [rtcweb] Plan for MTI video codec? Bernard Aboba
- Re: [rtcweb] Plan for MTI video codec? Matthew Kaufman
- Re: [rtcweb] Plan for MTI video codec? Martin Thomson
- Re: [rtcweb] Plan for MTI video codec? Peter Saint-Andre - &yet
- Re: [rtcweb] Plan for MTI video codec? Bernard Aboba
- Re: [rtcweb] Plan for MTI video codec? Cavigioli, Chris
- Re: [rtcweb] Plan for MTI video codec? Makaraju, Maridi Raju (Raju)
- Re: [rtcweb] Plan for MTI video codec? Roman Shpount
- Re: [rtcweb] Plan for MTI video codec? DRAGE, Keith (Keith)
- Re: [rtcweb] Plan for MTI video codec? Harald Alvestrand
- Re: [rtcweb] Plan for MTI video codec? Alexandre GOUAILLARD
- [rtcweb] VP8 in ISO (Re: Plan for MTI video codec… Harald Alvestrand
- Re: [rtcweb] VP8 in ISO (Re: Plan for MTI video c… Alexandre GOUAILLARD
- Re: [rtcweb] Plan for MTI video codec? Jonathan Rosenberg
- Re: [rtcweb] Plan for MTI video codec? Bernard Aboba
- Re: [rtcweb] Plan for MTI video codec? Alexandre GOUAILLARD
- Re: [rtcweb] Plan for MTI video codec? Watson Ladd
- Re: [rtcweb] Plan for MTI video codec? Jeremy Laurenson (jlaurens)
- Re: [rtcweb] Plan for MTI video codec? Jonathan Rosenberg
- Re: [rtcweb] Plan for MTI video codec? Alexandre GOUAILLARD
- [rtcweb] Scheduling a separate slot for MTI VC Di… Emil Ivov
- Re: [rtcweb] Plan for MTI video codec? Bernard Aboba
- Re: [rtcweb] Plan for MTI video codec? Harald Alvestrand
- Re: [rtcweb] Plan for MTI video codec? Bernard Aboba
- Re: [rtcweb] Plan for MTI video codec? Stephan Wenger
- Re: [rtcweb] Plan for MTI video codec? Cavigioli, Chris
- Re: [rtcweb] Plan for MTI video codec? Ron
- Re: [rtcweb] Plan for MTI video codec? Ca By
- Re: [rtcweb] Plan for MTI video codec? Justin Uberti
- Re: [rtcweb] Plan for MTI video codec? Victor Pascual
- Re: [rtcweb] Plan for MTI video codec? Cavigioli, Chris
- Re: [rtcweb] Plan for MTI video codec? Barry Dingle
- Re: [rtcweb] Plan for MTI video codec? DRAGE, Keith (Keith)
- Re: [rtcweb] Plan for MTI video codec? Martin Thomson
- Re: [rtcweb] Plan for MTI video codec? Andrew Allen
- Re: [rtcweb] Plan for MTI video codec? DRAGE, Keith (Keith)
- Re: [rtcweb] Plan for MTI video codec? Justin Uberti
- Re: [rtcweb] Plan for MTI video codec? Roman Shpount
- Re: [rtcweb] Plan for MTI video codec? Iñaki Baz Castillo
- Re: [rtcweb] Plan for MTI video codec? Barry Dingle
- Re: [rtcweb] Plan for MTI video codec? Bernard Aboba
- Re: [rtcweb] Plan for MTI video codec? Victor Pascual
- Re: [rtcweb] Plan for MTI video codec? Harald Alvestrand
- Re: [rtcweb] Plan for MTI video codec? Olle E. Johansson
- Re: [rtcweb] Plan for MTI video codec? DRAGE, Keith (Keith)
- Re: [rtcweb] Plan for MTI video codec? Ted Hardie
- Re: [rtcweb] Plan for MTI video codec? Stephan Wenger
- Re: [rtcweb] Plan for MTI video codec? Mohammed Raad
- Re: [rtcweb] Plan for MTI video codec? Cavigioli, Chris
- Re: [rtcweb] Plan for MTI video codec? Leon Geyser
- Re: [rtcweb] Plan for MTI video codec? Iñaki Baz Castillo
- Re: [rtcweb] Plan for MTI video codec? Ted Hardie
- Re: [rtcweb] Plan for MTI video codec? Stephan Wenger
- Re: [rtcweb] Plan for MTI video codec? Randell Jesup
- Re: [rtcweb] Plan for MTI video codec? Adam Roach
- Re: [rtcweb] Plan for MTI video codec? Cavigioli, Chris
- Re: [rtcweb] Plan for MTI video codec? Florian Weimer
- Re: [rtcweb] Plan for MTI video codec? markus.isomaki
- Re: [rtcweb] Plan for MTI video codec? Roman Shpount
- Re: [rtcweb] Plan for MTI video codec? Ron
- Re: [rtcweb] Plan for MTI video codec? markus.isomaki
- Re: [rtcweb] Plan for MTI video codec? Mohammed Raad
- Re: [rtcweb] Plan for MTI video codec? Ron