Preventing Fragmentation for Client Initiated Connections in the Session Initiation Protocol (SIP)
draft-petithuguenin-sip-outbound-fragmentation-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Marc Petit-Huguenin | ||
| Last updated | 2007-03-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
There is cases when a Session Initiation Protocol (SIP) client can initiate a bidirectional UDP stream or a TCP connection to a SIP server but the SIP server cannot do the same in the other direction. The server can reuse the existing bidirectional UDP stream or TCP connection but cannot use a TCP connection if the client chose to use a bidirectional UDP stream. This document described a method to force the client to initiate a TCP connection to the server.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)