Re: [codec] Skype IPR disclosure

stephen botzko <stephen.botzko@gmail.com> Mon, 29 March 2010 23:06 UTC

Return-Path: <stephen.botzko@gmail.com>
X-Original-To: codec@core3.amsl.com
Delivered-To: codec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5FA883A681D for <codec@core3.amsl.com>; Mon, 29 Mar 2010 16:06:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.205
X-Spam-Level:
X-Spam-Status: No, score=0.205 tagged_above=-999 required=5 tests=[AWL=-0.927, BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z3OtMoJBCBda for <codec@core3.amsl.com>; Mon, 29 Mar 2010 16:06:30 -0700 (PDT)
Received: from mail-gx0-f217.google.com (mail-gx0-f217.google.com [209.85.217.217]) by core3.amsl.com (Postfix) with ESMTP id 256093A67E2 for <codec@ietf.org>; Mon, 29 Mar 2010 16:06:30 -0700 (PDT)
Received: by gxk9 with SMTP id 9so1960689gxk.8 for <codec@ietf.org>; Mon, 29 Mar 2010 16:06:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type; bh=52bTg/+m/1/PT35x3YN3efa6+mV7IK7SL1NUErRps18=; b=jUEMDj2I87mj2qLNMa/dslGmmKjVIDl414sAsU+5lNK8Q4g/FiiiqNfwR8Fc90qmfV PSupIp0RXLKkGDDu8hEMJZHnB7TINKc3y8reKEbdDjo1nHRggzj/uyenGSC+cQev1SQI zwtFrmTDHHEY6WJu3fiDJoTaQ8gdq4Hj8+/Lg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=sP8UyNVTTuwIFcWZxE2ARPUt2imxtEt4gcFew21lNG9cxkdAL2RhxDR3/iGPj8yMsf CHQd5+MP0Iogi72mfYVTFqDnoFL0GaIa98NK0nCxwcWMKExK8HBVr32rJnlGex2U5Qbm ukm8OwZTr0Rok4gMAFm+cVlcmQdh+fH1yuH0w=
MIME-Version: 1.0
Received: by 10.231.79.202 with HTTP; Mon, 29 Mar 2010 16:06:55 -0700 (PDT)
In-Reply-To: <4BB0EB75.30909@sbcglobal.net>
References: <6e9223711003261015m5ea5d1bj1e5b5803a7be3eb4@mail.gmail.com> <C7D4D027.20876%stewe@stewe.org> <6e9223711003281024v25fefc8esc59a742b7fd4a909@mail.gmail.com> <4BB0D7F6.1040806@sbcglobal.net> <6e9223711003291028r69061a01t7f685b48da96271f@mail.gmail.com> <4BB0EB75.30909@sbcglobal.net>
Date: Mon, 29 Mar 2010 19:06:55 -0400
Received: by 10.101.154.17 with SMTP id g17mr831628ano.48.1269904015181; Mon, 29 Mar 2010 16:06:55 -0700 (PDT)
Message-ID: <6e9223711003291606lf591f71v55e6468d9d900083@mail.gmail.com>
From: stephen botzko <stephen.botzko@gmail.com>
To: Rob Glidden <rob.glidden@sbcglobal.net>
Content-Type: multipart/alternative; boundary="0016e68e8c08b947d60482f891e6"
Cc: Codec WG <codec@ietf.org>
Subject: Re: [codec] Skype IPR disclosure
X-BeenThere: codec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Codec WG <codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/codec>, <mailto:codec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/codec>
List-Post: <mailto:codec@ietf.org>
List-Help: <mailto:codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/codec>, <mailto:codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Mar 2010 23:06:31 -0000

I saw one person asking questions, to my mind that is not the same as "the
license terms are unacceptable to the community".  The jury is still out on
that one.

Stephen Botzko
On Mon, Mar 29, 2010 at 2:03 PM, Rob Glidden <rob.glidden@sbcglobal.net>wrote:

> Stephen:
>
> Exactly, well said, this is the point of my original email.
>
> To restate original email, the licensing terms on this particular
> disclosure are questioned, and unless there is a specific reason provided to
> use the particular IPR, there would be no apparent need to use it.
>
> Rob
>
>
> stephen botzko wrote:
>
> BCP 79 specifically says "No patent search is required" either by
> individuals or by the working group.
>
> If you know of blocking patents held by a third party, you should simply
> file the third-party disclosure, there is no need to discuss it on the
> list.  If you don't know of blocking patents, then there is nothing to
> discuss.
>
> So I stand by my assertion -
>
> The only case where examining the details of the patents in an IPR
> disclosure is ever necessary  is when (1) the license terms are unacceptable
> to the community, *and* (2) we need to use *some* of the referenced
> technology in the standard.
>
> Stephen Botzko
>
>
> On Mon, Mar 29, 2010 at 12:40 PM, Rob Glidden <rob.glidden@sbcglobal.net>wrote:
>
>> Even if the licensing terms are acceptable, offered IPR may well depend on
>> blocking patents owned by others.
>>
>> All the more likely in the case of more recent and narrowly-defined
>> technologies.
>>
>> Rob
>>
>>
>> stephen botzko wrote:
>>
>> >>> Stephan Wenger worte....
>> I continue to believe that it is within the IETF policy (and, arguably,
>> within common sense) to let people decide for themselves whether they want
>> to participate in discussions concerning third party patent matter, and,
>> independently of the outcome of this decision, still participate in the WG
>> (for example on purely technical subjects).  My fear is that, by exposing
>> folks to patent numbers and handy hyperlinks to patent material, you take
>> some of this choice away.
>>
>> So I believe that both “willful ignorance” and “avoidance [of exposure to
>> patent numbers]” are both within the language and the spirit of the IETF’s
>> patent policy.
>> >>>
>> I agree completely (also with  your reply to Marc).
>>
>> In practice, we begin by individually reviewing the IPR disclosures are
>> they announced.  99.9% of the time, the commercial terms are completely
>> acceptable, so there is no reason to do anything further.
>>
>> The only case where examining the details of the patents in an IPR is ever
>> necessary  is when (1) the terms are unacceptable to the community, *and*(2) we need to use
>> *some* of the referenced technology in the standard.  Even in that case,
>> it is best if the work is structured in such a way that so people can opt
>> out.
>>
>> In this particular situation, there has been no decision yet to use the
>> Skype contribution in the standard, so there is no reason to start diving
>> into this IPR disclosure are all right now.
>>
>> Stephen Botzko
>>
>>
>>
>
>