Skip to main content

ISDN Q.921-User Adaptation Layer

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3057.
Authors Malleswar Kalla , Ken Morneault , Selvam Rengasami , Greg Sidebottom
Last updated 2015-10-14 (Latest revision 2000-12-19)
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Proposed Standard
Additional resources Mailing list discussion
Stream WG state (None)
Document shepherd (None)
IESG IESG state Became RFC 3057 (Proposed Standard)
Action Holders
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Scott O. Bradner
Send notices to (None)
A new Request for Comments is now available in online RFC libraries.

        RFC 3057

        Title:      ISDN Q.921-User Adaptation Layer
        Author(s):  K. Morneault, S. Rengasami, M. Kalla,
                    G. Sidebottom 
        Status:     Standards Track
        Date:       February 2001
        Pages:      66
        Characters: 13601
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ietf-sigtran-iua-10.txt


This document defines a protocol for backhauling of 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 is a product of the Signaling Transport Working Group of
the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.