[tsvwg] New rev draft-briscoe-docsis-q-protection-01 (relevant to L4S)
Bob Briscoe <ietf@bobbriscoe.net> Fri, 17 December 2021 23:54 UTC
Return-Path: <ietf@bobbriscoe.net>
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 C29CE3A0CB1; Fri, 17 Dec 2021 15:54:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=bobbriscoe.net
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 zo_x7DePwhWU; Fri, 17 Dec 2021 15:54:10 -0800 (PST)
Received: from mail-ssdrsserver2.hostinginterface.eu (mail-ssdrsserver2.hostinginterface.eu [185.185.85.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 81C4F3A0CB3; Fri, 17 Dec 2021 15:54:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bobbriscoe.net; s=default; h=Content-Type:In-Reply-To:MIME-Version:Date: Message-ID:From:Cc:To:References:Subject:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=EeFg2dNEKoZRTj3nf2qiFNSbmEa/VaNc47UvcR1HQWs=; b=D2TZlFh1ZzMDyi/YFdchq8Atp0 2X7iNPaoHXEurar/Wj3eztWQpdV9TZ4sAc/XR46lN8gDyuZm1ritcnsvKNopnSbIcsfAvJDq0dkN3 DAet+oj2TSINBMrQj+uvTYOFvJBNwBom1SwiiXWzDYwbTs70/5E3FMAhWNW/AD2eLG+hfrEZhqucp VvJ2c+oirVmIRAdL5XmXCzjzHAdPcAuWxZTy4xbgdmVWsMDLNt4i4EkbXO/UU1AQARfuzvwpZMOtF TWcW5hJ+v/dx2NYoyCACZ38zFx2//YshCjZI4rhSVH/SeeU+qE18tf/G2T5bf0AkNvrc9B4A4P6A7 cVDZ/H9g==;
Received: from 67.153.238.178.in-addr.arpa ([178.238.153.67]:52546 helo=[192.168.1.11]) by ssdrsserver2.hostinginterface.eu with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from <ietf@bobbriscoe.net>) id 1myN3D-0003RM-14; Fri, 17 Dec 2021 23:54:08 +0000
References: <163978324595.8615.17531650787837213512@ietfa.amsl.com>
To: tsvwg IETF list <tsvwg@ietf.org>, Gorry Fairhurst <gorry@erg.abdn.ac.uk>, Wesley Eddy <wes@mti-systems.com>, "Black, David" <David.Black@dell.com>
Cc: "tsvwg-chairs@ietf.org" <tsvwg-chairs@ietf.org>
From: Bob Briscoe <ietf@bobbriscoe.net>
X-Forwarded-Message-Id: <163978324595.8615.17531650787837213512@ietfa.amsl.com>
Message-ID: <12f92eee-2ca1-8887-a257-48dec4afec53@bobbriscoe.net>
Date: Fri, 17 Dec 2021 23:54:06 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0
MIME-Version: 1.0
In-Reply-To: <163978324595.8615.17531650787837213512@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------3D179A398F92FC3B46F976B8"
Content-Language: en-GB
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - ssdrsserver2.hostinginterface.eu
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - bobbriscoe.net
X-Get-Message-Sender-Via: ssdrsserver2.hostinginterface.eu: authenticated_id: in@bobbriscoe.net
X-Authenticated-Sender: ssdrsserver2.hostinginterface.eu: in@bobbriscoe.net
X-Source:
X-Source-Args:
X-Source-Dir:
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/d1vkeizAMJ7CUrBtt3B4KfSebDg>
Subject: [tsvwg] New rev draft-briscoe-docsis-q-protection-01 (relevant to L4S)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 17 Dec 2021 23:54:16 -0000
Gorry, Wes, David, tsvwg, Gorry recently asked about the status of the queue protection draft. We've just posted an update - see links below. Once I know the status from the Independent Stream Editor (Adrian Farrel), I'll let you know. Summary of Diffs: * Added intended audience in abstract. * Added explanation for why an I-D is being published repeating what it says in the DOCSIS spec. * Avoiding describing NQB as unresponsive, 'cos it states it has the same responsiveness requirements as any other traffic. * Added defaults for input parameters (not sure how they got omitted before) * Allowed for variable time resolution (reflecting a change in the DOCSIS spec since original publication) * Added logic to handle overflow of queuing score * Added discussion of the best value to set the queue delay threshold CRITICALqL to. * Added discussion of how VPNs are partially allowed for * New section giving rationale for redirecting rather than discarding 'ejected' packets. * Added pointer to wider discussion of latency enforcement in L4S architecture Plus a large amount of clarification throughout, particularly helped by Adrian Farrel's review. Bob -------- Forwarded Message -------- Subject: New Version Notification for draft-briscoe-docsis-q-protection-01.txt Date: Fri, 17 Dec 2021 15:20:45 -0800 From: internet-drafts@ietf.org To: Bob Briscoe <ietf@bobbriscoe.net>, Greg White <G.White@CableLabs.com>, Greg White <g.white@cablelabs.com> A new version of I-D, draft-briscoe-docsis-q-protection-01.txt has been successfully submitted by Bob Briscoe and posted to the IETF repository. Name: draft-briscoe-docsis-q-protection Revision: 01 Title: The DOCSIS(r) Queue Protection Algorithm to Preserve Low Latency Document date: 2021-12-17 Group: Individual Submission Pages: 29 URL: https://www.ietf.org/archive/id/draft-briscoe-docsis-q-protection-01.txt Status: https://datatracker.ietf.org/doc/draft-briscoe-docsis-q-protection/ Html: https://www.ietf.org/archive/id/draft-briscoe-docsis-q-protection-01.html Htmlized: https://datatracker.ietf.org/doc/html/draft-briscoe-docsis-q-protection Diff: https://www.ietf.org/rfcdiff?url2=draft-briscoe-docsis-q-protection-01 Abstract: This informational document explains the specification of the queue protection algorithm used in DOCSIS technology since version 3.1. A shared low latency queue relies on the non-queue-building behaviour of every traffic flow using it. However, some flows might not take such care, either accidentally or maliciously. If a queue is about to exceed a threshold level of delay, the queue protection algorithm can rapidly detect the flows most likely to be responsible. It can then prevent harm to other traffic in the low latency queue by ejecting selected packets (or all packets) of these flows. The document is designed for three types of audience: a) congestion control designers who need to understand how to keep on the 'good' side of the lagorithm; b) implementers of the algorithm who want to understand it in more depth; or c) designers of algorithms with similar goals, perhaps for non-DOCSIS scenarios. The IETF Secretariat
- [tsvwg] New rev draft-briscoe-docsis-q-protection… Bob Briscoe
- Re: [tsvwg] Fwd: New rev draft-briscoe-docsis-q-p… Gorry Fairhurst