Re: Leverage Patent Search API to reduce BCP79 related issues [was:

Martin Rex <mrex@sap.com> Thu, 10 May 2012 16:31 UTC

Return-Path: <mrex@sap.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 C29B821F870A for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 09:31:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.079
X-Spam-Level:
X-Spam-Status: No, score=-10.079 tagged_above=-999 required=5 tests=[AWL=0.170, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
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 gtxb+W3L7Tpn for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 09:31:48 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 8000721F8705 for <ietf@ietf.org>; Thu, 10 May 2012 09:31:48 -0700 (PDT)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id q4AGVjws010110 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 10 May 2012 18:31:45 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201205101631.q4AGViCG025328@fs4113.wdf.sap.corp>
Subject: Re: Leverage Patent Search API to reduce BCP79 related issues [was:
To: housley@vigilsec.com
Date: Thu, 10 May 2012 18:31:44 +0200
In-Reply-To: <34D509ED-2D64-4383-A49E-F249D4263EF9@vigilsec.com> from "Russ Housley" at May 10, 12 11:56:42 am
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
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 16:31:51 -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.

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...


-Martin