Re: [tcpm] RFC 1323: Timestamps option
David Borman <david.borman@windriver.com> Fri, 26 January 2007 20:05 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HAXJm-0002lP-JY; Fri, 26 Jan 2007 15:05:02 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HAXJl-0002lI-UF for tcpm@ietf.org; Fri, 26 Jan 2007 15:05:01 -0500
Received: from mail.windriver.com ([147.11.1.11] helo=mail.wrs.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HAXJj-00066k-Gv for tcpm@ietf.org; Fri, 26 Jan 2007 15:05:01 -0500
Received: from ALA-MAIL03.corp.ad.wrs.com (ala-mail03 [147.11.57.144]) by mail.wrs.com (8.13.6/8.13.6) with ESMTP id l0QK4ruK012031; Fri, 26 Jan 2007 12:04:53 -0800 (PST)
Received: from ala-mail06.corp.ad.wrs.com ([147.11.57.147]) by ALA-MAIL03.corp.ad.wrs.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 26 Jan 2007 12:04:53 -0800
Received: from [192.168.117.73] ([192.168.117.73]) by ala-mail06.corp.ad.wrs.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 26 Jan 2007 12:04:53 -0800
In-Reply-To: <20070126194217.D300616E703@lawyers.icir.org>
References: <20070126194217.D300616E703@lawyers.icir.org>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <F2997536-93BF-4BA7-BB9C-2F1D211DDB1C@windriver.com>
Content-Transfer-Encoding: 7bit
From: David Borman <david.borman@windriver.com>
Subject: Re: [tcpm] RFC 1323: Timestamps option
Date: Fri, 26 Jan 2007 14:05:34 -0600
To: mallman@icir.org
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 26 Jan 2007 20:04:53.0442 (UTC) FILETIME=[3E439220:01C74185]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: TCP Maintenance and Minor Extensions WG <tcpm@ietf.org>
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
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
You've probably already seen my reply to Sally, but I'll clarify a few things: On Jan 26, 2007, at 1:42 PM, Mark Allman wrote: > + Why is the "best case" that you'll get multiple samples per > RTT? It > seems to me that the underlying assumption is that "more is > better", > but I am not sure it is. We have done some analysis that suggests > more samples are not better. I don't want to say our analysis is > the last word here, but I'd be interested in hearing arguments for > taking more samples [using the current RTO estimator] per RTT > being > a clear win. > > I think this is an important point in choosing a path. I.e., if > multiple RTT measurements matter then that might suggest a > different > approach than if multiple RTTs buy you little/nothing. Perhaps "best case" was the wrong term. Being guaranteed at least one good RTT measurement per RTT is a good thing. The current RTO estimator is based on getting one sample per RTT, no matter how much data flows during that time. As you know, when you start using all the samples from multiple Timestamps options, if you just feed them into the current RTO estimator it can seriously skew the results, especially if you are getting lots of samples per RTT. In my reply to Sally, I suggested taking the average of all the Timestamps received during one RTT, and feeding that into the RTO estimator. An alternative would be to take the largest sample received during the RTT interval, and feed that into the estimator. That'd be even easier to implement. Do you have any thoughts as to which would be better? Another alternative would be to only use the sample from the Timestamps option in the ACK for the sequence number that is being timed, i.e. back to one sample per RTT. But that is still a win over the old method, because with Timestamps, we know that the measurement will always be accurate, even if there was a retransmission during the RTT. But I totally agree, just feeding in the more frequent samples from the Timestamps into the RTO estimator is not a good thing. -David Borman _______________________________________________ tcpm mailing list tcpm@ietf.org https://www1.ietf.org/mailman/listinfo/tcpm
- [tcpm] RFC 1323: Timestamps option David Borman
- Re: [tcpm] RFC 1323: Timestamps option Sally Floyd
- Re: [tcpm] RFC 1323: Timestamps option Mark Allman
- Re: [tcpm] RFC 1323: Timestamps option David Borman
- Re: [tcpm] RFC 1323: Timestamps option Matt Mathis
- Re: [tcpm] RFC 1323: Timestamps option Fernando Gont
- Re: [tcpm] RFC 1323: Timestamps option David Borman
- Re: [tcpm] RFC 1323: Timestamps option David Malone
- Re: [tcpm] RFC 1323: Timestamps option Mark Allman
- Re: [tcpm] RFC 1323: Timestamps option Mark Allman
- Re: [tcpm] RFC 1323: Timestamps option Richard Wendland
- [tcpm] RE: RFC 1323: Timestamps option Mahdavi, Jamshid
- Re: [tcpm] RFC 1323: Timestamps option Kacheong Poon
- Re: [tcpm] RFC 1323: Timestamps option Gavin McCullagh
- [tcpm] Re: RFC 1323: Timestamps option David Borman
- Re: [tcpm] Re: RFC 1323: Timestamps option Joe Touch
- Re: [tcpm] Re: RFC 1323: Timestamps option David Borman
- Re: [tcpm] Re: RFC 1323: Timestamps option Matt Mathis
- Re: [tcpm] Re: RFC 1323: Timestamps option Joe Touch
- Re: [tcpm] Re: RFC 1323: Timestamps option David Borman
- Re: [tcpm] Re: RFC 1323: Timestamps option David Borman
- Re: [tcpm] Re: RFC 1323: Timestamps option Matt Mathis
- Re: [tcpm] Re: RFC 1323: Timestamps option Joe Touch