RFC 4166: Telephony Signalling Transport over Stream Control Transmission Protocol (SCTP) Applicability Statement
In plain English — editorial summary, not part of the RFC
This document describes the applicability of the several protocols developed under the signalling transport framework. A description of the main issues regarding the use of the Stream Control Transmission Protocol (SCTP) and an explanation of each adaptation layer for transport of telephony signalling information over IP infrastructure are given. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4166
- Published
- February 2006
- Authors
- L. Coene; J. Pastor-Balbas
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 23
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4165Signaling System 7 (SS7) Message Transfer Part 2 (MTP2) - User Peer-to-Peer Adaptation Layer (M2PA)Current
September 2005
- RFC 4168The Stream Control Transmission Protocol (SCTP) as a Transport for the Session Initiation Protocol (SIP)Updated
October 2005
- RFC 4170Tunneling Multiplexed Compressed RTP (TCRTP)Current
November 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?