Hadriel Kaplan wrote: > >> -----Original Message----- >> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Juha >> Heinanen >> >> Christer Holmberg writes: >> >> > Last, you say that if the UA does not get keep=yes back the UA will >> > not send CRLFs. Not receiving keep=yes simply indicates that the edge >> > proxy does not support the Outbound keep-alive techniques. >> >> this is not true, because the proxy may still be able to send back, >> e.g., single CRLF, but does not understand your "keep" parameter. in >> fact, that is the case with openser proxy once the CRLF patch has been >> committed. > > Openser will send back a CRLF when it gets a CRLF? Interesting, but it's > proprietary. There is nothing in SIP to say "send back a CRLF when you get a > CRLF". This draft is proposing a standardized way to do that, for both > transport types.
Then we may very well consider making "respond to CRLF with CRLF" a proposed standardized way too. I mean it is simple and works. Which I prefer over negotiation protocols. -jiri > > >> > What the UA does in that case is a UA implementation issue. >> >> that is not what hadriel said. > > See my other email - it was what I meant - not getting the keep=yes means the > other end doesn't support this draft. Caveat emptor at that point. > > -hadriel > _______________________________________________ > 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
