Hi Jiri, I can definitely see the pro's/con's of it, and think it's interesting as a BTNS trick; though probably not for my particular customer types per se.
But I actually have a very different question about the draft: Why did you submit it to the IETF SIP WG? By that I mean it should interoperate without any protocol changes AFAICT, and anyone can do it right now. So if you just want to document it publicly as an option anyone can do anytime, why not just submit an Informational doc to SIPPING, or even just as an individual informational draft? (and avoid the hassle ;) If you want it to work across all domains with their unique policies and such, and get people to comment on all the nuances they are worried about, well then that's a horse of a different color. But I'm really just curious what you're trying to achieve, so I can know what types of comments you're looking for. -hadriel p.s. sorry if you answered that already - I may have missed it. _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [EMAIL PROTECTED] for questions on current sip Use [EMAIL PROTECTED] for new developments on the application of sip
