forked from w3c/webrtc-charter
-
Notifications
You must be signed in to change notification settings - Fork 0
/
webrtc-charter.html
598 lines (508 loc) · 38.1 KB
/
webrtc-charter.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
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
<!DOCTYPE html>
<html lang="en-US">
<head>
<meta charset="utf-8" />
<title>[DRAFT] Web Real-Time Communications 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/Guide/pubrules-style.css" />
<link rel="stylesheet" type="text/css" href="https://www.w3.org/2006/02/charter-style.css" />
<style type="text/css">
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="#scope">Scope</a></li>
<li><a href="#deliverables">Deliverables</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">[DRAFT] Web Real-Time Communications Working Group Charter</h1>
<p><em>This is draft revised charter for the W3C WebRTC Working Group for discussion in the Working Group. It has no formal standing.</em></p>
<p class="mission">The
<strong>mission</strong> of the Web Real-Time Communications Working Group is to define client-side APIs to enable Real-Time Communications in Web browsers.</p>
<p>These APIs should enable building applications that can be run inside a browser, requiring no extra downloads or plugins, that allow communication between parties using audio, video and supplementary real-time communication, without having to use intervening servers (unless needed for firewall traversal, or for providing intermediary services). APIs enabling supplementary functions, such as recording, image capture and screen sharing are also in scope.</p>
<div class="noprint">
<p class="join"><a href="https://www.w3.org/2004/01/pp-impl/47318/join">Join the Web Real-Time Communications Working Group</a>.</p>
</div>
<p style="padding: 0.5ex; border: 1px solid green"> This proposed charter is available
on <a href="https://github.com/w3c/webrtc-charter">GitHub</a>.
Feel free to raise <a href="https://github.com/w3c/webrtc-charter/issues">issues</a>.
</p>
<section id="details">
<table class="summary-table">
<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="Duration">
<th>
End date
</th>
<td>
<i class="todo">31 March 2020</i>
</td>
</tr>
<tr>
<th>Charter extension</th>
<td>See <a href="#history">Change History</a>.
</td>
</tr>
<tr>
<th>
Chairs
</th>
<td>
<ul>
<li>Bernard Aboba</li>
<li>Harald Alvestrand</li>
<li>Stefan Håkansson</li>
</ul>
</td>
</tr>
<tr>
<th>
Team Contacts
</th>
<td>
<ul>
<li>Dominique Hazaël-Massieux</li>
<li>Vivien Lacourba</li>
</ul>
(0.3 <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>
</section>
<section id="scope" class="scope">
<h2>Scope</h2>
<p>Enabling real-time communications between Web browsers require the following client-side technologies to be available:</p>
<ul>
<li>API functions to explore device capabilities, e.g. camera, microphone, speakers,</li>
<li>API functions to capture media from local devices (e.g. camera and microphone, but also output devices such as a screen),</li>
<li>API functions for encoding and other processing of those media streams,</li>
<li>API functions for accessing the data in these media streams,</li>
<li>API functions for transferring data between peers,</li>
<li>API functions for establishing direct peer-to-peer connections, including firewall/NAT traversal,</li>
<li>API functions for decoding and processing (including echo canceling, stream synchronization and a number of other functions) of those streams at the incoming end,</li>
<li>Delivery to the user of those media streams via local screens and audio output devices (partially covered with HTML5).</li>
</ul>
The working group will address issues related to using these functions
in various contexts on the Web platform, such as:
<ul>
<li>Traditional Web pages</li>
<li>Web Workers of various types</li>
<li>Iframes, with appropriate access controls</li>
<li>Applications that span multiple pages</li>
<li>
Pages, workers and frames specifying content security policies
or other security mechanisms that should impact the use of these
APIs
</li>
</ul>
<div id="section-out-of-scope">
<h3 id="out-of-scope">Out of Scope</h3>
<p>The definition of the network protocols used to establish the connections between peers is out of scope for this group; in general, it is expected that protocols considerations will be handled in the IETF.</p>
<p>The definition of any new codecs for audio and video is out of scope.</p>
</div>
<div>
<h3>Success Criteria</h3>
<p>To advance to Proposed Recommendation, each specification is expected to have two independent implementations of each feature defined in the specification.</p>
<p>To advance to Proposed Recommendation, interoperability between the independent implementations (that is, bidirectional audio and video communication between the implementations) should be demonstrated.</p>
</div>
</section>
<section id="deliverables">
<h2>
Deliverables
</h2>
<p>More detailed milestones and updated publication schedules are available on the <a href="https://www.w3.org/2011/04/webrtc/">group home 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>
<div id="normative">
<h3>
Normative Specifications
</h3>
<p>The Working Group will deliver specifications that cover at least the following functions, unless they are found to be fully specified within other Working Groups' finished results:</p>
<dl>
<dt>Media Stream Functions</dt>
<dd>API functions to manipulate media streams for interactive real-time communications, connecting various processing functions to each other, and to media devices and network connections, including media manipulation functions for e.g. allowing to synchronize streams. Supplementary functions such as recording of media streams are also in scope.</dd>
<dt>Audio Stream Functions</dt>
<dd>An extension of the Media Stream Functions to process audio streams, to enable features such as automatic gain control, mute functions and echo cancellation.</dd>
<dt>Video Stream Functions</dt>
<dd>An extension of the Media Stream Functions to process video streams, to enable features such as bandwidth limiting, image manipulation or "video mute".</dd>
<dt>Functional Component Functions</dt>
<dd>API functions that allow to query for the components present in an implementation, instantiate them, and connect them to media streams.</dd>
<dt>Data Access Functions</dt>
<dd>API functions that allow Web applications to access and manipulate data in media streams.</dd>
<dt>Data Transfer Functions</dt>
<dd>API functions to provide interfaces that enable the transfer of data between peers,
Included in this category are API functions for message-based as well as stream-based communications.
<br>The WG will consider any necessary API changes or extensions to enable use of more than one data transfer protocol to support the data transfer functions.</dd>
<dt>P2P Connection Functions</dt>
<dd>API functions to provide interfaces that enable the conveyance of parameters necessary to establish peer to peer connections, based on the protocols selected by the IETF RTCWeb Working Group. Included in this category are also API functions to allow identification of the peer.</dd>
</dl>
<p>The Working Group may decide to group the specified functions in one or more specifications, and to develop extensions to its existing specifications to bring additional functionality identified as needed.</p>
<p>The Working Group has already started and will continue work on the following specifications: </p>
<dl>
<dt id="927" class="spec"><a href="https://www.w3.org/TR/webrtc/" rel="versionof">WebRTC 1.0: Real-time Communication Between Browsers</a></dt>
<dd>JavaScript APIs to allow media and data to be sent to and received from another browser or device implementing the appropriate set of real-time protocols</dd>
<dd>Adopted Candidate Recommendation: <a href="https://www.w3.org/TR/2017/CR-webrtc-20171102/">Candidate Recommendation 02 November 2017</a></dd>
<dd>Reference Draft: <a href="https://www.w3.org/TR/2017/CR-webrtc-20171102/">Candidate Recommendation 02 November 2017</a><br>
associated <a href="https://lists.w3.org/Archives/Member/member-cfe/2017Nov/0001.html"> Call for Exclusion</a> on 02 November 2017
ended on 01 January 2018<br>Produced under <a href="https://www.w3.org/2015/07/webrtc-charter.html">2015 WebRTC Working Group Charter</a></dd>
<dt id="989" class="spec"><a href="https://www.w3.org/TR/mediacapture-streams/" rel="versionof">Media Capture and Streams</a></dt>
<dd>JavaScript APIs that allow local media, including audio and video, to be requested from a platform</dd>
<dd>Adopted Candidate Recommendation: <a href="https://www.w3.org/TR/2017/CR-mediacapture-streams-20171003/">Candidate Recommendation 03 October 2017</a></dd>
<dd>Reference Draft:
<a href="https://www.w3.org/TR/2017/CR-mediacapture-streams-20171003/">Candidate Recommendation 03 October 2017</a><br>
associated <a href="https://lists.w3.org/Archives/Member/member-cfe/2017Oct/0000.html"> Call for Exclusion</a> on 03 October 2017
ended on 02 December 2017<br>Produced under <a href="https://www.w3.org/2015/07/webrtc-charter.html">2015 WebRTC Working Group Charter</a></dd>
<dt id="1051" class="spec"><a href="https://www.w3.org/TR/mediastream-recording/" rel="versionof">MediaStream Recording</a></dt>
<dd>a JavaScript API to record MediaStreams</dd>
<dd>Adopted Working Draft: <a href="https://www.w3.org/TR/2017/WD-mediastream-recording-20170621/">21 June 2017</a></dd>
<dd>Reference Draft:
<a href="https://www.w3.org/TR/2015/WD-mediastream-recording-20150908/">Working Draft 08 September 2015</a><br>
associated <a href="https://lists.w3.org/Archives/Member/member-cfe/2013Feb/0001.html"> Call for Exclusion</a> on 06 February 2013
ended on 05 July 2013<br>Produced under <a href="https://www.w3.org/2011/04/webrtc-charter.html">2011 WebRTC Working Group Charter</a></dd>
<dt id="1120" class="spec"><a href="https://www.w3.org/TR/image-capture/" rel="versionof">"MediaStream Image Capture"</a></dt>
<dd>a JavaScript API to capture still images from a video MediaStream</dd>
<dd>Adopted Working Draft: <a href="https://www.w3.org/TR/2017/WD-image-capture-20170621/">21 June 2017</a></dd>
<dd>Reference Draft:
<a href="https://www.w3.org/TR/2013/WD-image-capture-20130709/">Working Draft 09 July 2013</a><br>
associated <a href="https://lists.w3.org/Archives/Member/member-cfe/2013Jul/0000.html"> Call for Exclusion</a> on 09 July 2013
ended on 06 December 2013<br>Produced under <a href="https://www.w3.org/2011/04/webrtc-charter.html">2011 WebRTC Working Group Charter</a></dd>
<dt id="1194" class="spec"><a href="https://www.w3.org/TR/mediacapture-depth/" rel="versionof">Media Capture Depth Stream Extensions</a></dt>
<dd>An extension to the Media Capture and Streams API to capture depth streams (e.g. from 3D cameras)</dd>
<dd>Adopted Working Draft: <a href="https://www.w3.org/TR/2017/WD-mediacapture-depth-20170418/">18 April 2017</a></dd>
<dd>Reference Draft:
<a href="https://www.w3.org/TR/2015/WD-mediacapture-depth-20151208/">Working Draft 08 December 2015</a><br>
associated <a href="https://lists.w3.org/Archives/Member/member-cfe/2014Oct/0001.html"> Call for Exclusion</a> on 07 October 2014
ended on 06 March 2015<br>Produced under <a href="https://www.w3.org/2011/04/webrtc-charter.html">2011 WebRTC Working Group Charter</a></dd>
<dt id="1197" class="spec"><a href="https://www.w3.org/TR/webrtc-stats/" rel="versionof">Identifiers for WebRTC's Statistics API</a></dt>
<dd>JavaScript APIs that allow access to statistical information about a peer-to-peer connection established via the WebRTC API</dd>
<dd>Adopted Working Draft: <a href="https://www.w3.org/TR/2018/WD-webrtc-stats-20180131/">31 January 2018</a></dd>
<dd>Reference Draft:
<a href="https://www.w3.org/TR/2014/WD-webrtc-stats-20141021/">Working Draft 21 October 2014</a><br>
associated <a href="https://lists.w3.org/Archives/Member/member-cfe/2014Oct/0007.html"> Call for Exclusion</a> on 23 October 2014
ended on 20 March 2015<br>Produced under <a href="https://www.w3.org/2011/04/webrtc-charter.html">2011 WebRTC Working Group Charter</a></dd>
<dt id="1215" class="spec"><a href="https://www.w3.org/TR/audio-output/" rel="versionof">Audio Output Devices API</a></dt>
<dd>JavaScript APIs that let a Web application manage how audio is rendered on the user audio output devices</dd>
<dd>Adopted Candidate Recommendation: <a href="https://www.w3.org/TR/2017/CR-audio-output-20171003/">Candidate Recommendation 03 October 2017</a></dd>
<dd>Reference Draft:
<a href="https://www.w3.org/TR/2017/CR-audio-output-20171003/">Candidate Recommendation 03 October 2017</a><br>
associated <a href="https://lists.w3.org/Archives/Member/member-cfe/2017Oct/0000.html"> Call for Exclusion</a> on 03 October 2017
ended on 02 December 2017<br>Produced under <a href="https://www.w3.org/2015/07/webrtc-charter.html">2015 WebRTC Working Group Charter</a> </dd>
<dt id="1216" class="spec"><a href="https://www.w3.org/TR/screen-capture/" rel="versionof">Screen Capture</a></dt>
<dd>An extension to the Media Capture and Streams API to use a user's display, or parts thereof, as the source of a MediaStream.</dd>
<dd>Adopted Working Draft: <a href="https://www.w3.org/TR/2016/WD-screen-capture-20160714/">14 July 2016</a></dd>
<dd>Reference Draft:
<a href="https://www.w3.org/TR/2015/WD-screen-capture-20150210/">Working Draft 10 February 2015</a><br>
associated <a href="https://lists.w3.org/Archives/Member/member-cfe/2015Feb/0001.html"> Call for Exclusion</a> on 10 February 2015
ended on 10 July 2015<br>Produced under <a href="https://www.w3.org/2011/04/webrtc-charter.html">2011 WebRTC Working Group Charter</a></dd>
<dt id="1221" class="spec"><a href="https://www.w3.org/TR/mediacapture-fromelement/" rel="versionof">Media Capture from DOM Elements</a></dt>
<dd>An extension to DOM elements to allow to capture a media stream from their content</dd>
<dd>Adopted Working Draft: <a href="https://www.w3.org/TR/2017/WD-mediacapture-fromelement-20170906/">06 September 2017</a></dd>
<dd>Reference Draft:
<a href="https://www.w3.org/TR/2015/WD-mediacapture-fromelement-20150219/">Working Draft 19 February 2015</a><br>
associated <a href="https://lists.w3.org/Archives/Member/member-cfe/2015Feb/0009.html"> Call for Exclusion</a> on 19 February 2015
ended on 19 July 2015<br>Produced under <a href="https://www.w3.org/2011/04/webrtc-charter.html">2011 WebRTC Working Group Charter</a></dd>
<dt class="spec"><a href="https://w3c.github.io/webrtc-dscp-exp/">DSCP Control API</a></dt>
<dd>An extension to the WebRTC 1.0 API to enable experimentation with QoS marking.</dd>
<dd>Draft state: <a href="https://w3c.github.io/webrtc-dscp-exp/">Editor's draft</a></dd>
</dl>
<p>This work will be done in collaboration with the IETF. The W3C will define APIs to ensure that application developers can control the components or the architecture for selection and profiling of the wire protocols that have been produced by the IETF Real-Time Communication in WEB-browsers (RTCWeb) Working Group. While the specified API Functions will not constrain implementations into supporting a specific profile, they will be compatible with the Profile that is specified by the RTCWeb Working Group.</p>
<p>As the name indicates, WebRTC 1.0: Real-time Communication Between Browsers is a first version of APIs for real-time communication, sometimes referred to as the PeerConnection API. The activities in the ORTC (Object Real-time Communications) Community Group indicate that there is interest in additional APIs to provide more direct control over WebRTC than what the PeerConnection API offers.</p>
<p>In recognition of this interest, the Working Group intends to start work on a new set of object-oriented APIs for real-time communication.</p>
<p>In developing these new APIs, the Working Group will adhere to the following principles:</p>
<ul>
<li>Direct control: The new APIs are intended to provide direct control over the details of real-time communication, where the application can directly specify how information should be transmitted, without any built-in negotiation semantics.</li>
<li>Standalone operation: The new APIs will be complete enough to allow applications to write solely to the new APIs to complete common tasks.</li>
<li>Backwards-compatibility: The new APIs will extend the WebRTC 1.0 APIs, rather than replace them. Applications that use the PeerConnection API will continue to function, unless there is a clear and compelling reason to deprecate specific 1.0 functionality.</li>
<li>Feature independence: Features may be introduced in the new APIs that are not available when using the PeerConnection API.</li>
</ul>
<p>The Working Group will take the work done by the ORTC Community Group as a source of input, and when contemplating similar APIs in the Working Group, make efforts to align with the ORTC CG on API methodologies and nomenclature. This may include scheduled design meetings with relevant WG and CG stakeholders to foster convergence of the APIs.</p>
<p>The specified API Functions and the requirements on their implementation must offer functionality that ensures that users' expectations of privacy and control over their devices are met - this includes, but is not limited to, ensuring that users can control what local devices an application can access for capturing media, and are able to at any time revoke that access.</p>
<p>Similarly, all the deliverables must address issues of security. The security and privacy goals and requirements will be harmonized with those developed by the IETF RTCWeb Working Group.</p>
<p>Similarly, all deliverables must address issues of accessibility
including relevant requirements listed in the <a href="https://w3c.github.io/apa/media-accessibility-reqs/">Media User Accessibility
Requirements document (MAUR)</a>, such as multiple well-synchronized
instances of the same media type. The accessibility goals and requirements
will be developed in coordination with the <a href="https://www.w3.org/WAI/APA/">Accessible Platform Architectures Working Group</a>.</p>
</div>
<div id="ig-other-deliverables">
<h3>
Other Deliverables
</h3>
<p>A comprehensive test suite for all features of a specification is necessary to ensure the specification's robustness, consistency, and implementability, and to promote interoperability between User Agents. Therefore, each specification must have a companion test suite, which should be completed by the end of the Last Call phase, and must be completed, with an implementation report, before transition from Candidate Recommendation to Proposed Recommendation. Additional tests may be added to the test suite at any stage of the Recommendation track, and the maintenance of a implementation report is encouraged. </p>
<p>In particular, since WebRTC deals with communications, specific attention will be brought to the interoperability testing of the WebRTC API implementations (both browser-to-browser and browser-to-native).</p>
<p>Other non-normative documents may be created such as:</p>
<ul>
<li>Primers</li>
<li>Requirements and use case document for specifications</li>
<li>Non-normative group notes</li>
</ul>
<p>Given sufficient resources, this Working Group should review other Working Groups' deliverables that are identified as being relevant to the Working Group's mission. </p>
</div>
<div id="timeline">
<h3>Timeline</h3>
<p>The <a href="https://www.w3.org/2011/04/webrtc/">group's home page</a> provides current data about all of the group's specifications. Although the group expects all of its active deliverables to progress during this charter period, the charter does not include detailed milestone data for each specification because such data is speculative and easily becomes out of date. The Working Group does expect the following to occur:</p>
<ul>
<li>Media Capture and Streams: updated Candidate Recommendation in Q2 2018, Proposed Recommendation in Q4 2018, Recommendation in Q1 2019</li>
<li>WebRTC 1.0: updated Candidate Recommendation in Q2 2018, Proposed Recommendation in Q4 2018, Recommendation in Q1 2019</li>
<li>Object-oriented APIs: First Public Working Draft in Q3 2018, Candidate Recommendation in Q2 2019</li>
</ul>
</div>
</section>
<section id="coordination">
<h2>Coordination</h2>
<p>For all specifications, this Working Group will seek <a href="https://www.w3.org/Guide/Charter.html#horizontal-review">horizontal review</a> for accessibility, internationalization, performance, privacy, and security with the relevant Working and Interest Groups, and with the <a href="https://www.w3.org/2001/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/2017/Process-20170301/#RecsWD" title="First Public Working Draft">FPWD</a> and at least 3 months before <a href="https://www.w3.org/2017/Process-20170301/#RecsCR" title="Candidate Recommendation">CR</a>, and should be issued when major changes occur in a specification.</p>
<p>Additional technical coordination with the following Groups will be made, per the <a href="https://www.w3.org/2017/Process-20170301/#WGCharter">W3C Process Document</a>:</p>
<div>
<h3 id="w3c-coordination">W3C Groups</h3>
<dl>
<dt><a href="https://www.w3.org/WebPlatform/WG/">Web Platform Working Group</a></dt>
<dd>The Web Platform Working Group defines a number of markup elements and APIs that serves as the basis on which the RTC APIs have been developed. In addition, all the APIs developed by this group are based on WebIDL which the Web Platform Working Group is specifying.</dd>
<dt><a href="https://www.w3.org/2009/dap/">Devices and Sensors Working Group</a></dt>
<dd>The Devices and Sensors Working Group develops APIs to access sensors which have similarities with APIs needed to access media devices. The group was also initially involved in the design of the media capture APIs.</dd>
<dt><a href="https://www.w3.org/2011/audio/">Audio Working Group</a></dt>
<dd>The API developed by the Audio Working Group builds upon the <code>MediaStream</code> object built by this group; further collaboration on the management of audio output device is expected.</dd>
<dt><a href="https://www.w3.org/2011/webappsec/">Web Application Security Working Group</a></dt>
<dd>The Web Application Security Working Group is developing guidance on APIs that expose sensitive information, and an API to manage permissions, both of which matter to several of this group specifications.</dd>
<dt><a href="https://www.w3.org/2014/secondscreen/">Second Screen Working Group</a></dt>
<dd>The Second Screen Presentation Working Group is developing APIs to allow rendering of media on secondary devices; potential overlap with features enabled by the Audio Output Devices API will need to be looked at.</dd>
<dt><a href="https://www.w3.org/2013/01/webperf">Web Performance Working Group</a></dt>
<dd>The Web Performance Working Group APIs share goals and characteristics with the WebRTC Statistics API.</dd>
<dt><a href="https://www.w3.org/2011/webtv/">Media and Entertainment Interest Group</a></dt>
<dd>Work on gathering use cases and requirements for Home Networking scenarios within the Media and Entertainment Interest Group may uncover aspects that affect the design of real-time communications functions. The WebRTC Working Group will coordinate with the Interest Group on these use cases and requirements as appropriate.</dd>
</dl>
<h3 id="external-coordination">External Organizations</h3>
<dl>
<dt><a href="https://datatracker.ietf.org/wg/#art">IETF Applications and Real-Time Area</a> (ART)</dt>
<dd>The RTC APIs developed by this group will build upon the protocols and formats developed in the IETF RTCWeb Working Group. Subsequent to the termination of that WG, this WG will liaise with other groups of the ART area and elsewhere in the IETF as appropriate; of particular interest are the MMUSIC, AVTEXT and QUIC working groups.</dd>
</dl>
<dl>
<dt><a href="https://spec.whatwg.org/">Web Hypertext Application Technology Working Group</a> (WHATWG)</dt>
<dd>The RTC APIs developed by this group will potentially reference the Fetch, Streams and other
API specifications maintained by the WHATWG</dd>
</dl>
</div>
</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>
</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/2017/Process-20170301/#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 on a public repository, 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/2011/04/webrtc/">WebRTC Working Group home page.</a>
</p>
<p>
Most WebRTC 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 in its repositories' GitHub issues and on its public mailing list <a href="mailto:public-webrtc@w3.org">public-webrtc@w3.org</a> (<a href="https://lists.w3.org/Archives/Public/public-webrtc/" title="Public archives of the WebRTC mailing-list">archives</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/2017/Process-20170301/#Consensus"> W3C Process Document (section 3.3</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>After mailing list and other informal discussion, substantive change proposals should be submitted as GitHub pull requests. These can come from the editors or from WG members.</p>
<p>Chairs are responsible for determining whether or not there is WG consensus for the changes contained in a pull request.
<p>Editors are responsible for “curating” the pull requests to reject frivolous ones and substantive ones that the Chairs have determined do not comply with the IPR policies.</p>
<p>In cases where the editors make substantive changes without WG consensus, those changes must be labeled as provisional. The chairs are responsible for resolving the status of such changes.</p>
<p>
When the Chair puts a question and observes dissent, after due consideration of different opinions, the Chair should record a decision (possibly after a formal vote) and any objections, and move on.
</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 and/or web-based survey), with a response period from one week to 10 working days, depending on the chair's evaluation of the group consensus on the issue.
If no objections are raised on the mailing list 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 or the Director.
</p>
<p>
This charter is written in accordance with the <a href="https://www.w3.org/Consortium/Process/policies#Votes">W3C Process Document (Section 3.4, Votes)</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://w3.org/Consortium/Patent-Policy-20040205/">W3C Patent Policy</a> (5 February 2004 Version updated 1 August 2017). To promote the widest adoption of Web standards, W3C seeks to issue Recommendations 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/2004/01/pp-impl/">W3C Patent Policy Implementation</a>.
</p>
</section>
<section id="licensing">
<h2>Licensing</h2>
<p>This Working Group will use the <a href="https://www.w3.org/Consortium/Legal/copyright-software">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/groups#GAGeneral">section 5.2</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/2017/Process-20170301/#CharterReview">W3C Process Document (section 5.2.3)</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/2011/04/webrtc-charter.html">Initial Charter</a>
</th>
<td>
5 May 2011
</td>
<td>
30 September 2015
</td>
<td>
N/A
</td>
</tr>
<tr>
<th>
<a href="https://www.w3.org/2015/07/webrtc-charter.html">Rechartered</a>
</th>
<td>
27 July 2015
</td>
<td>
31 March 2018
</td>
<td>
This charter reflected the actual split of the various features identified in well-defined specifications, and added <span class="new">WebRTC NV</span> in scope for the group.
</td>
</tr>
<tr>
<th>
<a class="todo">Rechartered</a>
</th>
<td>
<span class="todo">@@@</span>
</td>
<td>
<span class="todo">@@@</span>
</td>
<td>
<span class="todo">@@@</span>
</td>
</tr>
</tbody>
</table>
</section>
</section>
</main>
<hr />
<footer>
<address>
<a href="mailto:dom@w3.org">Dominique Hazael-Massieux</a>, <a href="mailto:vivien@w3.org">Vivien Lacourba</a>
</address>
<p class="copyright">
<a href="https://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> ©
2011-2018
<a href="https://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup>
(
<a href="https://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>,
<a href="https://www.ercim.eu/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>,
<a href="https://www.keio.ac.jp/">Keio</a>,
<a href="http://ev.buaa.edu.cn/">Beihang</a>
), All Rights Reserved.
<abbr title="World Wide Web Consortium">W3C</abbr> <a href="https://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="https://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="https://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.
</p>
</footer>
</body>
</html>