Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 21 Sep 2005 19:16:26 +0200
From:      =?ISO-8859-1?Q?Sten_Daniel_S=F8rsdal?= <lists@wm-access.no>
To:        Robert Watson <rwatson@freebsd.org>
Cc:        freebsd-net@freebsd.org
Subject:   Re: UDP dont fragment bit
Message-ID:  <4331956A.2060406@wm-access.no>
In-Reply-To: <20050921142903.J34322@fledge.watson.org>
References:  <20050918212110.61962.qmail@web54501.mail.yahoo.com>	<20050920134408.Y34322@fledge.watson.org>	<43313924.9050009@wm-access.no>	<20050921114511.D34322@fledge.watson.org>	<4331539D.9030204@wm-access.no>	<20050921134029.M34322@fledge.watson.org>	<43315E6F.1020003@wm-access.no> <20050921142903.J34322@fledge.watson.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Robert Watson wrote:
> 
> On Wed, 21 Sep 2005, Sten Daniel Sørsdal wrote:
> 
> While the below is perfectly valid and useful and should be easy to
> implement with andre's proposed change, would you prefer an interface
> that allowed you to query the TCP connection and ask it what pathwise
> MTU it had already probed for the route?  The kernel host cache already
> maintains a number of paramaters associated with built TCP connections
> to a host, such as the probed PMTU, estimated RTT and variance,
> estimated bandwidth, congestion window, and so on.  While it wouldn't
> necessarily replace logic to reprobe connection conditions, it seems as
> though if you're going to go to the trouble of building a separate
> control TCP connection, you might as well benefit from what it finds.
> 
> You can find a list of current host cache properties in
> src/sys/netinet/tcp_hostcache.c, struct hc_metrics.
> 

Often there already is need for a tcp connection for authentication,
negotiation and so forth.

RTT could, among other things, make a discovery process choose how fine
the increments/descrements should be.

Estimated bandwidth could also help the actual data transport start out
with a more situation correct value.

However with the abundance of routers modifying TCP MSS correctly
incorrectly and the odd chance that the data path of UDP packets is
different than TCP packets it wouldnt really give anything necessarily
reliable discovery process. And taking advantage of such values could
make the process more complex or less reliable.



-- 
Sten Daniel Sørsdal



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4331956A.2060406>