Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Section 3.2.2: Clarify Use Case #123

Merged
merged 11 commits into from
Dec 8, 2023
Merged

Section 3.2.2: Clarify Use Case #123

Changes from 10 commits
Commits
Show all changes
11 commits
Select commit Hold shift + click to select a range
9ceaf3c
Section 3.2.2: Clarify Use Case
aboba Sep 8, 2023
97b7926
Clarify ULL and add betting
aboba Sep 8, 2023
c3c13d9
Remove mention of data channel
aboba Sep 12, 2023
c9fdfb5
Update index.html
aboba Sep 21, 2023
fb1f656
Remove betting
aboba Sep 28, 2023
5f5c424
Clarify RTP usage
aboba Oct 17, 2023
facc7b0
Remove "unresolved issues" note
aboba Oct 17, 2023
cc8839c
Update index.html
aboba Oct 19, 2023
1674bc8
Rewrite PR
aboba Nov 14, 2023
65df139
Update index.html
aboba Nov 14, 2023
3c5a954
Remove "milions"
aboba Dec 6, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 15 additions & 11 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -303,15 +303,19 @@ <h4>Game streaming</h4>
transported using RTP or RTCDataChannel.</p>
</section>
<section id="auction">
<h4>Low latency Broadcast with Fanout</h4>
<p>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.
P2P relays may be used to improve scalability, potentially using different transport than
the original stream.</p>
<p class="note">This use case has completed a Call for Consensus (CfC) [[?CFC-Low-Latency]] but has unresolved issues.</p>
<h4>Ultra Low latency Broadcast with Fanout</h4>
<p>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)
aboba marked this conversation as resolved.
Show resolved Hide resolved
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.
</p>
<table class="simple">
<thead>
<tr>
Expand All @@ -336,8 +340,8 @@ <h4>Low latency Broadcast with Fanout</h4>
</tr>
</tbody>
</table>
<p>Experience: |pipe|, Peer5 and Dolby are examples of this use case, with media
transported via RTP or RTCDataChannel.</p>
<p>Experience: |pipe| and Dolby are examples of this use case, with media
transported via RTP.</p>
</section>
</section>
<section id="iot*">
Expand Down
Loading