Hi from a maintainer of rt(c)p-types

[ystreet]

Hi!

I noticed from https://crates.io/crates/rtp-types/reverse_dependencies and https://crates.io/crates/rtcp-types/reverse_dependencies that you are depending on the rtp-types and rtcp-types. First of all, thanks. Let me know if you have any issues using those crates in regards to documentation, missing functionality, etc.

I also noticed that you have implemented parsing and writing RTP header extensions on top of rtp-types which is something that I eventually want to implement within rtp-types itself.

If you want/need to contact me about rt(c)p-types, you can either file an issue in the respective repositories, or use the email mentioned in my github profile.

P.S. I also have stun-types and stun-proto crates that implement relevant features of STUN which may be interesting for you.

[kbalt]

Hey,

Also thank you for making & maintaining these crates, they saved me a lot of time!

I also noticed that you have implemented parsing and writing RTP header extensions on top of rtp-types which is something that I eventually want to implement within rtp-types itself.

I'm looking forward to that, since currently this does require some workarounds like a custom RtpPacketWriter and other odd looking code, to do it efficiently.

P.S. I also have stun-types and stun-proto crates that implement relevant features of STUN which may be interesting for you.

Nice, I'll look into that.

I've left you an issue I've ran into https://github.com/ystreet/rtcp-types/issues/14 :)