Internet-Draft Mobile L4S November 2026
Poreba, et al. Expires 24 May 2027 [Page]
Workgroup:
Transport Area Working Group
Internet-Draft:
draft-sporeba-tsvwg-mobile-l4s-latest
Published:
Intended Status:
Best Current Practice
Expires:
Authors:
S. Poreba
Google LLC
L. Colitti
Google LLC
S. Irlanki
Samsung R&D

Best Practices for L4S Implementation for Mobile Devices

Abstract

This document describes best practices for deployment of Low Latency, Low Loss, and Scalable Throughput (L4S) in mobile devices. It defines the responsibilities of the host operating system and the link-layer (modem and Wi-Fi) subsystems to ensure successful end-to-end low-latency communication.

About This Document

This note is to be removed before publishing as an RFC.

The latest revision of this draft can be found at https://fridek.github.io/draft-sporeba-tsvwg-mobile-l4s/draft-sporeba-tsvwg-mobile-l4s.html. Status information for this document may be found at https://datatracker.ietf.org/doc/draft-sporeba-tsvwg-mobile-l4s/.

Source for this draft and an issue tracker can be found at https://github.com/fridek/draft-sporeba-tsvwg-mobile-l4s.

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on 24 May 2027.

▲

Table of Contents

1. Introduction

L4S (Low Latency, Low Loss, Scalable Throughput) [RFC9330] offers a framework to significantly reduce queueing delay and loss while maintaining consistent throughput. Mobile devices often have to react to quickly changing connectivity conditions and may be subject to variable throughput and connection quality. This can cause large variations in user-perceived latency and greater bufferbloat than in other devices. Deploying L4S in a mobile ecosystem requires co-operation across multiple layers: the network stack, the host operating system (OS), link-layer drivers and firmware (e.g., Wi-Fi and cellular modem), and the network. This document outlines best current practices for the mobile device subsystems to achieve reliable, low-latency performance in the field.

1.1. Conventions and Definitions

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.

This document uses the four codepoint names of the 2-bit IP-ECN field defined in [RFC3168] and Section 1.3 of [RFC9332]: Not-ECT, ECT(0), ECT(1), and CE. In addition, the following collective terms are used:

ECN-capable packet:

An IP packet carrying ECT(0), ECT(1), or CE in the IP-ECN field (that is, any codepoint other than Not-ECT).

L4S identifier (and L4S packet):

An IP-ECN field set to ECT(1) or CE, which link-layer and network nodes use to classify packets as L4S packets without per-flow state (Section 5.1 of [RFC9331], Section 2.3 of [RFC9332]). Note that sending endpoints mark outgoing L4S packets as ECT(1), whereas CE indicates congestion experienced along the path.

NQB packet (and NQB traffic):

Non-queue building IP packet(s) with DSCP set to value 45 as defined by Section 6.1 of [RFC9956].

2. Mobile Device Architecture

Modern mobile devices separate the host operating system from link-layer subsystems such as cellular modems and Wi-Fi (Figure 1). The host operating system runs applications and manages socket APIs, transport protocols, and the IP stack. Link-layer subsystems manage wireless channel acquisition and air-interface retransmissions, and maintain their own internal packet buffers in both directions. Both the host operating system and link-layer subsystems need to correctly implement behaviours on the downlink and uplink paths relevant to L4S to achieve low-latency benefits.

+---------------- Mobile Device ----------------+
|                                               |
| +--------------+   +------------------------+ |
| |   Host OS    |   |  Link-Layer Subsystem  | |
| |              |   |   (Wi-Fi / Cellular)   | |
| | Apps, Socket |   |                        | |
| | APIs & TCP/  |   | +--------------------+ | |   Downlink
| | UDP/IP Stack |<----| Inbound Reordering |<----------------
| |              |   | |       Buffer       | | |
| |              |   | +--------------------+ | |
| |              |   | +--------------------+ | |    Uplink
| |              |---->|   Uplink Queues    |---------------->
| |              |   | |  & Channel Access  | | |
| |              |   | +--------------------+ | |
| +--------------+   +------------------------+ |
+-----------------------------------------------+
Figure 1: Mobile Device Data Path for Downlink and Uplink L4S

5. Security Considerations

L4S introduces potential abuse vectors where applications mark queue-building traffic as low-latency. This risk is amplified if networks without low-latency queues instead prioritise ECT(1)-marked traffic using alternative heuristics (such as bandwidth allocation multipliers) without an active end-to-end congestion-marking feedback loop, incentivising endpoints to mark ECT(1) without implementing L4S congestion control. Regardless of network behaviour, host stacks and applications MUST NOT mark traffic as ECT(1) unless using compliant L4S congestion control. As described in Section 4.2.4, the link-layer subsystem MUST implement queueing and scheduling safeguards to defend against starvation and unbounded queueing delay.

6. IANA Considerations

This document has no IANA actions.

7. References

7.1. Normative References

[RFC2119]
Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/rfc/rfc2119>.
[RFC8174]
Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, , <https://www.rfc-editor.org/rfc/rfc8174>.
[RFC9331]
De Schepper, K. and B. Briscoe, Ed., "The Explicit Congestion Notification (ECN) Protocol for Low Latency, Low Loss, and Scalable Throughput (L4S)", RFC 9331, DOI 10.17487/RFC9331, , <https://www.rfc-editor.org/rfc/rfc9331>.
[RFC9768]
Briscoe, B., Kühlewind, M., and R. Scheffenegger, "More Accurate Explicit Congestion Notification (AccECN) Feedback in TCP", RFC 9768, DOI 10.17487/RFC9768, , <https://www.rfc-editor.org/rfc/rfc9768>.
[RFC9956]
White, G., Fossati, T., and R. Geib, "A Non-Queue-Building Per-Hop Behavior (NQB PHB) for Differentiated Services", RFC 9956, DOI 10.17487/RFC9956, , <https://www.rfc-editor.org/rfc/rfc9956>.

7.2. Informative References

[I-D.ietf-intarea-reordering]
White, G., Johansson, I., Das, D., and C. Box, "Proposal for Updates to Guidance on Packet Reordering", Work in Progress, Internet-Draft, draft-ietf-intarea-reordering-00, , <https://datatracker.ietf.org/doc/html/draft-ietf-intarea-reordering-00>.
[I-D.livingood-low-latency-deployment]
Livingood, J., "ISP Dual Queue Networking Deployment Observations", Work in Progress, Internet-Draft, draft-livingood-low-latency-deployment-16, , <https://datatracker.ietf.org/doc/html/draft-livingood-low-latency-deployment-16>.
[IEEE-802.11-2024]
IEEE, "IEEE Standard for Information Technology--Telecommunications and Information Exchange between Systems - Local and Metropolitan Area Networks--Specific Requirements - Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications", IEEE Std 802.11-2024, DOI 10.1109/IEEESTD.2025.10979691, , <https://doi.org/10.1109/IEEESTD.2025.10979691>.
[IMC16-QCUT]
Guo, Y., Qian, F., Chen, Q. A., Mao, Z. M., and S. Sen, "Understanding On-device Bufferbloat for Cellular Upload", ACM Proceedings of the 2016 Internet Measurement Conference (IMC '16), DOI 10.1145/2987443.2987490, , <https://doi.org/10.1145/2987443.2987490>.
[RFC3168]
Ramakrishnan, K., Floyd, S., and D. Black, "The Addition of Explicit Congestion Notification (ECN) to IP", RFC 3168, DOI 10.17487/RFC3168, , <https://www.rfc-editor.org/rfc/rfc3168>.
[RFC9000]
Iyengar, J., Ed. and M. Thomson, Ed., "QUIC: A UDP-Based Multiplexed and Secure Transport", RFC 9000, DOI 10.17487/RFC9000, , <https://www.rfc-editor.org/rfc/rfc9000>.
[RFC9330]
Briscoe, B., Ed., De Schepper, K., Bagnulo, M., and G. White, "Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: Architecture", RFC 9330, DOI 10.17487/RFC9330, , <https://www.rfc-editor.org/rfc/rfc9330>.
[RFC9332]
De Schepper, K., Briscoe, B., Ed., and G. White, "Dual-Queue Coupled Active Queue Management (AQM) for Low Latency, Low Loss, and Scalable Throughput (L4S)", RFC 9332, DOI 10.17487/RFC9332, , <https://www.rfc-editor.org/rfc/rfc9332>.
[RFC10055]
Duke, M., "Configuring UDP Sockets for Explicit Congestion Notification (ECN) for Common Platforms", RFC 10055, DOI 10.17487/RFC10055, , <https://www.rfc-editor.org/rfc/rfc10055>.
[TS23.501]
3GPP, "System architecture for the 5G System (5GS); Stage 2", 3GPP TS 23.501, n.d., <https://www.3gpp.org/dynareport/23501.htm>.
[TS38.300]
3GPP, "NR; NR and NG-RAN Overall description; Stage-2", 3GPP TS 38.300, n.d., <https://www.3gpp.org/dynareport/38300.htm>.

Authors' Addresses

Sebastian Poreba
Google LLC
Lorenzo Colitti
Google LLC
Sandeep Irlanki
Samsung R&D