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

Brian E Carpenter <brian.e.carpenter@gmail.com> Sat, 10 January 2009 20:32 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 2188428C18B; Sat, 10 Jan 2009 12:32:07 -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 752513A689E for <ietf@core3.amsl.com>; Sat, 10 Jan 2009 12:32:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.972
X-Spam-Level:
X-Spam-Status: No, score=-1.972 tagged_above=-999 required=5 tests=[AWL=-0.613, BAYES_00=-2.599, SARE_LWSHORTT=1.24]
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 CshbQyeW1zcb for <ietf@core3.amsl.com>; Sat, 10 Jan 2009 12:32:04 -0800 (PST)
Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.189]) by core3.amsl.com (Postfix) with ESMTP id E7F0A3A6888 for <ietf@ietf.org>; Sat, 10 Jan 2009 12:32:03 -0800 (PST)
Received: by ti-out-0910.google.com with SMTP id a6so7029013tib.25 for <ietf@ietf.org>; Sat, 10 Jan 2009 12:31:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=AKScxdMPLz414lt0cabgtMXeqepb+H+e+xAq4oYmEv0=; b=C3g1KLKKOP+RK8IQ2tgp2K8t0HXglZ8cqUVXOwl4Ru7CK1u31Bc92NcwDbiPT79A6N z46aYb7e7I46BeMTHu89JXu+x9OupvjNO2OyEmxS/SQOV7Z51P53w4Id/jVcphpszEbg aVFRcwFCZnSqGcWxTSQlgiPK+uW0cfLY4wSTg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=Dcudbkrj4dnlfr/xpg/yfzYiDzsQ17l8QpPtVxKdKsc/3WsjoD1ITe6cCs+DoLTp6v Vg1x0rzmuGSP9Xt6G6ZBgrzrxaWloNrPALASRpxc5M3tOWQpC5lG5aclP4/46ukTnvim Ubz532ud/NCBW/yTH+7uEhjFJatnwfI9QuoOA=
Received: by 10.110.105.5 with SMTP id d5mr18535528tic.11.1231619508944; Sat, 10 Jan 2009 12:31:48 -0800 (PST)
Received: from ?10.1.1.4? (118-93-185-90.dsl.dyn.ihug.co.nz [118.93.185.90]) by mx.google.com with ESMTPS id i9sm5256591tid.25.2009.01.10.12.31.45 (version=SSLv3 cipher=RC4-MD5); Sat, 10 Jan 2009 12:31:48 -0800 (PST)
Message-ID: <496905AF.7090209@gmail.com>
Date: Sun, 11 Jan 2009 09:31:43 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: [Trustees] ANNOUNCEMENT: The IETF Trustees invite your review and comments on a proposed Work-Around to the Pre-5378 Problem
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> <7D0E9557A84E06BFB4E120CA@PST.jck.com>
In-Reply-To: <7D0E9557A84E06BFB4E120CA@PST.jck.com>
Cc: Simon Josefsson <simon@josefsson.org>, Theodore Tso <tytso@mit.edu>, '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.

Which is why I suggest that we should support the Trustees' proposed
short term fix, to allow normal work to continue +/- cutting and pasting
some boilerplate. We do have a glitch in 5378 to mend, but let's get that
off the critical path.

   Brian

On 2009-01-11 09:12, John C Klensin wrote:
> +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
> 
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf