Hi, >> I agree with Hadriel. The idea is to let the client do it, so that >> the proxy doesn't need to handle it, e.g. by providing short >> registration refresh timers etc in order to make sure the NAT >> bindings stay open. > >christer, > >could you then, please, restrict the scope of your draft to udp >connected UAs, because if they are tcp connected, clients can keep >their nat binding open by simply sending double CRLFs. if they get back >single CRLF, then fine, but if they don't, it is fine too. The UA *CAN* send double CRLF, but the problem is that the edge proxy doesn't know whether the UA is going to do it, so it may provide short registration refreshes also for TCP connections. So, based on your previous request, my intention is to do some re-wording and say that it is unspecified what the UA does if it doesn't receive keep=yes. So, that would not forbid the UA to use double CRLF even if it doesn't receive keep=yes. 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
