From 9ceaf3c64f45706f4b20f429b3c5a19a69d0f73c Mon Sep 17 00:00:00 2001 From: Bernard Aboba Date: Fri, 8 Sep 2023 12:07:07 -0700 Subject: [PATCH 01/11] Section 3.2.2: Clarify Use Case Fix for #103 --- index.html | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/index.html b/index.html index 9af9718..347249d 100644 --- a/index.html +++ b/index.html @@ -303,12 +303,11 @@

Game streaming

transported using RTP or RTCDataChannel.

-

Low latency Broadcast with Fanout

-

There are streaming applications that require large scale as well as low latency. - Examples include sporting events, church services, webinars and company 'Town Hall' meetings. - Live audio, video and data is sent to thousands (or even millions) of recipients. - Limited interactivity may be supported, such as allowing authorized participants to ask - questions at a company meeting. Both the media sender and receivers may be behind a NAT. +

Ultra Low latency Broadcast with Fanout

+

There are streaming applications that require large scale as well as ultra low latency. + Examples include sporting events, auctions and financial news. Live audio, video and data is sent to + thousands (or even millions) of recipients. Limited interactivity may be supported, such as + capturing video or audio from auction bidders. Both the media sender and receivers may be behind a NAT. P2P relays may be used to improve scalability, potentially using different transport than the original stream.

This use case has completed a Call for Consensus (CfC) [[?CFC-Low-Latency]] but has unresolved issues.

@@ -336,7 +335,7 @@

Low latency Broadcast with Fanout

-

Experience: |pipe|, Peer5 and Dolby are examples of this use case, with media +

Experience: |pipe| and Dolby are examples of this use case, with media transported via RTP or RTCDataChannel.

From 97b7926888faca3ed0dc28f5760ef5f4799b6470 Mon Sep 17 00:00:00 2001 From: Bernard Aboba Date: Fri, 8 Sep 2023 14:20:37 -0700 Subject: [PATCH 02/11] Clarify ULL and add betting --- index.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/index.html b/index.html index 347249d..ba8fe01 100644 --- a/index.html +++ b/index.html @@ -304,8 +304,8 @@

Game streaming

Ultra Low latency Broadcast with Fanout

-

There are streaming applications that require large scale as well as ultra low latency. - Examples include sporting events, auctions and financial news. Live audio, video and data is sent to +

There are streaming applications that require large scale as well as ultra low latency (glass-glass latency less than 500ms). + Examples include auctions, betting and financial news. Live audio, video and data is sent to thousands (or even millions) of recipients. Limited interactivity may be supported, such as capturing video or audio from auction bidders. Both the media sender and receivers may be behind a NAT. P2P relays may be used to improve scalability, potentially using different transport than From c3c13d9118b1cd47ae8d2a2ebd204868c6c62e51 Mon Sep 17 00:00:00 2001 From: Bernard Aboba Date: Tue, 12 Sep 2023 07:18:19 -0700 Subject: [PATCH 03/11] Remove mention of data channel --- index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.html b/index.html index ba8fe01..5d6ea48 100644 --- a/index.html +++ b/index.html @@ -336,7 +336,7 @@

Ultra Low latency Broadcast with Fanout

Experience: |pipe| and Dolby are examples of this use case, with media -transported via RTP or RTCDataChannel.

+transported via RTP.

From c9fdfb5dc67cc10f25b94066cef8a9b2de161413 Mon Sep 17 00:00:00 2001 From: Bernard Aboba Date: Thu, 21 Sep 2023 07:22:06 -0700 Subject: [PATCH 04/11] Update index.html --- index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.html b/index.html index 5d6ea48..06aa109 100644 --- a/index.html +++ b/index.html @@ -308,7 +308,7 @@

Ultra Low latency Broadcast with Fanout

Examples include auctions, betting and financial news. Live audio, video and data is sent to thousands (or even millions) of recipients. Limited interactivity may be supported, such as capturing video or audio from auction bidders. Both the media sender and receivers may be behind a NAT. - P2P relays may be used to improve scalability, potentially using different transport than + Peer-to-peer relays may be used to improve scalability, potentially using different transport than the original stream.

This use case has completed a Call for Consensus (CfC) [[?CFC-Low-Latency]] but has unresolved issues.

From fb1f6564d0fa071023692e2c79e0858f303dd2a4 Mon Sep 17 00:00:00 2001 From: Bernard Aboba Date: Thu, 28 Sep 2023 07:28:08 -0700 Subject: [PATCH 05/11] Remove betting --- index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.html b/index.html index 06aa109..177bc53 100644 --- a/index.html +++ b/index.html @@ -305,7 +305,7 @@

Game streaming

Ultra Low latency Broadcast with Fanout

There are streaming applications that require large scale as well as ultra low latency (glass-glass latency less than 500ms). - Examples include auctions, betting and financial news. Live audio, video and data is sent to + Examples include auctions and financial news. Live audio, video and data is sent to thousands (or even millions) of recipients. Limited interactivity may be supported, such as capturing video or audio from auction bidders. Both the media sender and receivers may be behind a NAT. Peer-to-peer relays may be used to improve scalability, potentially using different transport than From 5f5c424541fe5ac928932dc8193ab02058bc5a6a Mon Sep 17 00:00:00 2001 From: Bernard Aboba Date: Mon, 16 Oct 2023 23:01:18 -0700 Subject: [PATCH 06/11] Clarify RTP usage --- index.html | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/index.html b/index.html index 177bc53..3be819d 100644 --- a/index.html +++ b/index.html @@ -304,12 +304,13 @@

Game streaming

Ultra Low latency Broadcast with Fanout

-

There are streaming applications that require large scale as well as ultra low latency (glass-glass latency less than 500ms). - Examples include auctions and financial news. Live audio, video and data is sent to - thousands (or even millions) of recipients. Limited interactivity may be supported, such as - capturing video or audio from auction bidders. Both the media sender and receivers may be behind a NAT. - Peer-to-peer relays may be used to improve scalability, potentially using different transport than - the original stream.

+

There are streaming applications that require large scale as well as ultra low latency + (glass-glass latency less than 300ms). Examples include auctions. Live audio, video + and data is sent to thousands (or even millions) of recipients. Limited interactivity + may be supported, such as capturing audio/video from auction bidders. Both the media + sender and receivers may be behind a NAT. Peer-to-peer relays may be used to improve + scalability, with ingestion, distribution and fanout utilizing RTP. +

This use case has completed a Call for Consensus (CfC) [[?CFC-Low-Latency]] but has unresolved issues.

From facc7b0a42ae6af2f5b2b8d76c0effab0ab464d4 Mon Sep 17 00:00:00 2001 From: Bernard Aboba Date: Tue, 17 Oct 2023 07:27:13 -0700 Subject: [PATCH 07/11] Remove "unresolved issues" note --- index.html | 1 - 1 file changed, 1 deletion(-) diff --git a/index.html b/index.html index 3be819d..5a50f6f 100644 --- a/index.html +++ b/index.html @@ -311,7 +311,6 @@

Ultra Low latency Broadcast with Fanout

sender and receivers may be behind a NAT. Peer-to-peer relays may be used to improve scalability, with ingestion, distribution and fanout utilizing RTP.

-

This use case has completed a Call for Consensus (CfC) [[?CFC-Low-Latency]] but has unresolved issues.

From cc8839c51e3a47f8d6a989fccddda8897514d6c6 Mon Sep 17 00:00:00 2001 From: Bernard Aboba Date: Thu, 19 Oct 2023 13:59:46 -0700 Subject: [PATCH 08/11] Update index.html --- index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.html b/index.html index 5a50f6f..df409b3 100644 --- a/index.html +++ b/index.html @@ -308,7 +308,7 @@

Ultra Low latency Broadcast with Fanout

(glass-glass latency less than 300ms). Examples include auctions. Live audio, video and data is sent to thousands (or even millions) of recipients. Limited interactivity may be supported, such as capturing audio/video from auction bidders. Both the media - sender and receivers may be behind a NAT. Peer-to-peer relays may be used to improve + sender and receivers may be behind a NAT. Peer-to-peer relays are used to improve scalability, with ingestion, distribution and fanout utilizing RTP.

From 1674bc8edfeb3e5f2a6509803e4b8f1287d76e23 Mon Sep 17 00:00:00 2001 From: Bernard Aboba Date: Mon, 13 Nov 2023 21:49:38 -0800 Subject: [PATCH 09/11] Rewrite PR --- index.html | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/index.html b/index.html index df409b3..44c50ca 100644 --- a/index.html +++ b/index.html @@ -305,11 +305,15 @@

Game streaming

Ultra Low latency Broadcast with Fanout

There are streaming applications that require large scale as well as ultra low latency - (glass-glass latency less than 300ms). Examples include auctions. Live audio, video - and data is sent to thousands (or even millions) of recipients. Limited interactivity - may be supported, such as capturing audio/video from auction bidders. Both the media - sender and receivers may be behind a NAT. Peer-to-peer relays are used to improve - scalability, with ingestion, distribution and fanout utilizing RTP. + such as auctions. Live audio, video and data is sent to thousands (or even millions) + of recipients. Limited interactivity may be supported, such as capturing audio/video + from auction bidders. Both the media senders and receivers may be behind a NAT. + Peer-to-peer relays are used to improve scalability, with ingestion, distribution and + fanout requiring unreliable/unordered transport to reduce latency, and support for + retransmission and forward error correction to provide robustness. In this use case, + low latency is more important than media quality, so that low latency congestion + control algorithms are required, and latency-enducing effects such as head of line + blocking are to be avoided.

From 65df13963ca5999f64af7d85d0036368c6f75961 Mon Sep 17 00:00:00 2001 From: Bernard Aboba Date: Mon, 13 Nov 2023 21:55:26 -0800 Subject: [PATCH 10/11] Update index.html --- index.html | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/index.html b/index.html index 44c50ca..ecabc71 100644 --- a/index.html +++ b/index.html @@ -313,7 +313,8 @@

Ultra Low latency Broadcast with Fanout

retransmission and forward error correction to provide robustness. In this use case, low latency is more important than media quality, so that low latency congestion control algorithms are required, and latency-enducing effects such as head of line - blocking are to be avoided. + blocking are to be avoided. Reception of media via events is problematic, due to + lack of coupling between the event loop and the receive window.

From 3c5a954d11b040dad7f1379a2fc35f43e88d3d9f Mon Sep 17 00:00:00 2001 From: Bernard Aboba Date: Wed, 6 Dec 2023 00:22:07 -0500 Subject: [PATCH 11/11] Remove "milions" --- index.html | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/index.html b/index.html index ecabc71..ecd6279 100644 --- a/index.html +++ b/index.html @@ -305,13 +305,13 @@

Game streaming

Ultra Low latency Broadcast with Fanout

There are streaming applications that require large scale as well as ultra low latency - such as auctions. Live audio, video and data is sent to thousands (or even millions) - of recipients. Limited interactivity may be supported, such as capturing audio/video - from auction bidders. Both the media senders and receivers may be behind a NAT. - Peer-to-peer relays are used to improve scalability, with ingestion, distribution and - fanout requiring unreliable/unordered transport to reduce latency, and support for - retransmission and forward error correction to provide robustness. In this use case, - low latency is more important than media quality, so that low latency congestion + such as auctions. Live audio, video and data is sent to thousands of recipients. + Limited interactivity may be supported, such as capturing audio/video from + auction bidders. Both the media senders and receivers may be behind a NAT. + Peer-to-peer relays are used to improve scalability, with ingestion, distribution + and fanout requiring unreliable/unordered transport to reduce latency, and support + for retransmission and forward error correction to provide robustness. In this use + case, low latency is more important than media quality, so that low latency congestion control algorithms are required, and latency-enducing effects such as head of line blocking are to be avoided. Reception of media via events is problematic, due to lack of coupling between the event loop and the receive window.