RFC 4666: Signaling System 7 (SS7) Message Transfer Part 3 (MTP3) - User Adaptation Layer (M3UA)
In plain English — editorial summary, not part of the RFC
This memo defines a protocol for supporting the transport of any SS7 MTP3-User signalling (e.g., ISUP and SCCP messages) over IP using the services of the Stream Control Transmission Protocol. Also, provision is made for protocol elements that enable a seamless operation of the MTP3-User peers in the SS7 and IP domains. This protocol would be used between a Signalling Gateway (SG) and a Media Gateway Controller (MGC) or IP-resident Database, or between two IP-based applications. It is assumed that the SG receives SS7 signalling over a standard SS7 interface using the SS7 Message Transfer Part (MTP) to provide transport. This document obsoletes RFC 3332. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4666
- Published
- September 2006
- Authors
- K. Morneault; J. Pastor-Balbas
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 124
- Also known as
- —
- Obsoletes:
- RFC 3332
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4233Integrated Services Digital Network (ISDN) Q.921-User Adaptation LayerUpdated
January 2006
- RFC 3868Signalling Connection Control Part User Adaptation Layer (SUA)Current
October 2004
- RFC 3807V5.2-User Adaptation Layer (V5UA)Current
June 2004
- RFC 3331Signaling System 7 (SS7) Message Transfer Part 2 (MTP2) - User Adaptation LayerCurrent
September 2002
- RFC 3873Stream Control Transmission Protocol (SCTP) Management Information Base (MIB)Current
September 2004
- RFC 3578Mapping of Integrated Services Digital Network (ISDN) User Part (ISUP) Overlap Signalling to the Session Initiation Protocol (SIP)Current
August 2003
- RFC 3398Integrated Services Digital Network (ISDN) User Part (ISUP) to Session Initiation Protocol (SIP) MappingCurrent
December 2002
- RFC 3257Stream Control Transmission Protocol Applicability StatementCurrent
April 2002
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?