From: Jeff Garzik <jgarzik@pobox.com>
To: Tom Lendacky <toml@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, davem@redhat.com, kuznet@ms2.inr.ac.ru
Subject: Re: [PATCH] IPSec protocol application order
Date: Wed, 19 Feb 2003 16:29:50 -0500 [thread overview]
Message-ID: <20030219212950.GC4977@gtf.org> (raw)
In-Reply-To: <1045687340.3419.14.camel@tomlt2.austin.ibm.com>
On Wed, Feb 19, 2003 at 02:42:19PM -0600, Tom Lendacky wrote:
> The IPSec RFC (2401) and IPComp RFC (3173) specify the order in which
> the COMP, ESP and AH protocols must be applied when being applied in
> transport mode. Specifically, COMP must be applied first, then ESP
> and then AH. Also, transport mode protocols must be applied before
> tunnel mode protocols.
>
> Here is a patch that creates the xfrm_tmpl structures in the order
> required by the RFCs. The patch requires that the application order
> of new transformations/protocols be specified for transport mode
> in order to have an xfrm_tmpl structure created. If this is not
> desired, an additional transport mode loop can be placed ahead of the
> COMP/ESP/AH transport mode loops that creates xfrm_tmpl structures
> for protocols other than COMP/ESP/AH.
hmmm... do you really need to duplicate all that code, just to define
the order?
next prev parent reply other threads:[~2003-02-19 21:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 20:42 [PATCH] IPSec protocol application order Tom Lendacky
2003-02-19 21:29 ` Jeff Garzik [this message]
2003-02-19 21:20 ` David S. Miller
2003-02-19 22:05 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2003-02-19 21:48 Tom Lendacky
2003-02-19 21:39 ` David S. Miller
2003-02-19 22:07 ` YOSHIFUJI Hideaki / 吉藤英明
2003-02-19 23:03 Tom Lendacky
2003-02-20 1:32 ` David S. Miller
2003-02-20 0:57 ` Chris Wedgwood
2003-02-20 6:51 ` David S. Miller
2003-02-20 14:40 Tom Lendacky
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=20030219212950.GC4977@gtf.org \
--to=jgarzik@pobox.com \
--cc=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=toml@us.ibm.com \
/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.