Re: ANNOUNCEMENT: The IETF Trustees invite your comments on ...

John C Klensin <john-ietf@jck.com> Thu, 29 January 2009 15:13 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3815828C15A; Thu, 29 Jan 2009 07:13:48 -0800 (PST)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 44C7928C119 for <ietf@core3.amsl.com>; Thu, 29 Jan 2009 07:13:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.609
X-Spam-Level:
X-Spam-Status: No, score=-2.609 tagged_above=-999 required=5 tests=[AWL=-0.010, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fu95nRqFnpSk for <ietf@core3.amsl.com>; Thu, 29 Jan 2009 07:13:46 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id DD68B28C15A for <ietf@ietf.org>; Thu, 29 Jan 2009 07:13:45 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1LSYa6-000CaB-HC; Thu, 29 Jan 2009 10:13:26 -0500
Date: Thu, 29 Jan 2009 10:13:25 -0500
From: John C Klensin <john-ietf@jck.com>
To: Dean Willis <dean.willis@softarmor.com>
Subject: Re: ANNOUNCEMENT: The IETF Trustees invite your comments on ...
Message-ID: <81505B356E235991A3511BF0@PST.JCK.COM>
In-Reply-To: <EF8706F0-F195-4629-A31B-6A25D6E46EB5@softarmor.com>
References: <20090124154913.53426.qmail@simone.iecc.com> <B5720E65D2354F659809CA433C4D0C59@DGBP7M81> <p06240814c5a109bd52c0@[165.227.249.206]> <EF8706F0-F195-4629-A31B-6A25D6E46EB5@softarmor.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

--On Thursday, January 29, 2009 0:58 -0600 Dean Willis
<dean.willis@softarmor.com> wrote:

> The real risk is where some other SDO can hold IETF liable for
> damages induced by the irrational aggrievement of someone who
> contributed to the IETF.

I might add "aggrievement" (rational or otherwise) of someone
who contributed to the work in the IETF and suddenly finds him
or herself unable to obtain a copy of the derived and updated
standard except at a high per-copy price backed by credible
threats of prosecution for illegal copies.  The IESG could
probably figure out ways to head off that particular situation,
which, personally, I'd consider A Good Thing too, but it is
rather a different topic.

> While we can't do much about the
> irrational contributor, we can at least avoid making express
> commitments to indemnify third parties who use our
> pre-5378-note-well specifications. This puts the conflict
> between the irrationally aggrieved party and the third party,
> leaving the IETF out of the shooting, which is a Good Thing.

Yes, exactly.

    john

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf