Re: 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> Thu, 08 January 2009 22:28 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 ED66C28C0F5; Thu, 8 Jan 2009 14:28:17 -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 412143A68A2; Thu, 8 Jan 2009 14:28:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.569
X-Spam-Level:
X-Spam-Status: No, score=-2.569 tagged_above=-999 required=5 tests=[AWL=0.030, 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 qEJaKrEgERxb; Thu, 8 Jan 2009 14:28:15 -0800 (PST)
Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.184]) by core3.amsl.com (Postfix) with ESMTP id A91D73A68B5; Thu, 8 Jan 2009 14:28:14 -0800 (PST)
Received: by ti-out-0910.google.com with SMTP id a6so6210089tib.25 for <multiple recipients>; Thu, 08 Jan 2009 14:28:00 -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=UcVxKdfTcu/9TIuEyGc+cKBbKAXQ7tMPwbJNYmKSeyQ=; b=huYxNpBVWVuNo2CuGQqvz5uR/ipXCqDijqvz/dn2GoKl6LQ7zllzd5+yNEzQ9ie1cR 7PHrhtGGnzih1sq3Ejcaq6Bcv78QNmhsreUuwsydSu/s3iCAC9GNSweIM+2CsKDm0kQv zSynO+gr7yIrv17+7GJzAL+4aPMlTMXQto7xo=
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=p+0i0OjJbgnxMp2BaLEpUhC9FM7/C+7YXo2J+pvd5IfUBALOAShBsO0aI6BF1tlae9 d9u16oNSzDAkfT3TG5qWP7KheDooNmUbWNwW4hTTGBzPrtMADeS7YsKrKIps8SjlStdM Ko214kKwFA7M/zQwXPyTATdC6Pmp3cudiL9nI=
Received: by 10.110.28.15 with SMTP id b15mr8689010tib.56.1231453680704; Thu, 08 Jan 2009 14:28:00 -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 a14sm2235434tia.32.2009.01.08.14.27.56 (version=SSLv3 cipher=RC4-MD5); Thu, 08 Jan 2009 14:27:59 -0800 (PST)
Message-ID: <49667DEF.6010900@gmail.com>
Date: Fri, 09 Jan 2009 11:27:59 +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: Ed Juskevicius <edj.etc@gmail.com>
Subject: Re: ANNOUNCEMENT: The IETF Trustees invite your review and comments on a proposed Work-Around to the Pre-5378 Problem
References: <70873A2B7F744826B0507D4B84903E60@noisy>
In-Reply-To: <70873A2B7F744826B0507D4B84903E60@noisy>
Cc: 'Trustees' <trustees@ietf.org>, wgchairs@ietf.org, 'IETF Discussion' <ietf@ietf.org>, iab@iab.org, iesg@ietf.org, rfc-editor@rfc-editor.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="utf-8"
Content-Transfer-Encoding: base64
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

Ed,

Thanks for this.

As I understand it, the proposal boils down to adding a disclaimer to
affected documents that reads:

"This document contains material from IETF Documents or IETF Contributions
published before November 10, 2008 and, to the Contributor’s knowledge,
the person(s) controlling the copyright in such material have not granted
the IETF Trust the right to allow modifications of such material outside
the IETF Standards Process. Without obtaining an adequate license from the
person(s) controlling the copyright, this document may not be modified outside
the IETF Standards Process, and derivative works of it may not be created
outside the IETF Standards Process, except to format it for publication as
an RFC and to translate it into languages other than English."

That's a little bit long-winded but I agree that this is a correct fix.
However, I didn't see in your note an explanation of the procedure
for approving the use of this boilerplate (and preventing it being
used simply as an easy way out). Rather than ranting about that, I
will shortly submit an I-D that makes a concrete and, I hope, simple
proposal for that as a fix to RFC5378. I see no reason that we need
to revisit RFC5378 in a fundamental way.

Regards

      Brian

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