netdev
[Top] [All Lists]

Re: zero window probes on linux (fwd)

To: ak@xxxxxxx
Subject: Re: zero window probes on linux (fwd)
From: Praveen Kumar Amritaluru <praveen@xxxxxxxxxxxx>
Date: Wed, 14 Apr 2004 17:56:14 +0530 (IST)
Cc: netdev@xxxxxxxxxxx
In-reply-to: <20040414141010.267a6204.ak@xxxxxxx> from Andi Kleen at Apr "14," 2004 "02:10:10" pm
Sender: netdev-bounce@xxxxxxxxxxx
> > > > > >     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. 


        Are u aware of other production network stacks sending unacceptable
        segment as a zero-window probe? Can you list them. This is just for
        my information.

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

<Prev in Thread] Current Thread [Next in Thread>