Steffen Vogel

No updates so far. However, contributions are very welcome :)

Here is a [list of changes since RFC5389](https://www.rfc-editor.org/rfc/rfc8489#section-19) which need to be implemented: - [ ] Added support for DTLS-over-UDP [RFC6347](https://www.rfc-editor.org/rfc/rfc6347). - [ ] Made clear that the RTO is...

Aggressive nomination has been deprecated in RFC 8445: > The nomination process that was referred to as "aggressive nomination" in [RFC 5245](https://www.rfc-editor.org/rfc/rfc5245) has been deprecated in this specification. But I...

It actually says, that aggressive nomination is always activated: https://github.com/pion/ice/blob/19ffbe7e61754a77b7e1924933db2d54b20b25e3/agent_config.go#L168 Hence, I will close this issue.

Thanks @nils-ohlmeier for the insight. I am also wondering why Pion enables aggressive nomination always without a functioning option to disable it...

@jech Maybe fixing this in `pion/webrtc` is the better place? `ICETransportPolicy` is a setting from the `webrtc` module if I am not mistaken?

I am excited to see that you picked up the PR @ashellunts Let me know if I can support with testing, reviewing or something else :)

> Thanks. I will appreciate if you can read PR changes and maybe notice something completely wrong. I will dig into the RFC a bit more into detail later. Something...

> Not sure. But for me it looks logical to have either passive agent or active one. I've had a look at RFC6544, which is mainly concerned about active/passive/so TCP...

We have now merged #134 :) So work on this issue can proceed. My first naive to use a `stun.Client` for `stun-nat-behaviour` failed as we basically need to establish two...