From: "David S. Miller" <davem@redhat.com>
To: jmorris@intercode.com.au
Cc: mk@linux-ipv6.org, kuznet@ms2.inr.ac.ru, netdev@oss.sgi.com,
usagi@linux-ipv6.org
Subject: Re: [PATCH] xfrm ip6ip6
Date: Sun, 01 Jun 2003 01:34:52 -0700 (PDT) [thread overview]
Message-ID: <20030601.013452.68050592.davem@redhat.com> (raw)
In-Reply-To: <Mutt.LNX.4.44.0306010158450.7298-100000@excalibur.intercode.com.au>
From: James Morris <jmorris@intercode.com.au>
Date: Sun, 1 Jun 2003 02:01:42 +1000 (EST)
We need to either filter them out or make sure they are
displayed as ipip.
Part of the answer will depend on whether we want to expose xfrm-based
ipip tunnels for general use, or only use them internally for ipcomp.
I think it is an error to extend PF_KEY for our Linux purposes.
Our API here is basically defined to be whatever is in KAME :-)
However, setkey should filter entries it does not understand.
Currently I see no use for exposing these tunnel transforms
outside of the kernel. Mobile IPV6, if it decides to use
xfrm6_tunnel, can configure them itself in the kernel side support.
Or, if user side is more appropriate for MIPV6 access, we may allow
it to use xfrm netlink interface somehow.
next prev parent reply other threads:[~2003-06-01 8:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-31 15:20 [PATCH] xfrm ip6ip6 Mitsuru KANDA / 神田 充
2003-05-31 16:01 ` James Morris
2003-06-01 8:34 ` David S. Miller [this message]
2003-05-31 16:06 ` James Morris
2003-06-01 8:30 ` David S. Miller
2003-06-13 16:03 ` [PATCH] xfrm ip6ip6 (revised) Mitsuru KANDA / 神田 充
2003-06-13 16:11 ` YOSHIFUJI Hideaki / 吉藤英明
2003-06-13 16:13 ` YOSHIFUJI Hideaki / 吉藤英明
2003-06-13 18:08 ` Ville Nuorvala
2003-06-13 19:07 ` David S. Miller
2003-06-13 19:19 ` David S. Miller
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=20030601.013452.68050592.davem@redhat.com \
--to=davem@redhat.com \
--cc=jmorris@intercode.com.au \
--cc=kuznet@ms2.inr.ac.ru \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).