All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sandy Harris <sandy@storm.ca>
To: Mitsuru KANDA <mk@linux-ipv6.org>
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com,
	cryptoapi-devel@kerneli.org, design@lists.freeswan.org,
	usagi@linux-ipv6.org
Subject: Re: [Design] [PATCH] USAGI IPsec
Date: Mon, 21 Oct 2002 07:46:16 -0700	[thread overview]
Message-ID: <3DB41338.3070502@storm.ca> (raw)
In-Reply-To: m3k7kpjt7c.wl@karaba.org

Mitsuru KANDA wrote:

>Hello Linux kernel network maintainers,
>
>I'm a member of USAGI project.
>
>In IPv6 specifications, IPsec is mandatory.
>
>We implemented IPsec for Linux IP stack.
>
>At present, our implementation includes:
>	PF_KEY V2 interface,
>	Security Association Database and
>	Security Policy Database for whole IP versions,
>	IPsec for IPv6,(transport, tunnel mode),
>	IPsec for IPv4 (transport mode),
>
>Would you mind checking it ?
>
Is this code being checked in to the mainline kernel? Or becoming part 
of the
CryptoAPI patch set? Bravo, in either case.

How does that affect FreeS/WAN development?

>  
>


  parent reply	other threads:[~2002-10-20 23:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-11  8:05 [PATCH] USAGI IPsec Mitsuru KANDA
2002-10-12 17:11 ` [Design] " Sandy Harris
2002-10-12  2:27   ` David S. Miller
2002-10-19  1:40     ` Zach Brown
2002-10-21 14:46 ` Sandy Harris [this message]
2002-10-21  2:41   ` David S. Miller
2002-10-21  3:42     ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-21  7:34     ` [CryptoAPI-devel] " Herbert Valerio Riedel
2002-10-22  2:27       ` Sandy Harris
2002-10-22  5:02       ` Jari Ruusu
2002-10-24 14:50         ` Jean-Luc Cooke
2002-10-28 13:55           ` JuanJo Ciarlante
2002-10-21  4:22   ` Andre Hedrick

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3DB41338.3070502@storm.ca \
    --to=sandy@storm.ca \
    --cc=cryptoapi-devel@kerneli.org \
    --cc=design@lists.freeswan.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mk@linux-ipv6.org \
    --cc=netdev@oss.sgi.com \
    --cc=usagi@linux-ipv6.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.