Re: Problems with draft-ietf-ipr-subm-rights-fix

Brian E Carpenter <brc@zurich.ibm.com> Wed, 22 September 2004 11:31 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26116 for <ipr-wg-web-archive@ietf.org>; Wed, 22 Sep 2004 07:31:28 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CA5Rx-0004Y5-DK for ipr-wg-web-archive@ietf.org; Wed, 22 Sep 2004 07:38:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CA5JK-0001iB-Hv; Wed, 22 Sep 2004 07:29:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CA5HY-0001Ag-Rd for ipr-wg@megatron.ietf.org; Wed, 22 Sep 2004 07:27:32 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25746 for <ipr-wg@ietf.org>; Wed, 22 Sep 2004 07:27:28 -0400 (EDT)
Received: from mtagate4.de.ibm.com ([195.212.29.153]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CA5O1-0004RW-Mj for ipr-wg@ietf.org; Wed, 22 Sep 2004 07:34:17 -0400
Received: from d12nrmr1507.megacenter.de.ibm.com (d12nrmr1507.megacenter.de.ibm.com [9.149.167.1]) by mtagate4.de.ibm.com (8.12.10/8.12.10) with ESMTP id i8MBQqLi103662; Wed, 22 Sep 2004 11:26:52 GMT
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232]) by d12nrmr1507.megacenter.de.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id i8MBQq3V195432; Wed, 22 Sep 2004 13:26:52 +0200
Received: from zurich.ibm.com (sig-9-145-252-205.de.ibm.com [9.145.252.205]) by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id NAA78286; Wed, 22 Sep 2004 13:26:50 +0200
Message-ID: <4151617A.1010604@zurich.ibm.com>
Date: Wed, 22 Sep 2004 13:26:50 +0200
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en, fr, de
MIME-Version: 1.0
To: Harald Tveit Alvestrand <harald@alvestrand.no>
References: <78DE523C593F1423F9435FD7@B50854F0A9192E8EC6CDA126>
In-Reply-To: <78DE523C593F1423F9435FD7@B50854F0A9192E8EC6CDA126>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Content-Transfer-Encoding: 7bit
Cc: ipr-wg@ietf.org
Subject: Re: Problems with draft-ietf-ipr-subm-rights-fix
X-BeenThere: ipr-wg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPR-WG <ipr-wg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipr-wg>, <mailto:ipr-wg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipr-wg@ietf.org>
List-Help: <mailto:ipr-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipr-wg>, <mailto:ipr-wg-request@ietf.org?subject=subscribe>
Sender: ipr-wg-bounces@ietf.org
Errors-To: ipr-wg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Content-Transfer-Encoding: 7bit

below...

Harald Tveit Alvestrand wrote:
> Hello,
> 
> IETF Last Call and IESG discussion uncovered 2 problems with the 
> proposed draft-ietf-ipr-subm-rights-fix.
> Both were actually problems with RFC 3667....
> 
> 1) C. M. Heard discovered that section 6 did not permit an RFC Editor 
> contribution to be published with the standard copyright notice and 
> disclaimer; as written, it only permits the special variants given there.
> 
> 2) The RFC Editor discovered that one word had been changed from RFC 
> 3667 to draft-ietf-ipr-subm-rights-fix; section 4.2 a(A) was changed 
> from reading "RFC" to "Internet Draft".
> 
> This turns out to be a change from the i-d version of the document to 
> the RFC version that none of the authors caught in Auth48.
> This illustrates the fact that 4.2 only says that the authors grant the 
> right to publish the draft, not to publish the RFC.... this seems 
> strange to the RFC Editor.
> 
> Suggested disposition (AD's opinion):
> 
> For 1): Change section 6 bullet b to contain 3 alternatives, the third 
> one being:
> 
>        C. The Copyright Notice specified in Section 5.4 and the
>           disclaimer specified in section 5.5
> 

Looks good.

> For 2): Ignore the issue in this revision, and leave it to the RFC 
> Editor's "instructions to RFC Authors" to say that a request to publish 
> a draft as an RFC is taken to mean that permission to do so is granted.

OK, but this is a BCP and the instructions to authors are Informational.
It seems odd to have an Informational overriding a BCP.

    Brian

> 
> If this is found reasonable by the WG, I can do this via an RFC Editor 
> note, and have the document on the way to the RFC Editor as soon as it's 
> clear the WG finds it reasonable.
> 
> Your thoughts?
> 
>                   Harald
> 
> 
> _______________________________________________
> Ipr-wg mailing list
> Ipr-wg@ietf.org
> https://www1.ietf.org/mailman/listinfo/ipr-wg
> 

_______________________________________________
Ipr-wg mailing list
Ipr-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/ipr-wg