Re: [tcpm] RFC 1323: Timestamps option
Matt Mathis <mathis@psc.edu> Fri, 26 January 2007 19:49 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HAX4d-0001AN-RK; Fri, 26 Jan 2007 14:49:23 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HAX4c-0001AG-GU for tcpm@ietf.org; Fri, 26 Jan 2007 14:49:22 -0500
Received: from mailer1.psc.edu ([128.182.58.100]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HAX4Y-0003Lt-1u for tcpm@ietf.org; Fri, 26 Jan 2007 14:49:22 -0500
Received: from tesla.psc.edu (tesla.psc.edu [128.182.58.233]) by mailer1.psc.edu (8.13.8/8.13.3) with ESMTP id l0QJnHpS018591 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 26 Jan 2007 14:49:17 -0500 (EST)
Received: from localhost.psc.edu (localhost.psc.edu [127.0.0.1]) by tesla.psc.edu (8.13.1/8.13.1) with ESMTP id l0QJnHMM000773; Fri, 26 Jan 2007 14:49:17 -0500
Date: Fri, 26 Jan 2007 14:49:17 -0500
From: Matt Mathis <mathis@psc.edu>
To: David Borman <david.borman@windriver.com>
Subject: Re: [tcpm] RFC 1323: Timestamps option
In-Reply-To: <018977E8-C9F4-42E2-A877-95330F65E7D3@windriver.com>
Message-ID: <Pine.LNX.4.58.0701261400060.14317@tesla.psc.edu>
References: <018977E8-C9F4-42E2-A877-95330F65E7D3@windriver.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
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
On Fri, 26 Jan 2007, David Borman wrote: > One of the topics that has been discussed in the past for the > revision of RFC 1323 is to relax the requirement on when to send the > Timestamps option. I'd like to come to some resolution on this issue. > > Current: > The Timestamps option is negotiated during the initial SYN exchange. > If both sides support it, then every packet in the connection has to > have the Timestamps option. ... snip ... > > My viewpoint > ------------ > Right now, I'm inclined to leave the Timestamps option alone; you > negotiate it during the SYN exchange, and then include it on every > packet. I'm willing to be convinced otherwise, but now I've placed a > stake in the ground, and the mailing list will have to decide if > there is sufficient reason to change the behavior. The real problem is a zero configuration issue: for the 100 million or so US home users on DSL (or worse, compressing modems), timestamps offer little gain and often substantial penalty. For the 10 Million(?) US university users, timestamps are necessary for good performance. Who do you think the manufacturers cater to? The simple answer is the home user, but many current systems use some sort of heuristic (e.g. is the interface faster than 100 Mb/s?). The current situation forces us to try to educate 9.99 million non-network savvy users how to inspect and tweak their kernels. I want ZERO config from at least 9.6 kbs to 9 Gbps. Some form of late timestamp negotiation is required before this can become the default. (BTW Japan and Europe, with true high speed to the home might change the equation quite a bit. This path leads to some ugly market positions.) Thanks, --MM-- P.S. The default WSCALE for MS Vista and mainline Linux is now 8 and 7 respectively for large memory systems, so the harder part of the zero config problem has already been solved. These correspond to 16 and 8 MByte TCP buffers. Roll out is going to take a while, but that will give people a chance to notice how the traffic might affect the network. QoS anyone? Thanks, --MM-- ------------------------------------------- Matt Mathis http://www.psc.edu/~mathis Work:412.268.3319 Home/Cell:412.654.7529 ------------------------------------------- Evil is defined by mortals who think they know "The Truth" and use force to apply it to others. _______________________________________________ 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