Operational Guidance for Deployment of L4S in the Internet
draft-white-tsvwg-l4sops-02
| Document | Type |
Replaced Internet-Draft
(tsvwg WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Greg White | ||
| Last updated | 2023-03-01 (Latest revision 2021-02-22) | ||
| Replaced by | draft-ietf-tsvwg-l4sops | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Informational | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-tsvwg-l4sops | |
| Consensus boilerplate | Unknown | ||
| 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
This document is intended to provide additional guidance to operators of end-systems, operators of networks, and researchers beyond that provided in [I-D.ietf-tsvwg-ecn-l4s-id] and [I-D.ietf-tsvwg-aqm-dualq-coupled] in order to ensure successful deployment of L4S [I-D.ietf-tsvwg-l4s-arch] in the Internet. The focus of this document is on potential interactions between L4S flows and Classic ECN ([RFC3168]) flows in Classic ECN bottleneck links. The document discusses the potential outcomes of these interactions, describes mechanisms to detect the presence of [RFC3168] bottlenecks, and identifies opportunites to prevent and/or detect and resolve fairness problems in such networks.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)