RFC 4165: Signaling System 7 (SS7) Message Transfer Part 2 (MTP2) - User Peer-to-Peer Adaptation Layer (M2PA)
In plain English — editorial summary, not part of the RFC
This document defines a protocol supporting the transport of Signaling System Number 7 (SS7) Message Transfer Part (MTP) Level 3 signaling messages over Internet Protocol (IP) using the services of the Stream Control Transmission Protocol (SCTP). This protocol would be used between SS7 Signaling Points using the MTP Level 3 protocol. The SS7 Signaling Points may also use standard SS7 links using the SS7 MTP Level 2 to provide transport of MTP Level 3 signaling messages. The protocol operates in a manner similar to MTP Level 2 so as to provide peer-to-peer communication between SS7 endpoints. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4165
- Published
- September 2005
- Authors
- T. George; B. Bidulock; R. Dantu; H. Schwarzbauer; K. Morneault
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 53
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3788Security Considerations for Signaling Transport (SIGTRAN) ProtocolsCurrent
June 2004
- RFC 4166Telephony Signalling Transport over Stream Control Transmission Protocol (SCTP) Applicability StatementCurrent
February 2006
- 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
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?