From: Christoph Paasch <christoph.paasch@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: johnwheffner@gmail.com, eric.dumazet@gmail.com,
Yurij.Plotnikov@oktetlabs.ru, netdev@vger.kernel.org,
Alexandra.Kossovsky@oktetlabs.ru
Subject: Re: TCP socket receives strange packet
Date: Tue, 14 Oct 2014 09:54:30 -0700 [thread overview]
Message-ID: <20141014165430.GI28432@Paaschs-MacBook-Pro.local> (raw)
In-Reply-To: <20141014.125004.1504941413142780868.davem@davemloft.net>
On 14/10/14 - 12:50:04, David Miller wrote:
> From: Christoph Paasch <christoph.paasch@gmail.com>
> Date: Tue, 14 Oct 2014 09:41:44 -0700
>
> > there was a long discussion whether for the updated version of RFC1323 (now
> > published as RFC 7323) a segment must be dropped if it does not contain a
> > timestamp. The rationale (defended by Joe Touch) was that it must be there to
> > protect against wrapped sequence numbers while others argued that mandating
> > a drop might result in stalling connections if (for one reason or another) a
> > host sends a segment without TS (or a middlebox removed it).
> >
> > The RFC now says that a host SHOULD drop segments without timestamps.
>
> There are too many middle-boxes that drop timestamps for that to be a tenable
> way to behave, especially by default.
>
> If you want to be disconnected from various parts of the internet, feel free
> to follow that RFC's recommendations.
I'm completely with you. We actually argued against Joe Touch, who wanted to
have a "MUST" for dropping these segments without TS.
Cheers,
Christoph
next prev parent reply other threads:[~2014-10-14 16:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 14:09 TCP socket receives strange packet Yurij M. Plotnikov
2014-10-14 15:00 ` Eric Dumazet
2014-10-14 15:40 ` John Heffner
2014-10-14 16:41 ` Christoph Paasch
2014-10-14 16:50 ` David Miller
2014-10-14 16:54 ` Christoph Paasch [this message]
2014-10-14 16:32 ` David Miller
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=20141014165430.GI28432@Paaschs-MacBook-Pro.local \
--to=christoph.paasch@gmail.com \
--cc=Alexandra.Kossovsky@oktetlabs.ru \
--cc=Yurij.Plotnikov@oktetlabs.ru \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=johnwheffner@gmail.com \
--cc=netdev@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