Re: Last Call: <draft-farrresnickel-ipr-sanctions-05.txt> (Sanctions Available for Application to Violators of IETF IPR Policy) to Informational RFC

Hector Santos <hsantos@isdg.net> Thu, 10 May 2012 10:05 UTC

Return-Path: <hsantos@isdg.net>
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 56B8121F86A4 for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 03:05:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.05
X-Spam-Level:
X-Spam-Status: No, score=-2.05 tagged_above=-999 required=5 tests=[AWL=0.549, 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 96AZzRf78Ltl for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 03:05:01 -0700 (PDT)
Received: from dkim.winserver.com (secure.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id D10DC21F86A1 for <ietf@ietf.org>; Thu, 10 May 2012 03:05:00 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2972; t=1336644291; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=P0xVWCW82TsfhhHFMFMpEuANsPI=; b=BJvf3vujz/km74cYu0f9 AmHmcy5nXanl89h0vHglFgLBoyKs1LcxuPi5Wbvc7mBfic7UJgDwBoJC3i9huAOb PILmajpS7RBd7T5YCqitmJHsmY/qHmASp8haLjASQBLIYyrLAFKvCNG4V0xJ8JSv ZGnSJ6zl3X0FD0b2ojK7Khk=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Thu, 10 May 2012 06:04:51 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com; adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from opensite.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 1256125033.53896.4744; Thu, 10 May 2012 06:04:50 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=2972; t=1336644278; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=ZOls+Im mpN22yw/jwNBJ7QTwH/Ud8JvadkMT7blnisA=; b=TO8bokMUlNUanrnl8zCZnb5 ZJYX+Z2lgwnqCyXjuhaTzvZnw1z1mOnLlM+AiYp//8SxIYi9WiW23h5OpY+ttenC 7vTEu0V576bQ0wcBC1NLNRY+vg8OVvb1zXZ1REovgZCxknA4AHwZbP3NAO9tssFx 6dzkGo9dIveW1qn0qTmM=
Received: by beta.winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Thu, 10 May 2012 06:04:38 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 1855010800.5934.7964; Thu, 10 May 2012 06:04:37 -0400
Message-ID: <4FAB92BF.8090408@isdg.net>
Date: Thu, 10 May 2012 06:04:47 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Last Call: <draft-farrresnickel-ipr-sanctions-05.txt> (Sanctions Available for Application to Violators of IETF IPR Policy) to Informational RFC
References: <20120507215610.10679.15815.idtracker@ietfa.amsl.com> <4FAA140B.4010703@gmail.com> <4FAAD14F.40009@qualcomm.com> <6.2.5.6.2.20120509150640.090d7098@resistor.net> <AEFA3A3E-F672-4522-BCF9-5D75DC82D112@cisco.com> <4FAB2563.3090309@qualcomm.com> <4FAB643C.108@gmail.com>
In-Reply-To: <4FAB643C.108@gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: Pete Resnick <presnick@qualcomm.com>, IETF discussion list <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 10:05:02 -0000

Brian E Carpenter wrote:
> 
> Fair enough. I can't agree with SM though - as for appeals under RFC 2026,
> the person bringing up an issue really has to provide a factual summary,
> exactly to avoid witch hunts. It can be very short:
> 
>    Hi, I noticed that US Patent 12345 was filed in March 2010, and
>    draft-blo-foobar was posted that June, and Jo Blo was an author
>    of both. It looks as if they describe the same method, so why
>    wasn't there an IPR disclosure in 2010? Would the WG Chairs consider
>    sanctions against Jo Blo appropriate?
> 
> Possible text:
> 
>    Any IETF participant can draw attention to an apparent violation
>    of the IETF's IPR policy.  This can be done by sending email to
>    the appropriate IETF mailing list, including a short summary of
>    the known facts and, optionally, a call for sanctions to be
>    applied.

+1.

I think the major part of the issue is the growing potential and ease 
to violate BCP79 section 6.2.1 in regards to belated patent filings 
after contributions are made as your above "Jo Blo" scenario reflects.

With the relaxation of patentability guidelines, software/business 
methods and availability of low cost Provisional Patents, it is far 
easier to fall trap to violation BCP79 6.2.1

Provisional Patents is the cheapest way to begin the patent process 
allowing up to one year to complete the full patent. This is an ideal 
way to first test the market which also legally allows the usage of 
"Patent Pending" in marketing material.  If the I-D gets no interest, 
then there is little cost (less than $200) lost to forget about the 
work.  In one year, the provisional patent expires.  There is 
strategic value not to disclose IP related information in the I-D 
perhaps to maximize interest and perhaps this is a IETF new dilemma 
the draft should also focus on and address.

For example, in the draft 2.1, the 3rd paragraph talks about 
"Timeliness" and specifically states:

    The timeliness of disclosure is very important within [BCP79].  No
    precise definition of "timeliness" is given in [BCP79] and it is not
    the purpose of this document to do so.

However, where provisional patent filings are in play, there is at 
least 1 year allowance and incentive to not disclose and that could be 
a problem depending on the speed and interest of the I-D development. 
The draft intro can highlight belated IPR disclosures and section 2.1 
first paragraph, for example, can add:

    According to [BCP79], individual IETF participants have a
    personal responsibility to disclose or ensure the timely disclosure
    of IPR of which they are aware or plan to create .....

So overall, more text emphasizing specifically BC979 section 6.2.1 to 
help highlight the awareness for document authors with a goal to lower 
the concerns of implementators who are watchful of protocols having 
current IPR disclosures and now belated IPR disclosure issues which 
much easier to occur today.

-- 
HLS