Re: IPv6 WG Document Status

Margaret Wasserman <margaret@thingmagic.com> Wed, 03 November 2004 16:05 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 LAA22173 for <ipv6-web-archive@ietf.org>; Wed, 3 Nov 2004 11:05:50 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPNtI-0000A0-Uw for ipv6-web-archive@ietf.org; Wed, 03 Nov 2004 11:21:45 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPNaE-0007l2-JX; Wed, 03 Nov 2004 11:02:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPNVA-0006cp-0g for ipv6@megatron.ietf.org; Wed, 03 Nov 2004 10:56:48 -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 KAA21494 for <ipv6@ietf.org>; Wed, 3 Nov 2004 10:56:45 -0500 (EST)
Received: from mail.thingmagic.com ([207.31.248.245] helo=thingmagic.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPNkU-0008Oi-VH for ipv6@ietf.org; Wed, 03 Nov 2004 11:12:39 -0500
Received: from [10.0.0.75] (account margaret HELO [192.168.2.2]) by thingmagic.com (CommuniGate Pro SMTP 4.1.8) with ESMTP-TLS id 185604; Wed, 03 Nov 2004 10:51:01 -0500
Mime-Version: 1.0
X-Sender: margaret@mail.thingmagic.com
Message-Id: <p0602045dbdaea9ff66dc@[192.168.2.2]>
In-Reply-To: <Pine.LNX.4.61.0411021950220.20018@netcore.fi>
References: <C1FB6232-2CF0-11D9-9F4D-000D93330CAA@innovationslab.net> <Pine.LNX.4.61.0411021950220.20018@netcore.fi>
Date: Wed, 03 Nov 2004 10:56:14 -0500
To: Pekka Savola <pekkas@netcore.fi>, Brian Haberman <brian@innovationslab.net>
From: Margaret Wasserman <margaret@thingmagic.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Cc: IPv6 WG <ipv6@ietf.org>
Subject: Re: IPv6 WG Document Status
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4

At 7:53 PM +0200 11/2/04, Pekka Savola wrote:
>>  http://www.innovationslab.net/~brian/IETF61/IPv6/IPv6DocumentStatus.html
>
>
>Generic comment: is token really on Margaret w/ all of those AD 
>followup documents?

Hi Pekka,
Sort of...  When a document is updated, the document automatically 
goes to the AD Followup state until AD decides what other state it 
should be moved to.  Sometimes that takes a little while...

Let me give a bit more information about the IPv6 documents that I 
currently have in AD Followup.

The two MIBs (draft-ietf-ipv6-inet-tunnel-mib-03.txt and 
draft-ietf-ipv6-rfc2013-update-04.txt) were nearly approved during 
their first IESG telechat last week.  IANA had some questions (asked 
28-Oct), so Bert is holding a discuss until those questions are 
resolved.  The authors have answered the questions (on 28-Oct and 
29-Oct), and we're waiting for confirmation from IANA that their 
issues has been addressed.  I suppose I could put these into 
"External Party", but I want to remember to follow up if we don't 
hear from IANA before the IETF meeting.

The router selection draft (draft-ietf-ipv6-router-selection-06.txt) 
was updated on 14-Oct to address IESG discuss comments (from Steve 
Bellovin, Bill Fenner, Bert Wijnen and Alex Zinin).  There is ongoing 
discussion (last message on 2-Nov) between the author (Dave Thaler) 
and (some of?) the discuss-holders about whether or not their 
comments have been adequately addressed.  It appears that completely 
addressing the issues will require another document re-spin, so this 
will probably go back into "Revised ID Needed" once we know what is 
required.  I have not yet figured out whether a conference call will 
be needed to discuss the issues with this document, so I am keepign 
in AD Followup for now.

The ULA document (draft-ietf-ipv6-unique-local-addr-07.txt) also had 
several IESG discuss comments (from Steve Bellovin, Bill Fenner, Ted 
Hardie and Alex Zinin).  The document was updated (on 25-Oct) to 
address the most straightforward of those comments, but none of the 
ADs have indicated that their issues are fully addressed yet (by 
clearing their discuss).  I may need to review the changes and ask 
specific ADs to clear their discusses, but I haven't done that yet. 
It will definitely take at least one more round of updates to address 
all of the AD concerns with this document, though, and discussion is 
ongoing between various ADs and authors about this.  Also, there is 
an ongoing discussion of this document in ARIN that may need  to be 
considered if/when it converges on a specific recommendation.

So, all four of these documents are in AD Followup, because I need to 
track the conversations and determine what the next steps should be. 
However, I don't believe that any of these documents is blocking on 
an action from me at this particular moment.

Does that make sense?

Margaret






--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------