Re: [Tsvwg] Input for draft-paxson-tcp-rto-00.txt
Scott Bradner <sob@harvard.edu> Thu, 25 November 1999 15:00 UTC
Received: from newdev.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18510 for <tsvwg@ietf.org>; Thu, 25 Nov 1999 10:00:31 -0500 (EST)
Received: (from sob@localhost) by newdev.harvard.edu (8.9.3/8.9.3) id KAA21841; Thu, 25 Nov 1999 10:00:29 -0500 (EST)
Date: Thu, 25 Nov 1999 10:00:29 -0500
From: Scott Bradner <sob@harvard.edu>
Message-Id: <199911251500.KAA21841@newdev.harvard.edu>
To: Reiner.Ludwig@eed.ericsson.se, vern@ee.lbl.gov
Subject: Re: [Tsvwg] Input for draft-paxson-tcp-rto-00.txt
Cc: tsvwg@ietf.org
Reiner, this document is trying to ensure that someone who wants to implement TCP *as it is currently defined* can do so from RFCs - this part of the TCP spec had never been documented in RFCs (though it had been elsewhere and in lots of code) It is proposed standard because it defines what the current IETF standard is for this function Proposals for changes to the way TCP works for the future can be considered on their own merits in the future. Scott
- 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