Re: Last Call: TCP Slow Start, Congestion Avoidance, Fast Retransmit, and Fast Recovery Algorithms to Proposed Standard

Geert Jan de Groot <GeertJan.deGroot@ripe.net> Tue, 19 March 1996 19:23 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa20503; 19 Mar 96 14:23 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa20499; 19 Mar 96 14:23 EST
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa10928; 19 Mar 96 14:23 EST
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa20490; 19 Mar 96 14:23 EST
Received: from ncc.ripe.net by IETF.CNRI.Reston.VA.US id aa20486; 19 Mar 96 14:23 EST
Received: from office.ripe.net by ncc.ripe.net with SMTP id AA22380 (5.65a/NCC-2.31); Tue, 19 Mar 1996 20:23:07 +0100
Message-Id: <9603191923.AA22380@ncc.ripe.net>
To: The IESG <iesg@IETF.CNRI.Reston.VA.US>
Cc: Richard Stevens <rstevens@noao.edu>
X-Orig-Sender: iesg-request@IETF.CNRI.Reston.VA.US
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Geert Jan de Groot <GeertJan.deGroot@ripe.net>
X-Organization: RIPE Network Coordination Centre
X-Phone: +31 20 592 5065
Subject: Re: Last Call: TCP Slow Start, Congestion Avoidance, Fast Retransmit, and Fast Recovery Algorithms to Proposed Standard
In-Reply-To: Your message of "Tue, 19 Mar 1996 13:19:06 EST." <9603191319.aa18538@IETF.CNRI.Reston.VA.US>
Date: Tue, 19 Mar 1996 20:23:06 +0100
X-Orig-Sender: GeertJan.deGroot@ripe.net

Hi,

It is probably obvious from my previous message on this that I
fully support this document to go to PS. 
My main reason for suggesting BCP earlier is that it is a shorter
path - the code has been running for several years so it has a good
track record ;-)

Sorry to send this to the IESG but that what you asked to do...

Cheers,

Geert Jan



On Tue, 19 Mar 96 13:19:06 -0500  The IESG wrote:
> The IESG has received a request to consider "TCP Slow Start, Congestion
> Avoidance, Fast Retransmit, and Fast Recovery Algorithms"
> <draft-stevens-tcpca-spec-01.txt> as a Proposed Standard.  This has
> been reviewed in the IETF but is not the product of an IETF Working
> Group.
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send any comments to the
> iesg@cnri.reston.va.us or ietf@cnri.reston.va.us mailing lists by April
> 18, 1996.
>