Re: [rtcweb] VP8 vs H.264 - the core issue

Christer Holmberg <christer.holmberg@ericsson.com> Fri, 25 October 2013 11:26 UTC

Return-Path: <christer.holmberg@ericsson.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 714B311E83C1 for <rtcweb@ietfa.amsl.com>; Fri, 25 Oct 2013 04:26:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.792
X-Spam-Level:
X-Spam-Status: No, score=-3.792 tagged_above=-999 required=5 tests=[AWL=-1.194, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 CYQc6tJuJi7H for <rtcweb@ietfa.amsl.com>; Fri, 25 Oct 2013 04:25:54 -0700 (PDT)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id 86F6B11E8316 for <rtcweb@ietf.org>; Fri, 25 Oct 2013 04:25:36 -0700 (PDT)
X-AuditID: c1b4fb38-b7f178e00000233b-a7-526a552f60fb
Received: from ESESSHC006.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id 00.8C.09019.F255A625; Fri, 25 Oct 2013 13:25:35 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.201]) by ESESSHC006.ericsson.se ([153.88.183.36]) with mapi id 14.02.0328.009; Fri, 25 Oct 2013 13:25:35 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>, Leon Geyser <lgeyser@gmail.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] VP8 vs H.264 - the core issue
Thread-Index: AQHO0WFQ3TqGWYrUlUulPtrUXYOsppoFQslwgAAEDsCAAABB/Q==
Date: Fri, 25 Oct 2013 11:25:34 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C4F4C3C@ESESSMB209.ericsson.se>
References: <52681A96.2020904@alvestrand.no> <526826AF.5030308@librevideo.org> <52690090.2050609@alvestrand.no> <BBE9739C2C302046BD34B42713A1E2A22DFCD683@ESESSMB105.ericsson.se> <AE1A6B5FD507DC4FB3C5166F3A05A4843D45DC08@TK5EX14MBXC266.redmond.corp.microsoft.com> <5269764C.4030801@librevideo.org> <52698758.5040404@bbs.darktech.org> <CAD6AjGSb5syh0HO+89fH8cGZ0zqM6gYLPj3aeTRQLN0u8W4cSg@mail.gmail.com> <5269F098.2020904@alvestrand.no> <E44893DD4E290745BB608EB23FDDB7620A0F272E@008-AM1MPN1-043.mgdnok.nokia.com> <949EF20990823C4C85C18D59AA11AD8B0BF358@FR712WXCHMBA11.zeu.alcatel-lucent.com> <CAGgHUiRtXUAJTotAFX7YwQ6cS_OD-MpAb+898c6OYxm7D5xXKw@mail.gmail.com>, <949EF20990823C4C85C18D59AA11AD8B0BF4A7@FR712WXCHMBA11.zeu.alcatel-lucent.com>
In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B0BF4A7@FR712WXCHMBA11.zeu.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.146]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1C4F4C3CESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrHLMWRmVeSWpSXmKPExsUyM+Jvja5+aFaQwcZjmhZPG88yWnSvnsVm sfZfO7sDs0frs72sHjtn3WX3WLLkJ1MAcxSXTUpqTmZZapG+XQJXxoKfm1kKLgdV/Gh/xdbA uNWti5GDQ0LARGLOltouRk4gU0ziwr31bF2MXBxCAkcZJU7cXM0M4SxhlNj65Tk7SAObgIVE 9z9tkLiIQDOjxI3u1Ywg3cICxhJL/l5nArFFgIb+f9QDZTtJLGiZygpiswioSnzZ/4EdxOYV 8JXo2LsfattnVonHneeZQRKcAtESj0/8BWtgBDrp+6k1YIOYBcQlbj2ZzwRxqoDEkj0Q9RIC ohIvH/9jhbCVJH5suMQCciizQL7EqXnyELsEJU7OfMIygVFkFpJJsxCqZiGpgijRk7gxdQob hK0tsWzha2YIW1dixr9DUDXWEhduXWNEVrOAkWMVI0dxanFSbrqRwSZGYJwd3PLbYgfj5b82 hxilOViUxHk/vnUOEhJITyxJzU5NLUgtii8qzUktPsTIxMEp1cDYfutc5k/mlUHVfZq/ts6/ k7hgwf6qKefui+u1qnUYiqxTtd2v2lViKHp/BXNgYOHM+X2Mxvt9TDmX+Szf59/ed3TZnTOi XXcWy+52LJ+6NvH71n8nN1u8P72nM+nDug7+99Mv7Nyq86y6/Hu8y8q5QfzthRPe3/z5oafp Rka89lkDK0eVLikHJZbijERDLeai4kQAeHlPxoECAAA=
Subject: Re: [rtcweb] VP8 vs H.264 - the core issue
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: Fri, 25 Oct 2013 11:26:04 -0000


>While VP8 might give you what you want in webrtc islands, it would not be able to communicate outside those islands, where the predominant codec is still H.248.

If we choose the H.248 codec, we also need to choose an MTI encoding: text or binary ;)

Regards,

Christer


________________________________
From: Leon Geyser [mailto:lgeyser@gmail.com]
Sent: 25 October 2013 10:05
To: rtcweb@ietf.org
Cc: Markus.Isomaki@nokia.com; harald@alvestrand.no; DRAGE, Keith (Keith)
Subject: Re: [rtcweb] VP8 vs H.264 - the core issue

It would be nice if video just works for the end user instead of them having to install a different browser or buying a different device with a different browser.

I personally think there needs to be a MTI video codec even if it is an old codec such as H.261. Although the codec should not require a lot of bandwidth to look decent which excludes something such as MJPEG.


On 25 October 2013 10:50, DRAGE, Keith (Keith) <keith.drage@alcatel-lucent.com<mailto:keith.drage@alcatel-lucent.com>> wrote:
Agree

We can either explicitly make a "no MTI" decision, or just let it become the default by the absence of agreement.

Keith

> -----Original Message-----
> From: rtcweb-bounces@ietf.org<mailto:rtcweb-bounces@ietf.org>
> [mailto:rtcweb-bounces@ietf.org<mailto:rtcweb-bounces@ietf.org>] On Behalf Of Markus.Isomaki@nokia.com<mailto:Markus.Isomaki@nokia.com>
> Sent: 25 October 2013 09:04
> To: harald@alvestrand.no<mailto:harald@alvestrand.no>; rtcweb@ietf.org<mailto:rtcweb@ietf.org>
> Subject: Re: [rtcweb] VP8 vs H.264 - the core issue
>
> Hi,
>
> Harald Alvestrand wrote:
> >
> > Formalistically, the people who argue for abandoning an
> MTI, like the
> > people who argue for adapting an antiquated codec, have not
> put in a
> > draft by the chairs' deadline of October 6, so have not
> made a proposal.
> >
> > But I'm not the one who argued for this to be put on the
> agenda for 2 hours.
> > The people who pushed for this to be on the agenda for 2
> hours need to
> > come forward and say why they believe this is a good use of
> our time.
> > I haven't yet heard a VP8 proponent saying so.
> >
>
> I thought it has been mainly the VP8 proponents who have
> insisted to continue this discussion and have it on the agenda.
>
> I am a H.264 proponent but it's clear to me there is no
> consensus, no substantially new information since March, and
> for that reason the IETF should not pick either H.264 or VP8
> as *mandatory*. And consequently 2 hours is too much time for this.
>
> It is useful to discuss pros and cons of H.264 and VP8 and
> compare them, since most likely every WebRTC endpoint will
> implement at least one of them, but I think we need to stop
> pushing for the decision of mandating one of them.
>
> Of course, if we come back to this issue every November, we
> can eventually choose H.264 as mandatory, after all of its
> IPR has expired :-)
>
> Markus
> _______________________________________________
> 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