Thomas Eizinger
Thomas Eizinger
> > Oh, I don't want to really bother with this CLA as signing it would require **giving away my home address**. I guess this PR still serves as a...
Thank you for the comment! > Related to that, str0m's ICE isn't strictly RFC compliant – it's compatible. A [simplifying assumption](https://github.com/algesten/str0m/blob/main/docs/ice.md?rgh-link-date=2023-12-07T20%3A31%3A15Z#one-to-one-relationship-ice-agent---session---data-stream) is that there is one agent instance per peer...
Okay thank you for your input! I'll see what I can come up with :)
Just as a heads-up, I've now started work on our connectivity layer that is based on `str0m`. Tracking issue here: https://github.com/firezone/firezone/issues/2966. PRs incoming :)
After https://github.com/algesten/str0m/pull/446 is merged, I would start on making `openssl` pluggable. What do people think about the following: - Introduce on-by-default `openssl` feature - Introduce a `Dtls` trait that covers...
> > * Feature-flag the current `Rtc::new` constructor to require `openssl` > > I think feature flags should enable config options, rather than change behavior. I.e. we will have the...
I've submitted a draft here: https://github.com/algesten/str0m/pull/447, please have a look.
This is resolved, thank you!
> Let's keep this as a place to report interest in separating the ice agent into a separate crate. Has there been any new interest?
FWIW, we are using just str0m's ICE agent very successfully in production and I believe the only reason why we didn't end up creating a separate crate is that we...