RFC 4233: Integrated Services Digital Network (ISDN) Q.921-User Adaptation Layer
In plain English — editorial summary, not part of the RFC
This document defines a protocol for backhauling of Integrated Services Digital Network (ISDN) Q.921 User messages over IP using the Stream Control Transmission Protocol (SCTP). This protocol would be used between a Signaling Gateway (SG) and Media Gateway Controller (MGC). It is assumed that the SG receives ISDN signaling over a standard ISDN interface. This document obsoletes RFC 3057. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4233
- Published
- January 2006
- Authors
- K. Morneault; S. Rengasami; M. Kalla; G. Sidebottom
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 73
- Also known as
- —
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 3331Signaling System 7 (SS7) Message Transfer Part 2 (MTP2) - User Adaptation LayerCurrent
September 2002
- RFC 3807V5.2-User Adaptation Layer (V5UA)Current
June 2004
- RFC 3873Stream Control Transmission Protocol (SCTP) Management Information Base (MIB)Current
September 2004
- RFC 3868Signalling Connection Control Part User Adaptation Layer (SUA)Current
October 2004
- RFC 4666Signaling System 7 (SS7) Message Transfer Part 3 (MTP3) - User Adaptation Layer (M3UA)Current
September 2006
- RFC 3525Gateway Control Protocol Version 1Obsoleted
June 2003
- RFC 3332Signaling System 7 (SS7) Message Transfer Part 3 (MTP3) - User Adaptation Layer (M3UA)Obsoleted
September 2002
- RFC 3015Megaco Protocol Version 1.0Obsoleted
November 2000
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?