[Webkit-unassigned] [Bug 271191] New: [WebRTC] Add support for L4S(RFC 9330)

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=271191

            Bug ID: 271191
           Summary: [WebRTC] Add support for L4S(RFC 9330)
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebRTC
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: sun.shin at webkit.org
                CC: youennf at gmail.com

As we all know, Apple began supporting Low Latency, Low Loss, and Scalable Throughput (L4S) [1][2] 
on its platforms starting with iOS 17 and iPadOS 17 [3]. 

This support extends to both the QUIC and TCP networking stacks. Specifically:
- QUIC: Apple’s QUIC implementation fully supports L4S.
- TCP: Apple’s TCP implementation supports only the receiver-side L4S

>From the WebRTC implementation perspective, active development is underway to integrate L4S within the Chromium project. 
This includes the mechanisms for ECN marking collection from the UDP Socket Layer [4].

However, to fully leverage L4S functionality, additional implementations are necessary. 
This includes the development of receiver-side feedback and the optimization of feedback response intervals,
as outlined in RFCs 6679 and 8888 [5][6].

Our team is actively contributing to this endeavor through participation in both the W3C WebRTC
and IETF AVTCORE working groups, driving the standards forward [7][8].

>From a practical standpoint, we are collaborating with Comcast to conduct field trials via 
NVIDIA’s GeForce NOW cloud gaming service, demonstrating the real-world benefits of L4S [9].

Furthermore, we have extended cloud gaming support to Safari on macOS with the release of version 2.0.59, 
showcasing our commitment to cross-platform compatibility [10].

As we continue to support L4S through native implementations, the goal of this task is 
to expand this support to encompass WebRTC implementations.

[1] https://datatracker.ietf.org/doc/html/rfc9330 
[2] https://datatracker.ietf.org/doc/html/rfc9331
[3] https://developer.apple.com/documentation/network/testing_and_debugging_l4s_in_your_app 
[4] https://bugs.chromium.org/p/webrtc/issues/detail?id=15368 
[5] https://datatracker.ietf.org/doc/html/rfc6679
[6] https://datatracker.ietf.org/doc/html/rfc8888
[7] https://github.com/w3c/webrtc-nv-use-cases/pull/118
[8] https://datatracker.ietf.org/doc/draft-majali-avtcore-rtcp-fb-timing-cfg/ 
[9] https://corporate.comcast.com/stories/comcast-kicks-off-industrys-first-low-latency-docsis-field-trials
[10] https://www.nvidia.com/en-us/geforce-now/release-highlights/

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20240318/c5511a66/attachment.htm>