lkml.org 
[lkml]   [2000]   [Nov]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] document ECN in 2.4 Configure.help
On Sun, 5 Nov 2000, David S. Miller wrote:

> Date: Mon, 6 Nov 2000 01:34:14 -0600 (CST)
> From: Oliver Xymoron <oxymoron@waste.org>
>
> I'm still not sure why it's been decided not to do fallback or how
> this whole situation is any different from path MTU discovery.
>
> We don't use fallbacks for path MTU discovery (I assume you are
> referring to black hole detection, we don't do it, never have never
> will), you have to explicitly turn path-mtu discovery off. It's been
> on by default for 3 or 4 years now :-)

Hmmm, for some reason I thought we had it, but it's been a non-issue for a
long time. The ECN thing hasn't bitten me yet either, happily.

So the question then becomes what is the process whereby we decide that
Linux will follow standards that are known to silently break things in a
large part of the real world. We explicitly don't do this with a user's
hardware, and I think we have other work-arounds for network
interoperability. How big and how badly does something have to break
before it becomes something we work around?

--
"Love the dolphins," she advised him. "Write by W.A.S.T.E.."

-
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/

\
 
 \ /
  Last update: 2005-03-22 12:45    [W:0.069 / U:0.204 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site