Another thing:
 
Also keep in mind, that by removing TCP we would also remove the possibility 
for the edge proxy to provide the keep-alive interval to the UA, AND the 
possibility for the edge proxy to possibly do something if it does not receive 
a keep-alive within that interval.
 
But, again, I will do whatever we agree to do :)
 
Regards,
 
Christer

________________________________

Lähettäjä: Christer Holmberg
Lähetetty: to 8.5.2008 11:51
Vastaanottaja: Juha Heinanen
Kopio: Jiri Kuthan; Hadriel Kaplan; Francois Audet; [email protected]
Aihe: VS: VS: [Sip] Draft: draft-holmberg-sip-keep-00.txt


Hi,

>>So, you are saying the following: if the UA does not support CRLF the
>>UA itself will include a short registration interval in the REGISTER
>>request?
>
>yes.
>
>>That is not standardized behavior either, and I am not sure that is how UAs 
>>work.
>
>i didn't claim that it is standardized.  it is simply a practical UA 
>implementers way to solve the problem without yet another addition to sip 
>protocol, which we sick of.
 
I agree it's a prectial way, but is that how UAs work today?
 
I am happy if we can do things without yet another addition to the protocol, 
but doing things based on assumptions on how we THINK UAs should work isn't 
going to be very useful.

>>"you can write that if registration interval would be as short as default 
>>keepalive interval then it is not recommended to send keepalives."
>
>ok, looks like i tried something to make you happy, but i'll take that back, 
>because the discussion has shown that nothing like that is
>needed.  i repeat, if UA is using TCP, your draft should clearly say that the 
>keep stuff is NOT used.
 
If people agree that TCP is not a problem,  I can remove 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

Reply via email to