Service in the Public Switched Telephone Network/Intelligent Network Requesting InTernet Service Protocol Requirements
RFC 3298, “Service in the Public Switched Telephone Network/Intelligent Network Requesting InTernet Service Protocol Requirements”, is an Informational document published in September 2002 by I. Faynberg, J. Gato, H. Lu, L. Slutsman. The canonical text is published by the RFC Editor.
Abstract
This document describes the SPIRITS protocol requirements, based on the architecture presented in RFC 3136. (SPIRITS stands for "Service in the PSTN/IN Requesting InTernet Service".) The purpose of the protocol is to support services that originate in the Public Switched Telephone Network (PSTN) and necessitate the interactions between the PSTN and the Internet. Similarly, such services are called SPIRITS services. (Internet Call Waiting, Internet Caller-ID Delivery, and Internet Call Forwarding are examples of SPIRIT services, but the protocol is to define the building blocks from which many other services can be built.) On the PSTN side, the SPIRITS services are initiated from the Intelligent Network (IN) entities; the earlier IETF work on the PSTN/Internet Interworking (PINT) resulted in the protocol (RFC 2848) in support of the services initiated the other way around--from the Internet to PSTN. To this end, this document lists general requirements for the SPIRITS protocol as well as those pertinent to IN, Wireless IN, and PINT building blocks. The document also presents the SPIRITS WG consensus on the choice of the SPIRITS signaling protocol. This memo provides information for the Internet community.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 3298 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 3297 Content Negotiation for Messaging Services based on Email
- RFC 3296 Named Subordinate References in Lightweight Directory Access Protocol Directories
- RFC 3300 Internet Official Protocol Standards
- RFC 3295 Definitions of Managed Objects for the General Switch Management Protocol
- RFC 3301 Layer Two Tunnelling Protocol : ATM access network extensions
- RFC 3294 General Switch Management Protocol Applicability
- RFC 3302 Tag Image File Format - image/tiff MIME Sub-type Registration
- RFC 3293 General Switch Management Protocol Packet Encapsulations for Asynchronous Transfer Mode , Ethernet and Transmission Control Protocol