RE: [Sip] Impossible to use real persistent connection with sip

["Colasanto, Eric (Eric)" <ecolasanto@lucent.com>]

I think a new parameter will work well to specify the creation of a persistent socket.
;pc=0 when the socket is NOT persistent, or don't include this parameter.
;pc=1 when the socket is persistent.

After setting up this socket will all subsequent SIP messages be required to have the pc=1
to utilize the persistent socket. Or will any SIP message destined for an endpoint supported by a
persistent socket utilize the socket, reguardless of the presence of the pc parameter?

Then there is the issue of when/how does one destroy the persistent connection(s).
Should this be left to the application/user which is controlling the generation/consumption of
the SIP messages?
 

Eric J. Colasanto 
(508) 862-3386 



-----Original Message-----
From: James Ford [mailto:james_s_ford@hotmail.com]
Sent: Thursday, February 06, 2003 2:17 AM
To: rajnishjain@lucent.com; sip@ietf.org
Cc: ecolasanto@lucent.com; vkg@ih2mail.ih.lucent.com
Subject: RE: [Sip] Impossible to use real persistent connection with sip


An even simpler solution will be to add a parameter to the Via header such 
as
pc; (or pc=1 so that we will not have troubles with Microsoft). Pc stands 
for persistent connection.

Guys, what do I need to do to move on this thing so that we will have a new 
draft to solve the problem?
I think many implementations will be interested in using a real persistent 
connection especially when TLS will be more deployed.

Thanks,
James S. Ford


>From: "Jain, Rajnish (Rajnish)" <rajnishjain@lucent.com>
>To: "'James Ford'" <james_s_ford@hotmail.com>, sip@ietf.org
>CC: "Colasanto, Eric (Eric)" <ecolasanto@lucent.com>,   "Gurbani, Vijay K 
>(Vijay)" <vkg@ih2mail.ih.lucent.com>
>Subject: RE: [Sip] Impossible to use real persistent connection with sip
>Date: Tue, 4 Feb 2003 07:20:22 -0500
>
>James,
>
>The option of adding a SIP header field seems to be more flexible. That 
>way,
>when that header field is not present, the persistent connection is jointly
>owned by both UAs. And at their discretion they can close it. This allows 
>us
>to be backward compatible while enabling a new capability.
>
>Thanks,
>Rajnish
>
>-----Original Message-----
>From: James Ford [mailto:james_s_ford@hotmail.com]
>Sent: Tuesday, February 04, 2003 2:45 AM
>To: sip@ietf.org
>Subject: [Sip] Impossible to use real persistent connection with sip
>
>
>Hi,
>The SIP standard does not specify who is responsible for closing TCP
>connections. This means that both client and server transaction can close
>the connection. A reasonable implementation for a transaction will be to
>close any open connection (incoming or outgoing) before termination in 
>order
>to free unused resources.
>This behavior actually makes it impossible to count on a persistent
>connection.
>For example, A UA that is always talking to the same destination using TLS
>will want to use one connection per day. This is impossible since the 
>server
>might close the connection as soon as the first transaction terminates.
>
>I can see several ways to solve this problem:
>1.	Specify that the UA that opened the connection will be responsible for
>closing it.
>2.	Add a header to sip requests that asks the server not to close the
>connection by itself.
>
>What do you think?
>James S Ford.
>
>
>
>
>
>
>_________________________________________________________________
>Add photos to your e-mail with MSN 8. Get 2 months FREE*.
>http://join.msn.com/?page=features/featuredemail
>
>_______________________________________________
>Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
>This list is for NEW development of the core SIP Protocol
>Use sip-implementors@cs.columbia.edu for questions on current sip
>Use sipping@ietf.org for new developments on the application of sip


_________________________________________________________________
Protect your PC - get McAfee.com VirusScan Online 
http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip