-
Notifications
You must be signed in to change notification settings - Fork 9
/
Copy pathindex.html
946 lines (931 loc) · 43.6 KB
/
index.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
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
<!DOCTYPE html>
<html lang="en-US">
<head>
<meta charset="utf-8">
<title>
Web & Networks Interest 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>
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">Motivation and Background</a>
</li>
<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 style="list-style: none"></li>
<li>
<a href="#patentpolicy">Patent Disclosures</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 & Networks Interest Group Charter
</h1>
<p class="mission">
The <strong>mission</strong> of the <a href="https://www.w3.org/web-networks/">
Web & Networks Interest Group </a>
is to explore solutions for web applications to leverage network
information and capabilities, and edge compute to achieve better performance
and better efficiency of network resource allocation, both on the device and network.
</p>
<div class="noprint">
<p class="join">
<a href="https://www.w3.org/groups/ig/web-networks/join">Join the Web
& Networks Interest 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/web-networks-charter/">GitHub</a>. Feel free to
raise <a href=
"https://github.com/w3c/web-networks-charter/issues">issues</a>.
</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/ig/web-networks/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>
<th>
End date
</th>
<td>
<i class="todo">CfP + 2 years</i>
</td>
</tr>
<tr>
<th>
Chairs
</th>
<td>
Dan Druta (AT&T);
Sudeep Divakaran (Intel);
Song Xu (China Mobile)
</td>
</tr>
<tr>
<th>
Team Contacts
</th>
<td>
(0.05 FTE)
</td>
</tr>
<tr>
<th>
Meeting Schedule
</th>
<td>
<strong>Teleconferences:</strong> A regular teleconference will be held,
at least quarterly, with additional calls as required. Task Forces may have
separate calls that will not overlap with each other. <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 1 per year.
</td>
</tr>
</table>
</div>
<section id="background" class="background">
<h2>
Motivation and Background
</h2>
<p>
New trends are seen in network traffic patterns due to emerging
new use-cases that leverage computing resources across device,
edge, and cloud that are shaping the focus areas for the Interest Group
charter. These trends are leading indicators of the types of next generation
applications. This also entail new dependencies and challenges to meet expectations
for quality of experience and efficient usage of networking and computing resources.
</p>
<p>A few such trends are highlighted below:</p>
<ul>
<li>
Offloading capabilities that enable efficient usage of compute across Client-Edge-Cloud is gaining traction in
several use-cases. Some of the use-cases are listed in the explainer draft <a href=
"https://w3c.github.io/edge-computing-web-exploration/">Client-Edge-Cloud coordination Use Cases and Requirements</a>.
</li>
<li>
Uplink traffic data patterns have seen a large increase in data sizes and use-case requirements, which is a
shift from the past, where applications data were predominantly in the downlink direction.
The <a href="https://www.ericsson.com/49dd9d/assets/local/reports-papers/mobility-report/documents/2023/ericsson-mobility-report-june-2023.pdf">
Ericsson Mobility Report June 2023</a> highlighted increase in uplink data-intensive
content and growth in data consumption. Uplink-demanding services like XR are re-shaping
how networks need to be deployed for efficient resource utilization.
</li>
<li>
The <a href="https://www.business.att.com/content/dam/attbusiness/guides/att-network-edge-use-cases.pdf">AT&T Network Edge Use-Cases</a> report lists the trends in new use-cases where Edge Networks can play a key role.
</li>
<li>
To succeed in edge computing, a strategy leveraging the latest networking and web standards will be key.
Gartner in its report <a href="https://www.gartner.com/en/documents/4263499">Build an Edge Computing Strategy</a>
highlights the importance of creating and socializing the vision in the eco-system.
</li>
<li>
New advancements in 6G and AI that can leverage peer-to-peer communications, mesh architectures and sustainable modes of communications
will further drive innovations in the Web application space.
</li>
</ul>
</section>
<section id="scope" class="scope">
<h2>
Scope
</h2>
<p>
The Web & Networks Interest Group's scope spans Web and
Networking technologies that can <strong>enhance the quality of
experience of web applications</strong>, by exposing Web APIs that
consider factors such as network performance, device capabilities (e.g. client devices, edge or cloud) for improved
distributed compute and data transfer latencies, while preserving security and privacy requirements.</p>
<p>The scope of the group encompasses both wired and wireless networks.</p>
<p>
Topics and areas that are in-scope for the Interest Group include:
</p>
<ul>
<li>
<strong>Client-Edge-Cloud Coordination</strong> and evolving next generation use-cases
for edge computing, network usage patterns and challenges (e.g., new uplink centric use-cases,
graphics distributed rendering, distributed computing, generative AI applications, etc.).
</li>
<li>
<strong>Application hints to the network</strong> (e.g. ways for applications to
declare their operational wishes to the network). Specifically, the group will
focus on hints (e.g., QoS, user perception metrics) that can be used to optimize
network resource allocation and performance achieve best web application and
network performance. For instance:
<ul>
<li>Latency vs bandwidth trade-offs, for instance high bandwidth
4K video stream, or low latency video call, etc.
</li>
<li>Prediction based hints for look-ahead network resource planning, balancing and allocation.
</li>
</ul>
</li>
<li><strong>Network hints to device applications</strong> to enable migration of compute
functions across the network between client, edge or cloud depending on user experience
and compute requirements, and improved resource utilization.
</li>
<li>
<strong>Evaluation of Privacy and Security risks</strong> of distributed compute-based
solutions and evaluate related mitigation considerations using hardware and software support.
</li>
</ul>
<p>Among those, the primary focus of the group is expected to be on discovering and
defining standardization items on the following topics on:</p>
<ul>
<li>the role of Edge Computing offloading for browsers and Web applications and
study the privacy & security related challenges to enable it;</li>
<li>the role of network performance monitoring and prediction for Web application optimizations;</li>
<li>the role of application hints and network metrics that can enable sustainable and efficient networking solutions, without compromising user-experience.</li>
</ul>
<p>
The tasks that the Interest Group will undertake include:
</p>
<ul>
<li>
<strong>Identify opportunities for network and application
collaborations</strong> that seem like good candidates for
adoption, analyse them in relation to existing standardization
efforts, and, when relevant, build the case for additional and/or
prioritized standardization.
</li>
<li>
<strong>Liaise and coordinate with relevant networking standards
organizations</strong> (esp. ETSI, 3GPP, IETF, etc) to track their
activities and provide them with relevant use
cases and requirements from web applications.
</li>
<li><strong>Collaborate with W3C Working and Interest Groups</strong> on
common use-cases like peer-to-peer or multi-cast content distribution,
edge computing, identifiers, capability discovery, improving diagnostics for
last mile networks, standardization of trace formats for network emulation browser tools, etc.
</li>
<li>
<strong>Share the latest developments in networking
standardization bodies</strong>, comprised of telecommunication
network system vendors and network operators, with the ecosystem of web browsers and
web application developers.
</li>
<li>
<strong>Propose incubation of new work</strong> to identify network-related
parameters from different web applications' requirements,
that can impact the applications networking performance. Also,
consider work on exposing new Web APIs and new Control Messaging
between device and network, to leverage various elements in the
networking path to improve user experience.
</li>
<li>
<strong>Represent knowledge about networking technologies</strong>
and gather data about network deployments to support web
browser developer tools for profiling and performance analysis
under various network conditions.
</li>
<li>
<strong>Analyze secure networking and trust model requirements</strong> needed
in the context of Edge Computing and offload to Edge.
</li>
<li>
<strong>Study measurement techniques to gather data metrics</strong> that can
give insights around Network Efficiency improvement to aid Sustainability and
Power Efficiency.
</li>
<li>
<strong>Provide guidelines to browser developers</strong> on how to
improve web browser developer tools to profile application user
experience impact under different network conditions using new
pre-defined simulation models.
</li>
<li>
<strong>Provide guidelines to web application developers</strong>
on evaluating trade-offs between compute on edge devices
versus on cloud for computation-centric operations, to improve
quality of experience under different radio access type and quality
conditions.
</li>
</ul>
<p>
The Interest Group also provides use cases and requirements to guide
other groups at W3C.
</p>
<div id="section-out-of-scope">
<h3 id="out-of-scope">
Out of Scope
</h3>
<p>
The technical development of standards is not in scope for the
Interest Group. Technical specification discussions are expected to take place
within the appropriate W3C groups if such a group exists, or within
a dedicated Community Group when incubation is
needed.
</p>
</div>
<div>
<h3 id="success">
Success Criteria
</h3>
<p>
The Interest Group will have succeeded if it can achieve the
following:
</p>
<ul id="stakeholders">
<li>Participation from various stakeholder communities, including
browser vendors, media professionals, cloud providers, hardware and software
developers, telecommunications companies, cable operators, application
developers, regulators, and users.
</li>
<li>Members of the Interest Group join relevant W3C Groups and
drive the development of work items.
</li>
<li>Engagement and coordination with other organizations in the
Telecommunications, Edge Computing, Media, Security and Internet industries to recommend and coordinate
technical standards development and promote adherence to W3C and/or
other standards.
</li>
</ul>
</div>
</section>
<section id="deliverables">
<h2>
Deliverables
</h2>
<p>Updated document status is available on the <a href="https://www.w3.org/groups/ig/web-networks/publications">group publication status page</a>.</p>
<ul>
<li>The primary deliverables of the Web & Networks Interest Group are
IG Notes that identify
<ol>
<li>List of new use-cases and innovations in networking domain that can benefit Web applications</li>
<li> Identify use-cases which require innovative solutions to improve sustainability and optimal network energy utilization.</li>
<li>Requirements for existing and/or new technical specifications</li>
<li>Gap-analysis between use-case requirements and current Web Platform standards</li>
</ol>
</li>
<li>The group will also maintain a public list of the network-related
features on the Web that it is tracking and investigating. These
features will include identified gaps, stable features deployed in
browser implementations, as well as features under development in W3C
and external groups.
</li>
</ul>
<div id="normative">
<h3>
Normative Specifications
</h3>
<p>
The Interest Group will not deliver any normative specifications.
</p>
</div>
<div id="ig-other-deliverables">
<h3>
Other Deliverables
</h3>
<p>
Other non-normative documents may be created such as:
</p>
<ul>
<li>Primer or Best Practice documents to support web developers
when designing applications.
</li>
</ul>
<p> As of the day of chartering, the Web and Networks Interest Group is working on the following document:
<ul>
<li><a href="https://www.w3.org/TR/edge-cloud-reqs/">Client-Edge-Cloud coordination Use Cases and Requirements</a> aims to introduce the use cases and requirements of a client, edge, and cloud coordination mechanism and its standardization.</li>
</ul>
</div>
<div id="timeline">
<h3>
Timeline
</h3>
<p>The IG will, during its lifetime, undertake different activities that may proceed in parallel.
This will include presentations by external Guest speakers or IG members (at least once per quarter) on
upcoming technologies in Wireless and Wired Telecommunication Standards and new trends in Use-cases.</p>
<ul>
<li>Identify and define requirements for the discovery and capability description of network nodes used
to offload web based workloads to the edge. Findings, analysis and requirements document with Q3 2024 delivery.</li>
<li>Organize a W3C Workshop in H2 2025 to consolidate new use-cases, requirements and respective cost-benefit analysis,
and document outcome in a Whitepaper.</li>
</ul>
</div>
</section>
<section id="coordination">
<h2>
Coordination
</h2>
<p>
For all deliverables, this Interest Group will seek <a href="https://www.w3.org/Guide/documentreview/#how_to_get_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 document transition, including <a href="https://www.w3.org/Consortium/Process/#RecsWD" title="First Public Working Draft">FPWD</a> and <a href="https://www.w3.org/Consortium/Process/#WGNote">IG Note</a>.
The Interest Group is encouraged to engage collaboratively with the horizontal review groups throughout the development of each deliverable.
The Interest Group is encouraged to proactively notify the horizontal review groups when major changes occur in its technical reports following a review.
</p>
<p>Each Note or transmission of proposed work should contain a section detailing all known
security and privacy implications for implementers, Web authors, and end users as well as recommendations for mitigations.
There should be a clear description of the residual risk
to the user or operator of that protocol
after threat mitigation has been deployed.</p>
<p>This Interest Group expects to follow the
TAG <a href="https://www.w3.org/TR/design-principles/">Web Platform Design Principles</a>.
</p>
<p>
Potential technical coordination and evaluation with the following Groups will be
made, per the <a href=
"https://www.w3.org/Consortium/Process/#WGCharter">W3C Process
Document</a>. This is not an exhaustive list and new collaborations with W3C
Groups or external groups may be included as appropriate.
</p>
<div>
<h3 id="w3c-coordination">
W3C Groups
</h3>
<dl>
<dt>
<a href="https://www.w3.org/WoT/IG/">Web of Things Interest
Group</a>
</dt>
<dd>
Web of Things depends on networking technologies on the edge and in
the cloud when exposing interactions between Things, which can also include
Edge devices. The Web & Networks IG should coordinate with Web of Things IG to
ensure future work considers networking parameters that impact communication and
performance in both IoT and edge compute offload like use-cases. The group should
also evaluate extending Thing Description for Edge Compute Devices.
</dd>
<dt>
<a href="https://www.w3.org/2017/03/webtv-charter.html">Media and
Entertainment Interest Group</a>
</dt>
<dd>
The Media and Entertainment Interest Group's scope covers Web
technologies used in the end-to-end pipeline — including capture,
production, distribution and consumption — of continuous media
and their associated technologies such as timed text.
</dd>
<dt>
<a href="https://www.w3.org/das/">Devices and Sensors Working
Group</a> and <a href="https://wicg.io/">Web Incubator Community
Group</a>
</dt>
<dd>
The Devices and Sensors Working Group (DAS WG) defines
client-side APIs that enable the development of Web Applications
that interact with device hardware and sensors. The
<a href="https://w3c.github.io/sensors/">Generic Sensor API</a>
defines a framework for exposing sensor data to the web platform
in a consistent way. Sensors produce high frequency data that
sets low latency requirements for delivery over the network.
</dd>
<dt>
<a href="https://www.w3.org/webperf/">Web Performance Working Group</a>
</dt>
<dd>
The Web Performance Working Group's scope of work includes user agent
features and APIs to observe and improve aspects of application performance,
such as measuring network and rendering performance, responsiveness and
interactivity, memory and CPU use, application failures, and similar APIs
and infrastructure to enable measurement and delivery of better user experience.
The Web & Networks IG will discuss ways to improve application performance under varying
network conditions or new content delivery infrastructures (e.g. Edge Computing).
</dd>
<dt><a href="https://www.w3.org/2018/distributed-tracing/">Distributed Tracing Working Group</a></dt>
<dd>The Distributed Tracing Working Group defines standards for interoperability between tracing tools to enable propagation and correlation of tracing data across different implementations. The Web & Networks IG will coordinate with this group on topics around standardizing trace formats for potential network emulation browser tools.</dd>
<dt>
<a href="https://www.w3.org/2011/04/webrtc/">Web Real-Time
Communications Working Group</a>
</dt>
<dd>
The Web Real-Time Communications Working Group works on the
WebRTC Next Version (WebRTC-NV). The Web & Networks IG should
coordinate with this group to ensure the <a href=
"https://w3c.github.io/webrtc-nv-use-cases/">next version use
cases</a> can be implemented efficiently considering requirements
on the networks such as exchange of large files without
disruption to audio/video sessions, maintain a long-term
connection and seek to minimize power consumption. Secondarily,
explore implications of the new transport protocols such as the
QUIC.
</dd>
<dt><a href="https://www.w3.org/groups/wg/webtransport">WebTransport Working Group</a></dt>
<dd>The WebTransport Working Group develops APIs that enable data transfer between browsers and servers with support for multiple streams, unidirectional streams, out-of-order delivery, variable reliability and pluggable protocols.</dd>
<dt>
<a href=
"https://www.w3.org/groups/wg/webmachinelearning/">Web Machine
Learning Working Group</a>
</dt>
<dd>
The Web Machine Learning Working Group develops an API
for machine learning inference in the browser. The Web & Networks
IG should coordinate with this group to explore on how to load
balance computing between cloud-based and client-side machine
learning using network hints including bandwidth and latency,
radio power consumption, and available computing power and
battery on the client.
</dd>
<dt><a href="https://www.w3.org/groups/wg/auto/">Automotive Working Group</a></dt>
<dd>
The automotive segment is leveraging network connectivity to Edge and Cloud services
for its in-vehicle services and autonomous driving solutions. The Web & Networks IG
will engage with Automotive WG to explore new use-cases in the areas of wireless
networking and edge computing in the automotive sector.
</dd>
<dt><a href="https://www.w3.org/2019/did-wg/">Decentralized Identifier Working Group</a></dt>
<dd>
The Decentralized Identifier Working Group scope is to standardize the DID URI scheme,
the data model and syntax of DID Documents. For the networking and distributed edge
computing use-cases analyzed within the Web & Networks IG, the IG will coordinate with
DID WG to explore the potential of DID and suitable solutions to address the use-case requirements.
</dd>
<dt><a href="https://www.w3.org/WAI/APA/">Accessible Platform Architectures Working Group</a></dt>
<dd>The Web & Network Interest Group will seek guidance from the APA Working Group to ensure the
accessibility of protocol and interactions of possible technical solutions be taken into account
early in their design process.</dd>
</dl>
<h3 id="external-coordination">
External Organizations
</h3>
<dl>
<dt>
<a href="https://www.3gpp.org/">3GPP</a>
</dt>
<dd>
The 3rd Generation Partnership Project (3GPP) unites
telecommunications standards development organizations (ARIB,
ATIS, CCSA, ETSI, TSDSI, TTA, TTC), known as “Organizational
Partners” and provides their members with a stable environment to
produce the Reports and Specifications that define 3GPP
technologies.
</dd>
<dt>
<a href="https://www.arib.or.jp/english/">ARIB</a>
</dt>
<dd>
The Association of Radio Industries and Businesses is aimed to
conduct investigation, research & development and consultation of
utilization of radio waves from the view of developing radio
industries, and to promote realization and popularization of new
radio systems in the field of telecommunications and
broadcasting.
</dd>
<dt>
<a href="https://www.etsi.org/">ETSI</a>
</dt>
<dd>
The European Telecommunications Standards Institute produces
globally-applicable standards for Information and Communications
Technologies (ICT), including fixed, mobile, radio, converged,
broadcast and internet technologies.
</dd>
<dt>
<a href="https://www.ieee.org/">IEEE</a>
</dt>
<dd>
Institute of Electrical and Electronics Engineers (IEEE) develops
a family of IEEE 802.11 standards that cover Wireless LAN
technology.
</dd>
<dt>
<a href="https://www.ietf.org/">IETF</a>
</dt>
<dd>
Internet Engineering Task Force is an open-standards development
organization which develops and promotes Internet standards,
cooperating closely with the W3C and ISO/IEC standards bodies and
dealing in particular with standards of the TCP/IP and Internet
protocol suite. Relevant IETF work include e.g. <a href=
"https://httpwg.org/http-extensions/client-hints.html">HTTP
Client Hints</a> for proactive content negotiation.
</dd>
<dt>
<a href="https://www.gsma.com/">GSMA</a>
</dt>
<dd>
The GSMA represents the interests of mobile operators worldwide,
uniting more than 750 operators with over 350 companies in the
broader mobile ecosystem, including handset and device makers,
software companies, equipment providers and internet companies,
as well as organisations in adjacent industry sectors.
</dd>
<dt>
<a href="https://www.itu.int/ITU-T/">ITU-T</a>
</dt>
<dd>
ITU Telecommunication Standardization Sector is the part of the
UN agency ITU that defines elements in information and
communication technologies infrastructure. Their work includes
Multimedia Application Framework for IPTV services. For example,
H.762: Lightweight interactive multimedia framework for IPTV
services (LIME) gives a subset of HTML, CSS and ECMAScript for
use in IPTV terminals.
</dd>
<dt>
<a href="https://metaverse-standards.org/">Metaverse Standards Forum</a>
</dt>
<dd>Metaverse Standards Forum is a venue for cooperation between standards organizations
and companies to foster the development of interoperability standards for an open and
inclusive metaverse, and accelerate their development and deployment.
</dd>
<dt>
<a href="https://www.iso.org/committee/45316.html">ISO/IEC JTC 1/SC 29</a>
</dt>
<dd>
ISO/IEC JTC 1/SC 29 is in
charge of the development of standards for coded representation
of digital audio, video and related data.
</dd>
</dl>
</div>
</section>
<section class="participation">
<h2 id="participation">
Participation
</h2>
<p>
To be successful, this Interest Group is expected to have 6 or more
active participants for its duration, including representatives from
the <a href="#stakeholders">key stakeholders identified above</a>.
The Chairs and Task Force leaders are expected to contribute half of a working day per
week towards the Interest 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/Consortium/cepc/">Code of Ethics and Professional Conduct</a>.</p>
</section>
<section id="communication">
<h2>
Communication
</h2>
<p id="public">
Technical discussions for this Interest 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. Drafts of its documents 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) is
available from the <a href="https://www.w3.org/groups/ig/web-networks/">Interest Group home page</a>.
</p>
<p>
Most Interest 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 the public mailing list
<a id="public-name" href=
"mailto:public-networks-ig@w3.org">public-networks-ig@w3.org</a> (<a href=
"https://lists.w3.org/Archives/Public/public-networks-ig/">archive</a>)
and on <a id="public-github" href=
"https://github.com/w3c/web-networks/issues">GitHub issues</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 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 Interest 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/policies#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 Disclosures
</h2>
<p>
The Interest Group provides an opportunity to share perspectives on
the topic addressed by this charter. W3C reminds Interest Group
participants of their obligation to comply with patent disclosure
obligations as set out in <a href=
"https://www.w3.org/Consortium/Patent-Policy/#sec-Disclosure">Section
6</a> of the W3C Patent Policy. While the Interest Group does not
produce Recommendation-track documents, when Interest Group
participants review Recommendation-track specifications from Working
Groups, the patent disclosure obligations do apply. 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 Interest 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/#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/2019/05/web-networks-ig-charter.html">Initial Charter</a>
</th>
<td>
2019-05-15
</td>
<td>
2020-12-31
</td>
<td>
First charter
</td>
</tr>
<tr>
<th>
<a href="https://lists.w3.org/Archives/Public/public-new-work/2020Dec/0007.html">Charter Extension</a>
</th>
<td>
</td>
<td>
30 April 2021
</td>
<td>
Needed to finalize new charter incorporating TPAC 2020 feedback
</td>
</tr>
<tr>
<th>
<a href="https://www.w3.org/2021/04/web-networks-charter.html">New Charter</a>
</th>
<td>
2021-04-08
</td>
<td>
2023-04-30
</td>
<td>
<ul>
<li>Updated scope based on group's workstreams around distributed compute linked use-cases</li>
<li>Included study of network hints to applications as a dedicated topic in the scope section, based on group’s current activities</li>
<li>Updated scope of web metrics identification and evaluation topic to include privacy analysis</li>
<li>Updated the list of tasks to include collaboration with specific W3C groups interested to leverage edge compute and networking elements like network information, diagnostic APIs and tools for their use-cases</li>
<li>Expanded the primary deliverables by splitting them into three key items – new use-cases, requirements and gap-analysis</li>
</ul>
</td>
</tr>
<th>
<a href="https://lists.w3.org/Archives/Public/public-new-work/2023Apr/0014.html">Charter Extension</a>
</th>
<td>
2023-04-27
</td>
<td>
2023-10-31
</td>
<td>
Charter extended
</td>
</tr>
<tr>
<th>
<a>Recharter Proposal</a>
</th>
<td>
2023-11-01
</td>
<td>
2025-10-31
</td>
<td>
<ul>
<li>Updated mission statement to include exploration of solutions to improve network resource allocation
and efficiency, and leveraging of new technologies like edge computing </li>
<li>Added Background section</li>
<li>Under Scope section, included Client-Edge-Cloud Coordination as a new topic </li>
<li>Added two study tasks around trust model and network resource utilization in Scope section</li>
</ul>
</td>
</tr>
</tbody>
</table>
</section>
</section>
</main>
<hr>
<footer>
<address>
<a href="mailto:dom@w3.org">Dominique Hazael-Massieux</i>
</address>
<p class="copyright">Copyright © 2023 <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/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
<a href="https://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and
<a rel="license" href="https://www.w3.org/Consortium/Legal/2015/copyright-software-and-document" title="W3C Software and Document Notice and License">permissive document license</a> rules apply.</p>
<hr>
<p>
<a href="https://github.com/w3c/web-networks-charter/">Yes, it's on
GitHub!</a>.
</p>
</footer>
</body>
</html>