From tsvwg-admin@ietf.org Sat Sep 9 15:34:21 2000 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA22758 for ; Sat, 9 Sep 2000 15:34:21 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA17538; Sat, 9 Sep 2000 15:31:31 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA17509 for ; Sat, 9 Sep 2000 15:31:30 -0400 (EDT) Received: from mailgate3.austin.ibm.com (mg03.austin.ibm.com [192.35.232.20]) by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA22727 for ; Sat, 9 Sep 2000 15:31:27 -0400 (EDT) Received: from netmail1.austin.ibm.com (netmail1.austin.ibm.com [9.53.250.96]) by mailgate3.austin.ibm.com (AIX4.3/8.9.3/8.9.3) with ESMTP id OAA45012 for ; Sat, 9 Sep 2000 14:10:41 -0500 Received: from austin.ibm.com (ambika.austin.ibm.com [9.53.150.77]) by netmail1.austin.ibm.com (8.8.5/8.8.5) with ESMTP id OAA05114 for ; Sat, 9 Sep 2000 14:31:28 -0500 Message-ID: <39BA900F.E574B12@austin.ibm.com> Date: Sat, 09 Sep 2000 14:31:27 -0500 From: venkat venkatsubra Organization: IBM X-Mailer: Mozilla 4.61 [en] (X11; U; AIX 4.3) X-Accept-Language: en MIME-Version: 1.0 To: tsvwg@ietf.org Content-Type: multipart/mixed; boundary="------------94C1A45C168C26911BEE6AFC" Subject: [Tsvwg] Limited Transmit algorithm Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Transport Area Working Group X-BeenThere: tsvwg@ietf.org This is a multi-part message in MIME format. --------------94C1A45C168C26911BEE6AFC Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit --------------94C1A45C168C26911BEE6AFC Content-Type: text/plain; charset=us-ascii; name="xx" Content-Disposition: inline; filename="xx" Content-Transfer-Encoding: 7bit Hello Mark, Hari, Sally, In the draft in the algorithm section (section 2) it says: * The amount of outstanding data would remain less than the congestion window plus 2 segments. In other words, the sender can only send two segments beyond the congestion window (cwnd). It should remain less than cwnd+2 or less than or equal to ? The next line seems to indicate less than or equal to. Thanks! Venkat --------------94C1A45C168C26911BEE6AFC-- _______________________________________________ tsvwg mailing list tsvwg@ietf.org http://www1.ietf.org/mailman/listinfo/tsvwg From tsvwg-admin@ietf.org Mon Sep 11 13:23:35 2000 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA06811 for ; Mon, 11 Sep 2000 13:23:35 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA18649; Mon, 11 Sep 2000 13:16:44 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA18620 for ; Mon, 11 Sep 2000 13:16:42 -0400 (EDT) Received: from lombok-fi.lerc.nasa.gov (lombok-fi.lerc.nasa.gov [139.88.112.33]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA06706 for ; Mon, 11 Sep 2000 13:16:41 -0400 (EDT) Received: from guns (guns.lerc.nasa.gov [139.88.87.35]) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) with ESMTP id NAA12469; Mon, 11 Sep 2000 13:16:25 -0400 (EDT) Message-Id: <200009111716.NAA12469@lombok-fi.lerc.nasa.gov> To: venkat venkatsubra From: Mark Allman Reply-To: mallman@grc.nasa.gov cc: tsvwg@ietf.org Subject: Re: [Tsvwg] Limited Transmit algorithm Organization: Late Night Hackers, NASA Glenn, Cleveland, Ohio Song-of-the-Day: 57 Channels Date: Mon, 11 Sep 2000 13:16:21 -0400 Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Transport Area Working Group X-BeenThere: tsvwg@ietf.org > In the draft in the algorithm section (section 2) it says: > > * The amount of outstanding data would remain less than the > congestion window plus 2 segments. In other words, the sender > can only send two segments beyond the congestion window (cwnd). > > It should remain less than cwnd+2 or less than or equal to ? > The next line seems to indicate less than or equal to. Yes, I think <=. Thanks! allman _______________________________________________ tsvwg mailing list tsvwg@ietf.org http://www1.ietf.org/mailman/listinfo/tsvwg From tsvwg-admin@ietf.org Wed Sep 13 13:10:52 2000 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA13010 for ; Wed, 13 Sep 2000 13:10:52 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA26179; Wed, 13 Sep 2000 13:07:49 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA26150 for ; Wed, 13 Sep 2000 13:07:47 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12864; Wed, 13 Sep 2000 13:07:48 -0400 (EDT) Message-Id: <200009131707.NAA12864@ietf.org> To: IETF-Announce: ; Cc: tsvwg@ietf.org From: The IESG Reply-to: iesg@ietf.org Date: Wed, 13 Sep 2000 13:07:48 -0400 Subject: [Tsvwg] Last Call: Enhancing TCP's Loss Recovery Using Limited Transmit to Proposed Standard Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Transport Area Working Group X-BeenThere: tsvwg@ietf.org The IESG has received a request from the Transport Area Working Group Working Group to consider Enhancing TCP's Loss Recovery Using Limited Transmit as a Proposed Standard. 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@ietf.org or ietf@ietf.org mailing lists by September 27, 2000. Files can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-limited-xmit-00.txt _______________________________________________ tsvwg mailing list tsvwg@ietf.org http://www1.ietf.org/mailman/listinfo/tsvwg From tsvwg-admin@ietf.org Thu Sep 14 11:20:40 2000 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA17027 for ; Thu, 14 Sep 2000 11:20:39 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA14268; Thu, 14 Sep 2000 11:11:19 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA14225 for ; Thu, 14 Sep 2000 11:11:13 -0400 (EDT) Received: from mail.kpnqwest.ch (mail.eunet.ch [146.228.10.7]) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA16063 for ; Thu, 14 Sep 2000 11:11:10 -0400 (EDT) From: dfvfpod@smtp.clover.com.hk Received: from oettinger.davidoff.ch ([195.49.110.243]) by mail.kpnqwest.ch (8.9.3/1.34) via ESMTP id PAA08892 for ; Thu, 14 Sep 2000 15:10:39 GMT env-from (dfvfpod@smtp.clover.com.hk) Received: from mail.mindspring.com by oettinger.davidoff.ch via SMTP id smtp\t9ef3l80.in; 14 Sep 2000 15:03:00 +0200 To: Date: Thu, 14 Sep 2000 05:28:42 Message-Id: <102.333812.433093@mail.mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Tsvwg] (no subject) Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Transport Area Working Group X-BeenThere: tsvwg@ietf.org Content-Transfer-Encoding: 7bit GET YOUR OWN 100 MEG WEBSITE FOR ONLY $11.95 PER MONTH TODAY! STOP PAYING $19.95 or more TODAY for your web site, WHEN YOU CAN GET ONE FOR ONLY $11.95 PER MONTH! DO YOU ALREADY HAVE A WEBSITE? ALL YOU HAVE TO DO IS TRANSFER THE DOMAIN TO OUR SERVERS AND UPLOAD YOUR DATA AND YOU ARE READY TO GO! YOUR NEW WEB SPACE CAN BE CREATED INSTANTLY WITH JUST A SIMPLE PHONE CALL TO OUR OFFICE. YOU CAN CHANGE THE DESIGN OF YOUR SITE AS MUCH AS YOU WANT with no extra charge! UNLIMITED TRAFFIC -- no extra charge! FRONT PAGE EXTENSIONS are FULLY SUPPORTED. A SET UP FEE OF $40.00 APPLIES for FIRST TIME CUSTOMERS. ALL FEES PREPAID IN ADVANCE FOR THE YEAR PLUS A $40.00 SET UP CHARGE. FOR DETAILS CALL 1 888 248 0765 Webhosting International _______________________________________________ tsvwg mailing list tsvwg@ietf.org http://www1.ietf.org/mailman/listinfo/tsvwg From tsvwg-admin@ietf.org Mon Sep 18 06:53:33 2000 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with SMTP id GAB01760 for ; Mon, 18 Sep 2000 06:53:32 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA19115; Mon, 18 Sep 2000 06:43:39 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA19084 for ; Mon, 18 Sep 2000 06:43:37 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA01489; Mon, 18 Sep 2000 06:43:36 -0400 (EDT) Message-Id: <200009181043.GAA01489@ietf.org> To: IETF-Announce: ; Cc: RFC Editor , IANA Cc: Internet Architecture Board Cc: tsvwg@ietf.org From: The IESG Date: Mon, 18 Sep 2000 06:43:36 -0400 Subject: [Tsvwg] Protocol Action: Computing TCP's Retransmission Timer to Proposed Standard Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Transport Area Working Group X-BeenThere: tsvwg@ietf.org The IESG has approved the Internet-Draft 'Computing TCP's Retransmission Timer' as a Proposed Standard. This document is the product of the Transport Area Working Group Working Group. The IESG contact persons are Allison Mankin and Scott Bradner. Technical Summary The Transmission Control Protocol (TCP) [RFC 793] uses a retransmission timer to ensure data delivery in the absence of any feedback from the remote data receiver. The duration of this timer is referred to as RTO (retransmission timeout). RFC 1122 specifies that the RTO should be calculated as described in Van Jacobson's 1988 Computer Communication Review paper on "Congestion Avoidance and Control" This document codifies the algorithm for setting the RTO. In addition, this document expands on the discussion in section 4.2.3.1 of RFC 1122 and upgrades the requirement of supporting the algorithm from a SHOULD to a MUST. RFC 2581 outlines the algorithm TCP uses to begin sending after the RTO expires and a retransmission is sent. This document does not alter the behavior outlined in RFC 2581 Thus this document defines the standard algorithm TCP senders are required to use to compute and manage their retransmission timer. Working Group Summary The proposed MIB was supported by the working group and no issues came up during IETF last-call. Protocol Quality This document was reviewed by Scott Bradner for the IESG. Note to RFC Editor: Please replace the first line of section 5 with the following An implementation MUST manage the retransmission timer(s) in such a way that a segment is never retransmitted too early, i.e. less than one RTO after the previous transmission of that segment. The following is the RECOMMENDED algorithm for managing the retransmission timer: _______________________________________________ tsvwg mailing list tsvwg@ietf.org http://www1.ietf.org/mailman/listinfo/tsvwg From tsvwg-admin@ietf.org Sat Sep 23 10:09:32 2000 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA21738 for ; Sat, 23 Sep 2000 10:09:32 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA27033; Sat, 23 Sep 2000 09:56:31 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA27005 for ; Sat, 23 Sep 2000 09:56:29 -0400 (EDT) Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110]) by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA21678 for ; Sat, 23 Sep 2000 09:56:26 -0400 (EDT) Received: from eed.ericsson.se (mailhost.eed.ericsson.se [164.48.133.33]) by penguin.wise.edt.ericsson.se (8.11.0/8.10.1/WIREfire-1.3) with ESMTP id e8NDuDZ12672 for ; Sat, 23 Sep 2000 15:56:13 +0200 (MEST) Received: from E00D05905E94A.eed.ericsson.se (rmt160174.am.ericsson.se [138.85.160.174]) by eed.ericsson.se (8.8.8+Sun/1.1.mit) with ESMTP id PAA09527 for ; Sat, 23 Sep 2000 15:56:07 +0200 (MET DST) Message-Id: <4.3.2.7.0.20000923152719.00d3aef0@chapelle.ericsson.se> X-Sender: eedrel@chapelle.ericsson.se X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sat, 23 Sep 2000 15:45:41 +0200 To: tsvwg@ietf.org From: Reiner Ludwig Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [Tsvwg] TCP Burst Limit Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Transport Area Working Group X-BeenThere: tsvwg@ietf.org I would like to get people's view on the following idea to see whether it is worth coming forward with an appropriate I-D. I.e., I would like to get a feeling for how controversial this may become ... The general idea is not new but had been discussed before, e.g., by Sally Floyd and Joe Touch (e.g., Burst-Or-Lose - BOL was one proposal). Problem: There are number of situation where TCP will send a burst: stretch-ACKs, large 'send' from the application shortly after the connection went idle (even with congestion window validation), sender reaches advertized window during fast recovery and new ACK arrives, and probably more ... Idea: Limit the number of segments that each ACK, DUPACK, and 'send' (from the app. after idle) may clock out to MAXBURST wich is suggested to be 4. Any comments? ///Reiner _______________________________________________ tsvwg mailing list tsvwg@ietf.org http://www1.ietf.org/mailman/listinfo/tsvwg