Requirements for Connection Reuse in the Session Initiation Protocol (SIP)
draft-mahy-sipping-connect-reuse-reqs-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Rohan Mahy | ||
| Last updated | 2002-06-19 | ||
| Replaced by | draft-ietf-sipping-connect-reuse-reqs | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-sipping-connect-reuse-reqs | |
| 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
When SIP entities use a connection oriented protocol to send a request, they typically originate their connections from an ephemeral port. The SIP protocol includes mechanisms which insure that responses to a request, and new requests sent in original direction reuse an existing connection. However, new requests sent in the opposite direction are unlikely to reuse the existing connection. This frequently causes a pair of SIP entities to use one connection for requests sent in each direction, and can result in potential scaling and performance problems. This document presents requirements for addressing this shortcoming, and separately proposes an example mechanism which addresses this deficiency.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)