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 20: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 7710E3A690D; Sat, 10 Jan 2009 12:13:33 -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 298033A69C9 for <ietf@core3.amsl.com>; Sat, 10 Jan 2009 12:13:32 -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 4znVAxBdlxQY for <ietf@core3.amsl.com>; Sat, 10 Jan 2009 12:13:31 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 387813A68DA for <ietf@ietf.org>; Sat, 10 Jan 2009 12:13:31 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1LLkCd-0000nX-9W; Sat, 10 Jan 2009 15:13:03 -0500
Date: Sat, 10 Jan 2009 15:12:54 -0500
From: John C Klensin <john-ietf@jck.com>
To: Theodore Tso <tytso@mit.edu>, Simon Josefsson <simon@josefsson.org>
Subject: Re: [Trustees] ANNOUNCEMENT: The IETF Trustees invite your reviewand comments on a proposed Work-Around to the Pre-5378 Problem
Message-ID: <7D0E9557A84E06BFB4E120CA@PST.jck.com>
In-Reply-To: <20090110191055.GB31579@mit.edu>
References: <FB8A848E-E415-4CDE-9E3F-5C74A5614F18@cisco.com> <49678B2A.8000100@dcrocker.net> <20090109181503.GP24908@verdi> <6E372F257B0C42E7AB9B7DA6231FF4E4@LROSENTOSHIBA> <p06240800c58d5466241b@[10.227.48.131]> <DBAA71AA401E5398212B1E03@PST.jck.com> <4967CAA1.9020608@gmail.com> <B2385D8E5F5BA599A174BD43@PST.jck.com> <4967E348.7050300@joelhalpern.com> <87d4evgu35.fsf@mocca.josefsson.org> <20090110191055.GB31579@mit.edu>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Disposition: inline
Cc: '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

+1

It seems to me that we are spending a great deal of energy on
non-problems (including the one Ted discusses below) and too
little time on real issues... like how to encourage people to do
real work around here (where requiring authors try to figure out
who might have contributed parts of a document that a
predecessor to one they are working on and get them to sign off
is not "encouragement").

    john


--On Saturday, January 10, 2009 14:10 -0500 Theodore Tso
<tytso@mit.edu> wrote:

> At least in the linux kernel, quoting a 2-3 sentences of an
> RFC in comments is common practice, even before RFC 5378.  It
> is also been done with great frequency in documentation,
> magazine articles and journals, and so on.  Fair use takes
> care of this problem, and there I don't think even the most
> insanely paranoid and unreasonable corporate lawyer would
> think that 2-3 sentences quoted in manuals, code, etc., would
> be unreasonable.  
> 
> Certainly this is something where we have over two decades
> historical practice, and if anyone thinks an IETF contributor
> or company would be suicidially idiotic enough from a Public
> Relations point of view to try to sue someone for using 2-3
> sentences when this would be pretty clearly fair use, and the
> reputations of said IETF contributor or company would be
> pilloried in the press, I would gently suggest that whoever is
> worried about is greatly disconneted from reality, if they
> were to think about the risks involved.




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