From: "Tom Lendacky" <toml@us.ibm.com>
To: "David S. Miller" <davem@redhat.com>
Cc: cw@f00f.org, kuznet@ms2.inr.ac.ru, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] IPSec protocol application order
Date: Thu, 20 Feb 2003 08:40:22 -0600 [thread overview]
Message-ID: <OFEE5E8DF8.35868017-ON86256CD3.004F81AF-86256CD3.005099DD@pok.ibm.com> (raw)
I believe that good documentation will also be required then. If it is
being decided that the user must enter the ipsec protocols in the proper
order using the setkey spdadd operation, then the user will need to know
what order in which to specify the arguments to setkey. Given that the
spdadd operation:
spdadd src-ip dst-ip any -P out ipsec ah/transport//require
esp/transport//require;
would result in improper ordering of the AH and ESP headers and therefore
interoperability problems, while
spdadd src-ip dst-ip any -P out ipsec esp/transport//require
ah/transport//require;
results in the proper order.
No where have I been able to find any user level documentation that says
what order the ipsec protocols need to be specified on the spdadd
operation. Without good documentation I believe support centers, both a
customer's own and/or a distributor's, may be getting a lot of unnecessary
calls.
Tom
next reply other threads:[~2003-02-20 14:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 14:40 Tom Lendacky [this message]
-- strict thread matches above, loose matches on Subject: below --
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-19 21:48 Tom Lendacky
2003-02-19 21:39 ` David S. Miller
2003-02-19 22:07 ` YOSHIFUJI Hideaki / 吉藤英明
2003-02-19 20:42 Tom Lendacky
2003-02-19 21:29 ` Jeff Garzik
2003-02-19 21:20 ` David S. Miller
2003-02-19 22:05 ` 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=OFEE5E8DF8.35868017-ON86256CD3.004F81AF-86256CD3.005099DD@pok.ibm.com \
--to=toml@us.ibm.com \
--cc=cw@f00f.org \
--cc=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®