Difference between revisions of "L4S-support"

From Nsnam
Jump to: navigation, search
(Created page with "{{TOC}} This is a summary page for links to various code related to using ns-3 to study L4S. [https://datatracker.ietf.org/doc/draft-ietf-tsvwg-l4s-arch/ L4S] is a proposed...")
 
Line 7: Line 7:
 
L4S includes the following protocol components:
 
L4S includes the following protocol components:
  
1) new ECN support in AQMs; in particular, the Dual Queue.  The current [https://tools.ietf.org/html/rfc3168 RFC 3168] ECN delivers a Congestion Experience (CE) signal that has the same semantics as a packet drop.  It can be thought of as a queue 'overload' signal, and endpoints are expected to react similarly to the detection of a packet drop.  The new ECN support is intended to deliver more [https://tools.ietf.org/html/draft-ietf-tcpm-accurate-ecn-13 accurate ECN feedback] (more granularity).  The feedback is based on what is used for DCTCP (the [https://man7.org/linux/man-pages/man8/tc-fq_codel.8.html 'ce_threshold'] in Linux codel implementation can be used to generate this feedback).
+
1) '''new ECN support in AQMs'''; in particular, the Dual Queue.  The current [https://tools.ietf.org/html/rfc3168 RFC 3168] ECN delivers a Congestion Experience (CE) signal that has the same semantics as a packet drop.  It can be thought of as a queue 'overload' signal, and endpoints are expected to react similarly to the detection of a packet drop.  The new ECN support is intended to deliver more [https://tools.ietf.org/html/draft-ietf-tcpm-accurate-ecn-13 accurate ECN feedback] (more granularity).  The feedback is based on what is used for DCTCP (the [https://man7.org/linux/man-pages/man8/tc-fq_codel.8.html 'ce_threshold'] in Linux codel implementation can be used to generate this feedback).
  
2) a new ECN codepoint to differentiate L4S-aware traffic from flows using RFC 3168 ECN semantics.  The IETF tsvwg decided to use the ECT(1) codepoint as an input signal for this purpose.
+
2) a '''new ECN codepoint''' to differentiate L4S-aware traffic from flows using RFC 3168 ECN semantics.  The IETF tsvwg decided to use the ECT(1) codepoint as an input signal for this purpose.
  
3) TCP Prague (a prototype congestion controller using the new feedback); the current version is based originally on [https://tools.ietf.org/html/rfc8257 DCTCP].
+
3) '''TCP Prague''' (a prototype congestion controller using the new feedback); the current version is based originally on [https://tools.ietf.org/html/rfc8257 DCTCP].
 +
 
 +
== Support within current and future ns-3 releases ==
 +
 
 +
ns-3.32 (latest ns-3 release), contains support for the following:
 +
 
 +
== External modules ==

Revision as of 21:47, 19 November 2020

Main Page - Current Development - Developer FAQ - Tools - Related Projects - Project Ideas - Summer Projects

Installation - Troubleshooting - User FAQ - HOWTOs - Samples - Models - Education - Contributed Code - Papers

This is a summary page for links to various code related to using ns-3 to study L4S. L4S is a proposed framework for deploying low-latency, low-loss, scalable congestion control in the Internet.

This page was last updated on November 19, 2020, in support of the IETF 109 ICCRG meeting.

L4S includes the following protocol components:

1) new ECN support in AQMs; in particular, the Dual Queue. The current RFC 3168 ECN delivers a Congestion Experience (CE) signal that has the same semantics as a packet drop. It can be thought of as a queue 'overload' signal, and endpoints are expected to react similarly to the detection of a packet drop. The new ECN support is intended to deliver more accurate ECN feedback (more granularity). The feedback is based on what is used for DCTCP (the 'ce_threshold' in Linux codel implementation can be used to generate this feedback).

2) a new ECN codepoint to differentiate L4S-aware traffic from flows using RFC 3168 ECN semantics. The IETF tsvwg decided to use the ECT(1) codepoint as an input signal for this purpose.

3) TCP Prague (a prototype congestion controller using the new feedback); the current version is based originally on DCTCP.

Support within current and future ns-3 releases

ns-3.32 (latest ns-3 release), contains support for the following:

External modules