The RTC spec keeps refering to the peer having an "ICE Agent." It would be nice to decouple and move the ICE stuff to a separate file. One day, maybe even move it out as its own node module, since punching holes in NATs is pretty useful (and pretty much the only part I have implemented thus far).
For example, ipfo currently contains this logic. The ice agent would also have to maintain the underlying STUN/TURN socket (encapsulate it from the RTCPeerConnection).
The RTC spec keeps refering to the peer having an "ICE Agent." It would be nice to decouple and move the ICE stuff to a separate file. One day, maybe even move it out as its own node module, since punching holes in NATs is pretty useful (and pretty much the only part I have implemented thus far).