A new Request for Comments is now available in online RFC libraries.
RFC 9957
Title: The DOCSIS Queue Protection Algorithm
to Preserve Low Latency
Author: B. Briscoe, Ed.,
G. White
Status: Informational
Stream: Independent
Date: May 2026
Mailbox: [email protected],
[email protected]
Pages: 28
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-briscoe-docsis-q-protection-07.txt
URL: https://www.rfc-editor.org/info/rfc9957
DOI: 10.17487/RFC9957
This Informational RFC explains the specification of the queue
protection algorithm introduced into Data-Over-Cable Service
Interface Specification (DOCSIS) technology at 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. This document is designed
for four audiences: a) congestion control designers who need to
understand how to keep on the "good" side of the algorithm; b)
implementers of the algorithm who want to understand it in more
depth; c) designers of algorithms with similar goals, perhaps for
non-DOCSIS scenarios; and d) researchers interested in evaluating the
algorithm.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected]. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
_______________________________________________
IETF-Announce mailing list -- [email protected]
To unsubscribe send an email to [email protected]
