From owner-freebsd-security Tue Oct 14 08:54:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA25779 for security-outgoing; Tue, 14 Oct 1997 08:54:49 -0700 (PDT) (envelope-from owner-freebsd-security) Received: from silver.sms.fi (silver.sms.fi [194.111.122.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA25774 for ; Tue, 14 Oct 1997 08:54:43 -0700 (PDT) (envelope-from pete@silver.sms.fi) Received: (from pete@localhost) by silver.sms.fi (8.8.7/8.7.3) id SAA22187; Tue, 14 Oct 1997 18:54:03 +0300 (EEST) Date: Tue, 14 Oct 1997 18:54:03 +0300 (EEST) Message-Id: <199710141554.SAA22187@silver.sms.fi> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: Petri Helenius To: Garrett Wollman Cc: freebsd-security@FreeBSD.ORG Subject: Re: IPv6 sources w/out export restriction In-Reply-To: <199710141532.LAA13155@khavrinen.lcs.mit.edu> References: <19970924075951.46946@keltia.freenix.fr> <199710141354.QAA21928@silver.sms.fi> <199710141532.LAA13155@khavrinen.lcs.mit.edu> X-Mailer: VM 6.22 under 19.15p7 XEmacs Lucid Sender: owner-freebsd-security@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Garrett Wollman writes: > < said: > > > This is why the code should be checked into CURRENT as my impression > > is that although it undergoes ongoing development, it's still very > > non-distruptive to non-ipv6 stuff so it would not hurt to be there. > > There are just too d*mn many IP{v6 implementations at this point to > choose any one of them to officially support. (They all have enough > things wrong with them...) > What other working implementations there are in addition to the INRIA one (for FreeBSD)? How does one get one of these? What's wrong with the INRIA one? Pete