14:02:40 <RRSAgent> RRSAgent has joined #web-networks
14:02:40 <RRSAgent> logging to https://www.w3.org/2022/03/04-web-networks-irc
14:03:07 <dom> Present+ Dom, Sudeep, DanDruta, LarryZhao, Uaqi, MichaelMcCool, PiersO'Hanlon, PeipeiGuo, SongXu
14:03:53 <dom> Meeting: Web & Networks IG #21: Edge Computing
14:04:12 <sudeep> sudeep has joined #web-networks
14:04:22 <dom> Agenda: https://lists.w3.org/Archives/Public/public-networks-ig/2022Mar/0000.html
14:04:32 <dom> Chair: Song, Sudeep, Dan
14:05:52 <dom> Sudeep: Welcome to this new IG call; there has been activity over the past 2 months on which it's useful to share updates
14:05:56 <McCool> McCool has joined #web-networks
14:07:04 <dom> ... today's agenda includes general updates, and then a focus on edge computing
14:07:07 <Eric_Siow> Eric_Siow has joined #web-networks
14:07:22 <dom> ... first a presentation on the value proposition of offload for stakeholders
14:07:38 <Peipei_Guo> Peipei_Guo has joined #web-networks
14:07:41 <dom> ... then a review of the use cases and requirements with PRs that have been raised
14:08:10 <dom> Topic: General updates
14:08:27 <dom> Sudeep: TPAC may be an hybrid event in September, with physical location in Vancouver
14:08:49 <dom> ... any thoughts on TPAC, feasibility for a potential IG meeting?
14:09:08 <Eric_Siow> q+
14:09:40 <dom> Michael: I'm based in Canada so can reach Vancouver fairly easily, but only meaningful if there is enough people showing up
14:09:43 <dom> ... maybe simpler to stay to virtual only
14:09:58 <dom> ack Eric_Siow
14:10:33 <dom> eric: my personal feeling: the past 2 years of zoom meetings have impacted the value of F2F meetings, relationship building, etc
14:11:14 <dom> DanD: +1 to eric
14:11:30 <dom> ... The IETF is having a hybrid in Vienna - we're going to see how that works out
14:11:48 <dom> ... getting back to F2F would a boost to our ability to cooperate
14:11:57 <dom> ... personally, Vancouver should be reasonably easy to reach
14:11:59 <dom> q+
14:14:47 <McCool> q+
14:15:57 <McCool> ack d
14:16:57 <dom> dom: with TPAC built for hybrid, but with China not being able to travel, a short hybrid meeting in TPAC combined with lots of discussions for those that can travel would be most valuable
14:17:06 <McCool> ack m
14:17:21 <dom> McCool: let's also discuss this over email
14:17:47 <dom> Subtopic: joint meeting with Games CG
14:17:58 <dom> Sudeep: we met with the Games CG  a couple of weeks ago
14:18:11 <dom> ... Song presented the work of the IG, and the CG participants shared their perspective
14:18:26 <dom> ... highlighted the distinction between indy vs AAA games, with varying impact of network
14:18:58 <dom> ... overall, the topics of latency, monitoring are ones they look at
14:19:13 <dom> ... we opened up the conversation around edge
14:19:15 <dom> q+
14:20:57 <Eric_Siow> q+
14:21:32 <dom> dom: they noted that the dependency on network and the interest on edge was more likely for AAA games
14:21:52 <dom> ... also, hoping to be able to share a summary from one of the CG participants around the current limitations of network APIs on the Web
14:22:28 <dom> Song: received interest on our Web & Networks IG presentation from Chinese colleagues who got it translated and shared on the W3C Chinese community
14:23:22 <dom> ... which triggered further interest, e.g. from https://dappworks.cn
14:24:47 <dom> eric: the CG didn't seem to spend a lot time on AAA games
14:24:49 <McCool> q+
14:24:53 <dom> ack me
14:24:54 <dom> ac Eric_Siow
14:25:24 <McCool> ack m
14:25:34 <dom> ack Eric_Siow
14:25:52 <dom> ... We need to find problem statement that resonates to a broader set of stakeholders
14:26:09 <dom> ... including with more outreach
14:27:29 <dom> Topic: Edge Computing and the Web
14:28:18 <dom> McCool: this slideset is about setting up the problem
14:28:28 <dom> ... skipping the first slides in the interest of time
14:28:44 <dom> ... we need to gather and organize use cases
14:28:53 <dom> ... but my focus today is how to organize stakeholders
14:29:02 <dom> [slide 9]
14:29:53 <dom> ... Rather than looking at specific companies, we're looking at business models with which our problem statements resonate, which I've organized in categories
14:30:06 <dom> ... some companies cumulate 5 or 6 of these models
14:32:56 <dom> [slide 10]
14:33:21 <dom> ... then for each of these business models, I look at what opportunities would emerge from solving the issue at hand
14:33:32 <dom> ... business opportunities specifically
14:36:04 <dom> ... I plan to bring this as PR to the use cases document
14:37:07 <dom> ... we've starting validating with specific companies on whether this matches their pain points
14:37:22 <dom> Dom: I like the model & the categories
14:37:39 <dom> Max: good starting point - we need to validate this with industry stakeholders
14:37:53 <dom> ... to reflect real industry input
14:38:08 <dom> McCool: let's iterate on corrections via a pull request
14:38:22 <dom> ... once it's in the document, we can iterate with feedback from other companies
14:38:28 <dom> Dom: +1
14:38:30 <dom> Max: sure
14:39:04 <dom> Song: I'm interested in the categories and descriptions of stakeholders
14:39:41 <dom> ... the developers I'm in touch with may not necessarily have great clarity on business considerations
14:39:58 <dom> ... this content will help them with moving the conversations with their business people
14:40:58 <dom> McCool: we'll also to include the fact that some companies will consider the edge as a threat to their business
14:41:08 <dom> [slide 11]
14:41:31 <dom> McCool: we'll want to derive requirements from use cases, with security & privacy applied throughout
14:42:15 <dom> ... I have prepared a PR that extends the requirements table, some of which has a dependency on the use cases PR
14:43:13 <dom> ... part of what we discuss is prioritizing use cases, which may lead to a prioritization of requirements
14:43:35 <dom> ... I've given a short name to each requirement to make it easier to refer to them
14:43:55 <dom> ... We'll also need a terminology section (e.g. edge cloud / edge resource / edge client)
14:44:56 <dom> -> https://github.com/w3c/edge-computing-web-exploration/pull/6 Expand Requirements Table PR
14:45:05 <dom> ... [review expanded requirements from PR]
14:49:57 <dom> Max: I've brought a PR with additional use cases, incl on Video Conference where edge may help a mobile terminal with more limited resources
14:51:58 <dom> -> https://github.com/w3c/edge-computing-web-exploration/pull/4 Pull request: Add more use cases #4
14:52:12 <dom> ... [review other proposed additional use cases]
14:52:40 <McCool> q+
14:52:50 <dom> ... We need some mechanism to deal with the PR - if no objection, I'm happy to merge them
14:52:55 <dom> ... we could also organize ad-hoc meetings
14:53:27 <dom> ... I'm happy to help with the mechanics of repo management
14:53:46 <dom> McCool: +1 on having someone responsible for merging
14:54:03 <dom> ... and then iterate with one-on-one meetings if needed
14:54:15 <dom> Max: will do
14:56:55 <dom> dom: thanks a lot for moving forward; we should look towards getting this published as first public interest group note
14:57:15 <dom> ... the chairs and I will caucus to support you towards that
14:57:39 <dom> Sudeep: Michael, you raised an issue about terminology - any plan on how to address it?
14:58:33 <dom> Michael: I can create a PR for the basic structure for the terminology
14:58:55 <dom> ... I'm looking for input on terms that need definitions
14:59:32 <McCool> q+
14:59:46 <dom> sudeep: any other W3C group that may have define these terms?
15:00:02 <dom> dom: probably not in W3C; but we should re-use external definitions where they match our needs
15:00:24 <dom> mccool: part of the challenges is that there are so many definitions to choose from
15:00:47 <dom> dand: re business models, one of the challenges is that it really matters who "pays" for the edge resources
15:00:56 <dom> ... on whose behalf is the resource allocation done
15:01:10 <dom> ... e.g. if the client does it, it's usually associated to caching / optimization proxy
15:01:19 <dom> ... when the server does it, it's associated more with a CDN
15:01:29 <dom> ... understanding that dynamic is critical for the Web
15:01:47 <dom> ... also key to the trust model
15:01:51 <dom> mccool: 100% agree
15:02:05 <dom> ... under security, one of the requirements will be who has control, who do I trust and why
15:02:23 <dom> RRSAgent, draft minutes
15:02:23 <RRSAgent> I have made the request to generate https://www.w3.org/2022/03/04-web-networks-minutes.html dom
15:02:28 <dom> RRSAgent, make log public
15:02:35 <McCool> ack m
15:03:03 <dom> Sudeep: thank you all for the progress and plan for moving forward
15:03:45 <dom> RRSAgent, draft minutes
15:03:45 <RRSAgent> I have made the request to generate https://www.w3.org/2022/03/04-web-networks-minutes.html dom
15:05:24 <Karen> Karen has joined #web-networks
16:27:39 <dom> Slideset: https://lists.w3.org/Archives/Public/www-archive/2022Mar/0000.html
16:27:41 <dom> RRSAgent, draft minutes
16:27:41 <RRSAgent> I have made the request to generate https://www.w3.org/2022/03/04-web-networks-minutes.html dom
16:29:03 <dom> i|Topic: Edge|Slideset: https://lists.w3.org/Archives/Public/www-archive/2022Mar/0000.html
16:29:06 <dom> RRSAgent, draft minutes
16:29:06 <RRSAgent> I have made the request to generate https://www.w3.org/2022/03/04-web-networks-minutes.html dom
16:30:06 <dom> s|0000.html|att-0000/Edge_Web-WNIG-Mar2022-McCool.pdf|g
16:30:07 <dom> RRSAgent, draft minutes
16:30:07 <RRSAgent> I have made the request to generate https://www.w3.org/2022/03/04-web-networks-minutes.html dom
16:31:02 <dom> s/slide 9/slide 4
16:31:05 <dom> s/slide 10/slide 5
16:31:08 <dom> s/slide 11/slide 6
16:31:10 <dom> RRSAgent, draft minutes
16:31:10 <RRSAgent> I have made the request to generate https://www.w3.org/2022/03/04-web-networks-minutes.html dom
16:32:31 <dom> Present+ Max, Eric
16:32:32 <dom> RRSAgent, draft minutes
16:32:32 <RRSAgent> I have made the request to generate https://www.w3.org/2022/03/04-web-networks-minutes.html dom
17:18:33 <Karen> Karen has joined #web-networks
18:42:51 <Karen> Karen has joined #web-networks