I-D ACTION:draft-jain-sipping-persistent-conn-reqs-01.txt

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: Requirements for Persistent Connection Management 
			  in the Session Initiation Protocol (SIP)
	Author(s)	: R. Jain, V. Gurbani
	Filename	: draft-jain-sipping-persistent-conn-reqs-01.txt
	Pages		: 15
	Date		: 2003-11-18
	
SIP over connection-oriented transport protocol based systems are 
likely to face certain distinct performance and behavioral issues 
that are not manifest when SIP is transported over connectionless 
protocols. Allowing SIP entities to mutually conserve connections 
over a predictable, extended period of time is one of the leading 
requirements to help SIP entities deliver their optimal 
performance in the network. Overall, this document contemplates 
transport layer connection management issues relating to SIP. 
Requirements and potential solutions for introducing a backward 
compatible notion of persistent connections in SIP are presented.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-jain-sipping-persistent-conn-reqs-01.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-jain-sipping-persistent-conn-reqs-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-jain-sipping-persistent-conn-reqs-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
<ftp://ftp.ietf.org/internet-drafts/draft-jain-sipping-persistent-conn-reqs-01.txt>

[Index of Archives]     [IETF]     [IETF Discussion]     [Linux Kernel]

  Powered by Linux