One topic that's come up in a number of implementations that I'm familiar with is that doing ICE from the get-go imposes a significant implementation hurdle. Since there are settings in which ICE isn't necessary, this raises the question of whether it makes sense to have a trivial version of Attach (previously Connect) which does not use ICE.
The tricky thing here is that even in situations where full ICE is not needed it's attractive to offer two addresses, one inside and one outside the NAT, so now we end up defining some kind of ICE lite lite, which tends towards the complexity of ICE as we want to handle just one more case. A middle ground would be to allow ICE lite support. _______________________________________________ P2PSIP mailing list [email protected] https://www.ietf.org/mailman/listinfo/p2psip
