RFC 4166 on Telephony Signalling Transport over Stream Control Transmission Protocol (SCTP) Applicability Statement
rfc-editor@rfc-editor.org Sat, 04 February 2006 00:19 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 1F5B8o-0007bu-4J; Fri, 03 Feb 2006 19:19:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F5B8k-0007SL-9N; Fri, 03 Feb 2006 19:18:59 -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 TAA00537; Fri, 3 Feb 2006 19:17:08 -0500 (EST)
Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F5BKF-0005zf-HI; Fri, 03 Feb 2006 19:30:52 -0500
Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.8/8.12.8) with ESMTP id k140Ii55009647; Fri, 3 Feb 2006 16:18:44 -0800
Received: (from apache@localhost) by nit.isi.edu (8.12.8/8.12.8/Submit) id k140IiCm009646; Fri, 3 Feb 2006 16:18:44 -0800
Date: Fri, 03 Feb 2006 16:18:44 -0800
Message-Id: <200602040018.k140IiCm009646@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="eaa7219e81554bfab586ad0c6527e740"
X-Spam-Score: -13.9 (-------------)
X-Scan-Signature: 36b1f8810cb91289d885dc8ab4fc8172
Cc: sigtran@ietf.org, rfc-editor@rfc-editor.org
Subject: RFC 4166 on Telephony Signalling Transport over Stream Control Transmission Protocol (SCTP) Applicability Statement
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 4166
Title: Telephony Signalling Transport over Stream
Control Transmission Protocol (SCTP) Applicability
Statement
Author: L. Coene, J. Pastor-Balbas
Status: Informational
Date: February 2006
Mailbox: lode.coene@siemens.com,
J.Javier.Pastor@ericsson.com
Pages: 23
Characters: 46659
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-sigtran-signalling-over-sctp-applic-09.txt
URL: http://www.rfc-editor.org/rfc/rfc4166.txt
This document describes the applicability of the several protocols
developed under the signalling transport framework. A
description of the main issues regarding the use of the Stream Control
Transmission Protocol (SCTP) and an explanation of each adaptation layer
for transport of telephony signalling information over IP infrastructure
are given. This memo provides information for the Internet community.
This document is a product of the Signaling Transport Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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
...
A new Request for Comments is now available in online RFC libraries.
RFC 4166
Title: Telephony Signalling Transport over Stream
Control Transmission Protocol (SCTP) Applicability
Statement
Author: L. Coene, J. Pastor-Balbas
Status: Informational
Date: February 2006
Mailbox: lode.coene@siemens.com,
J.Javier.Pastor@ericsson.com
Pages: 23
Characters: 46659
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-sigtran-signalling-over-sctp-applic-09.txt
URL: http://www.rfc-editor.org/rfc/rfc4166.txt
This document describes the applicability of the several protocols
developed under the signalling transport framework. A
description of the main issues regarding the use of the Stream Control
Transmission Protocol (SCTP) and an explanation of each adaptation layer
for transport of telephony signalling information over IP infrastructure
are given. This memo provides information for the Internet community.
This document is a product of the Signaling Transport Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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
...
_______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce