Internet DRAFT - draft-ietf-sigtran-m3ua

draft-ietf-sigtran-m3ua



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


        RFC 3332

        Title:      Signaling System 7 (SS7) Message Transfer Part 3
                    (MTP3) - User Adaptation Layer (M3UA)
        Author(s):  G. Sidebottom, K. Morneault, J. Pastor-Balbas
        Status:     Standards Track
        Date:       September 2002
        Mailbox:    greg@signatustechnologies.com, kmorneau@cisco.com,
                    j.javier.pastor@ericsson.com
        Pages:      120
        Characters: 265055
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ietf-sigtran-m3ua-12.txt

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


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 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.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.