Date: Thu, 14 May 1998 00:58:26 -0400 (EDT) From: "Matthew N. Dodd" <winter@jurai.net> To: Peter Wemm <peter@netplex.com.au> Cc: Bill Trost <trost@cloud.rain.com>, Julian Elischer <julian@whistle.com>, net@FreeBSD.ORG, core@FreeBSD.ORG Subject: Re: INRIA IPv6 on FreeBSD Message-ID: <Pine.BSF.3.96.980514005425.17033d-100000@sasami.jurai.net> In-Reply-To: <199805140447.MAA11059@spinner.netplex.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 14 May 1998, Peter Wemm wrote: > I guess the real question is... where do we want to end up? Do we want > to end up with a seamlessly integrated IPv6, or something that's kept at > arm's length? Also, there are other IPv6 implementations out there, > perhaps the most important is the Linux 2.1.x version. Where do they put > there include files? Putting our includes in a gratuitously different > location is only going to cause us pain. I think 'seamless integration' would be the correct goal. I envision a system where one may type 'ping foo.bar.com' and have it just work. > Due to the nature of the US regulations, this is almost irrelevant since > FreeBSD is distributed from US soil. If IPSEC and/or IPv6 crypto is > going to be implemented in FreeBSD, then it *must* be done as a > stand-alone package otherwise FreeBSD will cause major export nightmares > for people outside of the San Francisco area. US based mirrors would > not be able to carry open mirrors of FreeBSD. This problem is almost a > strike against WIDE unless their ipsec/crypto stuff is very easily and > completely paritioned. It would appear that their crypto code resides in sys/crypto and is enabled via config file options. I don't see this being any less seamless than the current soft-update hoops we have to jump through. /* Matthew N. Dodd | A memory retaining a love you had for life winter@jurai.net | As cruel as it seems nothing ever seems to http://www.jurai.net/~winter | go right - FLA M 3.1:53 */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980514005425.17033d-100000>