W3C WebRTC Meetup Update
This is a modal window.
The media could not be loaded, either because the server or network failed or because the format is not supported.
Formal Metadata
| Title |
| |
| Alternative Title |
| |
| Title of Series | ||
| Number of Parts | 542 | |
| Author | ||
| Contributors | ||
| License | CC Attribution 2.0 Belgium: You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor. | |
| Identifiers | 10.5446/61785 (DOI) | |
| Publisher | ||
| Release Date | ||
| Language |
Content Metadata
| Subject Area | ||
| Genre | ||
| Abstract |
|
00:00
Gamma functionGroup actionTable (information)Multiplication signWorld Wide Web ConsortiumSelf-organizationReal-time operating systemMereologyStandard deviationRight angleComputer animation
02:49
OvalGroup actionCommunications protocolWorld Wide Web ConsortiumSelf-organizationMultiplication signForcing (mathematics)CASE <Informatik>Standard deviationStability theoryCartesian coordinate systemClient (computing)Computer animation
04:57
Self-organizationGroup actionElement (mathematics)Local GroupStandard deviationWeb browserStandard deviationWorld Wide Web ConsortiumProcess (computing)Group actionTable (information)Self-organizationCommunications protocolDirection (geometry)Food energyWeb browserComputer animation
07:15
Gamma functionGroup actionLatent heatCartesian coordinate systemWeb browserMotion captureCore dumpTelecommunicationVideoconferencingContent (media)Computer animation
09:45
Personal digital assistantHypermediaMathematical analysisGame theoryStreaming mediaPoint cloudWeb browserInformationWebsiteGroup actionLocal GroupYouTubeVideoconferencingSample (statistics)ImplementationSoftware developerLattice (order)Element (mathematics)ExpressionElectric currentDecision theoryStaff (military)Slide ruleCASE <Informatik>Sampling (statistics)Slide ruleFeedbackImplementationFood energyEvent horizonWeb browserCommunications protocolMathematical analysisArtistic renderingStandard deviationVideoconferencingDifferent (Kate Ryan album)Group actionBroadcasting (networking)Point (geometry)MassRepository (publishing)Software repositoryClient (computing)World Wide Web ConsortiumSoftwareEmailStatement (computer science)Chemical equationYouTubeView (database)Staff (military)Electronic mailing listComputer animation
16:23
Perspective (visual)Traffic reportingGroup actionRight angleLattice (order)Computer animation
17:10
Message passingComputer animation
17:35
Polygon meshTape driveHypermediaNP-hardComputer animationProgram flowchart
Transcript: English(auto-generated)
00:07
We'll show you five. Yeah, yeah, yeah. And just shout if I'm running out of time. Well, everybody, thanks for coming out today. First speaker, always after me, he's going to give us an update on the W3C.
00:22
I forgot to take mine yesterday. A W3C update on WebRTC. Yeah. Yay, great. Hello, everyone. Hello, I'm going to start. So thank you for being here.
00:41
I'm glad to open that Dev Room. It's my first time at FOSDEM, so I'm very happy to be here in front of you. And I ask you to be kind, because I'm not used to present that much. And I'm open to feedback afterward. Just come and see me. Tell me how to improve. I would be very, very happy to hear you.
01:03
OK, my talk is about W3C. Do you know W3C? Who knows that? Raise your hand. OK, that was an easy question for everybody to raise their hand, right? It's a worldwide organization. Everybody knows it. They define standards. And it's quite far from us, right?
01:21
You don't know exactly what happened in that organization. There's big names and serious people around the table discussing things. And eventually, they agree on something that applies to the market. And they've got some working group. And there is one working group, which is about WebRTC.
01:44
OK, who works with WebRTC in the room? OK, that's great. That was also an easy question in the Dev Room real-time communication, right? So there is one working group that defines the standards for us on the market. So I thought that it was quite interesting to understand
02:04
how it works and what are the topics and maybe how to get involved into it so that the future is built by us, right? We are kind of part of the community. And the W3C is about getting the community
02:20
to reach consensus. So it makes sense to be around the table. So in fact, first, I was interested to know more about that organization. And I think that it could be interesting for you, too. By the way, I'm Romain. I work for a company, like everybody, right?
02:40
And I'm a co-organizer at DevFest in my city. Sorry, yeah, yeah, yeah. He's asleep, right. He's back. And I was co-organizer at a meetup that will soon revive, which is called the WebRTC Paris Meetup.
03:01
Soon revive because he's been asleep for a few months, a few years, in fact. And so connect with me if you want to talk about those topics, of course. You can reach me on Twitch every Thursday also. Right, so I talked about that. There has been a standard that enables all the industry
03:23
to agree on a protocol. Let's call the WebRTC standard. And it came only in 2021. So it's very late, in fact. If you are in the WebRTC industry for a while, you use that protocol for a long time.
03:42
2021 is not the beginning. It's kind of the end. So that's kind of what W3C is, is making sure that we agree on something stable. So from that moment, you can build on solid foundations your applications using WebRTC.
04:02
And that's why it's quite interesting. What is quite interesting also is that it's a corporate action across W3C and also IETF. So W3C is kind of the web, the usage of it.
04:20
And the other organization is more about how you structure the protocol, the next working protocol that enable the thing to flow across the clients. So that's quite interesting to join force on that particular topic. So they need to agree together. Like the working group at W3C need to agree also
04:41
with the working group at the IETF. I don't know how to pronounce that anyway. So yeah, happy, we've got a standard. But in fact, there is a lot of use case that are already on the market. So what is the working group doing?
05:00
So that work group, the W3C work group, they accept any individual to contribute or to participate. They also encourage anyone, any company, anyone, any company or any organization to become a member. So as an organization, you might be a company
05:25
that build a solution based on that protocol. Or you can be also a browser editor, for example. You can propose new standards. So that's quite powerful if you're a member. You can propose new standards. And as it's based on consensus, if your proposal
05:43
is a need on the market, you will have a community that will gather around you. And then finally, you can reach that consensus. Otherwise, if your proposal is not needed or is not appropriate, you will certainly
06:00
have rejection from the community or just nobody around you. So you can't reach consensus if there is nobody around you. So that's how it works. It's kind of democratic, in fact. It's having people gathering and trying to get better together. Each working group has leaders.
06:23
So at the W3C, sorry, the WebRTC working group, we've got leaders from Microsoft and Mozilla and I can't remember the third one, like the big players. Maybe Google or maybe not. I can't remember.
06:41
Anyway, so the big players are the leaders. And being a leader is a role that involves you to push forward the group without taking directions. So you need to provide energy to the group. You need to make the whole process to go on and on.
07:03
Make sure that there is a real consensus around the table and trying to, in the end, realize the mission of the working group. So the WebRTC working group has some topics.
07:21
So they worked on different topics in the past. We can have some mature topics that are already deployed in the different solutions, different browsers. So you can recognize those APIs that you might use every day.
07:40
So you can see that those APIs are widely accepted. They are solid. They are fundamental, in fact. So you can build on that. And there are also some topics that are still in discussion, more or less mature, but still in discussion. And those are still moving things.
08:01
You can see quite interesting topics in there, especially topics that are optimization for having better quality, core quality, video quality in your application. So it's more technical things. And also things that are more related to the UX,
08:20
how you will make the UX better when you handle the communication through the WebRTC APIs implemented in the browsers. For example, you've got this one, the capture handle. This is something quite interesting. It's like making sure that when you are in a tab in a browser
08:41
and that you share another tab in the browser, that the two tabs are aware of each other so that you can know that you are sharing a tab on a specific domain, for example, so that you can adapt your behavior as a WebRTC application.
09:02
You can adapt the behavior of your application depending on what is shared. And the contrary also is when you share, when as a tab is shared, the tab knows that it is actually streaming the content somewhere else. So you might also adapt the content of the tab
09:23
depending on that. So that's quite interesting, right? We haven't thought of that quite often. And this topic has been raised by members of the working group. So if you want to raise a topic, you can.
09:41
You can do it. The WebRTC working group is a statement that defines its mission. And in fact, in that statement, that fundamental statement, they try to see what are the use cases that we want to reach.
10:00
And that's also giving a glance of what could be the WebRTC API in the future, or what could be done through that API. So for example, OK, fire sharing, that's a great use case. I don't know what it's so used.
10:24
The funny hats use case, which brings a lot of technical challenges around that. And also bringing resources from the browser to get involved into the WebRTC protocol and the rendering of the videos.
10:45
And you've got those things that are trendy. All these things about analysis of the voice and also the image, they call that face. But we can do maybe a broader perspective with saying, how do we do the analysis?
11:04
How do we bring value to what is done through the channel offered by WebRTC? How do we add intelligence on top of that? So that's in the roadmap. You might already do that in your application,
11:20
trying to make sure that it's quite stable using the APIs that could be provided by your browsers, like Chrome, Chromium, or Firefox, or I don't know which one, Safari, and try to make sure that it's quite balanced. I mean, you try to cover the gaps. So you know that if it's still in discussion as a standard,
11:48
it might move in the future. All right, we've got other use cases, low latency broadcast with P2P relays. That was quite a topic, I think.
12:00
And that's a technical change, which is very high. But you know that it's something that might be addressed by the working group in the near future. So how do you contact? How do you get info? How do you engage with the working group? So that's kind of the API of the working group.
12:22
They've got a website. There is plenty of things. It's an institution. It's an organization for standardization. So it's quite a massive amount of text. But there is also a monthly discussion. So you can just drop by. It's broadcasted on YouTube. So you can drop by and listen to the topics that
12:42
are currently discussed. It's quite technical topics. But it's very interesting to know how it works, like the process of getting a consensus. You've got some samples that you can try on the future implementation. So you've got those topics that are still in discussion.
13:01
And when you go through that process, and at the end of the processes, they try to release some sample, what the standard should look like when you use that in the browser. Or you use it not only in the browser, but most of the samples are in browsers.
13:23
And finally, there is a massive amount of working group repository. It's mainly repositories for handling the modifications of documents. As you want to progress as a standard, you need to agree on a formal documentation of the standard.
13:43
And in fact, those repos are mostly used for making sure that everyone that has an issue can raise a point, and then the point can be discussed. And a proposal can also be done through those repos. If you are only a participant, not a member,
14:02
you can go into that discussion. You can propose things. You don't have the voice. Your voice is not as powerful as if you were a member. But in fact, you can drop your ideas. And for having discussed with them,
14:20
they're quite open with a different point of view. And especially when you are a user of those technologies, they are kind to have some feedback on what they're proposing. How to engage? There is a massive event from the W3C that is happening. In Siberia, which is quite near.
14:42
I mean, it's quite a good place. It will be in September next year. And there is also a mailing list and an IRC channel. How to contribute? They are promoting the thing that you use GitHub
15:01
for for any suggestion. They want to track everything. It's a distributed, decentralized working group. So they want things to be written so that also it's precise. And so that it can be discussed afterwards in a meeting.
15:21
You can propose new topics if you want. For example, I talked about starting something about energy consumption and WebRTC. That might be good. Also to understand how we impact the energy consumption of all the client devices and also maybe in the networks across to understand what is our impact on developing
15:43
new features and trying to get that into the balance when you choose adding new features. And if you want to get more info, I'm not. Yeah, yeah, that's the last slide. I'm about to, sorry, sorry. So I'm not from the W3C, just for you to know.
16:04
But you can reach out to those people. And they are dedicated staff for the WebRTC working group. They are very friendly. They are open for discussion. They can also bring you on the boat. So just reach out to them. And you can find those slides in my GitHub account.
16:22
Thank you. Just in time. OK, OK, OK, OK, OK, OK, OK. Right. Join me on every Thursday at the WebRTC wildcard show. It's on Twitch. Thank you.
16:42
Any question? No. Yes. What are you exactly doing from the perspective of the decentralizing messaging? Me, myself? No, nothing.
17:01
No. No. In fact, so there is no, as far as I know, I went through a lot of reports of what is happening in the working group. And I have not seen much thing about decentralized messaging. But if you want to start something about that,
17:21
they are OK for getting some help. Yeah. Any question? Thank you.
17:42
I'm good. This morning. Yeah, kind of hard.