SCTP as a Transport for SIP
draft-rosenberg-sip-sctp-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Jonathan Rosenberg , Henning Schulzrinne , Gonzalo Camarillo | ||
| Last updated | 2001-05-21 | ||
| 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
This document specifies a mechanism for usage of SCTP (the Stream Control Transmisson Protocol) as the transport between SIP entities. SCTP is a new protocol which provides several features that may prove beneficial for transport between SIP entities which exchange a large amount of messages, including gateways and proxies. As SIP is transport independent, support of SCTP is a relatively straightforward process, nearly identical to support for TCP.
Authors
Jonathan Rosenberg
Henning Schulzrinne
Gonzalo Camarillo
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)