Skip to main content

Reusing Transport Layer Connections in Session Initiation Protocol (SIP)
draft-jain-dispatch-sip-transport-connection-reuse-00

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Rajnish Jain , Vijay K. Gurbani , Hadriel Kaplan
Last updated 2009-09-08
RFC stream (None)
Intended RFC status (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

The current Session Initiation Protocol (SIP) specification dictates that a transport layer connection can carry SIP requests in only one direction i.e. from the client to the server. This presents scalability problems as twice the number of connections are needed for each pair of SIP entities that communicate with each other. The internet-draft [I-D.ietf-sip-connect-reuse] specifies a mechanism for reusing SIP over TLS connections. However, that document is predicated on secure TLS mutual authentication and specifically refrains connection reuse for transports such as SIP over TCP and SCTP. There are many situations, such as in Trust Domains [RFC3324], where TLS mutual authentication may not be required but where connection reuse is beneficial. This document specifies connection reuse for SIP over connection-oriented transports such as TCP and SCTP. It specifies the same mechanism for connection reuse as specified in [I-D.ietf-sip-connect-reuse], however, the solution is presented in the context of Trust Domains.

Authors

Rajnish Jain
Vijay K. Gurbani
Hadriel Kaplan

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)