There is a difference however. It is true that sending double-CRLF is sufficient to keep the NAT binding alive, even without the CRLF back.
However, getting the CRLF back tells the UA that the proxy is alive. Remember that outbound can be used for high-availability. The UA can use this to switch to a backup proxy. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Jiri Kuthan > Sent: Thursday, May 08, 2008 00:28 > To: Juha Heinanen > Cc: [email protected]; Audet, Francois (SC100:3055); Christer Holmberg > Subject: Re: [Sip] Draft: draft-holmberg-sip-keep-00.txt > > Juha Heinanen wrote: > > Christer Holmberg writes: > > > > > 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. > > True, I didn't realize that, with TCP we don't even need the > reverse CRLF. > > -jiri > > > > > -- juha > > > _______________________________________________ > 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 > _______________________________________________ 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
