Re: [tcpm] [Fwd: Confirmation for Auto-Post of I-D draft-ietf-tcpm-newcwv]
gorry@erg.abdn.ac.uk Tue, 17 December 2013 08:28 UTC
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D6931AE125 for <tcpm@ietfa.amsl.com>; Tue, 17 Dec 2013 00:28:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.739
X-Spam-Level:
X-Spam-Status: No, score=-4.739 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tNS880_ovbaM for <tcpm@ietfa.amsl.com>; Tue, 17 Dec 2013 00:28:37 -0800 (PST)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 746701AE134 for <tcpm@ietf.org>; Tue, 17 Dec 2013 00:28:34 -0800 (PST)
Received: from www.erg.abdn.ac.uk (blake.erg.abdn.ac.uk [139.133.210.30]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id 9DAC82B432B; Tue, 17 Dec 2013 08:28:32 +0000 (GMT)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by www.erg.abdn.ac.uk with HTTP; Tue, 17 Dec 2013 08:28:32 -0000
Message-ID: <c3b91ff8425bfa6def617736c7b1384d.squirrel@www.erg.abdn.ac.uk>
In-Reply-To: <CAK6E8=fkeCeT1O-=+nQd2kzXQXuBUF1vrMJDLbpoR088nsJ0eA@mail.gmail.com>
References: <8f78ebda09f5e658aa0cd61a38019a88.squirrel@www.erg.abdn.ac.uk> <CAK6E8=fkeCeT1O-=+nQd2kzXQXuBUF1vrMJDLbpoR088nsJ0eA@mail.gmail.com>
Date: Tue, 17 Dec 2013 08:28:32 -0000
From: gorry@erg.abdn.ac.uk
To: Yuchung Cheng <ycheng@google.com>
User-Agent: SquirrelMail/1.4.22
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Cc: "tcpm@ietf.org Extensions" <tcpm@ietf.org>
Subject: Re: [tcpm] [Fwd: Confirmation for Auto-Post of I-D draft-ietf-tcpm-newcwv]
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Tue, 17 Dec 2013 08:28:39 -0000
> On Mon, Dec 16, 2013 at 1:28 PM, <gorry@erg.abdn.ac.uk> wrote: >> >> We've submitted a revised ID for new-cwv. >> >> There are 2 main updates: >> >> - The draft now firmly recommends the use of pacing. We will provide >> performance data on pacing for the next IETF. >> >> - The draft has a small amendment to the algorithm to ensure that the >> NVP >> does not inhibit cwnd growth when a sender fully consumes the cwnd. >> There >> was previously a corner case in the measurement of pipeACK when a flow >> started or resumed that could result making newCWV more conservative >> than >> standard TCP (e.g. for a bulk flow). We think the correction is within >> the >> original spirit of new CWV. >> >> We'd welcome feedback on these or any other aspects. > > I appreciate the new section on burst mitigation but why standard track? > The previous discussions on STD track centres on whether we would include require a burst mitigation section, so this is now a good question. > The change has pro-found impact on congestion control as it changes > how cwnd increases per ACK and after idle. There are a lot to > experiment before we know this works well in real networks. > Are you referring to the new ack-mitigation section - requiring pacing after idle? Gorry >> >> Best wishes, >> >> the new CWV authors >> >> -------------------------------------------------------------------------- >> >> >> Hi, >> >> The IETF datatracker draft submission service has received your draft >> draft-ietf-tcpm-newcwv-04, and requires a >> confirmation step in order to be able to complete the posting of >> the draft. >> >> Please follow this link to the page where you can confirm the posting: >> Confirmation URL: >> http://datatracker.ietf.org/submit/status/56402/confirm/c575579feb585d58d82af80a319918630e8d0529/ >> >> >> Best regards, >> >> The IETF Secretariat >> through the draft submission service >> >> >> >> _______________________________________________ >> tcpm mailing list >> tcpm@ietf.org >> https://www.ietf.org/mailman/listinfo/tcpm >
- Re: [tcpm] [Fwd: Confirmation for Auto-Post of I-… gorry
- Re: [tcpm] [Fwd: Confirmation for Auto-Post of I-… Yuchung Cheng
- [tcpm] [Fwd: Confirmation for Auto-Post of I-D dr… gorry
- Re: [tcpm] [Fwd: Confirmation for Auto-Post of I-… Yuchung Cheng
- Re: [tcpm] [Fwd: Confirmation for Auto-Post of I-… Gorry Fairhurst
- Re: [tcpm] [Fwd: Confirmation for Auto-Post of I-… Yuchung Cheng
- Re: [tcpm] [Fwd: Confirmation for Auto-Post of I-… Scharf, Michael (Michael)