[tcpm] Fwd: I-D Action:draft-ietf-tcpm-ecnsyn-07.txt
Sally Floyd <sallyfloyd@mac.com> Tue, 18 November 2008 19:32 UTC
Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0757E3A6809; Tue, 18 Nov 2008 11:32:58 -0800 (PST)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0166D3A6809 for <tcpm@core3.amsl.com>; Tue, 18 Nov 2008 11:32:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q6q5mDssCa7j for <tcpm@core3.amsl.com>; Tue, 18 Nov 2008 11:32:55 -0800 (PST)
Received: from asmtpout016.mac.com (asmtpout016.mac.com [17.148.16.91]) by core3.amsl.com (Postfix) with ESMTP id DA7BF3A67F4 for <tcpm@ietf.org>; Tue, 18 Nov 2008 11:32:55 -0800 (PST)
MIME-version: 1.0
Received: from [192.168.1.132] ([70.231.247.191]) by asmtp016.mac.com (Sun Java(tm) System Messaging Server 6.3-7.03 (built Aug 7 2008; 32bit)) with ESMTPSA id <0KAJ0073ANMRTV30@asmtp016.mac.com> for tcpm@ietf.org; Tue, 18 Nov 2008 11:32:53 -0800 (PST)
Message-id: <F5E3B719-AA2D-4D50-A878-4A93053A1321@mac.com>
From: Sally Floyd <sallyfloyd@mac.com>
To: tcpm <tcpm@ietf.org>
Date: Tue, 18 Nov 2008 11:32:51 -0800
References: <36235E15-9019-476A-9CA7-519026635558@mac.com>
X-Mailer: Apple Mail (2.929.2)
Subject: [tcpm] Fwd: I-D Action:draft-ietf-tcpm-ecnsyn-07.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org
This is just a reminder that, though I won't be at the tcpm meeting today, we have made a revision to the draft-ietf-tcpm-ecnsyn draft, and it needs another round of working group review before moving back to the IESG for the final stages. "http://tools.ietf.org/html/draft-ietf-tcpm-ecnsyn-07" Many thanks, - Sally Begin forwarded message: > From: Sally Floyd <sallyfloyd@mac.com> > Date: November 5, 2008 4:04:56 PM PST > To: tcpm <tcpm@ietf.org> > Cc: "K. K. Ramakrishnan" <kkrama@research.att.com>, Amit Mondal <amitmondal2010@u.northwestern.edu > >, Aleksandar Kuzmanovic <akuzma@cs.northwestern.edu> > Subject: Re: [tcpm] I-D Action:draft-ietf-tcpm-ecnsyn-07.txt > > We have (finally) revised draft-ietf-tcpm-ecnsyn, on "Adding Explicit > Congestion Notification (ECN) Capability to TCP's SYN/ACK Packets", > and are finally ready for it to complete the standardization process. > > Here is the story: > > The draft had finished Working Group Last Call, and been forwarded > to the IESG for review. As a final step in revising the draft > after the AD Evaluation, we (the authors) reran the simulations > with an updated version of the ns-2 simulator, and found that in > some highly congested scenarios, ECN+ would significantly increase > the packet drop rate even further. (I am appending the 5/26/08 > email below.) > > In response to this, we have added a change to ECN+, which in > the new draft we call "ECN+/TryOnce". With ECN+/TryOnce, when > an ECN-Capable SYN/ACK packet is ECN-marked, the TCP responder > sends another SYN/ACK packet that is not ECN-Capable, and also > reduces the initial window to one packet. ECN+/TryOnce > shows most of the performance benefit of ECN+, and avoids the > problem of increasing the packet drop rate in times of high > congestion. > > I think it makes sense to pass this through the working group > before going back to the IESG. However, I won't be at IETF > in Minnesota, and am hoping that this can be done by email. > > The new version of the draft is at: > "http://tools.ietf.org/html/draft-ietf-tcpm-ecnsyn-07", > and that web page also gives the differences with earlier > versions of the draft. Any feedback would be appreciated. > > Many thanks, > - Sally > http://www.icir.org/floyd/ ... >> From: Internet-Drafts@ietf.org >> Date: November 3, 2008 12:30:01 PM PST >> To: i-d-announce@ietf.org >> Cc: tcpm@ietf.org >> Subject: [tcpm] I-D Action:draft-ietf-tcpm-ecnsyn-07.txt >> >> A New Internet-Draft is available from the on-line Internet-Drafts >> directories. >> This draft is a work item of the TCP Maintenance and Minor >> Extensions Working Group of the IETF. >> >> >> Title : Adding Explicit Congestion Notification (ECN) >> Capability to TCP's SYN/ACK Packets >> Author(s) : S. Floyd, I. Property >> Filename : draft-ietf-tcpm-ecnsyn-07.txt >> Pages : 33 >> Date : 2008-11-03 >> >> This draft specifies a modification to RFC 3168 to allow TCP SYN/ACK >> packets to be ECN-Capable. For TCP, RFC 3168 only specifies setting >> an ECN-Capable codepoint on data packets, and not on SYN and SYN/ACK >> packets. However, because of the high cost to the TCP transfer of >> having a SYN/ACK packet dropped, with the resulting retransmit >> timeout, this document specifies the use of ECN for the SYN/ACK >> packet itself, when sent in response to a SYN packet with the two ECN >> flags set in the TCP header, indicating a willingness to use ECN. >> Setting the initial TCP SYN/ACK packet as ECN-Capable can be of great >> benefit to the TCP connection, avoiding the severe penalty of a >> retransmit timeout for a connection that has not yet started placing >> a load on the network. The TCP responder (the sender of the SYN/ACK >> packet) must reply to a report of an ECN-marked SYN/ACK packet by >> resending a SYN/ACK packet that is not ECN-Capable. If the resent >> SYN/ACK packet is acknowledged, then the TCP responder reduces its >> initial congestion window from two, three, or four segments to one >> segment, thereby reducing the subsequent load from that connection on >> the network. If instead the SYN/ACK packet is dropped, or for some >> other reason the TCP responder does not receive an acknowledgement in >> the specified time, the TCP responder follows TCP standards for a >> dropped SYN/ACK packet (setting the retransmit timer). This document >> updates RFC 3168. >> >> A URL for this Internet-Draft is: >> http://www.ietf.org/internet-drafts/draft-ietf-tcpm-ecnsyn-07.txt >> >> Internet-Drafts are also available by anonymous FTP at: >> ftp://ftp.ietf.org/internet-drafts/ >> >> Below is the data which will enable a MIME compliant mail reader >> implementation to automatically retrieve the ASCII version of the >> Internet-Draft. > Content-Type: text/plain<BR>Content-ID: <2008-11-03122057.I-D@ietf.org > ><BR><BR> > >> _______________________________________________ >> tcpm mailing list >> tcpm@ietf.org >> https://www.ietf.org/mailman/listinfo/tcpm _______________________________________________ tcpm mailing list tcpm@ietf.org https://www.ietf.org/mailman/listinfo/tcpm
- [tcpm] I-D Action:draft-ietf-tcpm-ecnsyn-07.txt Internet-Drafts
- Re: [tcpm] I-D Action:draft-ietf-tcpm-ecnsyn-07.t… Sally Floyd
- Re: [tcpm] I-D Action:draft-ietf-tcpm-ecnsyn-07.t… Lars Eggert
- [tcpm] Fwd: I-D Action:draft-ietf-tcpm-ecnsyn-07.… Sally Floyd