Re: [Trustees] ANNOUNCEMENT: The IETF Trustees invite your reviewand comments on a proposed Work-Around to the Pre-5378 Problem

John C Klensin <john-ietf@jck.com> Sat, 10 January 2009 00:15 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 08D4B28C175; Fri, 9 Jan 2009 16:15:49 -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 EBC0228C175 for <ietf@core3.amsl.com>; Fri, 9 Jan 2009 16:15:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.637
X-Spam-Level:
X-Spam-Status: No, score=-2.637 tagged_above=-999 required=5 tests=[AWL=-0.038, 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 Ih+5z65GGblL for <ietf@core3.amsl.com>; Fri, 9 Jan 2009 16:15:47 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id EFF9928C16E for <ietf@ietf.org>; Fri, 9 Jan 2009 16:15:46 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1LLRVX-000GW5-5q; Fri, 09 Jan 2009 19:15:19 -0500
Date: Fri, 09 Jan 2009 19:15:11 -0500
From: John C Klensin <john-ietf@jck.com>
To: dcrocker@bbiw.net
Subject: Re: [Trustees] ANNOUNCEMENT: The IETF Trustees invite your reviewand comments on a proposed Work-Around to the Pre-5378 Problem
Message-ID: <4E10214514ADCED6F48CE2C3@PST.jck.com>
In-Reply-To: <4967DD05.6080301@dcrocker.net>
References: <70873A2B7F744826B0507D4B84903E60@noisy> <"FB8A848E-E415-4CDE-9E3F-5C74A561 4F18"@cisco.com> <49678B2A.8000100@dcrocker.net> <20090109181503.GP24908@verdi> <6E372F257B0C42E7AB9B7DA6231FF4E4@LROSENTOSHIBA> <p06240800c58d5466241b@[10.227.48.131]> <DBAA71AA401E5398212B1E03@PST.jck.com> <01N43GNGOAFY00007A@mauve.mrochek.com> <4967DD05.6080301@dcrocker.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Disposition: inline
Cc: ned+ietf@mauve.mrochek.com, 'IETF Discussion' <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 Friday, January 09, 2009 15:25 -0800 Dave CROCKER
<dhc2@dcrocker.net> wrote:

> ned+ietf@mauve.mrochek.com wrote:
>> This is EXACTLY the approach we should be using: Formulate a
>> set of goals, get agreement on them, and only then ask the
>> laywers to turn that informal specification into competent
>> legalese.
> ...
>> The difference was like night and day. 
> 
> 
> +1
> 
> That matches my experience, over the years.

If my memory is correct, that was exactly the basis on which the
most recent IPR WG was told to proceed.  For one reason or
another, it ended up expressing its ideas of the principles in
the form of quasi-legal documents (or, if you prefer, documents
containing legal-language statements) rather than publishing a
clear statement of those principles independent of those
documents.

In fairness to the WG, that turned out to be easier, especially
in the absence of clear consensus about which problems were most
important.

If the community -- and assorted ADs -- learn anything from this
experience it should be, IMO, that if such a document shows up
on Last Call instead of (or without) a normative statement of
principles against which legal text can be checked and verified,
we should Just Say No.

But that discussion doesn't help much with the short-term
problem.

    john





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