RFC 4233 on Integrated Services Digital Network (ISDN) Q.921-User Adaptation Layer

rfc-editor@rfc-editor.org Tue, 10 January 2006 01:36 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ew8RK-0000pw-0X; Mon, 09 Jan 2006 20:36:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ew8RF-0000o6-Vr; Mon, 09 Jan 2006 20:36:42 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17498; Mon, 9 Jan 2006 20:35:21 -0500 (EST)
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ew8Xp-0005mU-Cp; Mon, 09 Jan 2006 20:43:30 -0500
Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id k0A1aHi05183; Mon, 9 Jan 2006 17:36:17 -0800 (PST)
Message-Id: <200601100136.k0A1aHi05183@boreas.isi.edu>
To: ietf-announce@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Mon, 09 Jan 2006 17:36:16 -0800
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f
Cc: sigtran@ietf.org, rfc-editor@rfc-editor.org
Subject: RFC 4233 on Integrated Services Digital Network (ISDN) Q.921-User Adaptation Layer
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org

A new Request for Comments is now available in online RFC libraries.


        RFC 4233

        Title:      Integrated Services Digital Network (ISDN)
                    Q.921-User Adaptation Layer
        Author(s):  K. Morneault, S. Rengasami, M. Kalla,
                    G. Sidebottom
        Status:     Standards Track
        Date:       January 2006
        Mailbox:    kmorneau@cisco.com, mkalla@telcordia.com,
                    selvam@trideaworks.com,
                    greg@signatustechnologies.com
        Pages:      73
        Characters: 157857
        Obsoletes:  3057

        I-D Tag:    draft-ietf-sigtran-rfc3057bis-02.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4233.txt


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.

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
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

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.

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.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
ftp://ftp.isi.edu/in-notes/rfc4233.txt"><ftp://ftp.isi.edu/in-notes/rfc4233.txt>
_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce