Issue found with BCP 78 version 2

Harald Tveit Alvestrand <harald@alvestrand.no> Wed, 15 December 2004 07:52 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 CAA08657 for <ipr-wg-web-archive@ietf.org>; Wed, 15 Dec 2004 02:52:51 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CeU64-0005nY-DU for ipr-wg-web-archive@ietf.org; Wed, 15 Dec 2004 03:01:20 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CeTvb-0004C5-VG; Wed, 15 Dec 2004 02:50:32 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CeTtN-0003jd-UW for ipr-wg@megatron.ietf.org; Wed, 15 Dec 2004 02:48:14 -0500
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 CAA08262 for <ipr-wg@ietf.org>; Wed, 15 Dec 2004 02:48:12 -0500 (EST)
Received: from eikenes.alvestrand.no ([158.38.152.233]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CeU1Z-0005eV-1i for ipr-wg@ietf.org; Wed, 15 Dec 2004 02:56:41 -0500
Received: from localhost (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 2962661C23 for <ipr-wg@ietf.org>; Wed, 15 Dec 2004 08:47:42 +0100 (CET)
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 07138-05 for <ipr-wg@ietf.org>; Wed, 15 Dec 2004 08:47:40 +0100 (CET)
Received: from [192.168.1.145] (162.80-203-220.nextgentel.com [80.203.220.162]) by eikenes.alvestrand.no (Postfix) with ESMTP id 2AF1261C1C for <ipr-wg@ietf.org>; Wed, 15 Dec 2004 08:47:40 +0100 (CET)
Date: Wed, 15 Dec 2004 08:47:38 +0100
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: ipr-wg@ietf.org
Message-ID: <72F87969DF57869768A5BEA2@gloppen.hjemme.alvestrand.no>
X-Mailer: Mulberry/3.1.6 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Content-Transfer-Encoding: 7bit
Subject: Issue found with BCP 78 version 2
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: 386e0819b1192672467565a524848168
Content-Transfer-Encoding: 7bit

Folks,

the RFC Editor has identified a problem with the current rights draft, and 
has suggested a fix.

If nobody objects to this fix within a day or so, I'll tell them it's OK.

I did not want to change this without a public record.

                    Harald


---------- Forwarded Message ----------
Date: onsdag, desember 08, 2004 11:35:00 -0800
From: Bob Braden <braden@ISI.EDU>
To: rfc-editor@rfc-editor.org, sob@harvard.edu, harald@alvestrand.no
Cc: smb@research.att.com
Subject: Re: authors 48 hours: BCP 78, RFC 3907 
<draft-ietf-ipr-subm-rights-fix-00.txt> NOW AVAILABLE


Harald,

I should explain the nature of the current problem with BCP 79bis, and
my perplexity on how to fix it.

BCP 78 prescribes copyright boilerplate in an Internet Draft. In
practice, the RFC Editor inserts boilerplate that is very slightly
different for independent submissions:

 IETF submissions (text as in BCP 78):

   This document is subject to the rights, licenses and restrictions
   contained in BCP 78, and except as set forth therein, the authors
   retain all their rights.

 Independent submissions:

   This document is subject to the rights, licenses and restrictions
   contained in BCP 78 and at www.rfc-editor.org, and except as set
   forth therein, the authors retain all their rights.

This difference is consistent with the intent of the WG that developed
BCP 78, that the RFC Editor should determine the copyright rules for
independent submissions.  In particular, we have a broader allowance
for derivative works, as noted in www.rfc-editor.org/copyright.html.

In contrast, Section 5 of BCP 79 prescribes the IPR disclaimer
boilerplate that the RFC Editor must put into IETF submissions and
all RFC Editor submissions for which IPR has been declared.  It has
repeatedly been suggested to us that the simplest approach for us
is to always put in the disclaimer text, and we have agreed to this.

Unfortunately, the prescribed boilerplate includes the sentence:

      Information on the procedures with respect to rights
      in RFC documents can be found in BCP 78 and BCP 79.

This statement apparently covers BOTH BCP 78 copyright procedures and
BCP 79 patent procedures, and it is incomplete in the first case, as
noted above.

A proposed fix is to insert the following in the IPR boilerplate,

      Information on the procedures with respect to rights
      in RFC documents can be found in BCP 78, BCP 79, and
      at rfc-editor.org.

I have discussed this with Scott, and he said it "looks right".
But this change will contradict BCP 79bis (as well as BCP 79).

Is there a chance we can change BCP 79bis?

Thanks,

Bob Braden



	


---------- End Forwarded Message ----------





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