IETF Logo Mail Archive

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

Craig Partridge <craig@aland.bbn.com> Mon, 15 July 1996 15:35 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa14478; 15 Jul 96 11:35 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa14473; 15 Jul 96 11:35 EDT
Received: from ietf.org by CNRI.Reston.VA.US id aa09584; 15 Jul 96 11:35 EDT
Received: from ietf.org by ietf.org id aa26539; 15 Jul 96 11:34 EDT
Received: from aland.bbn.com by ietf.org id aa26535; 15 Jul 96 11:34 EDT
Received: (from craig@localhost) by aland.bbn.com (8.7.1/8.7.1) id IAA01452; Mon, 15 Jul 1996 08:34:29 -0700 (PDT)
Message-Id: <199607151534.IAA01452@aland.bbn.com>
To: iesg@ietf.org
cc: ietf@CNRI.Reston.VA.US
Subject: Re: Last Call: TCP Slow Start, Congestion Avoidance, Fast Retransmit, and Fast Recovery Algorithms to BCP
In-reply-to: Your message of Mon, 15 Jul 96 07:13:39 -0400. <9607150713.aa08723@IETF.CNRI.Reston.VA.US>
Date: Mon, 15 Jul 1996 08:34:28 -0700
X-Orig-Sender: iesg-request@ietf.org
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Craig Partridge <craig@aland.bbn.com>

    
    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 Best Current Practices RFC.
    This document has been reviewed in the IETF, but is not the product of
    an IETF Working Group.

    Note that this is a second last call. The first last call was for
    Proposed Standard status. During the Last Call, a number of the
    comments suggested that BCP was a a more appropriate category for this
    document.

Hi folks:

    I need a scorecard.

    How can something become a BCP when it is already a Standard?

    Slow Start and Congestion Avoidance have been a required part of TCP
(not a BCP, but an explicit MUST implement for conformance) since RFC 1122
came out.

Very puzzled,

Craig

v2.23.0 | Report a Bug | By Email