RFC 4168: The Stream Control Transmission Protocol (SCTP) as a Transport for the Session Initiation Protocol (SIP)
In plain English — editorial summary, not part of the RFC
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]
Document record
- Document ID
- RFC4168
- Published
- October 2005
- Authors
- J. Rosenberg; H. Schulzrinne; G. Camarillo
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 10
- Also known as
- —
- Updated by:
- RFC 8996
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4170Tunneling Multiplexed Compressed RTP (TCRTP)Current
November 2005
- RFC 4166Telephony Signalling Transport over Stream Control Transmission Protocol (SCTP) Applicability StatementCurrent
February 2006
- RFC 4165Signaling System 7 (SS7) Message Transfer Part 2 (MTP2) - User Peer-to-Peer Adaptation Layer (M2PA)Current
September 2005
- RFC 4175RTP Payload Format for Uncompressed VideoUpdated
September 2005
- RFC 4184RTP Payload Format for AC-3 AudioCurrent
October 2005
- RFC 4189Requirements for End-to-Middle Security for the Session Initiation Protocol (SIP)Current
October 2005
- RFC 4190Framework for Supporting Emergency Telecommunications Service (ETS) in IP TelephonyCurrent
November 2005
- RFC 4129Digital Private Network Signaling System (DPNSS)/Digital Access Signaling System 2 (DASS 2) Extensions to the IUA ProtocolCurrent
September 2005
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?