A new Request for Comments is now available in online RFC libraries.
RFC 3868
Title: Signalling Connection Control Part User Adaptation
Layer (SUA)
Author(s): J. Loughney, Ed., G. Sidebottom, L. Coene,
G. Verwimp, J. Keller, B. Bidulock
Status: Standards Track
Date: October 2004
Mailbox: john.Loughney@nokia.com,
greg@signatustechnologies.com,
lode.coene@siemens.com, gery.verwimp@siemens.com,
joe.keller@tekelec.com, bidulock@openss7.org
Pages: 131
Characters: 294116
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-sigtran-sua-16.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc3868.txt
This document defines a protocol for the transport of any Signalling
Connection Control Part-User signalling over IP using the Stream
Control Transmission Protocol. The protocol is designed to be modular
and symmetric, to allow it to work in diverse architectures, such as a
Signalling Gateway to IP Signalling Endpoint architecture as well as a
peer-to-peer IP Signalling Endpoint architecture.
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/rfc3868.txt>
-
_______________________________________________
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce
