Re: [tcpm] RFC 1323: Timestamps option

Gavin McCullagh <gavin.mccullagh@nuim.ie> Mon, 29 January 2007 15:55 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBYr9-0008Mq-Cc; Mon, 29 Jan 2007 10:55:43 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBYr7-0008KF-PX for tcpm@ietf.org; Mon, 29 Jan 2007 10:55:41 -0500
Received: from mail.nuim.ie ([149.157.1.19] helo=LARCH.MAY.IE) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBYqg-0005fn-7e for tcpm@ietf.org; Mon, 29 Jan 2007 10:55:41 -0500
Received: from retina-bcl.hamilton.local ([149.157.192.252]) by NUIM.IE (PMDF V6.2-X17 #30789) with ESMTPA id <01MCI9KKHBI8013D71@NUIM.IE> for tcpm@ietf.org; Mon, 29 Jan 2007 15:55:33 +0000 (GMT)
Received: from gavinmc by retina-bcl.hamilton.local with local (Exim 4.50) id 1HBYqY-0001Ah-Sw for tcpm@ietf.org; Mon, 29 Jan 2007 15:55:06 +0000
Date: Mon, 29 Jan 2007 15:55:06 +0000
From: Gavin McCullagh <gavin.mccullagh@nuim.ie>
Subject: Re: [tcpm] RFC 1323: Timestamps option
In-reply-to: <F2997536-93BF-4BA7-BB9C-2F1D211DDB1C@windriver.com>
To: tcpm@ietf.org
Message-id: <20070129155506.GG27467@nuim.ie>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline
User-Agent: Mutt/1.5.9i
References: <20070126194217.D300616E703@lawyers.icir.org> <F2997536-93BF-4BA7-BB9C-2F1D211DDB1C@windriver.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Gavin McCullagh <gavin.mccullagh@nuim.ie>
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
Errors-To: tcpm-bounces@ietf.org

Hi,

On Fri, 26 Jan 2007, David Borman wrote:

> But I totally agree, just feeding in the more frequent samples from                                                           
> the Timestamps into the RTO estimator is not a good thing.                                                                    

Indeed. Naturally, it is possible to adjust the RTO estimation to be able
to deal with receiving estimates more often, or even irregularly. Quite a
few OSes (eg Darwin, I think?) use a RTO timer (and time stamps) that ticks
every half a second, and so effectively rounds up to the nearest 500ms.  I
guess this shows that it doesn't matter too much what you do, as long as
you give a reasonable overestimate.

It is conceivable that people might want to use timestamps for things other
than RTO estimation. Some of the high-speed TCP variants want more RTT
samples (we're playing with one that expects an RTT sample per ACK at the
moment).  I don't think any of the suggested new behaviours would cause
problems with these uses, but it may be worth keeping in mind while
updating RFC 1323.

As an example of a more exotic use of the time stamp option, the most
recent version of FreeBSD's syncookies stashes information in the
timestamp:

        http://lists.freebsd.org/pipermail/freebsd-net/2006-September/011651.html

Gavin


_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www1.ietf.org/mailman/listinfo/tcpm