Re: [Tsvwg] Input for draft-paxson-tcp-rto-00.txt
Reiner Ludwig <Reiner.Ludwig@eed.ericsson.se> Wed, 01 December 1999 17:15 UTC
Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19130 for <tsvwg@ietf.org>; Wed, 1 Dec 1999 12:15:27 -0500 (EST)
Received: from eed.ericsson.se (mailhost.eed.ericsson.se [164.48.130.6]) by penguin.wise.edt.ericsson.se (8.9.3/8.9.3/WIREfire-1.5) with ESMTP id SAA04903; Wed, 1 Dec 1999 18:07:57 +0100 (MET)
Received: from eifel.eed.ericsson.se (eifel [164.48.194.242]) by eed.ericsson.se (8.8.8+Sun/1.1.mit) with ESMTP id SAA01848; Wed, 1 Dec 1999 18:07:54 +0100 (MET)
Message-Id: <4.2.0.58.19991201173810.00b028d0@chapelle.ericsson.se>
X-Sender: eedrel@chapelle.ericsson.se
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58
Date: Wed, 01 Dec 1999 18:07:35 +0100
To: mallman@grc.nasa.gov
From: Reiner Ludwig <Reiner.Ludwig@eed.ericsson.se>
Subject: Re: [Tsvwg] Input for draft-paxson-tcp-rto-00.txt
Cc: Reiner Ludwig <Reiner.Ludwig@eed.ericsson.se>, Vern Paxson <vern@ee.lbl.gov>, Scott Bradner <sob@harvard.edu>, tsvwg@ietf.org, van@cisco.com
In-Reply-To: <199912011535.KAA21046@lombok-fi.lerc.nasa.gov>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
At 16:35 01.12.99 , Mark Allman wrote: >However, I see no reason to block this document on the possibility >of getting evidence of a new and better RTO estimator at some point >in the future. This is not my intention. By now, I understand that the purpose of the I-D is to simply document the "de facto". This was not clear to me in the beginning. I now agree that it is a good idea to have this I-D become a proposed standard, and I appreciate your, Vern's and the other involved people's efforts. Furthermore, I certainly agree that any alternative for estimating the RTO will need to be *very* thoroughly verified before someone even thinks about feeding it into the IETF. When I started this thread (posting the pointer to our paper), I wanted to make people aware of some problems we found with the current "de facto" RTO. My intention was *not* to promote a new RTO that at this point has *not* been thoroughly verified. In my past mails, I'm merely questioning what the "de facto" for the RTO-MIN really is. ///Reiner
- Input for draft-paxson-tcp-rto-00.txt Reiner Ludwig
- Re: [Tsvwg] Input for draft-paxson-tcp-rto-00.txt Vern Paxson
- Re: [Tsvwg] Input for draft-paxson-tcp-rto-00.txt Reiner Ludwig
- Re: [Tsvwg] Input for draft-paxson-tcp-rto-00.txt Vern Paxson
- Re: [Tsvwg] Input for draft-paxson-tcp-rto-00.txt Reiner Ludwig
- Re: [Tsvwg] Input for draft-paxson-tcp-rto-00.txt Scott Bradner
- Re: [Tsvwg] Input for draft-paxson-tcp-rto-00.txt Reiner Ludwig
- Re: [Tsvwg] Input for draft-paxson-tcp-rto-00.txt Vern Paxson
- Re: [Tsvwg] Input for draft-paxson-tcp-rto-00.txt Reiner Ludwig
- Re: [Tsvwg] Input for draft-paxson-tcp-rto-00.txt Vern Paxson
- Re: [Tsvwg] Input for draft-paxson-tcp-rto-00.txt Reiner Ludwig
- Re: [Tsvwg] Input for draft-paxson-tcp-rto-00.txt Mark Allman
- Re: [Tsvwg] Input for draft-paxson-tcp-rto-00.txt Reiner Ludwig