Jiri, On p.15 it is explained that the UAC looks at the presence of the Require: outbound field falue in a response to registration.
This is to ensure that both the registrar and the edge proxy are compliant with this spec. The keep-alive would only be sent if present. Please suggest improved wording if you feel it is not clear enough. On the TCP keep-alive issue: this has been investigated in previous versions of the draft. It was dropped because of the fact that changing the TCP keep-alive is often a system-wide setting on most Operating Systems. Rohan, we use to have some words about this in the spec, but I think it's all gone from this version. Maybe the note should have been left here... > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Jiri Kuthan > Sent: Monday, March 03, 2008 10:53 > To: [email protected] > Subject: [Sip] keep-alive backwards compatibility in > draft-ietf-sip-outbound-12.txt > > I'm just wondering if folks have been worried about the UACs > that implement the aforementioned I-D and talk to a proxy/UAS > that doesn't do so? > > It appears to me that mandating a reconnect on lacking PONG > would lead to quite heavy traffic. > > (which is why without deeper knowledge of the history of this > I-D, I would be inclined to rely on TCP's keep-alive, which > is in there) > > -jiri > > > > -- > Jiri Kuthan http://iptel.org/~jiri/ > > _______________________________________________ > 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
