Re: [rtcweb] Plan for MTI video codec?
Adam Roach <adam@nostrum.com> Fri, 24 October 2014 23:32 UTC
Return-Path: <adam@nostrum.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 E809A1A1ABC for <rtcweb@ietfa.amsl.com>; Fri, 24 Oct 2014 16:32:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 ALtkxJTFwCaa for <rtcweb@ietfa.amsl.com>; Fri, 24 Oct 2014 16:32:43 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 436161A1A5D for <rtcweb@ietf.org>; Fri, 24 Oct 2014 16:32:43 -0700 (PDT)
Received: from Orochi.local (99-152-145-110.lightspeed.dllstx.sbcglobal.net [99.152.145.110]) (authenticated bits=0) by nostrum.com (8.14.9/8.14.7) with ESMTP id s9ONWcwx073238 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 24 Oct 2014 18:32:39 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 99-152-145-110.lightspeed.dllstx.sbcglobal.net [99.152.145.110] claimed to be Orochi.local
Message-ID: <544AE196.6080907@nostrum.com>
Date: Fri, 24 Oct 2014 18:32:38 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: Stephan Wenger <stewe@stewe.org>, Watson Ladd <watsonbladd@gmail.com>, Alexandre GOUAILLARD <agouaillard@gmail.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> <CAOW+2dugTtfLhk0VuJOk7OPEonGBApMjY93EZocH90RbX6X22w@mail.gmail.com> <CAHgZEq5t4-Cot9XkU_pfyfi0TBCUxfT79ZvpiLW=X5_KUQh5dA@mail.gmail.com> <CACsn0ck_VtMnf6740rh0ku1Qct7s-xrJEfokg6oufEi4wgrYAw@mail.gmail.com> <D069AC57.49A8E%stewe@stewe.org> <D06D5403.49D1D%stewe@stewe.org>
In-Reply-To: <D06D5403.49D1D%stewe@stewe.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/dYcbwnNM88l4TSYkZnv1TrKzArc
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
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: Fri, 24 Oct 2014 23:32:45 -0000
On 10/22/14 14:45, Stephan Wenger wrote: > I have to make one correction in the light of information that has > surfaced at the MPEG meeting currently ongoing in Strasbourg. (I’m not at > that meeting this time, but a colleague is and she briefed me.) > Nokia has made MPEG and ISO/IEC officially aware that they are not willing > to license essential patents under RAND terms. For those with MPEG > document access, please see M34917. The official declaration is dated > 9/19/2014, and is not yet available from the respective databases, as ISO > is apparently changing its recordation infrastructure. Thanks for the update. That's actually even more interesting than it first appears to be. The official rationale previously offered by Nokia was that the refusal to license patents [0] for VP8 was that VP8 had not been through an appropriate standards process [1]. The fact that Nokia is now using those same patents to *block* VP8-based work from going through an appropriate standards process pretty clearly exposes that claim as false. This isn't aimed at ensuring "open and collaborative efforts for standardization": this is aimed at suppressing technology. To be clear, my position remains that either VP8 or H.264 would be a suitable MTI, and (although not my preference) I would accept a situation in which both are required. Which is to say that I don't really have much at stake in the MTI conversation (as long as we do eventually do something to guarantee interop). But it does seem that Nokia isn't being forthcoming about its motives here, and I find that pretty distasteful. I would have preferred silence over lies. > My understanding of the joint ITU/ISO/IEC patent policy is that no > standard can be issued that has a type 3 declaration against it. To the > best of my knowledge, ISO has no established procedure how to deal with > type 3 (non-RAND) declarations and still keep the standard project going. > Unlike, for example, W3C and its Patent Advisory Groups. > The declaration does not list specific patents. To the best of my > knowledge, such info is not required (only desired) for ISO and IEC > standardization work--one of the few differences in patent policy > guidelines between ITU and ISO/IEC. > Therefore, I have to row back on my previous statement of likeliness of > having an ISO number for VP8 anytime soon. At this point, I just don’t > know whether, if ever, that will happen. I find the ISO policy as stated to be curious -- if it doesn't require citing patents, and categorically refuses to issue specs with type 3 declarations, I could effectively reduce the ISO output to zero by mechanically claiming a type 3 declaration on every specification under development. /a ____ [0] For absolute clarity, I make no assertion one way or another about the applicability of such patents to VP8. [1] As quoted in uncountably many publications: "Nokia believes that open and collaborative efforts for standardization are in the best interests of consumers, innovators and the industry as a whole. We are now witnessing one company attempting to force the adoption of its proprietary technology, which offers no advantages over existing, widely deployed standards such as H.264 and infringes Nokia's intellectual property. As a result, we have taken the unusual step of declaring to the Internet Engineering Task Force that we are not prepared to license any Nokia patents which may be needed to implement its RFC6386 specification for VP8, or for derivative codecs."
- [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