IETF Logo Mail Archive

Re: [tsvwg] WGLC for draft-ietf-tsvwg-byte-pkt-congest-10 - to conclude 28th June 2013

"Eggert, Lars" <lars@netapp.com> Thu, 20 June 2013 08:19 UTC

Return-Path: <lars@netapp.com>
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 521D911E8110 for <tsvwg@ietfa.amsl.com>; Thu, 20 Jun 2013 01:19:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.007
X-Spam-Level:
X-Spam-Status: No, score=-9.007 tagged_above=-999 required=5 tests=[AWL=1.592, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 s0bi5UzQTnMw for <tsvwg@ietfa.amsl.com>; Thu, 20 Jun 2013 01:19:28 -0700 (PDT)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id 2FC5411E810B for <tsvwg@ietf.org>; Thu, 20 Jun 2013 01:19:21 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,903,1363158000"; d="scan'208";a="66719630"
Received: from vmwexceht05-prd.hq.netapp.com ([10.106.77.35]) by mx12-out.netapp.com with ESMTP; 20 Jun 2013 01:19:21 -0700
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.35]) by vmwexceht05-prd.hq.netapp.com ([10.106.77.35]) with mapi id 14.03.0123.003; Thu, 20 Jun 2013 01:19:20 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: "Fred Baker (fred)" <fred@cisco.com>
Thread-Topic: [tsvwg] WGLC for draft-ietf-tsvwg-byte-pkt-congest-10 - to conclude 28th June 2013
Thread-Index: AQHObRd2EzOX5OhLOkW4d0bm20Ax8Zk+uOgA
Date: Thu, 20 Jun 2013 08:19:19 +0000
Message-ID: <E52195E7-341E-4B45-8D3A-F2173B164AC4@netapp.com>
References: <51C1CD63.7070106@erg.abdn.ac.uk> <20130619160823.GD44982@verdi> <8C48B86A895913448548E6D15DA7553B91EB9C@xmb-rcd-x09.cisco.com>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B91EB9C@xmb-rcd-x09.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.106.53.51]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2220148519BAFE45BF4CAE5BADB636B9@hq.netapp.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, tsvwg WG <tsvwg@ietf.org>
Subject: Re: [tsvwg] WGLC for draft-ietf-tsvwg-byte-pkt-congest-10 - to conclude 28th June 2013
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: Thu, 20 Jun 2013 08:19:33 -0000

Hi,

On Jun 19, 2013, at 20:04, Fred Baker (fred) <fred@cisco.com> wrote:
> I would agree that it makes little sense to almost-simultaneously update and obsolete RFC 2309.

I think you're vastly optimistic in terms of seeing an RFC out of the AQM WG-to-be :-)

> If we are going to have a working group whose job is to rewrite the AQM recommendation, which is what Wes said to TSVAREA that he wanted to do (and hence my draft) at IETF 86, it would be best to collaborate.

I think we should ship draft-ietf-tsvwg-byte-pkt-congest now, and figure out what to do with it and RFC2309 when the AQM is underway.

Lars

v2.23.0 | Report a Bug | By Email