Skip to content

Commit 3116893

Browse files
committed
intro: remove funny hats
and restrict the use-cases to what we know this is being used for primarily. fixes #122
1 parent ef682af commit 3116893

File tree

1 file changed

+10
-18
lines changed

1 file changed

+10
-18
lines changed

index.bs

Lines changed: 10 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -32,27 +32,19 @@ spec:streams; type:interface; text:ReadableStream
3232

3333
# Introduction # {#introduction}
3434

35-
The [[WEBRTC-NV-USE-CASES]] document describes several functions that
36-
can only be achieved by access to media (requirements N20-N22),
37-
including, but not limited to:
38-
* Funny Hats
39-
* Machine Learning
40-
* Virtual Reality Gaming
35+
The [[WEBRTC-NV-USE-CASES]] document describes the use-case of
36+
* Untrusted JavaScript Cloud Conferencing
37+
which requires that the conferencing server does not have access
38+
to the cleartext media (requirement N27).
4139

42-
These use cases further require that processing can be done in worker
43-
threads (requirement N23-N24).
44-
45-
Furthermore, the "trusted JavaScript cloud conferencing" use case
46-
requires such processing to be done on encoded media, not just the raw
47-
media.
40+
This specification provides access to encoded media,
41+
which is the output of the encoder part of a codec and the input to the
42+
decoder part of a codec which allows the user agent to apply encryption
43+
locally.
4844

49-
This specification gives an interface inspired by [[WEB-CODECS]] to
45+
The interface is inspired by [[WEB-CODECS]] to
5046
provide access to such functionality while retaining the setup flow of
51-
RTCPeerConnection.
52-
53-
This iteration of the specification provides access to encoded media,
54-
which is the output of the encoder part of a codec and the input to the
55-
decoder part of a codec.
47+
RTCPeerConnection
5648

5749
# Terminology # {#terminology}
5850

0 commit comments

Comments
 (0)