IETF
Meetings
1. Metaverse Side Meeting @IETF 115
Publication URL: https://github.com/giuseppefioccola/Metaverse-side-meeting-at-IETF
Introduction:
A side meeting @IETF115, which was well accepted. All the materials can be found in the above URL.
Agenda:
- QuicR and standardization of the metaverse - Cullen Jennings, Cisco
- ICN and networking for distributed AR/VR - Dirk Kutscher, The Hong Kong University
- Low Latency, Low Loss, Scalable Throughput (L4S) Internet Service - Koen De Schepper, Nokia
- Network innovation and standardization for metaverse - Robin Li, Huawei
Media over QUIC WG
Publication URL: https://datatracker.ietf.org/wg/moq/about/
Introduction:
Media over QUIC (moq) will develop a simple low-latency media delivery solution for ingest and distribution of media. This solution addresses use cases including live streaming, gaming, and media conferencing and will scale efficiently. The working group will define MoQ so that the media publication protocol can leverage coordinating relays, caches, or replication points wherever applicable to improve the delivery performance. Media content may be end-to-end encrypted in certain use cases, where the “end-to-end” keys are available to media sources and consumers, but not relays. Even when media content is end-to-end encrypted, the relays can access metadata needed for caching (such as timestamp), making media forwarding decisions (such as drop or delay under congestion), and so on.
Low Latency, Low Loss, Scalable Throughput (L4S)
1. Low Latency, Low Loss, Scalable Throughput (L4S) Internet Service: Architecture
Publication URL: https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-l4s-arch/
Introduction:
This document describes the L4S architecture, which enables Internet applications to achieve Low queuing Latency, Low Loss, and Scalable throughput (L4S). L4S is based on the insight that the root cause of queuing delay is in the capacity-seeking congestion controllers of senders, not in the queue itself. With the L4S architecture all Internet applications could (but do not have to) transition away from congestion control algorithms that cause substantial queuing delay, to a new class of congestion controls that can seek capacity with very little queuing. These are aided by a modified form of explicit congestion notification (ECN) from the network. With this new architecture, applications can have both low latency and high throughput.
2. DualQ Coupled AQMs for Low Latency, Low Loss and Scalable Throughput (L4S)
Publication URL: https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-aqm-dualq-coupled/
Introduction:
This specification defines a framework for coupling the Active Queue Management (AQM) algorithms in two queues intended for flows with different responses to congestion. This provides a way for the Internet to transition from the scaling problems of standard TCP Reno-friendly (‘Classic’) congestion controls to the family of ‘Scalable’ congestion controls. These are designed for consistently very Low queuing Latency, very Low congestion Loss and Scaling of per-flow throughput (L4S) by using Explicit Congestion Notification(ECN) in a modified way. Until the Coupled DualQ, these scalable L4S congestion controls could only be deployed where a clean-slate environment could be arranged, such as in private data centres.
3. Explicit Congestion Notification (ECN) Protocol for Very Low Queuing Delay (L4S)
Publication URL: https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-ecn-l4s-id/
Introduction:
This specification defines the protocol to be used for a new network service called low latency, low loss and scalable throughput (L4S). L4S uses an Explicit Congestion Notification (ECN) scheme at the IP layer that is similar to the original (or ‘Classic’) ECN approach, except as specified within. L4S uses ‘scalable’ congestion control, which induces much more frequent control signals from the network and it responds to them with much more fine-grained adjustments, so that very low (typically sub-millisecond on average) and consistently low queuing delay becomes possible for L4S traffic without compromising link utilization. Thus even capacity-seeking (TCP-like) traffic can have high bandwidth and very low delay at the same time, even during periods of high traffic load.
4. Operational Guidance for Deployment of L4S in the Internet
Publication URL: https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-l4sops/
Introduction:
This document is intended to provide guidance in order to ensure successful deployment of Low Latency Low Loss Scalable throughput(L4S) in the Internet. Other L4S documents provide guidance for running an L4S experiment, but this document is focused solely on potential interactions between L4S flows and flows using the original(‘Classic’) ECN over a Classic ECN bottleneck link. The document discusses the potential outcomes of these interactions, describes mechanisms to detect the presence of Classic ECN bottlenecks, and identifies opportunities to prevent and/or detect and resolve fairness problems in such networks. This guidance is aimed at operators of end-systems, operators of networks, and researchers.
IETF Mailing List
List address: metaverse@ietf.org
Archive: https://mailarchive.ietf.org/arch/browse/metaverse/
To subscribe: https://www.ietf.org/mailman/listinfo/metaverse