From: "David S. Miller" <davem@redhat.com>
To: James Sutherland <jas88@cam.ac.uk>
Cc: Miquel van Smoorenburg <miquels@traveler.cistron-office.nl>,
linux-kernel@vger.kernel.org
Subject: Re: ECN: Clearing the air (fwd)
Date: Sun, 28 Jan 2001 23:32:41 -0800 (PST) [thread overview]
Message-ID: <14965.7321.926528.391631@pizda.ninka.net> (raw)
In-Reply-To: <Pine.SOL.4.21.0101281642180.16734-100000@green.csi.cam.ac.uk>
In-Reply-To: <951am4$gbf$1@ncc1701.cistron.net> <Pine.SOL.4.21.0101281642180.16734-100000@green.csi.cam.ac.uk>
James Sutherland writes:
> Except you can detect and deal with these "PMTU black holes". Just as you
> should detect and deal with ECN black holes. Maybe an ideal Internet
> wouldn't have them, but this one does. If you can find an ideal Internet,
> go code for it: until then, stick with the real one. It's all we've got.
Guess what, Linux works not around PMTU black holes either for the
same exact reason we will not work around ECN.
I'm getting a bit tired of you, and I suppose others are as
well. You are being nothing but a pompous ass.
Anyways, let me quote a comment from the Linux source code where
we would have done PMTU black hole detection:
/* NOTE. draft-ietf-tcpimpl-pmtud-01.txt requires pmtu black
hole detection. :-(
It is place to make it. It is not made. I do not want
to make it. It is disguisting. It does not work in any
case. Let me to cite the same draft, which requires for
us to implement this:
"The one security concern raised by this memo is that ICMP black holes
are often caused by over-zealous security administrators who block
all ICMP messages. It is vitally important that those who design and
deploy security systems understand the impact of strict filtering on
upper-layer protocols. The safest web site in the world is worthless
if most TCP implementations cannot transfer data from it. It would
be far nicer to have all of the black holes fixed rather than fixing
all of the TCP implementations."
Golden words :-).
*/
Later,
David S. Miller
davem@redhat.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-29 7:38 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-28 0:14 jamal
2001-01-28 8:56 ` James Sutherland
2001-01-28 12:18 ` jamal
2001-01-28 13:29 ` James Sutherland
2001-01-28 14:34 ` Miquel van Smoorenburg
2001-01-28 16:44 ` James Sutherland
2001-01-29 7:32 ` David S. Miller [this message]
2001-01-29 12:30 ` Andi Kleen
2001-01-29 18:31 ` Albert D. Cahalan
2001-01-29 19:02 ` James H. Cloos Jr.
2001-01-29 19:27 ` George
2001-01-29 19:59 ` Alex Pennace
2001-01-28 14:54 ` Andi Kleen
2001-01-28 16:15 ` jamal
2001-01-28 17:11 ` James Sutherland
2001-01-28 18:07 ` jamal
2001-01-28 20:13 ` Gregory Maxwell
2001-01-29 2:58 ` David Lang
2001-01-29 7:20 ` David S. Miller
2001-01-28 19:42 ` Gregory Maxwell
2001-01-29 0:14 ` Jamie Lokier
2001-01-31 18:02 ` Alan Cox
2001-02-03 16:51 ` Michael H. Warfield
2001-01-29 12:57 ` Peter Samuelson
2001-01-28 17:39 ` Rogier Wolff
2001-01-28 18:01 ` Graham Murray
2001-01-28 18:08 ` jamal
2001-01-28 18:23 ` Rogier Wolff
2001-01-28 18:38 ` jamal
2001-01-28 20:18 ` Gregory Maxwell
2001-01-28 21:33 ` ECN fixes for Cisco gear Dax Kelson
2001-01-28 22:09 ` ECN connectivity surveys Dax Kelson
2001-01-28 21:45 ` ECN fixes for Cisco gear Lincoln Dale
2001-01-28 14:04 ` ECN: Clearing the air (fwd) Ben Ford
2001-01-28 14:09 ` James Sutherland
2001-01-28 15:38 ` Ben Ford
2001-01-28 19:55 ` Gregory Maxwell
2001-01-28 19:45 ` Gregory Maxwell
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=14965.7321.926528.391631@pizda.ninka.net \
--to=davem@redhat.com \
--cc=jas88@cam.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=miquels@traveler.cistron-office.nl \
/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®