Roadmap

[Sean-Der]

This is a covering ticket for the Pion WebRTC roadmap. If you have any requests feel free to leave them here/vote on others.

Planet Strike -- 1.0.0 (2018-06-20)

• SRTP (in Go)
• ICE-lite (We only respond to binding requests, requires host candidates. No STUN or TURN)
• DTLS (In C, using OpenSSL)
• API that allows users to receive media that closely matches the Javascript WebRTC API
• API that allows users to send media that closely matches the Javascript WebRTC API

Aliens of Gold -- 1.1.0 (2018-09-00)

• DataChannels
• STUN
• Full ICE (currently ice-lite only)
• Bundling

Quest for the Sigil -- 1.2.0 (2018-12-00)

• Port DTLS to Go from cgo (currently using OpenSSL)
• Mobile Support
• Transport Refactor

Spear of Destiny -- 2.0.0 (2019-04-00)

• ORTC
• Unified Plan
• DataChannel improvements (configurable reliability)
• Logging and ICE debugging
• Experimental QUIC support
• Experimental WebAssembly (WASM) support
• API Cleanup to better match the WebRTC Spec.
• Reliability improvements to SCTP and therefore Data Channels.
• ICE Regular Nomination

Beyond Heretic -- 2.1.0 (2019-08-00)

• TURN
• Trickle ICE
• mDNS Candidates

The HUNT Begins - 2.2.0 (2019-11-00)

• SCTP Performance Improvements (16x in some cases!)
• Extend SettingEngine to support SFU use cases
• TCP TURN Support
• PCM Support
• Add/Remove tracks at runtime
• IVF Reader to enable saving to disk

Future Shock - 3.0.0 (2020-12-14)

• ICE Restarts
• ICE TCP Candidates
• Remove non-Trickle ICE. Provide utility that emulates old behavior.
• SRTP AEAD_AES_128_GCM. Significant performance improvement in media crypto!
• Simulcast.
• Improved Media API so user doesn't need to managed PayloadType and SSRC
• Interceptor API that allows users to implement NACK, FEC and Congestion Control via Public API

Plutonia - 3.1.0 (2021-08-01)

• Transport Wide Congestion Control Interceptor, better Congestion Control then Sender+Receiver Reports
• H265 Packetizer
• FireFox Simulcast Support
• Sender/Recevier Report interceptors, can be used in pion/webrtc or outside
• UDPMux, Multiple PeerConnections can be served via the same UDP Port

System Shock 3.2.0 (2023-04-25)

• Congestion Control Interceptor
• AV1 Support
• Simulcast Sender
• Stats Interceptor

4.0.0 (2024-10-01)

• Active ICE TCP
• JitterBuffer Interceptor

No date picked

• Serialize/Deserialize PeerConnection API
• DTLS Restart
• Performance/Allocation testing to GitHub Actions
• Auto Change log generation/Remove manual process of releasing
• Automate fuzz testing, submit Pion to oss-fuzz
• H264 Interceptor (Analyze and attempt to fix common issues like no SPS/PPS with every IDR)
• Harden security (fuzzing and other automated tooling)
• TinyGo support. Pion for IoT devices

---

These things are ordered in the importance we have gotten from feedback. If you are building something and need a feature sooner please comment and we can move things around!

[notedit]

It seems it is a webrtc golang version. Any plan on SFU media server?

[Sean-Der]

Hey @notedit

Currently no, we may build an SFU using pions-WebRTC in the future though. You are right though, pions-WebRTC is a Golang version of libwebrtc (instead we don't use any libraries)

The goal is that people will be able to just do one go build and not have to worry about anything else, and other cool things like that!

If you do want to build an SFU would love to help! Can add features/debug things as needed

[notedit]

Thanks, I may try SFU media server based on your lib. Great work.

Dumb question ! Whats an SFU - am curious.... got a good link ?

…

On Mon, 18 Jun 2018 at 10:57 notedit ***@***.***> wrote: Thanks, I may try SFU media server based on your lib. Great work. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#9 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ATuCwr6MNYloOIZSGBOyCK2AipNk3l7mks5t92t2gaJpZM4UloWh> .

https://bloggeek.me/webrtc-multiparty-video-alternatives/ ?

…

On Mon, 18 Jun 2018 at 11:17 Ged Wed ***@***.***> wrote: Dumb question ! Whats an SFU - am curious.... got a good link ? On Mon, 18 Jun 2018 at 10:57 notedit ***@***.***> wrote: > Thanks, I may try SFU media server based on your lib. Great work. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <#9 (comment)>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/ATuCwr6MNYloOIZSGBOyCK2AipNk3l7mks5t92t2gaJpZM4UloWh> > . >

it looks to me like an SFU scales out better ?

…

On Mon, 18 Jun 2018 at 11:18 Ged Wed ***@***.***> wrote: https://bloggeek.me/webrtc-multiparty-video-alternatives/ ? On Mon, 18 Jun 2018 at 11:17 Ged Wed ***@***.***> wrote: > Dumb question ! Whats an SFU - am curious.... > got a good link ? > > On Mon, 18 Jun 2018 at 10:57 notedit ***@***.***> wrote: > >> Thanks, I may try SFU media server based on your lib. Great work. >> >> — >> You are receiving this because you are subscribed to this thread. >> Reply to this email directly, view it on GitHub >> <#9 (comment)>, or mute >> the thread >> <https://github.com/notifications/unsubscribe-auth/ATuCwr6MNYloOIZSGBOyCK2AipNk3l7mks5t92t2gaJpZM4UloWh> >> . >> >

[Sean-Der]

@gedw99 An SFU is so your users only have to upload video once (and can selectively download)

this is a good visualization

Thank you - appreciated the learning. This is really a great system. I will be helping. I think I can build a flutter GUI for mobile and desktop. If you want something like this as a PR let me know.

…

On Tue, 19 Jun 2018, 07:32 Sean DuBois, ***@***.***> wrote: @gedw99 <https://github.com/gedw99> An SFU is so your users only have to upload video once (and can selectively download) this <https://thenewdialtone.com/wp-content/uploads/2016/04/SFU-Video-Conferencing.jpg> is a good visualization — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#9 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ATuCwh-Otx3SlTD9aReAFkOeXV1SzgxKks5t-IzzgaJpZM4UloWh> .

[shazow]

Pretty excited about this. Personally I'm waiting for DataChannel support.

Many p2p projects (libp2p/ipfs, openbazaar, etc) rely on datachannels to create DHTs of peers, and end up having segregated networks between browser-based WebRTC peers vs native UDP-based peers, only being able to talk to each other over bridges that support both (usually NodeJS).

Having a robust Go-native WebRTC implementation with DataChannel support would be a huge milestone for all of these projects. Most of these projects are written in Go, too.

libp2p/go-libp2p#188 for example.

[Sean-Der]

@shazow Hey thanks for checking us out :)

Just moved it up! I will work on datachannels right after I finish sending video. I have had multiple people reach out to me about wanting that the most, so seems the right choice.

I will try to reach out to any projects that are looking for datachannels. It would be great if they had input on what features they needed most, so I could get it good enough as soon as possible.

[silbinarywolf]

Hey @Sean-Der, very very keen to see Data Channels implemented in this library as I'm aiming to build a real-time browser-based game in Golang.

I want Data Channels / UDP to avoid hitches and non-responsiveness when building games with an authoritative server model.
(Source if you're interested: https://new.gafferongames.com/post/why_cant_i_send_udp_packets_from_a_browser/ )

As of right now, there's no "off the shelf" libraries I can use to get here. The only other library that seemed reasonable was keroserene/go-webrtc, but unfortunately it has no pre-built Windows binaries so it's a non-starter for me as I dev' on Windows.

If donations will help get this done quicker, I'm more than happy to contribute some money!

All. Did you also see that the libp2p library also now has QUIC.
It's a pure golang alternative to webrtc data channels.
Huge

[shazow]

@gedw99 QUIC is not an alternative to WebRTC Data Channels. Browsers can't use QUIC to establish peer-to-peer connections with each other.

[Sean-Der]

@silbinarywolf Hey!

Thanks for checking us out :) That's really cool, I am excited to hear about all the use cases like this.

What I was thinking about doing was starting a bountysource (I personally don't need the money/will not incentive me anymore) but was hoping to incentive other contributors. I also might not be presenting work in a way that others can take on.

I think if others could make money AND I could say this could be really good for a resume/career etc... I could get some good Golang devs to help out. But not exactly sure where to start with that.

@shazow since your into libp2p repo then their QUIC implementation might be of interest.
https://github.com/libp2p/go-libp2p-quic-transport

And yes QUIC is not supported in all browsers, but it is supported on all mobiles and desktops because it has no dependencies at all. NOt even kernel level for the networking.

All i am saying is that its quite feasible that pions can support both webrtc and quic through an interface. Not saying it has to be this way but just leaving options on the table.