Comcast ISP Low Latency Deployment Design Recommendations
draft-livingood-low-latency-deployment-03
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Author | Jason Livingood | ||
| Last updated | 2024-03-31 (Latest revision 2023-09-28) | ||
| RFC stream | Independent Submission | ||
| Formats | |||
| Reviews |
TSVART Early review
(of
-07)
by Mirja Kühlewind
Ready w/nits
|
||
| Stream | ISE state | Response to Review Needed | |
| Consensus boilerplate | Unknown | ||
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The IETF's Transport Area Working Group (TSVWG) has finalized experimental RFCs for Low Latency, Low Loss, Scalable Throughput (L4S) and new Non-Queue-Building (NQB) per hop behavior. These documents do a good job of describing a new architecture and protocol for deploying low latency networking. But as is normal for many such standards, especially those in experimental status, certain deployment design decisions are ultimately left to implementers. This document explores the potential implications of key deployment design decisions and makes recommendations for those decisions that may help drive adoption.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)