IETF Logo Mail Archive

Re: [tcpm] Re: draft-ietf-tcpm-ecnsyn-03.txt backwards compatibility

Sally Floyd <sallyfloyd@mac.com> Wed, 09 January 2008 04:40 UTC

Return-path: <tcpm-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JCSkB-00063g-Ig; Tue, 08 Jan 2008 23:40:47 -0500
Received: from tcpm by megatron.ietf.org with local (Exim 4.43) id 1JCSk9-00063a-Up for tcpm-confirm+ok@megatron.ietf.org; Tue, 08 Jan 2008 23:40:45 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JCSk9-00063S-Kr for tcpm@ietf.org; Tue, 08 Jan 2008 23:40:45 -0500
Received: from smtpoutm.mac.com ([17.148.16.80]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JCSk7-0007HL-DX for tcpm@ietf.org; Tue, 08 Jan 2008 23:40:45 -0500
Received: from mac.com (asmtp002-s [10.150.69.65]) by smtpoutm.mac.com (Xserve/smtpout017/MantshX 4.0) with ESMTP id m094eW6P025080; Tue, 8 Jan 2008 20:40:32 -0800 (PST)
Received: from [192.168.1.101] (adsl-70-132-0-53.dsl.snfc21.sbcglobal.net [70.132.0.53]) (authenticated bits=0) by mac.com (Xserve/asmtp002/MantshX 4.0) with ESMTP id m094eU3I016347; Tue, 8 Jan 2008 20:40:30 -0800 (PST)
In-Reply-To: <20080109013436.D06BD32F2AC@lawyers.icir.org>
References: <20080109013436.D06BD32F2AC@lawyers.icir.org>
Mime-Version: 1.0 (Apple Message framework v624)
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-Id: <27fa302bfe7047223845594c72c07097@mac.com>
Content-Transfer-Encoding: 7bit
From: Sally Floyd <sallyfloyd@mac.com>
Subject: Re: [tcpm] Re: draft-ietf-tcpm-ecnsyn-03.txt backwards compatibility
Date: Tue, 08 Jan 2008 20:40:28 -0800
To: mallman@icir.org
X-Mailer: Apple Mail (2.624)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: Aleksandar Kuzmanovic <akuzma@northwestern.edu>, "K. K. Ramakrishnan" <kkrama@research.att.com>, Amit Mondal <a-mondal@northwestern.edu>, 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

>> Mark, is it time for me to submit the revised internet-draft?
>
> Yep---that sounds like the right thing to do.

Done.  It is at:
http://tools.ietf.org/html/draft-ietf-tcpm-ecnsyn-04

- Sally
http://www.icir.org/floyd/



The diffs:

    NOTE TO RFC EDITOR: PLEASE DELETE THIS NOTE UPON PUBLICATION.

    Changes from draft-ietf-tcpm-ecnsyn-03:

    * General editing.  This includes using the terms "initiator"
      and "responder" for the two ends of the TCP connection.
      Feedback from Alfred Hoenes.

    * Added some text to the backwards compatibility discussion,
      now in Appendix B, about the pros and cons of using a TCP
      flag for the TCP initiator to signal that it understands
      ECN-Capable SYN/ACK packets.  The consensus at this time is
      not to use such a flag.  Also added a recommendation that
      TCP implementations include a management interface to turn
      off the use of ECN for SYN/ACK packets.  From email from
      Bob Briscoe.



_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www1.ietf.org/mailman/listinfo/tcpm

v2.31.3 | Report a Bug | By Email | System Status