idnits 2.17.1 draft-ietf-sipping-isup-06.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3398 5 Title: Integrated Services Digital Network (ISDN) User 6 Part (ISUP) to Session Initiation Protocol (SIP) 7 Mapping 8 Author(s): G. Camarillo, A. B. Roach, J. Peterson, L. Ong 9 Status: Standards Track 10 Date: December 2002 11 Mailbox: Gonzalo.Camarillo@Ericsson.com, 12 adam@dynamicsoft.com, jon.peterson@neustar.biz, 13 lyOng@ciena.com 14 Pages: 68 15 Characters: 166197 16 Updates/Obsoletes/SeeAlso: None 18 I-D Tag: draft-ietf-sipping-isup-06.txt 20 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3398.txt 22 This document describes a way to perform the mapping between two 23 signaling protocols: the Session Initiation Protocol (SIP) and the 24 Integrated Services Digital Network (ISDN) User Part (ISUP) of 25 Signaling System No. 7 (SS7). This mechanism might be implemented 26 when using SIP in an environment where part of the call involves 27 interworking with the Public Switched Telephone Network (PSTN). 29 This document is a product of the Session Initiation Proposal 30 Investigation Working Group of the IETF. 32 This is now a Proposed Standard Protocol. 34 This document specifies an Internet standards track protocol for the 35 Internet community, and requests discussion and suggestions for 36 improvements. Please refer to the current edition of the "Internet 37 Official Protocol Standards" (STD 1) for the standardization state 38 and status of this protocol. Distribution of this memo is unlimited. 40 This announcement is sent to the IETF list and the RFC-DIST list. 41 Requests to be added to or deleted from the IETF distribution list 42 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 43 added to or deleted from the RFC-DIST distribution list should 44 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 46 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 47 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 48 help: ways_to_get_rfcs. For example: 50 To: rfc-info@RFC-EDITOR.ORG 51 Subject: getting rfcs 53 help: ways_to_get_rfcs 55 Requests for special distribution should be addressed to either the 56 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 57 specifically noted otherwise on the RFC itself, all RFCs are for 58 unlimited distribution.echo 59 Submissions for Requests for Comments should be sent to 60 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 61 Authors, for further information.