Hi, I have big issues with the keep-alive change in the -12 version.
Because, now the STUN keep-alives usage can't be applied between the UA and outbound proxy, unless the registrar supports outbound. I strongly think it should be possible to use STUN keep-alives for "pure" signalling NAT traversal, even if the "rest" of outbound is not used. So, while I DO agree with the Vancouver(?) decission to not include any "URI" keep parameter in the R-URI of the register request, I think we shall we keep the URI "keep" parameter definition, and e.g. allow it to be inserted into the Path header (I don't remember any discussions regarding removing that possibility) by the outbound proxy, in order to inform the UA that the outbound proxy supports STUN keep-alive. (OR, there should be another mechanism for the outbound proxy to inform the UA it supports STUN keep-alive) That would allow people to start using outbound for NAT traversal, even if the registrars haven't yet been updated to support outbound etc. At one point we decided that we will keep the STUN keep-alive usage and outbound in the same spec, but that we will describe the STUN keep-alive usage as a "stand alone" function (chapter 8 of the draft). But, now you have more or less "merged" the STUN keep-alive usage with the outbound function, and that is bad. Also, this change is not mentioned in the changes-since-the-previous-version part (if it is mentioned, I appologize for having missed it) Regards, Christer _______________________________________________ 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
