[Last-Call] Opsdir last call review of draft-ietf-tsvwg-aqm-dualq-coupled-24
Sheng Jiang via Datatracker <noreply@ietf.org> Fri, 26 August 2022 10:03 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: last-call@ietf.org
Delivered-To: last-call@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CFA1C14F735; Fri, 26 Aug 2022 03:03:18 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Sheng Jiang via Datatracker <noreply@ietf.org>
To: ops-dir@ietf.org
Cc: draft-ietf-tsvwg-aqm-dualq-coupled.all@ietf.org, last-call@ietf.org, tsvwg@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 8.14.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <166150819817.15288.14179198336101724610@ietfa.amsl.com>
Reply-To: Sheng Jiang <shengjiang@gmail.com>
Date: Fri, 26 Aug 2022 03:03:18 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/hHuqOBST8O9q-iGs2yuU9zVRxHs>
Subject: [Last-Call] Opsdir last call review of draft-ietf-tsvwg-aqm-dualq-coupled-24
X-BeenThere: last-call@ietf.org
X-Mailman-Version: 2.1.39
List-Id: IETF Last Calls <last-call.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/last-call>, <mailto:last-call-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/last-call/>
List-Post: <mailto:last-call@ietf.org>
List-Help: <mailto:last-call-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/last-call>, <mailto:last-call-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2022 10:03:18 -0000
Reviewer: Sheng Jiang Review result: Has Issues Reviewer: Sheng Jiang Review result: Has Issues Document: draft-ietf-tsvwg-aqm-dualq-coupled-24 Review Date: 2022-08-26 I have reviewed this document as part of the Operational directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments were written with the intent of improving the operational aspects of the IETF drafts. Comments that are not addressed in last call may be included in AD reviews during the IESG review. Document editors and WG chairs should treat these comments just like any other last call comments. This experimental document defines a framework for coupling the AQM algorithms in two queues intended for flows with different responses to congestion. It is the network part of the L4S architecture that enables both very low queuing latency and high throughput at the same time. I have concerns on the operational description in this document. This document claims its mechanims can be deployed in the current network. But it lacks the description on how and why it can works back-compatibly. I heard there were intensive debate regarding to the usage of ECT (I did not participate it myself), but the document has not introduced the reason or background why it is allowed to use ECT from the urgement. Another minor comments, there is another reason that can cause the result mentioned in 4.2: if irresponsible terminals labels classic ect(0) flows into l4s ect(1), it would overload l4s queue. Regards, Sheng
- [Last-Call] Opsdir last call review of draft-ietf… Sheng Jiang via Datatracker
- Re: [Last-Call] [tsvwg] Opsdir last call review o… Bob Briscoe
- Re: [Last-Call] [tsvwg] Opsdir last call review o… Sheng Jiang
- Re: [Last-Call] [tsvwg] Opsdir last call review o… Bob Briscoe