Operational Guidance on Coexistence with Classic ECN during L4S Deployment
draft-ietf-tsvwg-l4sops-06
Document | Type |
Expired Internet-Draft
(tsvwg WG)
Expired & archived
|
|
---|---|---|---|
Author | Greg White | ||
Last updated | 2024-09-18 (Latest revision 2024-03-17) | ||
Replaces | draft-white-tsvwg-l4sops | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Associated WG milestone |
|
||
Document shepherd | Wesley Eddy | ||
IESG | IESG state | Expired | |
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | wesley.m.eddy@gmail.com |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document is intended to provide guidance in order to ensure successful deployment of Low Latency Low Loss Scalable throughput (L4S) in the Internet. Other L4S documents provide guidance for running an L4S experiment, but this document is focused solely on potential interactions between L4S flows and flows using the original ('Classic') ECN over a Classic ECN bottleneck link. The document discusses the potential outcomes of these interactions, describes mechanisms to detect the presence of Classic ECN bottlenecks, and identifies opportunities to prevent and/or detect and resolve fairness problems in such networks. This guidance is aimed at operators of end-systems, operators of networks, and researchers.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)