From owner-freebsd-security Tue Oct 14 08:59:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA26207 for security-outgoing; Tue, 14 Oct 1997 08:59:49 -0700 (PDT) (envelope-from owner-freebsd-security) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA26200 for ; Tue, 14 Oct 1997 08:59:46 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.5/8.8.5) id LAA13260; Tue, 14 Oct 1997 11:59:37 -0400 (EDT) Date: Tue, 14 Oct 1997 11:59:37 -0400 (EDT) From: Garrett Wollman Message-Id: <199710141559.LAA13260@khavrinen.lcs.mit.edu> To: Petri Helenius Cc: freebsd-security@FreeBSD.ORG Subject: Re: IPv6 sources w/out export restriction In-Reply-To: <199710141554.SAA22187@silver.sms.fi> References: <19970924075951.46946@keltia.freenix.fr> <199710141354.QAA21928@silver.sms.fi> <199710141532.LAA13155@khavrinen.lcs.mit.edu> <199710141554.SAA22187@silver.sms.fi> Sender: owner-freebsd-security@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk < said: > What other working implementations there are in addition to the INRIA > one (for FreeBSD)? There's the DARTNET one based on the NRL code (which is radically restructured every week or so I'm told, making it difficult to keep a stable code base). There's the one from WIDE in Japan. I've talked with people who know of others, but I can't be more specific. IPv6 right now is a research vehicle. It will not be production technology for some years. It would be very, very premature to incorporate any one implementation into our source tree at this time. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick