From: Rick Jones <rick.jones2@hp.com>
To: Stephen Hemminger <stephen.hemminger@vyatta.com>
Cc: Stephane Chazelas <Stephane_Chazelas@yahoo.fr>,
Stephen Hemminger <shemminger@vyatta.com>,
David Miller <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: rtt metric only for incoming connections?
Date: Tue, 27 May 2008 11:53:38 -0700 [thread overview]
Message-ID: <483C58B2.8080100@hp.com> (raw)
In-Reply-To: <20080527114311.2734402b@speedy>
>>Also, it seems we can't lower the initial RTO below the RFC 1122
>>default of 3 seconds. 3 seconds may be appropriate for a host
>>for which we don't know how many hops, links, satellites are
>>needed to reach it, but what about local/corporate networks
>>where it's possible to administratively know the rtt so that it
>>can be hardcoded in the routing table.
>
>
> Violating RFC's is not really that useful.
Yet the RFC's are not stone tablets, and they often represent a
"compromise" between things desirable for the great big internet and
those someone with a bounded network might have.
> If you have a network dropping SYN packets regularly than there are
> worse problems.
That is entirely plausible.
> Relying on TCP to overcome wireless network problems is not
> a good idea.
How is it any worse than relying on TCP to overcome network congestion
problems?-)
rick jones
prev parent reply other threads:[~2008-05-27 18:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 16:38 [iproute2] get_hz() with CONFIG_HIGH_RES_TIMERS Stephane Chazelas
2008-05-21 16:56 ` Patrick McHardy
2008-05-21 17:40 ` [PATCH] net: neighbour table ABI problem Stephen Hemminger
2008-05-21 20:35 ` David Miller
2008-05-22 0:20 ` Thomas Graf
2008-06-03 23:03 ` David Miller
2008-05-21 17:10 ` [iproute2] get_hz() with CONFIG_HIGH_RES_TIMERS Stephen Hemminger
2008-05-21 18:43 ` route metrics in jiffies?? Stephen Hemminger
2008-05-21 20:31 ` David Miller
2008-05-22 10:36 ` rtt metric only for incoming connections? Stephane Chazelas
2008-05-27 18:43 ` Stephen Hemminger
2008-05-27 18:53 ` Rick Jones [this message]
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=483C58B2.8080100@hp.com \
--to=rick.jones2@hp.com \
--cc=Stephane_Chazelas@yahoo.fr \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
--cc=stephen.hemminger@vyatta.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).