netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cong Wang <amwang@redhat.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
	Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
	Patrick McHardy <kaber@trash.net>,
	Eric Dumazet <edumazet@google.com>
Subject: Re: [RFC PATCH net-next] tcp: introduce tcp_tw_interval to specifiy the time of TIME-WAIT
Date: Tue, 09 Oct 2012 11:42:16 +0800	[thread overview]
Message-ID: <1349754136.2420.0.camel@cr0> (raw)
In-Reply-To: <20121008140743.GC22939@hmsreliant.think-freely.org>

On Mon, 2012-10-08 at 10:07 -0400, Neil Horman wrote:
> On Mon, Oct 08, 2012 at 11:17:37AM +0800, Cong Wang wrote:
> > On Tue, 2012-10-02 at 08:09 -0400, Neil Horman wrote:
> > > No, its not very friendly, but the people using this are violating the RFC,
> > > which isn't very friendly. :)
> > 
> > Could you be more specific? In RFC 793, AFAIK, it is allowed to be
> > changed:
> > 
> > http://tools.ietf.org/html/rfc793
> > 
> > " To be sure that a TCP does not create a segment that carries a
> >   sequence number which may be duplicated by an old segment remaining in
> >   the network, the TCP must keep quiet for a maximum segment lifetime
> >   (MSL) before assigning any sequence numbers upon starting up or
> >   recovering from a crash in which memory of sequence numbers in use was
> >   lost.  For this specification the MSL is taken to be 2 minutes.  This
> >   is an engineering choice, and may be changed if experience indicates
> >   it is desirable to do so."
> > 
> Its the length of time that represents an MSL that was the choice, not the fact
> that reusing a TCP before the expiration of the MSL is a bad idea.
> 
> > or I must still be missing something here... :)
> > 
> Next paragraph down:
> 	This specification provides that hosts which "crash" without
>     retaining any knowledge of the last sequence numbers transmitted on
>     each active (i.e., not closed) connection shall delay emitting any
>     TCP segments for at least the agreed Maximum Segment Lifetime (MSL)
>     in the internet system of which the host is a part.  In the
>     paragraphs below, an explanation for this specification is given.
>     TCP implementors may violate the "quiet time" restriction, but only
>     at the risk of causing some old data to be accepted as new or new
>     data rejected as old duplicated by some receivers in the internet
>     system. .... etc.
> 
> 

Ah, ok. Thanks for the detailed answer!

  reply	other threads:[~2012-10-09  3:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-27  8:41 [RFC PATCH net-next] tcp: introduce tcp_tw_interval to specifiy the time of TIME-WAIT Cong Wang
2012-09-27 14:23 ` Neil Horman
2012-09-27 17:02   ` Rick Jones
2012-09-28  6:33   ` Cong Wang
2012-09-28  6:43     ` David Miller
2012-09-28 17:30       ` Rick Jones
2012-09-28 13:16     ` Neil Horman
2012-10-02  7:04       ` Cong Wang
2012-10-02 12:09         ` Neil Horman
2012-10-08  3:17           ` Cong Wang
2012-10-08 14:07             ` Neil Horman
2012-10-09  3:42               ` Cong Wang [this message]
2012-09-27 17:05 ` David Miller
2012-09-28  6:39   ` Cong Wang
2012-09-28  6:44     ` 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=1349754136.2420.0.camel@cr0 \
    --to=amwang@redhat.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kaber@trash.net \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.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).