RFC 3298: Service in the Public Switched Telephone Network/Intelligent Network (PSTN/IN) Requesting InTernet Service (SPIRITS) Protocol Requirements
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC3298
- Published
- September 2002
- Authors
- I. Faynberg; J. Gato; H. Lu; L. Slutsman
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 17
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3303Middlebox communication architecture and frameworkCurrent
August 2002
- RFC 3304Middlebox Communications (midcom) Protocol RequirementsCurrent
August 2002
- RFC 3290An Informal Management Model for Diffserv RoutersCurrent
June 2002
- RFC 3289Management Information Base for the Differentiated Services ArchitectureCurrent
June 2002
- RFC 3307Allocation Guidelines for IPv6 Multicast AddressesUpdated
September 2002
- RFC 3317Differentiated Services Quality of Service Policy Information BaseCurrent
March 2003
- RFC 3320Signaling Compression (SigComp)Updated
January 2003
- RFC 3321Signaling Compression (SigComp) - Extended OperationsUpdated
January 2003
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?