Merge pull request #153 from fippo/ssrc-unsigned

SHA: 43cf96c
Reason: push, by @alvestrand

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

Author: alvestrand

index.html

@@ -8,7 +8,7 @@
   <link href="https://www.w3.org/2008/site/images/favicon.ico" rel="icon">
   <meta content="Bikeshed version 44af0bf3e, updated Fri Jul 29 17:05:16 2022 -0700" name="generator">
   <link href="https://www.w3.org/TR/webrtc-encoded-transform/" rel="canonical">
-  <meta content="d614e892d0989eb873aa7318c362c30c9e0df6db" name="document-revision">
+  <meta content="43cf96c03b8f91dbc79a391b8fa1e2411bddcf34" name="document-revision">
 <style>/* style-autolinks */
 
 .css.css, .property.property, .descriptor.descriptor {
@@ -687,20 +687,28 @@ <h2 class="no-num no-toc no-ref" id="contents">Table of Contents</h2>
   </nav>
   <main>
    <h2 class="heading settled" data-level="1" id="introduction"><span class="secno">1. </span><span class="content">Introduction</span><a class="self-link" href="#introduction"></a></h2>
-   <p>The <a data-link-type="biblio" href="#biblio-webrtc-nv-use-cases">[WEBRTC-NV-USE-CASES]</a> document describes the use-case of</p>
+   <p>The <a data-link-type="biblio" href="#biblio-webrtc-nv-use-cases">[WEBRTC-NV-USE-CASES]</a> document describes several functions that
+can only be achieved by access to media (requirements N20-N22),
+including, but not limited to:</p>
    <ul>
     <li data-md>
-     <p>Untrusted JavaScript Cloud Conferencing</p>
+     <p>Funny Hats</p>
+    <li data-md>
+     <p>Machine Learning</p>
+    <li data-md>
+     <p>Virtual Reality Gaming</p>
    </ul>
-   which requires that the conferencing server does not have access
-to the cleartext media (requirement N27). 
-   <p>This specification provides access to encoded media,
-which is the output of the encoder part of a codec and the input to the
-decoder part of a codec which allows the user agent to apply encryption
-locally.</p>
-   <p>The interface is inspired by <a data-link-type="biblio" href="#biblio-web-codecs">[WEB-CODECS]</a> to
+   <p>These use cases further require that processing can be done in worker
+threads (requirement N23-N24).</p>
+   <p>Furthermore, the "trusted JavaScript cloud conferencing" use case
+requires such processing to be done on encoded media, not just the raw
+media.</p>
+   <p>This specification gives an interface inspired by <a data-link-type="biblio" href="#biblio-web-codecs">[WEB-CODECS]</a> to
 provide access to such functionality while retaining the setup flow of
-RTCPeerConnection</p>
+RTCPeerConnection.</p>
+   <p>This iteration of the specification provides access to encoded media,
+which is the output of the encoder part of a codec and the input to the
+decoder part of a codec.</p>
    <h2 class="heading settled" data-level="2" id="terminology"><span class="secno">2. </span><span class="content">Terminology</span><a class="self-link" href="#terminology"></a></h2>
    <h2 class="heading settled" data-level="3" id="specification"><span class="secno">3. </span><span class="content">Specification</span><a class="self-link" href="#specification"></a></h2>
    <p>The Streams definition doesn’t use WebIDL much, but the WebRTC spec does.