Re: [rtcweb] Proposed Video Selection Process

Stefan Slivinski <sslivinski@lifesize.com> Thu, 21 November 2013 22:42 UTC

Return-Path: <sslivinski@lifesize.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 AE8E71AE1A8 for <rtcweb@ietfa.amsl.com>; Thu, 21 Nov 2013 14:42:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.7
X-Spam-Level:
X-Spam-Status: No, score=-3.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_BAD_LINEBREAK=0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] 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 PsKWQEP6BzG0 for <rtcweb@ietfa.amsl.com>; Thu, 21 Nov 2013 14:41:59 -0800 (PST)
Received: from na3sys009aog111.obsmtp.com (na3sys009aog111.obsmtp.com [74.125.149.205]) by ietfa.amsl.com (Postfix) with SMTP id 237111AE117 for <rtcweb@ietf.org>; Thu, 21 Nov 2013 14:41:59 -0800 (PST)
Received: from mail1.lifesize.com ([207.114.244.10]) (using TLSv1) by na3sys009aob111.postini.com ([74.125.148.12]) with SMTP ID DSNKUo6MLxLNXUXdTtb45O4mLCtZIdjPCfTG@postini.com; Thu, 21 Nov 2013 14:41:52 PST
Received: from ausmsex00.austin.kmvtechnologies.com ([fe80::edad:d9e3:99d1:8109]) by ausmsex00.austin.kmvtechnologies.com ([fe80::edad:d9e3:99d1:8109%14]) with mapi; Thu, 21 Nov 2013 16:37:52 -0600
From: Stefan Slivinski <sslivinski@lifesize.com>
To: "'juberti@google.com'" <juberti@google.com>, "'fluffy@iii.ca'" <fluffy@iii.ca>
Date: Thu, 21 Nov 2013 16:37:51 -0600
Thread-Topic: [rtcweb] Proposed Video Selection Process
Thread-Index: Ac7nCY1UVfbilTf/R/G3xSUBSsvtlQAAMKQR
Message-ID: <7949EED078736C4881C92F656DC6F6C130EA8AD7E8@ausmsex00.austin.kmvtechnologies.com>
In-Reply-To: <CAOJ7v-3ruj91wd=1_TUevapamLxNJ93Ukd=VU+Gq7Q19YTvc+A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_7949EED078736C4881C92F656DC6F6C130EA8AD7E8ausmsex00aust_"
MIME-Version: 1.0
Cc: "'rtcweb@ietf.org'" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Proposed Video Selection Process
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, 21 Nov 2013 22:42:01 -0000

Having some experience with patent trolls I have come to the realization that if you have means they will sue you for pretty much anything even if you do not actually infringe on their patents. You are then in the position of fighting them or paying them off.

I think it is naïve to believe you can ever completely avoid IPR by picking some archaic codec. I think we need to come up with a different solution to defend against infringement claims rather than trying to avoid them


From: Justin Uberti [mailto:juberti@google.com]
Sent: Thursday, November 21, 2013 04:31 PM
To: Cullen Jennings <fluffy@iii.ca>;
Cc: rtcweb@ietf.org <rtcweb@ietf.org>;
Subject: Re: [rtcweb] Proposed Video Selection Process

Even the proposal that recommended H.264 as MTI indicated that the technical merit of the currently proposed codecs is equivalent, and the fundamental question is IPR.
http://tools.ietf.org/agenda/88/slides/slides-88-rtcweb-8.pdf

Put another way, if the alleged IPR issues associated with either H.264 or VP8 disappeared overnight, this discussion would be instantly over.


On Thu, Nov 21, 2013 at 2:14 PM, Cullen Jennings <fluffy@iii.ca<mailto:fluffy@iii.ca>> wrote:

On Nov 21, 2013, at 12:36 PM, Justin Uberti <juberti@google.com<mailto:juberti@google.com>> wrote:

> That said, I think the general understanding here is that this is no longer a technical decision.
>

I'll note that some people strongly disagree with this is not a technical decision but there are others who do think it is is no longer a technical decision.

_______________________________________________
rtcweb mailing list
rtcweb@ietf.org<mailto:rtcweb@ietf.org>
https://www.ietf.org/mailman/listinfo/rtcweb