RFC 4168

The Stream Control Transmission Protocol (SCTP) as a Transport for the Session Initiation Protocol (SIP), October 2005

File formats:
icon for text file icon for PDF icon for HTML
Status:
PROPOSED STANDARD
Updated by:
RFC 8996
Authors:
J. Rosenberg
H. Schulzrinne
G. Camarillo
Stream:
IETF
Source:
sip (rai)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC4168

Discuss this RFC: Send questions or comments to the mailing list sipcore@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 4168


Abstract

This document specifies a mechanism for usage of SCTP (the Stream Control Transmission Protocol) as the transport mechanism between SIP (Session Initiation Protocol) entities. SCTP is a new protocol that provides several features that may prove beneficial for transport between SIP entities that 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. [STANDARDS-TRACK]


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.




Advanced Search