implementation reports for rfc246[01]bis (Re: RFC 2461- issue list)

JINMEI Tatuya / 神明達哉 <jinmei@isl.rdc.toshiba.co.jp> Mon, 03 November 2003 23:51 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04322 for <ipv6-archive@odin.ietf.org>; Mon, 3 Nov 2003 18:51:49 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGoTl-0002tL-KZ for ipv6-archive@odin.ietf.org; Mon, 03 Nov 2003 18:51:31 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA3NpPjn011110 for ipv6-archive@odin.ietf.org; Mon, 3 Nov 2003 18:51:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGoTk-0002t7-LY for ipv6-web-archive@optimus.ietf.org; Mon, 03 Nov 2003 18:51:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04273 for <ipv6-web-archive@ietf.org>; Mon, 3 Nov 2003 18:51:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AGoTh-0000ux-00 for ipv6-web-archive@ietf.org; Mon, 03 Nov 2003 18:51:21 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AGoTh-0000uu-00 for ipv6-web-archive@ietf.org; Mon, 03 Nov 2003 18:51:21 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGoTO-0002jV-QU; Mon, 03 Nov 2003 18:51:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGoST-0002i5-Md for ipv6@optimus.ietf.org; Mon, 03 Nov 2003 18:50:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04207 for <ipv6@ietf.org>; Mon, 3 Nov 2003 18:49:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AGoSQ-0000tL-00 for ipv6@ietf.org; Mon, 03 Nov 2003 18:50:02 -0500
Received: from shuttle.wide.toshiba.co.jp ([202.249.10.124]) by ietf-mx with esmtp (Exim 4.12) id 1AGoSP-0000tH-00 for ipv6@ietf.org; Mon, 03 Nov 2003 18:50:02 -0500
Received: from ocean.jinmei.org (unknown [2001:4f8:3:bb:208:dff:fe40:3f37]) by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 4B7B915214; Tue, 4 Nov 2003 08:50:00 +0900 (JST)
Date: Tue, 04 Nov 2003 08:49:58 +0900
Message-ID: <y7vu15lnhax.wl@ocean.jinmei.org>
From: JINMEI Tatuya / 神明達哉 <jinmei@isl.rdc.toshiba.co.jp>
To: Pekka Savola <pekkas@netcore.fi>
Cc: ipv6@ietf.org
Subject: implementation reports for rfc246[01]bis (Re: RFC 2461- issue list)
In-Reply-To: <Pine.LNX.4.44.0310240927150.19368-100000@netcore.fi>
References: <9C422444DE99BC46B3AD3C6EAFC9711B047CA17F@tayexc13.americas.cpqcorp.net> <Pine.LNX.4.44.0310240927150.19368-100000@netcore.fi>
User-Agent: Wanderlust/2.10.1 (Watching The Wheels) Emacs/21.3 Mule/5.0 (SAKAKI)
Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan.
MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen")
Content-Type: text/plain; charset="US-ASCII"
Sender: ipv6-admin@ietf.org
Errors-To: ipv6-admin@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Id: IP Version 6 Working Group (ipv6) <ipv6.ietf.org>
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>

>>>>> On Fri, 24 Oct 2003 09:41:35 +0300 (EEST), 
>>>>> Pekka Savola <pekkas@netcore.fi> said:

> My initial thought is also that we should not make RFC 2461bis (or
> 2462bis) include every extension specified since 1998.  Those can stay
> very well in separate drafts.  Of course, we should still consider whether
> we want to enable the base spec to give more flexibility (e.g., the
> solicitation timers etc.) for those extensions.  There is a clear 
> distinction between these two, IMHO.

> Another thought: if we recycle RFC2461bis to DS, I think we should re-do
> the implementation reports if we changed the code (not sure whether new
> reports is _required_..).  This may not be a bad thing, as the current
> implementation reports should (IMHO) be a bit more detailed than that..

(I'm writing this since I don't think I've seen a message replying to
this part.  But if I miss it, please just ignore this one.)

Yes, we're planning to call for implementation reports when
rfc246[01]bis are ready to be recycled to DS.

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba Corp.
					jinmei@isl.rdc.toshiba.co.jp

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