Re: [rtcweb] Finishing up the Video Codec document, MTI (again, still, sorry)

Ron <ron@debian.org> Thu, 04 December 2014 14:51 UTC

Return-Path: <ron@debian.org>
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 391541AD3BB for <rtcweb@ietfa.amsl.com>; Thu, 4 Dec 2014 06:51:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] 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 oGxscxLjwhEJ for <rtcweb@ietfa.amsl.com>; Thu, 4 Dec 2014 06:51:53 -0800 (PST)
Received: from ipmail07.adl2.internode.on.net (ipmail07.adl2.internode.on.net [150.101.137.131]) by ietfa.amsl.com (Postfix) with ESMTP id A00C41A1B10 for <rtcweb@ietf.org>; Thu, 4 Dec 2014 06:51:52 -0800 (PST)
Received: from ppp14-2-2-160.lns21.adl2.internode.on.net (HELO mailservice.shelbyville.oz) ([14.2.2.160]) by ipmail07.adl2.internode.on.net with ESMTP; 05 Dec 2014 01:21:51 +1030
Received: from localhost (localhost [127.0.0.1]) by mailservice.shelbyville.oz (Postfix) with ESMTP id 27644FFEE9 for <rtcweb@ietf.org>; Fri, 5 Dec 2014 01:21:39 +1030 (CST)
X-Virus-Scanned: Debian amavisd-new at mailservice.shelbyville.oz
Received: from mailservice.shelbyville.oz ([127.0.0.1]) by localhost (mailservice.shelbyville.oz [127.0.0.1]) (amavisd-new, port 10024) with LMTP id YICSjDMqFLVg for <rtcweb@ietf.org>; Fri, 5 Dec 2014 01:21:38 +1030 (CST)
Received: from hex.shelbyville.oz (hex.shelbyville.oz [192.168.1.6]) by mailservice.shelbyville.oz (Postfix) with ESMTPS id B9943FF88C for <rtcweb@ietf.org>; Fri, 5 Dec 2014 01:21:38 +1030 (CST)
Received: by hex.shelbyville.oz (Postfix, from userid 1000) id AE47780470; Fri, 5 Dec 2014 01:21:38 +1030 (ACDT)
Date: Fri, 5 Dec 2014 01:21:38 +1030
From: Ron <ron@debian.org>
To: rtcweb@ietf.org
Message-ID: <20141204145138.GH10449@hex.shelbyville.oz>
References: <547511DB.5050100@nostrum.com> <54759A4C.6020806@gmail.com> <5476092D.4010406@nostrum.com> <15EF2452-2C2C-420B-B972-C37EACE57850@apple.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <15EF2452-2C2C-420B-B972-C37EACE57850@apple.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/z6aHw3s1nEC2fCuZ0c6l1BV7m9s
Subject: Re: [rtcweb] Finishing up the Video Codec document, MTI (again, still, sorry)
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: Thu, 04 Dec 2014 14:51:55 -0000

On Wed, Dec 03, 2014 at 10:33:04AM -0800, David Singer wrote:
> 
> Consider finally: a small company for whom WebRTC is important.
> 
> Let’s look at the choices:
> 
> 1.  Follow the mandate, implement VP8, and risk a ruinous lawsuit from Nokia.
> 
> 2.  Reject the mandate, do not implement VP8, and be formally therefore not conformant and therefore not in receipt of a license from company X; risk a ruinous lawsuit from X.
> 
> 3.  Do not implement WebRTC, and risk a ruinous loss of relevance.

This seems more like a hypothetical small strawman than a situation
that any *real* small company has expressed to this group.

Your concern for small operators is heartwarming, but I think if you
consult the list archives to see what such people have actually said
for themselves, the only ruinous legal barrier that Nokia appears to
have them worried about is the IPR it holds on H.264 that is outside
the pool MPEG-LA operates, with no clear guarantee of its terms.

And we *still* don't have an IPR statement from them about this.
How many times should we need to ask them to respect the IETF process?


Fear of VP8 here would appear to be directly proportional to something
much simpler than what you claim.

If someone would like to graph "Number of H.264 patents held" vs
"Fear of VP8 being MTI", I think you'll find the real correlation
that you're grasping for here to be fairly obvious.

  hth!
  Ron