[html5] r6022 - [e] (0) Add notes about negotiating video resolution in a peer-to-peer scenario.

whatwg at whatwg.org whatwg at whatwg.org
Thu Apr 21 15:25:47 PDT 2011


Author: ianh
Date: 2011-04-21 15:25:46 -0700 (Thu, 21 Apr 2011)
New Revision: 6022

Modified:
   complete.html
   index
   source
Log:
[e] (0) Add notes about negotiating video resolution in a peer-to-peer scenario.

Modified: complete.html
===================================================================
--- complete.html	2011-04-20 22:45:20 UTC (rev 6021)
+++ complete.html	2011-04-21 22:25:46 UTC (rev 6022)
@@ -239,7 +239,7 @@
 
   <header class=head id=head><p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
    <hgroup><h1>Web Applications 1.0</h1>
-    <h2 class="no-num no-toc">Living Standard — Last Updated 20 April 2011</h2>
+    <h2 class="no-num no-toc">Living Standard — Last Updated 21 April 2011</h2>
    </hgroup><p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
    <p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
    <!--<p class="impl"><strong>Implementors!</strong> We have a <a href="http://www.whatwg.org/mailing-list#implementors">mailing list</a> for you too!</p>-->
@@ -73930,6 +73930,19 @@
   the session. The <code><a href=#peerconnection>PeerConnection</a></code> API does not support
   bidirectional ("sendrecv") audio or video media streams. <a href=#refsSDPOFFERANSWER>[SDPOFFERANSWER]</a></p>
 
+  <p>User agents may negotiate any codec and any resolution, bitrate,
+  or other quality metric. User agents are encouraged to initially
+  negotiate for the native resolution of the stream. For streams that
+  are then rendered (using a <code><a href=#video>video</a></code> element), user agents
+  are encouraged to renegotiate for a resolution that matches the
+  rendered display size.</p>
+
+  <p class=note>Starting with the native resolution means that if
+  the Web application notifies its peer of the native resolution as it
+  starts sending data, and the peer prepares its <code><a href=#video>video</a></code>
+  element accordingly, there will be no need for a renegotiation once
+  the stream is flowing.</p>
+
   <p>All SDP media descriptions for streams represented by
   <code><a href=#stream>Stream</a></code> objects must include a label attribute ("<code title="">a=label:</code>") whose value is the value of the
   <code><a href=#stream>Stream</a></code> object's <code title=dom-stream-label><a href=#dom-stream-label>label</a></code> attribute. <a href=#refsSDP>[SDP]</a> <a href=#refsSDPLABEL>[SDPLABEL]</a></p>

Modified: index
===================================================================
--- index	2011-04-20 22:45:20 UTC (rev 6021)
+++ index	2011-04-21 22:25:46 UTC (rev 6022)
@@ -243,7 +243,7 @@
 
   <header class=head id=head><p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
    <hgroup><h1 class=allcaps>HTML</h1>
-    <h2 class="no-num no-toc">Living Standard — Last Updated 20 April 2011</h2>
+    <h2 class="no-num no-toc">Living Standard — Last Updated 21 April 2011</h2>
    </hgroup><p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
    <p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
    <!--<p class="impl"><strong>Implementors!</strong> We have a <a href="http://www.whatwg.org/mailing-list#implementors">mailing list</a> for you too!</p>-->
@@ -73968,6 +73968,19 @@
   the session. The <code><a href=#peerconnection>PeerConnection</a></code> API does not support
   bidirectional ("sendrecv") audio or video media streams. <a href=#refsSDPOFFERANSWER>[SDPOFFERANSWER]</a></p>
 
+  <p>User agents may negotiate any codec and any resolution, bitrate,
+  or other quality metric. User agents are encouraged to initially
+  negotiate for the native resolution of the stream. For streams that
+  are then rendered (using a <code><a href=#video>video</a></code> element), user agents
+  are encouraged to renegotiate for a resolution that matches the
+  rendered display size.</p>
+
+  <p class=note>Starting with the native resolution means that if
+  the Web application notifies its peer of the native resolution as it
+  starts sending data, and the peer prepares its <code><a href=#video>video</a></code>
+  element accordingly, there will be no need for a renegotiation once
+  the stream is flowing.</p>
+
   <p>All SDP media descriptions for streams represented by
   <code><a href=#stream>Stream</a></code> objects must include a label attribute ("<code title="">a=label:</code>") whose value is the value of the
   <code><a href=#stream>Stream</a></code> object's <code title=dom-stream-label><a href=#dom-stream-label>label</a></code> attribute. <a href=#refsSDP>[SDP]</a> <a href=#refsSDPLABEL>[SDPLABEL]</a></p>

Modified: source
===================================================================
--- source	2011-04-20 22:45:20 UTC (rev 6021)
+++ source	2011-04-21 22:25:46 UTC (rev 6022)
@@ -84460,6 +84460,19 @@
   bidirectional ("sendrecv") audio or video media streams. <a
   href="#refsSDPOFFERANSWER">[SDPOFFERANSWER]</a></p>
 
+  <p>User agents may negotiate any codec and any resolution, bitrate,
+  or other quality metric. User agents are encouraged to initially
+  negotiate for the native resolution of the stream. For streams that
+  are then rendered (using a <code>video</code> element), user agents
+  are encouraged to renegotiate for a resolution that matches the
+  rendered display size.</p>
+
+  <p class="note">Starting with the native resolution means that if
+  the Web application notifies its peer of the native resolution as it
+  starts sending data, and the peer prepares its <code>video</code>
+  element accordingly, there will be no need for a renegotiation once
+  the stream is flowing.</p>
+
   <p>All SDP media descriptions for streams represented by
   <code>Stream</code> objects must include a label attribute ("<code
   title="">a=label:</code>") whose value is the value of the




More information about the Commit-Watchers mailing list