Merge pull request #1151 from w3c/cr-sotd

Prepare status of the document for CR publication

webrtc.html

@@ -22,10 +22,19 @@
     devices developed by the Media Capture Task Force.</p>
   </section>
   <section id="sotd">
-    <p>The Editors and active contributors of WebRTC 1.0 intend to publish a
-    Candidate Recommendation soon. Consequently, this is a Request for Comments
-    by the WebRTC Working Group to seek wide review of this document.</p>
     <p>The API is based on preliminary work done in the WHATWG.</p>
+
+    <p>While the specification is feature complete and is expected to be stable, there are also a number of <a href="https://github.com/w3c/webrtc-pc/issues?utf8=%E2%9C%93&amp;q=is%3Aopen%20is%3Aissue%20-label%3AEditorial%20">known substantive issues</a> on the specification that will be addressed during the Candidate Recommendation period based on implementation experience feedback.</p>
+
+    <p>It might also evolve based on feedback gathered as its <a href="https://github.com/w3c/web-platform-tests/tree/master/webrtc">associated test suite</a> evolves. This test suite will be used to build an <a href="https://wpt.fyi/webrtc">implementation report</a> of the API.</p>
+
+    <p>To go into Proposed Recommendation status, the group expects to demonstrate implementation of each feature in at least two deployed browsers, and at least one implementation of each optional feature. Mandatory feature with only one implementation may be marked as optional in a revised Candidate Recommendation where applicable.</p>
+
+    <p>The following features are marked as risk:</p>
+    <ul>
+      <li>The value <a href="#dom-rtcrtcpmuxpolicy-negotiate"><code>negotiate</code></a> of RTCRtcpMuxPolicy</li>
+    </ul>
+
   </section>
   <section class="informative" id="intro">
     <h2>Introduction</h2>