Re: [rtcweb] H.264's high-low play (Was: H.264 IPR disclosures (or persistent lack thereof))

"DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com> Sun, 15 December 2013 06:03 UTC

Return-Path: <keith.drage@alcatel-lucent.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 E822F1AE10B for <rtcweb@ietfa.amsl.com>; Sat, 14 Dec 2013 22:03:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-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 lIWwOBi3Lhz9 for <rtcweb@ietfa.amsl.com>; Sat, 14 Dec 2013 22:03:46 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 052441AE107 for <rtcweb@ietf.org>; Sat, 14 Dec 2013 22:03:45 -0800 (PST)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id rBF63aRI026884 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sun, 15 Dec 2013 00:03:38 -0600 (CST)
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id rBF63Z4u032400 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 15 Dec 2013 07:03:36 +0100
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.203]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.02.0247.003; Sun, 15 Dec 2013 07:03:35 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Basil Mohamed Gohar <basilgohar@librevideo.org>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] H.264's high-low play (Was: H.264 IPR disclosures (or persistent lack thereof))
Thread-Index: AQHO+OLQbBCgbPEvnk+J0qU8kV36NppUC90AgAAVGACAAAPAgIAAXLaAgABAMPA=
Date: Sun, 15 Dec 2013 06:03:35 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B0F9699@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <20131212214310.GR3245@audi.shelbyville.oz> <CECFA3EA.AC30E%stewe@stewe.org> <949EF20990823C4C85C18D59AA11AD8B0F8739@FR712WXCHMBA11.zeu.alcatel-lucent.com> <20131213024334.GV3245@audi.shelbyville.oz> <949EF20990823C4C85C18D59AA11AD8B0F88D6@FR712WXCHMBA11.zeu.alcatel-lucent.com> <20131213033344.GW3245@audi.shelbyville.oz> <CECFF758.205FF%mzanaty@cisco.com> <E44893DD4E290745BB608EB23FDDB7620A16219B@008-AM1MPN1-042.mgdnok.nokia.com> <20131214102855.GY3245@audi.shelbyville.oz> <20131214122049.604352b3@rainpc> <20131214132520.GZ3245@audi.shelbyville.oz> <52AC7B89.3030103@bbs.darktech.org> <CAHp8n2==FmVsdr3+HLT226pv3wm9i8ma_fE0EyDM0dY0PfbZjA@mail.gmail.com> <52ACCAAA.8040303@bbs.darktech.org> <CABcZeBMj8igNggmXKqZtZX24a41C9yaG5hXBkTQ0tF7HZOagUg@mail.gmail.com> <52AD1B95.1050400@librevideo.org>
In-Reply-To: <52AD1B95.1050400@librevideo.org>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.38]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
Subject: Re: [rtcweb] H.264's high-low play (Was: H.264 IPR disclosures (or persistent lack thereof))
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, 15 Dec 2013 06:03:49 -0000

As that statement has never been put to a decision, you cannot say it is a goal, or is not a goal. 

It is just plain not determined.

Keith
 

> -----Original Message-----
> From: rtcweb [mailto:rtcweb-bounces@ietf.org] On Behalf Of 
> Basil Mohamed Gohar
> Sent: 15 December 2013 03:02
> To: rtcweb@ietf.org
> Subject: Re: [rtcweb] H.264's high-low play (Was: H.264 IPR 
> disclosures (or persistent lack thereof))
> 
> On 12/14/2013 04:29 PM, Eric Rescorla wrote:
> > On Sat, Dec 14, 2013 at 1:16 PM, cowwoc 
> <cowwoc@bbs.darktech.org> wrote:
> >> On 14/12/2013 3:00 PM, Silvia Pfeiffer wrote:
> >>>
> >>> While I'm all for vp8, this argument is a far shot. I 
> actually think 
> >>> that the longer we wait, the easier it will be to pick vp8.
> >>>
> >>> Did you notice that the only objection to choosing vp8 
> that returns 
> >>> in the survey is the Nokia ipr statement? There is no mention any 
> >>> more of lack of hw support? When Google makes the binary 
> offer that 
> >>> Cisco made for h264, that goes away. I wonder what 
> objections will remain??
> >>>
> >>> Time is actually on the side of royalty free in this case faict.
> >>>
> >>
> >> I think there is a bit of a fallacy at play here. H.264's 
> installed 
> >> base in the context of WebRTC is exactly zero. Why? 
> Because there is 
> >> no meaningful encoder support on any platform.
> > 
> > "Installed base" here also means the very large number of existing 
> > devices which speak SIP and which have H.264-only.
> > 
> > With that said, there are also a large number of devices 
> with built-in 
> > H.264 encoders.
> > 
> > 
> >> IPR-issues aside, does anyone honestly think that we'd be 
> better off 
> >> with a video codec monopoly? I'd much rather see VP8 and H.264 
> >> compete on equal footing. I believe that one of Mozilla's primary 
> >> goals for entering the mobile market was to create competition in 
> >> that space, which is why I hope that they will push for 
> competition in this space as well.
> > 
> > I'm not sure what you think "Mozilla" should do other than 
> what it's 
> > doing, which is to support both codecs.
> > 
> > -Ekr
> 
> Ekr,
> 
> Can you provide something that points to this:
> 
> > "Installed base" here also means the very large number of existing 
> > devices which speak SIP and which have H.264-only.
> 
> as a fact?  I'm particularly interested in the "very large 
> number" part more than the H.264-only part.  How many SIP 
> devices are really out there that have any a passing interest 
> or chance at being an interop target for rtcweb?
> 
> The reason I ask is because amongst the most pressing 
> strengths of H.264 as MTI for rtcweb is interop, but interop 
> is not a primary goal of rtcweb.  Introducing the burden of 
> H.264 into the spec for new devices, technologies, and 
> methods should not be a factor if the true relevance is 
> minimal or, in fact, small enough to be considered non-existent.
> 
> --
> Libre Video
> http://librevideo.org
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>