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

Yoav Nir <ynir@checkpoint.com> Wed, 09 May 2012 10:38 UTC

Return-Path: <ynir@checkpoint.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 3076221F8567 for <ietf@ietfa.amsl.com>; Wed, 9 May 2012 03:38:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.411
X-Spam-Level:
X-Spam-Status: No, score=-10.411 tagged_above=-999 required=5 tests=[AWL=0.188, BAYES_00=-2.599, 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 fhUpVgzv68AD for <ietf@ietfa.amsl.com>; Wed, 9 May 2012 03:38:18 -0700 (PDT)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 6CD8621F855D for <ietf@ietf.org>; Wed, 9 May 2012 03:38:17 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id q49AbAX7002398; Wed, 9 May 2012 13:37:45 +0300
X-CheckPoint: {4FAA5651-5-1B221DC2-2FFFF}
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Wed, 9 May 2012 13:37:12 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: SM <sm@resistor.net>
Date: Wed, 09 May 2012 13:37:15 +0300
Subject: Re: Last Call: <draft-farrresnickel-ipr-sanctions-05.txt> (Sanctions Available for Application to Violators of IETF IPR Policy) to Informational RFC
Thread-Topic: Last Call: <draft-farrresnickel-ipr-sanctions-05.txt> (Sanctions Available for Application to Violators of IETF IPR Policy) to Informational RFC
Thread-Index: Ac0tz7EVxLJy+DceRT+REpZnuHXpfQ==
Message-ID: <F7C15739-CBD0-41AF-9FEB-6000971D8A79@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> <6.2.5.6.2.20120509013727.0a999478@resistor.net>
In-Reply-To: <6.2.5.6.2.20120509013727.0a999478@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <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 10:38:20 -0000

On May 9, 2012, at 12:28 PM, SM wrote:

> 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? :-)  

Dean Anderson often linked to his website: http://www.av8.net/IETF-watch/People/ (also loads of fun without the "People" path). IANAL but this does sound like libel.

More recently, but not related to IPR issues, during the last IETF quite a few of our prominent members were calling for sanctions (removal of posting privileges) after some of the IETF.Fact.Check posts.

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

I'm fine with it as it is. I just hope the IETF is not held responsible for postings by individuals.