From: "David S. Miller" <davem@redhat.com>
To: ecki@lina.inka.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] document ECN in 2.4 Configure.help
Date: Mon, 6 Nov 2000 19:34:01 -0800 [thread overview]
Message-ID: <200011070334.TAA01403@pizda.ninka.net> (raw)
In-Reply-To: <E13syeh-00018h-00@calista.inka.de> (message from Bernd Eckenfels on Tue, 07 Nov 2000 03:38:35 +0100)
In-Reply-To: <E13syeh-00018h-00@calista.inka.de>
From: Bernd Eckenfels <ecki@lina.inka.de>
Date: Tue, 07 Nov 2000 03:38:35 +0100
Because this will add a Fallback (non ECN) packet to every denied
target. I think this is bad policy at least. It might violate the
RFCs, too. Keep in mind, we cannot recognice a rejection due to
ECN.
It does in fact violate RFCs because the fallback has to handle the
case where ECN rejection comes in the form of a (perfectly valid)
TCP reset.
Any workaround which ignores TCP resets is broken from the start and
is not to be implemented.
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:[~2000-11-07 3:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-07 2:38 Bernd Eckenfels
2000-11-07 3:34 ` David S. Miller [this message]
2000-11-10 22:00 ` Werner Almesberger
-- strict thread matches above, loose matches on Subject: below --
2000-11-06 6:15 Barry K. Nathan
2000-11-06 7:03 ` David S. Miller
2000-11-06 12:16 ` Dominik Kubla
2000-11-06 7:34 ` Oliver Xymoron
2000-11-06 7:30 ` David S. Miller
2000-11-06 8:02 ` Oliver Xymoron
2000-11-06 10:46 ` Andrew Morton
2000-11-06 11:02 ` Alan Cox
2000-11-06 11:11 ` Andi Kleen
2000-11-06 13:02 ` jamal
2000-11-06 13:31 ` James A. Sutherland
2000-11-10 14:58 ` Pavel Machek
2000-11-06 13:08 ` 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=200011070334.TAA01403@pizda.ninka.net \
--to=davem@redhat.com \
--cc=ecki@lina.inka.de \
--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®