L4S-support - Revision history

Tomh: /* Support within current and future ns-3 releases */

2020-11-19T22:49:26Z

Support within current and future ns-3 releases

← Older revision		Revision as of 22:49, 19 November 2020
Line 22:		Line 22:

	* ns-3.34 is planned for end of January, and we hope to include these components:		* ns-3.34 is planned for end of January, and we hope to include these components:
	** TCP Prague model from 2020 GSoC program		** [https://gitlab.com/nsnam/ns-3-dev/-/merge_requests/373 TCP Prague] model from 2020 GSoC program
	** L4S support for FQ/Cobalt and FQ/PIE		** L4S support for [https://gitlab.com/nsnam/ns-3-dev/-/merge_requests/461 FQ/Cobalt and FQ/PIE]
	** Dual queue with L4S support		** [https://gitlab.com/tomhenderson/ns-3-dev/tree/dual-queue Dual queue] with L4S support
			** [https://github.com/Vivek-anand-jain/ns-3-dev-git/tree/ecnpp AccECN and ECN++]

	== External modules ==		== External modules ==

Tomh: /* Support within current and future ns-3 releases */

2020-11-19T22:46:46Z

Support within current and future ns-3 releases

← Older revision		Revision as of 22:46, 19 November 2020
Line 15:		Line 15:
	== Support within current and future ns-3 releases ==		== Support within current and future ns-3 releases ==

	ns-3.32 (latest ns-3 release), contains support for the following:		Some L4S-related code is in the ns-3 mainline, and some in external modules. Some is posted for review and will be incorporated into future releases, as currently planned below:

			* [https://www.nsnam.org/releases/ns-3-32/ ns-3.32] (latest ns-3 release), contains support for the following: DCTCP, CoDel with L4S support, FQ/CoDel with L4S support.

			* ns-3.33 is planned for end of November or early December. This release probably will not have additional L4S-related code.

			* ns-3.34 is planned for end of January, and we hope to include these components:
			** TCP Prague model from 2020 GSoC program
			** L4S support for FQ/Cobalt and FQ/PIE
			** Dual queue with L4S support

	== External modules ==		== External modules ==

Tomh: /* External modules */

2020-11-19T22:08:31Z

External modules

← Older revision		Revision as of 22:08, 19 November 2020
Line 18:		Line 18:

	== External modules ==		== External modules ==

			ns-3 has a framework for contributed code (extension modules maintained outside of the mainline). The [https://apps.nsnam.org ns-3 App Store] is a site for some of these modules.

			* [https://apps.nsnam.org/app/docsis-ns3/ DOCSIS models for Low Latency Docsis]

			* [https://gitlab.com/tomhend/modules/l4s-evaluation L4S evaluation framework] comparable to [https://github.com/heistp/sce-l4s-bakeoff Pete Heist's testbed experiments]

			* [https://apps.nsnam.org/app/quic/ QUIC] (does not have L4S, but is available for someone to try to add...)

Tomh at 21:47, 19 November 2020

2020-11-19T21:47:53Z

← Older revision		Revision as of 21:47, 19 November 2020
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 ==

Tomh: 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..."

2020-11-19T21:45:36Z

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..."

New page

{{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 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 [https://datatracker.ietf.org/meeting/109/materials/agenda-109-iccrg-01 IETF 109 ICCRG] meeting.

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).

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].