From: Ben Ford <ben@kalifornia.com>
To: James Sutherland <jas88@cam.ac.uk>
Cc: jamal <hadi@cyberus.ca>, linux-kernel@vger.kernel.org
Subject: Re: ECN: Clearing the air (fwd)
Date: Sun, 28 Jan 2001 06:04:17 -0800 [thread overview]
Message-ID: <3A7426E1.728BB87D@kalifornia.com> (raw)
In-Reply-To: <Pine.SOL.4.21.0101280852470.14226-100000@green.csi.cam.ac.uk>
James Sutherland wrote:
> I'm sure we all know what the IETF is, and where ECN came from. I haven't
> seen anyone suggesting ignoring RST, either: DM just imagined that,
> AFAICS.
>
> The one point I would like to make, though, is that firewalls are NOT
> "brain-damaged" for blocking ECN: according to the RFCs governing
> firewalls, and the logic behind their design, blocking packets in an
> unknown format (i.e. with reserved bits set) is perfectly legitimate. Yes,
> those firewalls should be updated to allow ECN-enabled packets
> through. However, to break connectivity to such sites deliberately just
> because they are not supporting an *experimental* extension to the current
> protocols is rather silly.
Do keep in mind, we aren't breaking connectivity, they are.
-b
-
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-28 14:02 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-28 0:14 ECN: Clearing the air (fwd) 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
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 ` Ben Ford [this message]
2001-01-28 14:09 ` ECN: Clearing the air (fwd) 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=3A7426E1.728BB87D@kalifornia.com \
--to=ben@kalifornia.com \
--cc=hadi@cyberus.ca \
--cc=jas88@cam.ac.uk \
--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