public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: R.E.Wolff@BitWizard.nl (Rogier Wolff)
To: jamal <hadi@cyberus.ca>
Cc: James Sutherland <jas88@cam.ac.uk>, linux-kernel@vger.kernel.org
Subject: Re: ECN: Clearing the air (fwd)
Date: Sun, 28 Jan 2001 18:39:32 +0100 (MET)	[thread overview]
Message-ID: <200101281739.SAA05979@cave.bitwizard.nl> (raw)
In-Reply-To: <Pine.GSO.4.30.0101280700580.24762-100000@shell.cyberus.ca> from jamal at "Jan 28, 2001 07:18:54 am"

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
subjective.  If the firewall operator is sufficiently paranoid, they
can say: "We don't trust the ECN implementation on our hosts behind
the firewall, so we want to disable it.". Firewall operators make
"lose connectivity to certain hosts/ports" decisions all the time.
That's what a firewall is about.

So... I think that the hotmail operators (or was it somewhere else
that started this debate?) simply get to chose. Lose connectivity to
part of the world because they block ECN or not.

But let it be known that it is THEIR decision. 


- If you implement a standard badly, you can get to be inoperable if
the standard gets expanded. That's what's happening here. Happens all
the time. 

- Note that Dave politely waited with announcing the impending
"cutoff" until he verified for sure that they did have a CHOICE.  

- The users (/customers) have gotten two weeks to bother the operators
into action, and the operators then have two weeks left to schedule
the upgrade. That seems pretty fair and resonable to me. 


			Roger.

-- 
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* There are old pilots, and there are bold pilots. 
* There are also old, bald pilots. 
-
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 17:39 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 [this message]
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=200101281739.SAA05979@cave.bitwizard.nl \
    --to=r.e.wolff@bitwizard.nl \
    --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