Re: [dhcwg] [Question]DHCPv6 implementations
JINMEI Tatuya / 神明達哉 <jinmei@isl.rdc.toshiba.co.jp> Fri, 25 June 2004 03:14 UTC
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA17352; Thu, 24 Jun 2004 23:14:15 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bdh3v-0007zt-Tb; Thu, 24 Jun 2004 23:07:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bdgf3-0002UW-C8 for dhcwg@megatron.ietf.org; Thu, 24 Jun 2004 22:41:53 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15838 for <dhcwg@ietf.org>; Thu, 24 Jun 2004 22:41:50 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1Bdgf1-000275-IL for dhcwg@ietf.org; Thu, 24 Jun 2004 22:41:51 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Bdge5-0001iQ-00 for dhcwg@ietf.org; Thu, 24 Jun 2004 22:40:54 -0400
Received: from shuttle.wide.toshiba.co.jp ([202.249.10.124]) by ietf-mx with esmtp (Exim 4.12) id 1Bdgcg-0001K2-00 for dhcwg@ietf.org; Thu, 24 Jun 2004 22:39:26 -0400
Received: from ocean.jinmei.org (unknown [3ffe:501:100f:1048:acae:2aa0:194e:20bc]) by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 6DEA21525D; Fri, 25 Jun 2004 11:39:19 +0900 (JST)
Date: Fri, 25 Jun 2004 11:39:26 +0900
Message-ID: <y7vsmcks6n5.wl@ocean.jinmei.org>
From: JINMEI Tatuya / 神明達哉 <jinmei@isl.rdc.toshiba.co.jp>
To: strates <strates@mail.ru>
Subject: Re: [dhcwg] [Question]DHCPv6 implementations
In-Reply-To: <1489.040621@mail.ru>
References: <1489.040621@mail.ru>
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"
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
Cc: dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
>>>>> On Mon, 21 Jun 2004 02:08:39 +0400, >>>>> strates <strates@mail.ru> said: > - KAME implementation for *BSDs: stateless DHCPv6, and they are not going > to improve it Just checking: what do you mean by "not going to improve it"? We (KAME) are actually seriously maintaining the implementation, including bug fixes and supporting new features. In fact, we've recently implemented the brand-new lifetime option, and have just newly supported the authentication mechanism. Perhaps you simply meant we do not have a plan to implement address allocation by DHCPv6. In that sense you're correct, though I'd not say "not going to improve it" meaning luck of a plan for one part of the big specification (even if the part is a major goal of the specification). Of course, I admit our implementation is "incomplete" in that it does not support address allocation. JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] [Question]DHCPv6 implementations strates
- Re: [dhcwg] [Question]DHCPv6 implementations JINMEI Tatuya / 神明達哉
- RE: [dhcwg] [Question]DHCPv6 implementations Bernie Volz
- Re: [dhcwg] [Question]DHCPv6 implementations Martin Stiemerling