mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: jamal <hadi@cyberus.ca>
To: Rogier Wolff <R.E.Wolff@BitWizard.nl>
Cc: James Sutherland <jas88@cam.ac.uk>, <linux-kernel@vger.kernel.org>
Subject: Re: ECN: Clearing the air (fwd)
Date: Sun, 28 Jan 2001 13:08:40 -0500 (EST)	[thread overview]
Message-ID: <Pine.GSO.4.30.0101281307090.24762-100000@shell.cyberus.ca> (raw)
In-Reply-To: <200101281739.SAA05979@cave.bitwizard.nl>



On Sun, 28 Jan 2001, Rogier Wolff wrote:

> jamal wrote:
> > > 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.
> > >
> >
> > This is the way it's done with all protocols. or i should say the way it
> > used to be done. How do you expect ECN to be deployed otherwise?
>
> Thinking about this a bit more:
>
> A sufficiently paranoid firewall should block requests that he doesn't
> fully understand. ECN was in this category, so old firewalls are
> "right" to block these. (Sending an 'RST' is not elegant. So be it.)
>
> However, ECN is now "understood", and operators are now in a position
> to configure their firewall to "do the right thing". This is


This would have been easier. The firewall operators were not provided with
this option. This is hard-coded. I agree with the rest of your message.

cheers,
jamal



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

  parent reply	other threads:[~2001-01-28 18:10 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
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 [this message]
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=Pine.GSO.4.30.0101281307090.24762-100000@shell.cyberus.ca \
    --to=hadi@cyberus.ca \
    --cc=R.E.Wolff@BitWizard.nl \
    --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

all inboxes | Powered by JetHome®