[ietf-provreg] okay, now for the next item(s)

Edward Lewis <edlewis@arin.net> Mon, 05 May 2003 19:36 UTC

Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13635 for <provreg-archive@ietf.org>; Mon, 5 May 2003 15:36:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Clng-00008V-00 for provreg-archive@ietf.org; Mon, 05 May 2003 15:39:00 -0400
Received: from nic.cafax.se ([192.71.228.17]) by ietf-mx with esmtp (Exim 4.12) id 19Clna-00008M-00 for provreg-archive@ietf.org; Mon, 05 May 2003 15:38:54 -0400
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.9/8.12.9) with ESMTP id h45JLRRN021412 for <ietf-provreg-outgoing@nic.cafax.se>; Mon, 5 May 2003 21:21:27 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]]) by nic.cafax.se (8.12.9/8.12.9/Submit) id h45JLRug021411 for ietf-provreg-outgoing; Mon, 5 May 2003 21:21:27 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from smtp2.arin.net (smtp2.arin.net [192.149.252.32]) by nic.cafax.se (8.12.9/8.12.9) with ESMTP id h45JLPRN021406 for <ietf-provreg@cafax.se>; Mon, 5 May 2003 21:21:26 +0200 (MEST)
Received: by smtp2.arin.net (Postfix, from userid 5003) id 5A85A2F8; Mon, 5 May 2003 15:21:25 -0400 (EDT)
Received: from arin.net (mta [192.136.136.126]) by smtp2.arin.net (Postfix) with ESMTP id C76D22F4; Mon, 5 May 2003 15:21:24 -0400 (EDT)
Received: from [127.0.0.1] (HELO [192.149.252.108]) by arin.net (CommuniGate Pro SMTP 4.1b4) with ESMTP id 225148; Mon, 05 May 2003 15:10:43 -0400
Mime-Version: 1.0
X-Sender: edlewis@127.0.0.1
Message-Id: <a05111b04badc65b02231@[192.149.252.108]>
Date: Mon, 05 May 2003 15:21:20 -0400
To: ietf-provreg@cafax.se
From: Edward Lewis <edlewis@arin.net>
Subject: [ietf-provreg] okay, now for the next item(s)
Cc: Edward Lewis <edlewis@arin.net>, jaap@sidn.nl
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,SIGNATURE_SHORT_SPARSE,SPAM_PHRASE_00_01 version=2.43-arin1
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

As Ted has mentioned, the IESG will be considering our core documents 
real soon.

We have two other outstanding items, okay three.

One is to clean up the milestones - a couple on the web page should 
have been deleted.

Two is that alternative transports is an issue that is essentially 
dead in the WG.  Not saying that alternative transports are illegal, 
forbidden, or otherwise politically untenable, just that there hasn't 
been enough energy to date to work on them as a WG item.  I don't 
foresee any lightening bolts in this area hitting soon, and 
considering that we just have one more work item, it might be that 
the WG is shut down without a second transport document.  (See my 
note below about what shutting down the group means.)

Three is the remaining WG draft:
    http://www.ietf.org/internet-drafts/draft-ietf-provreg-epp-ext-01.txt

In the next few days-weeks I anticipate a last call on this document, 
probably at least overlapping with the RIPE meeting next week.  (Jaap 
and I will be there, we can collect comments in person.)  When we 
pass this up, it will go as Informational.

What does it mean to close a WG?  It means that there are no formal 
document discussions, no IETF in person meetings, no nagging chairs 
whining about process and consensus.  However, you still have a 
mailing list, so long as there is a volunteer to maintain it.  (I'm 
not saying that cafax.se has hinted that it would pull the list 
service, but it is something to keep in mind, someone might want to 
be ready to take it over if need be.)

I'm sure there will be traffic on the list after the group closes 
down.  I'll stay subscribed for reference purposes, for one.  On this 
list implementation issues can be discussed and collected until it is 
time to progress from Proposed to Draft Standard.  When that time 
comes, a new WG will be formed to do the needed document review - and 
I trust that the formation of that will be a lot easier than the 
formation of the current one (there'll be a pre-existing charter to 
copy).

-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis                                            +1-703-227-9854
ARIN Research Engineer

Note to pilots: a three-point landing SHOULD NOT include a wing.