Re: Leverage Patent Search API to reduce BCP79 related issues [was:
ned+ietf@mauve.mrochek.com Thu, 10 May 2012 18:15 UTC
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6CBB21F86F0 for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 11:15:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U2nE0EDk3sFZ for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 11:15:53 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 2C6EB21F86EB for <ietf@ietf.org>; Thu, 10 May 2012 11:15:53 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OFBDNMNIW0001H9G@mauve.mrochek.com> for ietf@ietf.org; Thu, 10 May 2012 11:15:50 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OF7HODY84G0006TF@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Thu, 10 May 2012 11:15:45 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OFBDNJS9F80006TF@mauve.mrochek.com>
Date: Thu, 10 May 2012 11:14:05 -0700
Subject: Re: Leverage Patent Search API to reduce BCP79 related issues [was:
In-reply-to: "Your message dated Thu, 10 May 2012 18:31:44 +0200 (MEST)" <201205101631.q4AGViCG025328@fs4113.wdf.sap.corp>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <34D509ED-2D64-4383-A49E-F249D4263EF9@vigilsec.com> <201205101631.q4AGViCG025328@fs4113.wdf.sap.corp>
To: Martin Rex <mrex@sap.com>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2012 18:15:53 -0000
> Russ Housley wrote: > > > > BCP 79 says: > > > > "Reasonably and personally known": means something an individual > > knows personally or, because of the job the individual holds, > > would reasonably be expected to know. This wording is used to > > indicate that an organization cannot purposely keep an individual > > in the dark about patents or patent applications just to avoid the > > disclosure requirement. But this requirement should not be > > interpreted as requiring the IETF Contributor or participant (or > > his or her represented organization, if any) to perform a patent > > search to find applicable IPR. > > > > Your suggestion seems to be in direct conflict with BCP 79. > IMHO your quote from BCP79 (page 4, bullet l.) is a very important > point in BCP79. I can not speak for others, but the Internet Proxy > of our company blocks urls to all "well known" online patent search > and patent publication sites (and these are the only blocked sites > I've ever encountered) for the simple reason of the insane US patent > laws with this 3-fold "punitive damages" for "willful infringement" > of a patent, i.e. a patent that was known to exist when shipping. > As engineers, we MUST NOT read any patents because of this. > All of the patent reasarch stuff is done by patent lawyers exclusively. I don't know if a similar block exists, but the policy is the same for us. Such a policy, if implemented, could easily lead to various people being unable to participate in the process. > btw. I personally know only about one patent where I refused to be > listed as inventor because I considered my contribution to it to be > "obvious to someone skilled in the technology". When I read the > description after it had been processed by patent lawyers, I had > serious difficulties understanding what that text meant... A pretty common occurance, unfortunately. Ned
- Re: Last Call: <draft-farrresnickel-ipr-sanctions… Brian E Carpenter
- RE: Last Call: <draft-farrresnickel-ipr-sanctions… Yoav Nir
- Re: Last Call: <draft-farrresnickel-ipr-sanctions… Brian E Carpenter
- Re: Last Call: <draft-farrresnickel-ipr-sanctions… Yoav Nir
- Re: Last Call: <draft-farrresnickel-ipr-sanctions… SM
- Re: Last Call: <draft-farrresnickel-ipr-sanctions… Yoav Nir
- RE: Last Call: <draft-farrresnickel-ipr-sanctions… Adrian Farrel
- Re: Last Call: <draft-farrresnickel-ipr-sanctions… Brian E Carpenter
- Re: Last Call: <draft-farrresnickel-ipr-sanctions… SM
- Re: Last Call: <draft-farrresnickel-ipr-sanctions… Pete Resnick
- Re: Last Call: <draft-farrresnickel-ipr-sanctions… SM
- Re: Last Call: <draft-farrresnickel-ipr-sanctions… Fred Baker
- Re: Last Call: <draft-farrresnickel-ipr-sanctions… Randy Bush
- Re: Last Call: <draft-farrresnickel-ipr-sanctions… Pete Resnick
- Re: Last Call: <draft-farrresnickel-ipr-sanctions… Livingood, Jason
- Re: Last Call: <draft-farrresnickel-ipr-sanctions… Mark Andrews
- Re: Last Call: <draft-farrresnickel-ipr-sanctions… Randy Bush
- Re: Last Call: <draft-farrresnickel-ipr-sanctions… Peter Saint-Andre
- Re: Last Call: <draft-farrresnickel-ipr-sanctions… Brian E Carpenter
- Re: Last Call: <draft-farrresnickel-ipr-sanctions… SM
- Re: Last Call: <draft-farrresnickel-ipr-sanctions… Hector Santos
- Leverage Patent Search API to reduce BCP79 relate… Hector Santos
- Re: Leverage Patent Search API to reduce BCP79 re… Nick Hilliard
- Re: Leverage Patent Search API to reduce BCP79 re… Russ Housley
- Re: Leverage Patent Search API to reduce BCP79 re… Martin Rex
- URI listing (was: Leverage Patent Search API to r… SM
- Re: Leverage Patent Search API to reduce BCP79 re… ned+ietf
- Re: Leverage Patent Search API to reduce BCP79 re… Dave Crocker