-
Notifications
You must be signed in to change notification settings - Fork 58
/
wt-2024.html
512 lines (439 loc) · 25.1 KB
/
wt-2024.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
<!DOCTYPE html>
<html lang="en-US">
<head>
<meta charset="utf-8">
<title>WebTransport Working Group Charter</title>
<link rel="stylesheet" href="https://www.w3.org/2005/10/w3cdoc.css" type="text/css" media="screen">
<link rel="stylesheet" type="text/css" href="https://www.w3.org/OldGuide/pubrules-style.css">
<link rel="stylesheet" type="text/css" href="https://www.w3.org/2006/02/charter-style.css">
<style>
main {
max-width: 60em;
margin: 0 auto;
}
ul#navbar {
font-size: small;
}
dt.spec {
font-weight: bold;
}
dt.spec new {
background: yellow;
}
ul.out-of-scope > li {
font-weight: bold;
}
ul.out-of-scope > li > ul > li{
font-weight: normal;
}
.issue {
background: cornsilk;
font-style: italic;
}
.todo {
color: #900;
}
footer {
font-size: small;
}
</style>
</head>
<body>
<header id="header">
<aside>
<ul id="navbar">
<li><a href="#background">Background</a></li>
<li><a href="#scope">Scope</a></li>
<li><a href="#deliverables">Deliverables</a></li>
<li><a href="#success-criteria">Success Criteria</a></li>
<li><a href="#coordination">Coordination</a></li>
<li><a href="#participation">Participation</a></li>
<li><a href="#communication">Communication</a></li>
<li><a href="#decisions">Decision Policy</a></li>
<li><a href="#patentpolicy">Patent Policy</a></li>
<li><a href="#licensing">Licensing</a></li>
<li><a href="#about">About this Charter</a></li>
</ul>
</aside>
<p>
<a href="https://www.w3.org/"><img alt="W3C" height="48" src="https://www.w3.org/Icons/w3c_home" width="72"></a>
</p>
</header>
<main>
<h1 id="title"><i class="todo">PROPOSED</i> WebTransport Working Group Charter</h1>
<!-- delete PROPOSED after AC review completed -->
<p class="mission">The <strong>mission</strong> of the <a href="https://www.w3.org/groups/wg/webtransport">WebTransport Working Group</a> is to develop APIs that enable data transfer between browsers and servers with support for multiple data flows, unidirectional data flows, out-of-order delivery, variable reliability and pluggable protocols.</p>
<div class="noprint">
<p class="join"><a href="https://www.w3.org/groups/wg/webtransport/join/">Join the WebTransport Working Group.</a></p>
</div>
<!-- delete the GH link after AC review completed -->
<p style="padding: 0.5ex; border: 1px solid green"> This proposed charter is available
on <i class="todo"><a href="https://github.com/w3c/charter-drafts/">GitHub</a>.
Feel free to raise <a href="https://github.com/w3c/charter-drafts/issues">issues</a></i>.
</p>
<div id="details">
<table class="summary-table">
<tr id="Status">
<th>
Charter Status
</th>
<td>
See the <a href="https://www.w3.org/groups/wg/webtransport/charters">group status page</A> and <a href="#history">detailed change history</a>.
</td>
</tr>
<tr id="Duration">
<th>
Start date
</th>
<td>
<i class="todo">[dd monthname yyyy] (date of the "Call for Participation", when the charter is approved)</i>
</td>
</tr>
<tr id="CharterEnd">
<th>
End date
</th>
<td>
31 December 2025
</td>
</tr>
<tr>
<th>
Chairs
</th>
<td>
Will Law (Akamai), Jan-Ivar Bruaroey (Mozilla)
</td>
</tr>
<tr>
<th>
Team Contacts
</th>
<td>
<a href="mailto:ylafon@w3.org">Yves Lafon</a> (0.15 <abbr title="Full-Time Equivalent">FTE</abbr>)
</td>
</tr>
<tr>
<th>
Meeting Schedule
</th>
<td>
<strong>Teleconferences:</strong> approximately 1 per month
<br>
<strong>Face-to-face:</strong> we will meet during the W3C's annual Technical Plenary week; additional face-to-face meetings may be scheduled by consent of the participants, usually no more than 3 per year.
</td>
</tr>
</table>
</div>
<div id="background" class="background">
<h2>Motivation and Background</h2>
<p>The deployment of the QUIC protocol standardized in IETF (e.g. in the context of HTTP3) is expected to make QUIC support widely available, opening up the possibility to establish new types of network connections in Web applications for client-server data transfer (e.g. unreliable, unordered).</p>
</div>
<section id="scope" class="scope">
<h2>Scope</h2>
<p>The WebTransport Working Group, in collaboration with the <a href="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>
<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>
</section>
<section id="deliverables">
<h2>
Deliverables
</h2>
<p>Updated document status is available on the <a href="https://www.w3.org/groups/wg/webtransport/publications/">group publication status page</a>.</p>
<p><i>Draft state</i> indicates the state of the deliverable at the time of the charter approval. <i>Expected completion</i> indicates when the deliverable is projected to become a Recommendation, or otherwise reach a stable state.</p>
<section id="normative">
<h3>
Normative Specifications
</h3>
<p>
The Working Group will deliver the following W3C normative specifications:
</p>
<dl>
<dt id="web-transport" class="spec">WebTransport API</dt>
<dd>
<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>
<p class="draft-status"><b>Draft state:</b> <a href="https://www.w3.org/TR/webtransport/">W3C Working Draft</a></p>
<p class="milestone"><b>Expected completion:</b> Q2 2025</p>
<p><b>Adopted Draft:</b> <a href="https://www.w3.org/TR/2023/WD-webtransport-20231220/">https://www.w3.org/TR/2023/WD-webtransport-20231220/</a>, 2023-12-20</p>
<p><b>Exclusion Draft:</b> <a href="https://www.w3.org/TR/2021/WD-webtransport-20210504/">https://www.w3.org/TR/2021/WD-webtransport-20210504/</a>, 2021-05-04</p>
<p>Exclusion period began 2021-05-04; Exclusion period ended 2021-10-01.</p>
<p><b>Exclusion Draft Charter:</b></p> <a href="https://www.w3.org/2020/12/webtransport-wg-charter.html">https://www.w3.org/2020/12/webtransport-wg-charter.html</a>
</dd>
</dl>
</section>
<section id="ig-other-deliverables">
<h3>
Other Deliverables
</h3>
<p>
Other non-normative documents may be created such as:
</p>
<ul>
<li>Use case and requirement documents;</li>
<li>Test suite and implementation report for the specification;</li>
<li>Primer or Best Practice documents to support web developers when designing applications.</li>
</ul>
</section>
<section id="timeline">
<h3>Timeline</h3>
<ul>
<li>September 2020: First teleconference</li>
<li>January 2021: FPWD for WebTransport</li>
<li>Q4 2024: CR for WebTransport</li>
</ul>
</section>
</section>
<section id="success-criteria">
<h2>Success Criteria</h2>
<!-- Testing and interop -->
<p>In order to advance to
<a href="https://www.w3.org/Consortium/Process/#RecsPR" title="Proposed Recommendation">Proposed Recommendation</a>, each normative specification is expected to have
<a href="https://www.w3.org/Consortium/Process/#implementation-experience">at least two independent interoperable
implementations</a> of every feature defined in the specification, where
interoperability can be verified by passing open test suites, and two or
more implementations interoperating with each other.</p>
<p>There should be testing plans for each specification, starting from the earliest drafts.</p>
<p>
To promote interoperability, all changes made to specifications
in Candidate Recommendation
or to features that have deployed implementations
should have <a href='https://www.w3.org/2019/02/testing-policy.html'>tests</a>.
Testing efforts should be conducted via the <a href="https://github.com/web-platform-tests/wpt">Web Platform Tests</a> project.</p>
<!-- Horizontal review -->
<p>Each specification should contain sections detailing all known security and
privacy implications for implementers, Web authors, and end users.</p>
<p>
Each specification should contain a section on accessibility that describes the benefits and impacts, including ways specification features can be used to address them, and
recommendations for maximising accessibility in implementations.</p>
<!-- Design principles -->
<p>This Working Group expects to follow the
TAG <a href="https://www.w3.org/TR/design-principles/">Web Platform Design Principles</a>.
</p>
</section>
<section id="coordination">
<h2>Coordination</h2>
<p>For all specifications, this Working Group will seek <a href="https://www.w3.org/Guide/documentreview/#how_to_get_horizontal_review">horizontal review</a> for
accessibility, internationalization, privacy, and security with the relevant Working and
Interest Groups, and with the <a href="https://www.w3.org/groups/other/tag/" title="Technical Architecture Group">TAG</a>.
Invitation for review must be issued during each major standards-track document transition, including
<a href="https://www.w3.org/Consortium/Process/#RecsWD" title="First Public Working Draft">FPWD</a>. The
Working Group is encouraged to engage collaboratively with the horizontal review groups throughout development of
each specification. The Working Group is advised to seek a review at least 3 months before first entering
<a href="https://www.w3.org/Consortium/Process/#RecsCR" title="Candidate Recommendation">CR</a> and is encouraged
to proactively notify the horizontal review groups when major changes occur in a specification following a review.</p>
<p>Additional technical coordination with the following Groups will be made, per the <a href="https://www.w3.org/Consortium/Process/#WGCharter">W3C Process Document</a>:</p>
<section>
<h3 id="w3c-coordination">W3C Groups</h3>
<dl>
<dt><a href="https://www.w3.org/groups/wg/htmlwg">HTML Working Group</a></dt>
<dd>The HTML Working Group works together with the WHATWG to produce the W3C Recommendation of HTML. The HTML specification defines the WebSockets API which may play a role in fallback scenarios when a WebTransport connection cannot be established.</dd>
<dt><a href="https://www.w3.org/groups/wg/webrtc">Web Real-Time Communications Working Group</a></dt>
<dd>The WebRTC API developed by the WebRTC Working Group enables data transfer between peers with similar charactestics to the ones enabled by WebTransport, and may consider adopting the WebTransport API for peer-to-peer data transfer.</dd>
<dt><a href="https://www.w3.org/2011/webtv/">Media and Entertainment Interest Group</a></dt>
<dd>The Media and Entertainment Interest Group gather use cases and requirements around media on the Web, including media streaming. Media streaming is expected to be a possible field of application of the WebTransport API.</dd>
<dt><a href="https://www.w3.org/media-wg/">Media Working Group</a></dt>
<dd>The Media Working Group may develop an Encoders/Decoders API which, together with the WebTransport API, could be used to stream media content (e.g. in low-latency scenarios such as cloud gaming). Interoperability requirements between the APIs may need to be considered.</dd>
<dt><a href="https://www.w3.org/web-networks/">Web and Networks Interest Group</a></dt>
<dd>The Web & Networks Interest Group is looking at how evolutions of network technologies impact Web applications, of which the WebTransport API is a key recent element.</dd>
<dt><a href="https://www.w3.org/groups/wg/webappsec">Web Application Security Working Group</a></dt>
<dd>The mission of the Web Application Security Working Group is to develop security and policy mechanisms to improve the security of Web Applications, and enable secure cross-origin communication.</dd>
</dl>
</section>
<section>
<h3 id="external-coordination">External Organizations</h3>
<dl>
<dt><a href="https://datatracker.ietf.org/wg/webtrans/about/">IETF WebTransport Working Group</a></dt>
<dd>The IETF WebTransport Working Group defines the protocols and protocol extensions which the API will use to establish its client-server connections. The two groups expect to coordinate closely.</dd>
<dt><a href="https://datatracker.ietf.org/wg/masque/about/">IETF Multiplexed Application Substrate over QUIC Encryption Working Group</a></dt>
<dd>The IETF Multiplexed Application Substrate over QUIC Encryption Working Group develops mechanism(s) that allow configuring and concurrently running multiple proxied stream- and datagram-based flows inside an HTTPS connection.</dd>
<dt><a href="https://whatwg.org/">WHATWG</a></dt>
<dd>The WHATWG maintains the WebSockets API (currently as <a href="https://html.spec.whatwg.org/multipage/web-sockets.html">part of the HTML Living Standard</a>) which may play a role in fallback scenarios when a WebTransport connection cannot be established. It also maintains the <a href="https://streams.spec.whatwg.org/">Streams Standard</a> which is expected to inform how WebTransport exposes data transfer, and <a href="https://fetch.spec.whatwg.org/">Fetch</a> which might be impacted by the use of WebTransport.</dd>
</dl>
</section>
</section>
<section class="participation">
<h2 id="participation">
Participation
</h2>
<p>
To be successful, this Working Group is expected to have 6 or more active participants for its duration, including representatives from the key implementors of this specification, and active Editors and Test Leads for each specification. The Chairs, specification Editors, and Test Leads are expected to contribute half of a working day per week towards the Working Group. There is no minimum requirement for other Participants.
</p>
<p>
The group encourages questions, comments and issues on its public mailing lists and document repositories, as described in <a href='#communication'>Communication</a>.
</p>
<p>
The group also welcomes non-Members to contribute technical submissions for consideration upon their agreement to the terms of the <a href="https://www.w3.org/Consortium/Patent-Policy/">W3C Patent Policy</a>.
</p>
<p>Participants in the group are required (by the <a href="https://www.w3.org/Consortium/Process/#ParticipationCriteria">W3C Process</a>) to follow the
W3C <a href="https://www.w3.org/policies/code-of-conduct/">Code of Conduct</a>.</p>
</section>
<section id="communication">
<h2>
Communication
</h2>
<p id="public">
Technical discussions for this Working Group are conducted in <a href="https://www.w3.org/Consortium/Process/#confidentiality-levels">public</a>: the meeting minutes from teleconference and face-to-face meetings will be archived for public review, and technical discussions and issue tracking will be conducted in a manner that can be both read and written to by the general public. Working Drafts and Editor's Drafts of specifications will be developed in public repositories and may permit direct public contribution requests.
The meetings themselves are not open to public participation, however.
</p>
<p>
Information about the group (including details about deliverables, issues, actions, status, participants, and meetings) will be available from the <a href="https://www.w3.org/groups/wg/webtransport">WebTransport Working Group home page.</a>
</p>
<p>
Most WebTransport Working Group teleconferences will focus on discussion of particular specifications, and will be conducted on an as-needed basis.
</p>
<p>
This group primarily conducts its technical work on its <a id="public-github" href="https://github.com/w3c/webtransport">repositories' GitHub issues</a> and its public mailing list <a href="mailto:public-webtransport@w3.org">public-webtransport@w3.org</a> (<a href="https://lists.w3.org/Archives/Public/public-webtransport/">archive</a>).
The public is invited to review, discuss and contribute to this work.
</p>
<p>
The group may use a Member-confidential mailing list for administrative purposes and, at the discretion of the Chairs and members of the group, for member-only discussions in special cases when a participant requests such a discussion.
</p>
</section>
<section id="decisions">
<h2>
Decision Policy
</h2>
<p>
This group will seek to make decisions through consensus and due process, per the <a href="https://www.w3.org/Consortium/Process/#Consensus">W3C Process Document (section 5.2.1, Consensus)</a>. Typically, an editor or other participant makes an initial proposal, which is then refined in discussion with members of the group and other reviewers, and consensus emerges with little formal voting being required.</p>
<p>
However, if a decision is necessary for timely progress and consensus is not achieved after careful consideration of the range of views presented, the Chairs may call for a group vote and record a decision along with any objections.
</p>
<p>
To afford asynchronous decisions and organizational deliberation, any resolution (including publication decisions) taken in a face-to-face meeting or teleconference will be considered provisional.
A call for consensus (CfC) will be issued for all resolutions (for example, via email, GitHub issue or web-based survey), with a response period from <span id='cfc'>one week to 10 working days</span>, depending on the chair's evaluation of the group consensus on the issue.
If no objections are raised by the end of the response period, the resolution will be considered to have consensus as a resolution of the Working Group.
</p>
<p>
All decisions made by the group should be considered resolved unless and until new information becomes available or unless reopened at the discretion of the Chairs.
</p>
<p>
This charter is written in accordance with the <a href="https://www.w3.org/Consortium/Process/#Votes">W3C Process Document (Section 5.2.3, Deciding by Vote)</a> and includes no voting procedures beyond what the Process Document requires.
</p>
</section>
<section id="patentpolicy">
<h2>
Patent Policy
</h2>
<p>
This Working Group operates under the <a href="https://www.w3.org/Consortium/Patent-Policy/">W3C Patent Policy</a> (Version of 15 September 2020). To promote the widest adoption of Web standards, W3C seeks to issue Web specifications that can be implemented, according to this policy, on a Royalty-Free basis.
For more information about disclosure obligations for this group, please see the <a href="https://www.w3.org/groups/wg/webtransport/ipr/">licensing information</a>.
</p>
</section>
<section id="licensing">
<h2>Licensing</h2>
<p>This Working Group will use the <a href="https://www.w3.org/copyright/software-license/">W3C Software and Document license</a> for all its deliverables.</p>
</section>
<section id="about">
<h2>
About this Charter
</h2>
<p>
This charter has been created according to <a href="https://www.w3.org/Consortium/Process/#GAGeneral">section 3.4</a> of the <a href="https://www.w3.org/Consortium/Process/">Process Document</a>. In the event of a conflict between this document or the provisions of any charter and the W3C Process, the W3C Process shall take precedence.
</p>
<section id="history">
<h3>
Charter History
</h3>
<p>The following table lists details of all changes from the initial charter, per the <a href="https://www.w3.org/Consortium/Process/#CharterReview">W3C Process Document (section 4.3, Advisory Committee Review of a Charter)</a>:</p>
<table class="history">
<tbody>
<tr>
<th>
Charter Period
</th>
<th>
Start Date
</th>
<th>
End Date
</th>
<th>
Changes
</th>
</tr>
<tr>
<th>
<a href="https://www.w3.org/2020/09/webtransport-wg-charter.html">Initial Charter</a>
</th>
<td>
08 September 2020
</td>
<td>
30 September 2022
</td>
<td>
Initial Charter
</td>
</tr>
<tr>
<th>
<a href="https://www.w3.org/2020/12/webtransport-wg-charter.html">Rechartered</a>
</th>
<td>
15 December 2020
</td>
<td>
30 September 2022
</td>
<td>
New Patent Policy
</td>
</tr>
<tr>
<th>
<a href="https://www.w3.org/2023/01/webtransport-wg-charter.html">Rechartered</a>
</th>
<td>
18 January 2023
</td>
<td>
31 December 2023
</td>
<td>
Charter Extension
</td>
</tr>
<tr>
<th>
<a href="https://lists.w3.org/Archives/Member/w3c-ac-members/2024JanMar/0012.html">Chartered Extension</a>
</th>
<td>
24 January 2024
</td>
<td>
31 May 2024
</td>
<td>
Current charter extended. The group plans to work on a new charter during the extension. See the <a href="https://w3c.github.io/charter-drafts/wt-2024.html">draft charter</a> and raise comments via <a href="https://github.com/w3c/charter-drafts/">GitHub issues</a>.
</td>
</tr>
</tbody>
</table>
</section>
<section id="changelog">
<h3>Change log</h3>
<!-- Use this section for changes _after_ the charter was approved by the Director. -->
<p>Changes to this document are documented in this section.</p>
<!--
<dl id='changes'>
<dt>YYYY-MM-DD</dt>
<dd>[changes]]</dd>
</dl>
-->
</section>
</section>
</main>
<hr>
<footer>
<address>
<a href="mailto:ylafon@w3.org">Yves Lafon</a>
</address>
<p class="copyright">Copyright © 2024</i> <a href="https://www.w3.org/">World Wide Web Consortium</a>.<br>
<abbr title="World Wide Web Consortium">W3C</abbr><sup>®</sup>
<a href="https://www.w3.org/policies/#disclaimers">liability</a>,
<a href="https://www.w3.org/policies/#trademarks">trademark</a> and
<a rel="license" href="https://www.w3.org/copyright/software-license/" title="W3C Software and Document Notice and License">permissive document license</a> rules apply.</p>
<hr>
<p><span class='todo'><a href="https://github.com/w3c/charter-drafts">Yes, it's on GitHub!</a>.</span></p>
</footer>
</body>
</html>