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> Wed, 09 May 2012 09:41 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 AB06621F85B8 for <ietf@ietfa.amsl.com>; Wed, 9 May 2012 02:41:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.582
X-Spam-Level:
X-Spam-Status: No, score=-102.582 tagged_above=-999 required=5 tests=[AWL=0.017, BAYES_00=-2.599, 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 RuyEzfabHoWe for <ietf@ietfa.amsl.com>; Wed, 9 May 2012 02:41:57 -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 0BA5621F85B5 for <ietf@ietf.org>; Wed, 9 May 2012 02:41:57 -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 q499fPHF027497; Wed, 9 May 2012 02:41:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1336556504; i=@resistor.net; bh=08/Brvy+r69VNP5Jd723lTZPVKwKBwu5GKig5R3Qf0g=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=HZihEX5ZtmcrD/tisvJufAO/8h19HEMYb2ZZk+oRfPnO/pe5K7AZ3qHDVYsl/XxgL 86rs5ay4VyViggNUjxyZZQPCSyt02pAxmNLLDJ0YQs38PzeBIpNDyr+JuSykLfMnwY fFcBRfS/nq0MV/rjuUBNVXXfESuwxn0a+DwWwznM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1336556504; i=@resistor.net; bh=08/Brvy+r69VNP5Jd723lTZPVKwKBwu5GKig5R3Qf0g=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=vtbePUOBFSGr1ROBzwHgSR5V8SodF4X4P8v7fCnnida+XgjaJrXYWyNn3QRGfqXX6 O0FAHNGzlt2UvVfzN4Op8iJkPD3ME7DQQY2Q0MlebHwqPZBD6sabh88gtcVFC7VrE+ ByRmjpc6r39CE5aR6QYetn7dgQTdKTlqCEDlRffU=
Message-Id: <6.2.5.6.2.20120509013727.0a999478@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 09 May 2012 02:28:32 -0700
To: Yoav Nir <ynir@checkpoint.com>
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: <6585DDB2-11FB-4B49-B63E-4F75D540E920@checkpoint.com>
References: <20120507215610.10679.15815.idtracker@ietfa.amsl.com> <4FAA140B.4010703@gmail.com> <006FEB08D9C6444AB014105C9AEB133F017A7C056C4B@il-ex01.ad.checkpoint.com> <4FAA1A6A.5070500@gmail.com> <6585DDB2-11FB-4B49-B63E-4F75D540E920@checkpoint.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
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: Wed, 09 May 2012 09:41:57 -0000

Hi Yoav,
At 00:44 09-05-2012, Yoav Nir wrote:
>What the IETF writes in its policy amounts to a plea to users to 
>pretty please send only factual information. I don't know that it 
>makes a difference as to who is liable if the information turns out 
>to be non-factual.

Section 3 text mentions several paths for the issue, i.e. 
responsibility lies with the working group chair with escalation to 
area directors.  Paragraph 2 and 3 discusses about that.  The issue 
which predates this draft is mentioned in the message at 
http://www.ietf.org/mail-archive/web/ietf/current/msg71484.html

Do you know any IETF participant who is dumb enough to send a public 
request for sanctions? :-)  That can affect the individual's carrier 
path in the IETF and in the corporate world.  Some IETF participants 
might even ask lawyers to take action.  Watching "Behind enemy lines" 
(disambiguation required) might be instructive in this context.

At the end of the day, this draft is simply a matter of having an RFC 
for those who might find the information helpful.  Sometimes all one 
can do is to say "pretty please".

I'll +1 this draft as it stands.

Regards,
-sm