From owner-freebsd-current Wed Jan 5 12:40:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from abc.123.org (123.org [195.244.241.123]) by hub.freebsd.org (Postfix) with ESMTP id F27831551D; Wed, 5 Jan 2000 12:39:56 -0800 (PST) (envelope-from k@abc.123.org) Received: (from k@localhost) by abc.123.org (8.9.3/8.9.3) id VAA02110; Wed, 5 Jan 2000 21:39:31 +0100 (CET) (envelope-from k) Date: Wed, 5 Jan 2000 21:39:30 +0100 From: Kai Voigt To: "Louis A. Mamakos" Cc: committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: 4.0 code freeze scheduled for Jan 15th Message-ID: <20000105213930.C751@abc.123.org> References: <28153.947101446@zippy.cdrom.com> <200001052026.PAA61728@whizzo.transsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <200001052026.PAA61728@whizzo.transsys.com> Organization: 123.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Louis A. Mamakos wrote: > > Will we try to include the remaining KAME IPv6 integration into 4.0 before > the freeze? It would be nice to have 4.0 with a functioning IPv6 stack and > some applications. IPv6 is a very complex area and I believe that a -RELEASE should come with both a clean IPv6 stack and working userland tools. When looking at Linux and Solaris, they also lack a usable IPv6 support when it comes to userland tools. A lot of things need to be modified: ifconfig, route, ipfw, tcpd, ... and all the client/server tools you can find in /etc/inetd.conf I doubt that IPv6 will make it into 4.0-RELEASE, but I'm sure it will be a major item for this year. Kai -- kai voigt hamburger chaussee 36 24113 kiel 04 31 - 22 19 98 69 http://k.123.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message