From owner-freebsd-security Tue Oct 14 10:08:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA01661 for security-outgoing; Tue, 14 Oct 1997 10:08:33 -0700 (PDT) (envelope-from owner-freebsd-security) Received: from coconut.itojun.org (root@coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA01653 for ; Tue, 14 Oct 1997 10:08:28 -0700 (PDT) (envelope-from itojun@itojun.org) From: itojun@itojun.org Received: from localhost (itojun@localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.8.5/3.6Wbeta6) with ESMTP id CAA22477; Wed, 15 Oct 1997 02:07:51 +0900 (JST) To: Garrett Wollman cc: freebsd-security@FreeBSD.ORG In-reply-to: wollman's message of Tue, 14 Oct 1997 11:59:37 -0400. <199710141559.LAA13260@khavrinen.lcs.mit.edu> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: IPv6 sources w/out export restriction Date: Wed, 15 Oct 1997 02:07:50 +0900 Message-ID: <22473.876848870@coconut.itojun.org> Sender: owner-freebsd-security@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> 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. For more information about WIDE's implementation, see http://www.v6.wide.ad.jp/. (or ask me :-P) Ours include IPsec, and (at this moment) there's no legal restriction on crypto-export in Japan. We are trying hard to make a public release soon. itojun