From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: kuznet@ms2.inr.ac.ru, davem@redhat.com, jmorris@redhat.com,
netdev@oss.sgi.com
Subject: Re: IPsec and Path MTU
Date: Wed, 16 Jun 2004 10:43:19 -0400 [thread overview]
Message-ID: <28318.1087396999@marajade.sandelman.ottawa.on.ca> (raw)
In-Reply-To: Message from Herbert Xu <herbert@gondor.apana.org.au> of "Wed, 16 Jun 2004 21:43:45 +1000." <20040616114345.GA1559@gondor.apana.org.au>
-----BEGIN PGP SIGNED MESSAGE-----
>>>>> "Herbert" == Herbert Xu <herbert@gondor.apana.org.au> writes:
>> The pmtu WG is considering changing how PMTU is done. You may
>> want to look at draft-richardson-ipsec-fragment-XX.txt. This has
>> not yet been adopted as a WG draft, because nobody is sure which
>> WG should adopt it:-)
Herbert> I'd say that we should get the stack to work with the hosts
Herbert> that do send ICMP replies first, and then worry about those
Herbert> that don't :)
The proposal there is a compromise between what RFC1191 says, and what
people in the field (and most IPsec implementations, because we get
blamed) have done - it continues to send ICMP replies at all times that
the old logic would usefully do, while not causing huge headaches that
having ICMPs disappear causes.
My opinion is that any solution which does not address the problem of
ICMP blackholes is actually a step back because it causes things to
intermittently fail. Right now, things just fail for big packets,
period. That provides much large clue that there is a problem, which can
be worked around.
So, I'm agreeing with your :) -- we can tune the algorithm later, but
let's make sure that we do it ASAP.
- --
] "Elmo went to the wrong fundraiser" - The Simpson | firewalls [
] Michael Richardson, Xelerance Corporation, Ottawa, ON |net architect[
] mcr@xelerance.com http://www.sandelman.ottawa.on.ca/mcr/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Finger me for keys
iQCVAwUBQNBchIqHRg3pndX9AQFQWwQApGSYmkgs/4nogHYipee21MEannapT54m
sAle7/fBIxUqIKZev8/RlrnVI+n8+e//AQBooeRF1ubmrd0LfajVd1TwwKvdE40S
47ysQrgSm3BHGet1xn+QLxYc3l9WumP7Ey+EkUKi22azcnjEvJ35r5crkMy2kVcg
nALPB7hDwj0=
=+nu7
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-06-16 14:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-15 12:43 IPsec and Path MTU Herbert Xu
2004-06-15 14:50 ` Michael Richardson
2004-06-16 11:43 ` Herbert Xu
2004-06-16 14:43 ` Michael Richardson [this message]
2004-06-18 7:35 ` Glen Turner
2004-06-16 12:10 ` Herbert Xu
2004-06-16 14:12 ` James Morris
2004-06-16 20:23 ` Alexey Kuznetsov
2004-06-16 20:49 ` David S. Miller
2004-06-16 23:11 ` Herbert Xu
2004-06-17 17:58 ` David S. Miller
2004-06-17 21:31 ` Herbert Xu
2004-06-17 22:22 ` David S. Miller
2004-06-17 23:09 ` Herbert Xu
2004-06-16 19:56 ` Alexey Kuznetsov
2004-06-16 23:13 ` Herbert Xu
2004-06-17 19:01 ` Alexey Kuznetsov
2004-06-17 21:38 ` Herbert Xu
2004-06-17 22:29 ` David S. Miller
2004-06-17 23:12 ` Herbert Xu
2004-06-17 23:14 ` David S. Miller
2004-06-17 23:18 ` Herbert Xu
[not found] ` <20040618202551.GA2733@ms2.inr.ac.ru>
2004-06-18 22:21 ` Herbert Xu
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=28318.1087396999@marajade.sandelman.ottawa.on.ca \
--to=mcr@sandelman.ottawa.on.ca \
--cc=davem@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=jmorris@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@oss.sgi.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 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).