Interactions between Low Latency, Low Loss, Scalable Throughput (L4S) and Differentiated Services
draft-briscoe-tsvwg-l4s-diffserv-02

Document Type Expired Internet-Draft (individual)
Last updated 2019-05-08 (latest revision 2018-11-04)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-briscoe-tsvwg-l4s-diffserv-02.txt

Abstract

L4S and Diffserv offer somewhat overlapping services (low latency and low loss), but bandwidth allocation is out of scope for L4S. Therefore there is scope for the two approaches to complement each other, but also to conflict. This informational document explains how the two approaches interact, how they can be arranged to complement each other and in which cases one can stand alone without needing the other.

Authors

Bob Briscoe (ietf@bobbriscoe.net)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)