From: "David S. Miller" <davem@redhat.com>
To: Pekka Savola <pekkas@netcore.fi>
Cc: netdev@oss.sgi.com
Subject: Re: IPSEC and MPLS priority for 2.6?
Date: Wed, 17 Dec 2003 23:49:52 -0800 [thread overview]
Message-ID: <20031217234952.31efc004.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0312180930560.12194-100000@netcore.fi>
On Thu, 18 Dec 2003 09:36:15 +0200 (EET)
Pekka Savola <pekkas@netcore.fi> wrote:
> Andrew characterized (or Dave) did the lack of MPLS support as a huge
> issue for serious IPSEC usage in:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/must-fix/should-fix-7.txt
> [see below]
>
> .. I don't agree.
You're probably right, it's priority can be decreased.
If the MPLS stuff is ready later in the 2.6.x series though, it
will be very easy to merge safely.
next prev parent reply other threads:[~2003-12-18 7:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-18 7:36 IPSEC and MPLS priority for 2.6? Pekka Savola
2003-12-18 7:49 ` David S. Miller [this message]
2003-12-18 7:55 ` YOSHIFUJI Hideaki / 吉藤英明
2003-12-18 14:17 ` James R. Leu
2003-12-18 15:36 ` Pekka Savola
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=20031217234952.31efc004.davem@redhat.com \
--to=davem@redhat.com \
--cc=netdev@oss.sgi.com \
--cc=pekkas@netcore.fi \
/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).