netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: Bartek Wydrowski <b_wydrowski@yahoo.com.au>
Cc: netdev@oss.sgi.com, kuznet@ms2.inr.ac.ru
Subject: Re: RFC1323. No timestamping if SYN timestamp = 0. Bug or Feature?
Date: Thu, 23 Oct 2003 01:37:48 -0700	[thread overview]
Message-ID: <20031023013748.0dd168db.davem@redhat.com> (raw)
In-Reply-To: <20031022200152.17005.qmail@web13006.mail.yahoo.com>


It is impossible to comply to RFC1323 if we allow TSval in the
initial SYN packet to be zero, from RFC1323:

         When TSecr is not valid, its value must be zero.

It is therefore impossible to accept TSval as zero, because
our TSecr echo of that timestamp would be also zero and thus
invalid.

That is why we reject zero timestamps in the initial SYN packet.

  reply	other threads:[~2003-10-23  8:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-22 20:01 RFC1323. No timestamping if SYN timestamp = 0. Bug or Feature? Bartek Wydrowski
2003-10-23  8:37 ` David S. Miller [this message]
2003-10-24 13:16   ` Casey Carter

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=20031023013748.0dd168db.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=b_wydrowski@yahoo.com.au \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=netdev@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).