Document Action: 'Telephony Signalling Transport over SCTP applicability statement' to Informational RFC
The IESG <iesg-secretary@ietf.org> Fri, 24 September 2004 21:45 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23403; Fri, 24 Sep 2004 17:45:22 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CAxze-0005fk-VN; Fri, 24 Sep 2004 17:52:43 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CAxe7-000422-7X; Fri, 24 Sep 2004 17:30:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CAxXp-0002Yu-IL; Fri, 24 Sep 2004 17:23:57 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21845; Fri, 24 Sep 2004 17:23:55 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CAxet-0005FK-WF; Fri, 24 Sep 2004 17:31:16 -0400
Received: from apache by megatron.ietf.org with local (Exim 4.32) id 1CAxQc-0001EU-9V; Fri, 24 Sep 2004 17:16:30 -0400
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1CAxQc-0001EU-9V@megatron.ietf.org>
Date: Fri, 24 Sep 2004 17:16:30 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Cc: sigtran chair <lyong@ciena.com>, Internet Architecture Board <iab@iab.org>, sigtran mailing list <sigtran@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: Document Action: 'Telephony Signalling Transport over SCTP applicability statement' to Informational RFC
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
The IESG has approved the following document: - 'Telephony Signalling Transport over SCTP applicability statement ' <draft-ietf-sigtran-signalling-over-sctp-applic-09.txt> as an Informational RFC This document is the product of the Signaling Transport Working Group. The IESG contact persons are Jon Peterson and Allison Mankin. Technical Summary This document describes the applicability of the several protocols developed under the signalling transport framework[RFC2719]. A description of the main issues regarding the use of the Stream Control Transmission Protocol (SCTP)[RFC2960] and each adaptation layer for transport of telephony signalling nformation over IP infrastructure is explained. Working Group Summary The SIGTRAN WG supported the advancement of this Informational document. Protocol Quality This document was reviewed for the IESG by Jon Peterson. RFC-Editor Note: OLD: Section 3.2.1 "Therefore, this strategy should never be used in public Internet." NEW: "Therefore, this strategy should never be used on the public Internet." OLD: Section 4 "Access Signalling: This is the signalling that is needed between and access device and an exchange in the core network in order to" NEW: "... is needed between an access device and an..." ^^ OLD: (No IANA Considerations between Sections 4 and 5) NEW: 5 IANA Considerations This document introduces no considerations for the IANA. 6 Security Considerations OLD: 6 Security Considerations See specific Security considerations in each UAL technical specification for details. NEW: "See specific Security Considerations in each UAL Technical specification for details (for general security principles of SIGTRAN, see [RFCSIGSEC])." OLD: 6 Security Considerations ... but TLS is also considered as a perfectly valid option to be used in certain scenarios. NEW: "... but TLS is also considered a perfectly valid option to be used in certain scenarios (see [RFC3464] for more information on using TLS with SCTP)." OLD: (Missing references) NEW: [RFC3436] Jungmaier, A., Rescorla, E., Tuexen, M.,"Transport Layer Security over Stream Control Transmission Protocol", RFC3436, December 2002. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce