[rfc2462bis] still open issues
JINMEI Tatuya / 神明達哉 <jinmei@isl.rdc.toshiba.co.jp> Thu, 05 February 2004 16:31 UTC
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22478 for <ipv6-archive@odin.ietf.org>; Thu, 5 Feb 2004 11:31:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AomPC-0001qX-2l for ipv6-archive@odin.ietf.org; Thu, 05 Feb 2004 11:31:06 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i15GV6Dp007091 for ipv6-archive@odin.ietf.org; Thu, 5 Feb 2004 11:31:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AomPB-0001qA-Sr for ipv6-web-archive@optimus.ietf.org; Thu, 05 Feb 2004 11:31: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 LAA22469 for <ipv6-web-archive@ietf.org>; Thu, 5 Feb 2004 11:31:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AomPA-00014w-00 for ipv6-web-archive@ietf.org; Thu, 05 Feb 2004 11:31:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AomOL-0000zb-00 for ipv6-web-archive@ietf.org; Thu, 05 Feb 2004 11:30:14 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1AomNW-0000tA-00 for ipv6-web-archive@ietf.org; Thu, 05 Feb 2004 11:29:23 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AomNC-000175-0V; Thu, 05 Feb 2004 11:29:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AomMD-00011P-GZ for ipv6@optimus.ietf.org; Thu, 05 Feb 2004 11:28:01 -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 LAA22331 for <ipv6@ietf.org>; Thu, 5 Feb 2004 11:27:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AomMC-0000lq-00 for ipv6@ietf.org; Thu, 05 Feb 2004 11:28:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AomLG-0000gu-00 for ipv6@ietf.org; Thu, 05 Feb 2004 11:27:03 -0500
Received: from shuttle.wide.toshiba.co.jp ([202.249.10.124]) by ietf-mx with esmtp (Exim 4.12) id 1AomKQ-0000bg-00 for ipv6@ietf.org; Thu, 05 Feb 2004 11:26:10 -0500
Received: from ocean.jinmei.org (unknown [2001:200:0:4819:200:39ff:fe5e:cfd7]) by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 112C715263 for <ipv6@ietf.org>; Fri, 6 Feb 2004 01:26:10 +0900 (JST)
Date: Fri, 06 Feb 2004 01:26:09 +0900
Message-ID: <y7vsmhpmr1a.wl@ocean.jinmei.org>
From: JINMEI Tatuya / 神明達哉 <jinmei@isl.rdc.toshiba.co.jp>
To: ipv6@ietf.org
Subject: [rfc2462bis] still open issues
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sorry for bothering you all by the bunch of messages. This is the last one for now. (I'm afraid I'll be the "winner" of this week:-) The followings are the issues for rfc2462bis that are still open. I don't have particular proposals for them right now (particularly for the last two), and I'm afraid I won't be able to propose resolutions in the next revision of the draft. I noticed that there were discussions in the ML for (some of) the issues, which I've not completely caught up. Anyway, if you have particular opinions on some of them, please speak up by making a separate thread. If you could start the discussion with summarizing past discussions (if any), it would be great. Thanks, JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp ID 275 Many DAD related issues have been discussed, including if it is okay to omit DAD in some environments or if DAD can be replaced with DIID (duplicate interface ID detection). 277 The semantics of the M/O flags is not very clear. 281 It is not very clear if this document always require a 64-bit Interface ID. -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
- [rfc2462bis] still open issues JINMEI Tatuya / 神明達哉