From owner-freebsd-hackers Sun Dec 27 18:40:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA10399 for freebsd-hackers-outgoing; Sun, 27 Dec 1998 18:40:24 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from brooklyn.slack.net (brooklyn.slack.net [206.41.21.102]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA10394 for ; Sun, 27 Dec 1998 18:40:23 -0800 (PST) (envelope-from andrewr@brooklyn.slack.net) Received: from localhost (andrewr@localhost) by brooklyn.slack.net (8.8.7/8.8.7) with SMTP id VAA18679; Sun, 27 Dec 1998 21:42:47 -0500 (EST) Date: Sun, 27 Dec 1998 21:42:47 -0500 (EST) From: andrewr To: Yoshinobu Inoue cc: hackers@FreeBSD.ORG Subject: Re: IPv6 - when? which? In-Reply-To: <19981227132444B.shin@nd.net.fujitsu.co.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 27 Dec 1998, Yoshinobu Inoue wrote: > > KAME for 3.0 is almost ready. (IPsec and IPv6 is working. Some > user-land work is left.) > And I can make KAME for current as the next step, if it is necessary. As for the user-land stuff, what is still needed? and is that work only to be done by the KAME project team?? > > Because unified-ipv6 issue happened when I began TCP v4/v6 merging, I > tried to make TCP part alike INRIA code, as much as possible. > However this is not from formal unified-ipv6 source tree. It is being > prepared separately. > > If IPsec and IPv6 is needed for FreeBSD current so urgently, KAME will > soon be available. (But some major change will happen in the future, > as it is unified with other IPv6 protocol stacks) > Or if people think more unified version should be incorporated at > first, it will also be ready in few months. > > > Yoshinobu Inoue > shin@kame.net > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message