From: "Mitsuru KANDA / 神田 充" <mk@linux-ipv6.org>
To: jmorris@intercode.com.au, davem@redhat.com, kuznet@ms2.inr.ac.ru
Cc: netdev@oss.sgi.com, usagi@linux-ipv6.org
Subject: Re: [PATCH] IPv6 IPComp
Date: Sat, 17 May 2003 02:59:30 +0900 [thread overview]
Message-ID: <873cjebwn1.wl@karaba.org> (raw)
In-Reply-To: <Mutt.LNX.4.44.0305162329230.17250-100000@excalibur.intercode.com.au>
At Fri, 16 May 2003 23:40:18 +1000 (EST),
James Morris <jmorris@intercode.com.au> wrote:
...
> > Attached diff is for linux-2.5.69 + CS1.1137 .
> >
> > Could you check it?
> >
>
> Looks good!
Thank you!
> A few issues:
>
> The crypto/Kconfig file needs to be updated so that the deflate module is
> enabled when ipcomp6 is.
OK, I will send a small patch after this ipcomp6 patch is committed.
> In a subsequent patch, it would be good to define single NIP6() in a
> header file, as local versions are spreading.
Yes, this is a next issue for me.
I have a plan to do various small cleanups w/r AH6/ESP6/IPComp6...
> With current bk, you need to attach internal ipip xfrms to allow reception
> of uncompressed ipcomp packets in tunnel mode. See the current ipv4
> ipcomp code as an example. Any generic code for this should probably live
> in net/xfrm/xfrm_tunnel.c
I think so,
but it may take a time because currently ip6ip6 does not exist.
Regards,
-mk
next prev parent reply other threads:[~2003-05-16 17:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-16 12:14 [PATCH] IPv6 IPComp Mitsuru KANDA / 神田 充
2003-05-16 13:40 ` James Morris
2003-05-16 17:59 ` Mitsuru KANDA / 神田 充 [this message]
2003-05-16 21:00 ` David S. Miller
2003-05-17 3:40 ` Mitsuru KANDA / 神田 充
2003-05-19 8:24 ` Mitsuru KANDA / 神田 充
2003-05-20 6:35 ` David S. Miller
2003-05-20 7:44 ` Mitsuru KANDA / 神田 充
2003-05-17 16:15 ` Mitsuru KANDA / 神田 充
2003-05-17 22:30 ` David S. Miller
2003-05-16 21:35 ` Pekka Savola
2003-05-16 22:27 ` YOSHIFUJI Hideaki / 吉藤英明
2003-05-16 23:52 ` David S. Miller
2003-05-17 0:08 ` James Morris
2003-05-17 0:20 ` 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=873cjebwn1.wl@karaba.org \
--to=mk@linux-ipv6.org \
--cc=davem@redhat.com \
--cc=jmorris@intercode.com.au \
--cc=kuznet@ms2.inr.ac.ru \
--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).