Re: [tsvwg] New Version Notification for draft-baker-tsvwg-aqm-recommendation-00.txt
gorry@erg.abdn.ac.uk Wed, 13 March 2013 18:28 UTC
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E2A721F8E71; Wed, 13 Mar 2013 11:28:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.421
X-Spam-Level:
X-Spam-Status: No, score=-106.421 tagged_above=-999 required=5 tests=[AWL=-0.049, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YD6orn3eovTW; Wed, 13 Mar 2013 11:28:19 -0700 (PDT)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id F3B6C21F8DD4; Wed, 13 Mar 2013 11:28:15 -0700 (PDT)
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 F265C2B4400; Wed, 13 Mar 2013 18:28:12 +0000 (GMT)
Received: from 2001:df8:0:16:5ab0:35ff:fe7b:b828 (SquirrelMail authenticated user gorry) by www.erg.abdn.ac.uk with HTTP; Wed, 13 Mar 2013 18:28:13 -0000
Message-ID: <b6d8c6a56b1e4f066019c81da8a202a0.squirrel@www.erg.abdn.ac.uk>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B7D045F@xmb-rcd-x09.cisco.com>
References: <20130313164833.27324.89314.idtracker@ietfa.amsl.com> <8C48B86A895913448548E6D15DA7553B7D045F@xmb-rcd-x09.cisco.com>
Date: Wed, 13 Mar 2013 18:28:13 -0000
From: gorry@erg.abdn.ac.uk
To: "Fred Baker (fred)" <fred@cisco.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: "tsv-area@ietf.org" <tsv-area@ietf.org>, tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] New Version Notification for draft-baker-tsvwg-aqm-recommendation-00.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Mar 2013 18:28:20 -0000
Fred, Comments below: Section 2, pt 2 "Deployed AQM SHOULD use ECN as well as loss, and set thresholds to mark traffic earlier than it is lost." - This is not clear, I agree SHOULD use ECN for ECT traffic, of course. - I'm not sure about threshold question that sets ECN drop before ECN loss - I like the idea for various reasons (I'm not expanding that here), but this isn't what I understand as the current recommended TCP ECN reaction - which reacts to CE in the same way as loss? We need to be careful that we don't suggest not using ECN can gain advantage. Section 2 pt 3 - Again I agree, but not sure we can say this as a BCP requirement? I think we should think about how best to present this. Section 2 pt 4 - Agree and we also now have tunnel technologies considering ECN support, so also these? Section 2 pt 5 - Nice, but not not possible - so TCP without ECN *IS* going to cause loss and delay if it shares the same congested queue. The idea of defining guidance on what to expect here is also good, and maybe a significant step to getting a better understanding. I note that RFC 2309 does recommend RED but importantly it did not motivate it in the way that now makes AQM an imperative. It also largely pre-dated ECN and certainly the experience in ECN implementation. Gorry > Folks. I posted the email I sent yesterday as a draft, for discussion. I > welcome comments, and if substantive comments are made, suggested text. > > > On Mar 13, 2013, at 12:48 PM, <internet-drafts@ietf.org> > wrote: > >> >> A new version of I-D, draft-baker-tsvwg-aqm-recommendation-00.txt >> has been successfully submitted by Fred Baker and posted to the >> IETF repository. >> >> Filename: draft-baker-tsvwg-aqm-recommendation >> Revision: 00 >> Title: IETF Recommendations Regarding Active Queue Management >> Creation date: 2013-03-13 >> Group: Individual Submission >> Number of pages: 7 >> URL: >> http://www.ietf.org/internet-drafts/draft-baker-tsvwg-aqm-recommendation-00.txt >> Status: >> http://datatracker.ietf.org/doc/draft-baker-tsvwg-aqm-recommendation >> Htmlized: >> http://tools.ietf.org/html/draft-baker-tsvwg-aqm-recommendation-00 >> >> >> Abstract: >> Fifteen years after the IAB issued its recommendations regarding >> congestion control in RFC 2309, a major issue in the community is the >> issue that RFC addresses: Buffer bloat. It may be time to update the >> recommendation. >> >> >> >> >> The IETF Secretariat >> >
- Re: [tsvwg] New Version Notification for draft-ba… Fred Baker (fred)
- Re: [tsvwg] New Version Notification for draft-ba… Mikael Abrahamsson
- Re: [tsvwg] New Version Notification for draft-ba… gorry
- Re: [tsvwg] New Version Notification for draft-ba… Fred Baker (fred)
- Re: [tsvwg] New Version Notification for draft-ba… Fred Baker (fred)
- Re: [tsvwg] New Version Notification for draft-ba… Mikael Abrahamsson
- Re: [tsvwg] New Version Notification for draft-ba… Andrew McGregor
- Re: [tsvwg] New Version Notification for draft-ba… Mikael Abrahamsson
- Re: [tsvwg] New Version Notification for draft-ba… Andrew McGregor