You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: 2026/webtransport-wg-charter.html
+6-4Lines changed: 6 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -151,7 +151,8 @@ <h2>Motivation and Background</h2>
151
151
<sectionid="scope" class="scope">
152
152
<h2>Scope</h2>
153
153
<p>The WebTransport Working Group, in collaboration with the <ahref="https://datatracker.ietf.org/wg/webtrans/about/">IETF WebTransport Working Group</a> develops APIs that enable Web developers to make use of these new network capabilities, including possible fallback mechanisms to handle scenarios when a QUIC connection cannot be established.</p>
154
-
<p>These capabilities are expected to be useful in a wide variety of contexts where network performance has perceivable impacts on user experience, such as media streaming or cloud gaming.</p>
154
+
<p>The working group is also considering incubating mechanisms for peer-to-peer capability.</p>
155
+
<p>These capabilities are expected to be useful in a wide variety of contexts where network performance has perceivable impacts on user experience, such as media streaming or cloud gaming and real-time communications.</p>
155
156
156
157
</section>
157
158
@@ -176,11 +177,12 @@ <h3>
176
177
<dd>
177
178
<p>This specification defines a set of ECMAScript APIs to allow data to be sent and received between a browser and server, implementing pluggable protocols underneath with common APIs on top.</p>
178
179
<pclass="draft-status"><b>Draft state:</b><ahref="https://www.w3.org/TR/webtransport/">W3C Working Draft</a></p>
0 commit comments