What's the difference between pion/ice and ice code in pion/webrtc

[iPush]

Hi, i'm new here, Pion is a great work.
I'm wondering what's the difference between pion/ice and ice parts in pion/webrtc?

• pion/webrtc is the high-level wrap of pion/ice (and other stuff, stun/turn)
• pion/ice is the low-level and detailed implementation of ICE RFC
  so , developer should just program with pion/webrtc to use pion/ice ?

am i right ?
best wishes

[Sean-Der]

Hi @iPush

Thank you so much for your kind words! Hope you are enjoying using Pion :) Your explanation sounds right to me!

The ICE objects in pion/webrtc come from the webrtc-pc spec. This defines things like ICECandidate. We can't put these objects in pion/ice because they are WebRTC specific.

pion/ice is also used by people that don't use WebRTC you can see the importers here. I try and make sure that people that don't care about WebRTC aren't forced to import it.

---

If you are building something with pion/webrtc I would try to avoid using pion/ice (if possible). It is a lower level interface and the API may change at a different time then pion/webrtc. If you are building something with ICE using pion/ice directly makes sense to me!

[iPush]

Thank you so much!