From: Andi Kleen <ak@suse.de>
To: Praveen Kumar Amritaluru <praveen@india.hp.com>
Cc: netdev@oss.sgi.com
Subject: Re: zero window probes on linux (fwd)
Date: Wed, 14 Apr 2004 14:10:10 +0200 [thread overview]
Message-ID: <20040414141010.267a6204.ak@suse.de> (raw)
In-Reply-To: <200404141205.RAA06111@shilpa.india.hp.com>
On Wed, 14 Apr 2004 17:35:33 +0530 (IST)
Praveen Kumar Amritaluru <praveen@india.hp.com> wrote:
> > > > > This seems to be a bug. Has it been already fixed in later
> > > > > kernel versions or is this how it is intended to remain?
> > > >
> > > > iirc this was intentional. The RFC suggested method doesn't work when talking to
> > > > some stacks.
> > > >
> > >
> > > But that cannot be valid enough justification for doing
> > > something against RFC right?
> >
> > Of course it is. Welcome to the real world. RFC1122 has a lot of bugs and sometimes
> > does not describe really implemented practice (e.g. BSD set the defacto standard
> > in many behaviours and it does not always follow 1122)
>
> So do u consider mandating definition of zero-window probes as defined
> in RFC793 as a bug in RFC1122?
They are not directly a bug, but are just not what the world standardized on.
> Or else r u saying this bug is introduced in linux to take care of
> faulty stacks existing in the world. zero-window probes as defined
> in RFC1122 is not buggy right?
Implementing a production network stack is not about following some standard to the
letter, but about interoperating with real implementations in a useful matter.
Linux does that.
-Andi
next prev parent reply other threads:[~2004-04-14 12:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-13 10:13 zero window probes on linux (fwd) Praveen Kumar Amritaluru
2004-04-13 18:50 ` Andi Kleen
2004-04-14 8:57 ` Praveen Kumar Amritaluru
2004-04-14 11:41 ` Andi Kleen
2004-04-14 12:05 ` Praveen Kumar Amritaluru
2004-04-14 12:10 ` Andi Kleen [this message]
2004-04-14 12:26 ` Praveen Kumar Amritaluru
2004-04-15 13:20 ` Praveen Kumar Amritaluru
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=20040414141010.267a6204.ak@suse.de \
--to=ak@suse.de \
--cc=netdev@oss.sgi.com \
--cc=praveen@india.hp.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.