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

RTC capabillity negotiation #212

Open
wants to merge 8 commits into
base: main
Choose a base branch
from
+30 −2
Open

RTC capabillity negotiation #212

Changes from 6 commits
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
5af1b34
Capabillity negotiation model
aboba Jan 15, 2024
d0472ce
Update index.bs
aboba Jan 15, 2024
d0fa809
Update index.bs
aboba Jan 15, 2024
52dc67e
Word smithing
aboba Jan 15, 2024
e8b60ff
Improving line breaks
aboba Jan 15, 2024
94247cc
Simplify discussion of RTC negotiation
aboba Jan 16, 2024
83d0098
Clarify conferencing server limitations
aboba Jan 17, 2024
620eb4f
Fix line size
aboba Jan 17, 2024
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
32 changes: 30 additions & 2 deletions index.bs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1184,8 +1184,36 @@ spec: encrypted-media-draft; for: EME; urlPrefix: https://w3c.github.io/encrypte
or APIs but is provides an easier access to some information that can be
used to fingerprint users.
</p>

<section>
<section>
<h3 id='capabilities-model'>
Capabilities Model
</h3>
<p>
This specification supports {{MediaDecodingType}} values of {{file}},
{{media-source}} or {{webrtc}} as well as {{MediaEncodingType}}
values of {{record}} and {{webrtc}}.
</p>
<p>
In realtime communications as supported in [[webrtc]], media is
transported between peers. Although web sites can play a role in
aboba marked this conversation as resolved.
Show resolved Hide resolved
relaying of signaling between peers, they are typically not involved
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Signaling is known in WebRTC land but maybe we should be less specific and mention something like: exchanging the necessary information to negotiate the media parameters that are common to both user agents.
Then it is clear that since they need to do the exchange, they get the information.

in media transport, encoding or decoding. For 1-1 calls, peers
typically directly negotiate media to be sent and received.
</p>
<p>
In a conferencing scenario, a WebRTC peer can send media for
reception by dozens or even hundreds of receivers. To improve
scalability, applications make use of external servers, such as
selective forwarding units or conferencing bridges. These servers
negotiate media parameters with participants, ensuring consistency
across senders and receivers. This is vastly preferrable to
allowing browsers to negotiate with each potential peer, which
would require N (N -1) negotiations, while ensuring interoperability
between peers, which would not be supported if browsers were allowed
to "pick the one they like best".
</p>
</section>
<section>
<h3 id='decoding-encoding-fingerprinting'>
Decoding/Encoding and Fingerprinting
</h3>
Expand Down
Loading