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

Leon Geyser <lgeyser@gmail.com> Fri, 25 October 2013 09:05 UTC

Return-Path: <lgeyser@gmail.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 47A1B11E82FC for <rtcweb@ietfa.amsl.com>; Fri, 25 Oct 2013 02:05:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-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 CWZ-g8pd9jVS for <rtcweb@ietfa.amsl.com>; Fri, 25 Oct 2013 02:05:34 -0700 (PDT)
Received: from mail-lb0-x231.google.com (mail-lb0-x231.google.com [IPv6:2a00:1450:4010:c04::231]) by ietfa.amsl.com (Postfix) with ESMTP id BB6E611E82C8 for <rtcweb@ietf.org>; Fri, 25 Oct 2013 02:05:23 -0700 (PDT)
Received: by mail-lb0-f177.google.com with SMTP id u14so490633lbd.22 for <rtcweb@ietf.org>; Fri, 25 Oct 2013 02:05:13 -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=i637FphcrUAUDcBW4yGJU81OlpRqdMWEDAuVS+H0YmU=; b=nXggA9imDVm0z/fk2ggP27wRakQbzakavebzC/K9njxbeZfs+su7KIg5J8Seg0Cq6L 0wPyyqv79akwOiOb5lOc671Rrjs2LnFQNI3moHZnwutDtop5yTdXoGItwnIR+4RZZ//L U6JPDfOzREFLE85VxFnvFcjRr2VOhtiX0SSsJRWbR3NlGbIU+BHMa2D3N5SGfN3gFYim RldQ5TMQeus1v/BMgbwJaqbvKGHfwCMhChC1lJ3DFJwSvbux3j5LcSQZtpo8LHeGsup2 OHzsV+IdW5DMs+PNyGCNDE82IupzoVJDYSgJ0bkvQqJSx7GCa6KAVltBWHNlagKmOQoi BqlQ==
MIME-Version: 1.0
X-Received: by 10.152.121.3 with SMTP id lg3mr4537296lab.0.1382691913671; Fri, 25 Oct 2013 02:05:13 -0700 (PDT)
Received: by 10.114.168.70 with HTTP; Fri, 25 Oct 2013 02:05:13 -0700 (PDT)
In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B0BF358@FR712WXCHMBA11.zeu.alcatel-lucent.com>
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>
Date: Fri, 25 Oct 2013 11:05:13 +0200
Message-ID: <CAGgHUiRtXUAJTotAFX7YwQ6cS_OD-MpAb+898c6OYxm7D5xXKw@mail.gmail.com>
From: Leon Geyser <lgeyser@gmail.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary="089e0112d1645929b004e98d0c16"
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 09:05:35 -0000

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> 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] On Behalf Of Markus.Isomaki@nokia.com
> > Sent: 25 October 2013 09:04
> > To: harald@alvestrand.no; 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
> > https://www.ietf.org/mailman/listinfo/rtcweb
> >
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>