RE: Last Call: <draft-farrresnickel-ipr-sanctions-05.txt> (Sanctions Available for Application to Violators of IETF IPR Policy) to Informational RFC
"Adrian Farrel" <adrian@olddog.co.uk> Wed, 09 May 2012 10:58 UTC
Return-Path: <adrian@olddog.co.uk>
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 B23FE21F84D5 for <ietf@ietfa.amsl.com>; Wed, 9 May 2012 03:58:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level:
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100, 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 RY4d2w5qVfNb for <ietf@ietfa.amsl.com>; Wed, 9 May 2012 03:58:09 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id 7EB8421F846F for <ietf@ietf.org>; Wed, 9 May 2012 03:58:09 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id q49AvxG1012809; Wed, 9 May 2012 11:57:59 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id q49AvtoH012751 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 9 May 2012 11:57:57 +0100
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Yoav Nir' <ynir@checkpoint.com>, 'Brian E Carpenter' <brian.e.carpenter@gmail.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>
In-Reply-To: <6585DDB2-11FB-4B49-B63E-4F75D540E920@checkpoint.com>
Subject: RE: Last Call: <draft-farrresnickel-ipr-sanctions-05.txt> (Sanctions Available for Application to Violators of IETF IPR Policy) to Informational RFC
Date: Wed, 09 May 2012 11:57:53 +0100
Message-ID: <021301cd2dd2$96c18760$c4449620$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGQEkUpByYTCLejnCgd2FgvYaJqvQHQdm1yAO2O2oYCFkhzfAKp9XxClv+NclA=
Content-Language: en-gb
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
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:58:10 -0000
Hi, I don't even own a television on which to watch people pretending to be lawyers... Both Brian and Yoav are making a worthwhile point, but I don't see how this I-D changes what happens on IETF mailing lists as normal business. It is perfectly possible for the IETF lists to be used to libel someone with or without this I-D. Brian makes a good point that the text should make it clear what level of back-up we expect for such a claim. In writing the original text I had assumed that everyone behaves like a reasonable adult when participating in the IETF - gosh, am I naif? Will fold in text close to Brian's suggestion. Thanks, Adrian > I am not a lawyer either, but I think it depends on jurisdiction whether a mailing > list will be considered as a media outlet or merely a "conduit". > > 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. > > On May 9, 2012, at 10:19 AM, Brian E Carpenter wrote: > > > Yoav, > > > > IANAL, but as far as I know libel suits are normally against individuals > > (or media outlets such as newspapers). The defence against a libel > > suit in the British courts, the most popular jurisdiction for > > international libel suits, is factual accuracy. Therefore, I think > > the draft should state the need for factual evidence. > > > > And to be clear, there are plenty of precedents for libels originating > > outside the UK leading to successful suits in the UK courts, if they > > have been received in the UK via the Internet. > > > > Regards > > Brian Carpenter > > > > > > > > > > On 2012-05-09 08:07, Yoav Nir wrote: > >> I think that regardless of how it's worded, the real question is whether liability > falls to the person who sent the email (to a public mailing list) or the IETF. The > difference between "believe" and "shown" seems minor in comparison. > >> > >> -----Original Message----- > >> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of > Brian E Carpenter > >> Sent: 09 May 2012 09:52 > >> To: ietf@ietf.org > >> Subject: Re: Last Call: <draft-farrresnickel-ipr-sanctions-05.txt> (Sanctions > Available for Application to Violators of IETF IPR Policy) to Informational RFC > >> > >> I'd like to be reassured that this has been carefully reviewed by the IETF > counsel and the IETF Trust. In particular I would be interested in its possible > interaction with the IETF's liability insurance. > >> > >>> Any IETF participant can call for sanctions to be applied to anyone > >>> they believe has violated the IETF's IPR policy. This can be done by > >>> sending email to the appropriate IETF mailing list. > >> > >> That seems reasonable, but publishing such a belief without having the > wording checked by a libel lawyer might be risky. I think the draft should state > that a call for sanctions should be based on factual evidence and not on "belief". > How about > >> > >> Any IETF participant can call for sanctions to be applied to anyone > >> shown to have violated the IETF's IPR policy. This can be done by > >> sending email to the appropriate IETF mailing list, including a > >> a short summary of the relevant facts and events. > >> > >> Regards > >> Brian Carpenter > >> > >> On 2012-05-07 22:56, The IESG wrote: > >>> The IESG has received a request from an individual submitter to > >>> consider the following document: > >>> - 'Sanctions Available for Application to Violators of IETF IPR Policy' > >>> <draft-farrresnickel-ipr-sanctions-05.txt> as Informational RFC > >>> > >>> The IESG plans to make a decision in the next few weeks, and solicits > >>> final comments on this action. Please send substantive comments to the > >>> ietf@ietf.org mailing lists by 2012-06-04. Exceptionally, comments may > >>> be sent to iesg@ietf.org instead. In either case, please retain the > >>> beginning of the Subject line to allow automated sorting. > >>> > >>> Abstract > >>> > >>> > >>> The IETF has developed and documented policies that govern the > >>> behavior of all IETF participants with respect to Intellectual > >>> Property Rights (IPR) about which they might reasonably be aware. > >>> > >>> The IETF takes conformance to these IPR policies very seriously. > >>> However, there has been some ambiguity as to what the appropriate > >>> sanctions are for the violation of these policies, and how and by > >>> whom those sanctions are to be applied. > >>> > >>> This document discusses these issues and provides a suite of > >>> potential actions that may be taken within the IETF community. > >>> > >>> > >>> > >>> > >>> The file can be obtained via > >>> http://datatracker.ietf.org/doc/draft-farrresnickel-ipr-sanctions/ > >>> > >>> IESG discussion can be tracked via > >>> http://datatracker.ietf.org/doc/draft-farrresnickel-ipr-sanctions/ball > >>> ot/ > >>> > >>> > >>> No IPR declarations have been submitted directly on this I-D. > >>> > >>> > >>> > >> > >> Scanned by Check Point Total Security Gateway. > >> > > > > Scanned by Check Point Total Security Gateway.
- 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