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 07:45 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 0C19D21F85B5 for <ietf@ietfa.amsl.com>; Wed, 9 May 2012 00:45:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.408
X-Spam-Level:
X-Spam-Status: No, score=-10.408 tagged_above=-999 required=5 tests=[AWL=0.191, 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 Ym0vz3on4uyy for <ietf@ietfa.amsl.com>; Wed, 9 May 2012 00:45:03 -0700 (PDT)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 8629121F859E for <ietf@ietf.org>; Wed, 9 May 2012 00:44:50 -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 q497ifYM031985; Wed, 9 May 2012 10:44:41 +0300
X-CheckPoint: {4FAA2DE6-2-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 10:44:40 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Date: Wed, 09 May 2012 10:44:42 +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: Ac0tt5Z/rJewtmUURm6iFnZ4sUan0A==
Message-ID: <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>
In-Reply-To: <4FAA1A6A.5070500@gmail.com>
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 07:45:05 -0000
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