Re: Last Call: <draft-farrresnickel-ipr-sanctions-05.txt> (Sanctions Available for Application to Violators of IETF IPR Policy) to Informational RFC
SM <sm@resistor.net> Thu, 10 May 2012 08:18 UTC
Return-Path: <sm@resistor.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 D96B221F85E7 for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 01:18:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.583
X-Spam-Level:
X-Spam-Status: No, score=-103.583 tagged_above=-999 required=5 tests=[AWL=1.016, BAYES_00=-2.599, GB_I_LETTER=-2, USER_IN_WHITELIST=-100]
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 6X14FRA4W74t for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 01:18:54 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 810CF21F84FC for <ietf@ietf.org>; Thu, 10 May 2012 01:18:54 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q4A8Im1s004715 for <ietf@ietf.org>; Thu, 10 May 2012 01:18:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1336637933; i=@resistor.net; bh=0CpkFdn9TaxMBh+bzM0rmhF7bqLWs4beC8r901Xmllo=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=gbD29JrLALbZbuGfXF6DrBqF3T8a6X9UYD2Khrx5x9v+faAlJyrQ2GzyLlbmQ4WaL 5ceHFe/Da5B8OyI+fZx7p8ypkFfNn6pwGC6C60oqJFCahMgNCiMKkvHqXdYFAdVylz luRPqMyUKfRtz2v7UbU7D3ItYlPcgiGTcY3Mw2Mo=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1336637933; i=@resistor.net; bh=0CpkFdn9TaxMBh+bzM0rmhF7bqLWs4beC8r901Xmllo=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=2mo/HjBIM9unXsHjBGr80jVqEHUeSusweuG0sdRj7oqWM148lLzRiPGNwZrz2AF9s uiY461SQ/zpC3J3JawY9r6Siwdl9R+3JAgRJdXn/ZiTATZqkOafCaXJo5LeQZp3qtl /SsbUfV0PBGZWksfswqr36lxVDF31ZPDECRPpyDU=
Message-Id: <6.2.5.6.2.20120509210747.0a901d38@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 09 May 2012 23:30:17 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-farrresnickel-ipr-sanctions-05.txt> (Sanctions Available for Application to Violators of IETF IPR Policy) to Informational RFC
In-Reply-To: <m24nrozq83.wl%randy@psg.com>
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> <m2ipg4zuoj.wl%randy@psg.com> <4FAB2A79.3090402@qualcomm.com> <m24nrozq83.wl%randy@psg.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
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 08:18:59 -0000
At 20:09 09-05-2012, Randy Bush wrote: >participants should not call for sanctions. they should point out to wg >chairs, or ADs FACTS about questinable activity, non-disclosure, ... Yes. >and so forth. i hope that this is not a witch hunt. that it is not >creating courts and guillotines. we should assume people want to act in >a responsible fashion and provide simple gentle paths to be taken when >that assumption fails. There are times when it is difficult to keep assuming that people are acting in a responsible fashion given the high levels of unpleasantness. The situation can be such that simple gentle paths are ignored. Fred Baker commented [1]: "I'm concerned about people bringing baseless accusations, as yet another way to DOS a WG with IPR." It only takes an IPR disclosure to make the WG work difficult. It seems that an employer was not keen about the WG creation. There are currently three IPR related issues affecting different working groups. draft-farrresnickel-ipr-sanctions-05 does not affect any of these issues. In one of these cases, the IPR disclosure happened after the document went through a Last Call. A company gave up fighting a claim related to that IPR after spending US$1 million on lawyers. If you write open source software, you stay away from IPR if you don't like the users of your software to receive ransom letters. If someone wants to ask for sanctions, the person might have to file a third-party IPR disclosure first. It is unlikely that there will be any action under draft-farrresnickel-ipr-sanctions-05 unless one of the WG participants is listed as an inventor. At 23:46 09-05-2012, 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: Agreed. > 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? That could be added as an example. >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. I suggested an adaptation of existing text from the draft based on Pete's comments. I don't have a strong opinion about which text goes in. From the "island of stone money": "their island yields no metals, they had recourse to stone; stone, on which labour in fetching and fashioning has been expended, is as truly a representation of labour as the mined and minted coins of civilization." The German Government wanted the paths or highways, which were in bad condition to be repaired. The commands to the chiefs of the districts remained unheeded. It was decided to impose a fine by sending a man to mark a certain number of the stones with a cross in black paint. "This instantly worked like a charm"; the people repaired the highways. History will tell whether there is a parallel between the above and this draft. Regards, -sm 1. http://www.ietf.org/mail-archive/web/ietf/current/msg73287.html
- 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