From: jamal <hadi@cyberus.ca>
To: James Sutherland <jas88@cam.ac.uk>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: ECN: Clearing the air (fwd)
Date: Sun, 28 Jan 2001 13:07:01 -0500 (EST) [thread overview]
Message-ID: <Pine.GSO.4.30.0101281225520.24762-100000@shell.cyberus.ca> (raw)
In-Reply-To: <Pine.SOL.4.21.0101281704430.16734-100000@green.csi.cam.ac.uk>
On Sun, 28 Jan 2001, James Sutherland wrote:
> On Sun, 28 Jan 2001, jamal wrote:
> > We are allowing two rules to be broken, one is RFC 793 which
> > clearly and unambigously defines what a RST means. the second is
>
> This is NOT being violated: the RST is honoured as normal.
You are interpreting RST to mean "it says RST but maybe it was not RST;
let me try again"
I dont think thats honoring it ;->
[Just like the anti-harassment campaign goes: What part of NO dont
you understand, is it the N or the O?]
>
> > the firewall or IDS box which clearly is in violation.
>
> Disagreed: it is complying with firewall RFCs, rejecting suspect
> packets. Sending an RST isn't a very bright way to do it, but that's
> irrelevant: it happens. Deal with it.
It is what some idiot designer thought it meant.
If the administrator configured it, that is complying with RFCs.
> > I see that we mostly have philosphical differences. You'd rather adapt
> > to the criminal and most people would rather have the criminal adjust to
> > society.
>
> There is no "criminal": no rules are being broken. Since it is
> "society" (or a tiny minority thereof) which has changed the rules, it is
> "society" which must adapt to be compatible with existing rules.
>
;-> We are on different extremes for sure. It is "society" which clearly
says now that if you misunderstood the rule and didnt pay attention to
the definition of "reserved", here's the definition. You understand it
better? good, please conform.
You are saying that "society" should now say ok, since you misunderstood
we'll make our lives a lot more miserable and just live with your
ignorance.
>
> I'd have said that's still true - only "hackers" are qualified. The
> problem is just that the staff doing (or attempting) the job aren't
> necessarily qualified to do it properly...
The internet is growing so fast and the shortage of people is affecting
it. Look at what happened to MS ;-> ;->
>
> > If you think the CISCOs were bad sending RSTs, i am sure you havent heard
> > about the Raptor firewalls. They dont even bother to send you anything if
> > you have ECN enabled ;-> Simply swallow your SYNs.
>
> That's regarded as a better response, actually: just drop suspect packets.
>
But then how do you "degrade" nicely from it? If you want Linux to be
able to degrade nicely, what do you do in this case?
> > So tell me, what do you propose we deal with these? Do we further
> > disambiguate or assume the packet was lost?
> > I actually bothered calling Raptor, they chose to ignore me.
>
> You mean they are still shipping a firewall which drops ECN
> packets? Hrm...
>
Yeah, as far as i know
> No, just use English properly. "Must be zero" doesn't actually mean "must
> be set to zero when sending, and ignored when receiving/processing", which
> is probably what the standard SHOULD have said.
>
> However, it's too late now: ECN-disabled routes exist. ECN implementations
> should degrade as well as possible when handling these circumstances.
I think this is the right moment for this to be fixed. Way before it is
too late.
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/
next prev parent reply other threads:[~2001-01-28 18:08 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 [this message]
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 ` 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.0101281225520.24762-100000@shell.cyberus.ca \
--to=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
all inboxes | Powered by JetHome®