Re: When will the updated IPR RFCs be available?

Bill Fenner <fenner@gmail.com> Wed, 23 February 2005 03:44 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 WAA21745 for <ipr-wg-web-archive@ietf.org>; Tue, 22 Feb 2005 22:44:28 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3noX-0005fe-5e for ipr-wg-web-archive@ietf.org; Tue, 22 Feb 2005 23:07:53 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3NVX-0005qG-TI; Mon, 21 Feb 2005 19:02:31 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3Lm5-0007DQ-UL for ipr-wg@megatron.ietf.org; Mon, 21 Feb 2005 17:11:29 -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 RAA20997 for <ipr-wg@ietf.org>; Mon, 21 Feb 2005 17:11:22 -0500 (EST)
Received: from rproxy.gmail.com ([64.233.170.203]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3M8L-0006Un-K3 for ipr-wg@ietf.org; Mon, 21 Feb 2005 17:34:31 -0500
Received: by rproxy.gmail.com with SMTP id a41so356580rng for <ipr-wg@ietf.org>; Mon, 21 Feb 2005 14:11:21 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=o6cSKjiw30KZer/+lpEGcphlrhvdOJqdQRB5dy4xhPJf0khvln4Fw7leBaE1occIrEXFwyMu3Q3Cb5NO/DZSvNDct1K/une2zWTX2yZ694nPnEub7tYSWRqWfXIKceUsRzTiQss4wyHjiQ7XxyTzvi+9Emw+hYO3SSrYPUbrCuI=
Received: by 10.38.76.5 with SMTP id y5mr64064rna; Mon, 21 Feb 2005 14:11:21 -0800 (PST)
Received: by 10.38.10.4 with HTTP; Mon, 21 Feb 2005 14:11:21 -0800 (PST)
Message-ID: <ed6d469d0502211411ed2eab@mail.gmail.com>
Date: Mon, 21 Feb 2005 14:11:21 -0800
From: Bill Fenner <fenner@gmail.com>
To: ipr-wg@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: 7bit
Subject: Re: When will the updated IPR RFCs be available?
X-BeenThere: ipr-wg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Bill Fenner <fenner@gmail.com>
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: 50a516d93fd399dc60588708fd9a3002
Content-Transfer-Encoding: 7bit

On Tuesday, January 4, 2005, Harald Tveit Alvestrand wrote:
>As soon as the WG chair and the AD agree on a resolution to the
>issue raised in the thread marekd "Issue found with BCP 78 version 2".

I haven't been on the mailing list, so I'm looking through the
spam-laden archives; I think Harald is talking about

http://www1.ietf.org/mail-archive/web/ipr-wg/current/msg02552.html

Other than 4 replies suggesting a full URL, I don't see any
other messages suggesting that a resolution has been made.

Now I see that the proto-RFCs have been renumbered in the
author's queue, so the RFC-Editor's (apparently premature)
announcement in DC of the new numbers is obsolete.  (see
http://www1.ietf.org/proceedings_new/04nov/slides/plenaryw-2.pdf
slide #3).

What still has to happen for these RFCs to be published?
- The only opinions on the WG list seemed to be for changing
the URL to an absolute one; dunno whether to call that WG
consensus or how things are proceeding behind the
scenes.

- When I was creating a draft 1id-guidelines update for
these new RFCs, I noticed that the RFC-Editor copyright
statements A and B still say "I accept the provisions of ...";
changing these words in section 5.1 seemed to be the whole
point of revising rfc3667 in the first place.  [Normally I wouldn't
suggest a substantive change to a document in the RFC-Editor's
queue but clearly the other open issue is such a change]

- Although it's a relatively minor issue, these *were* publically
announced as RFC 3907/3908; was there a reason to change
the numbers?


I hate to be a party pooper, but it's been 9 months since this
"quick fix" was first published as an I-D where we all promised
to handle it expeditiously.  It's distressing to see this much
delay and change.

Thanks,
  Bill

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