RFC 3910: The SPIRITS (Services in PSTN requesting Internet Services) Protocol
In plain English — editorial summary, not part of the RFC
This document describes the Services in PSTN (Public Switched Telephone Network) requesting Internet Services (SPIRITS) protocol. The purpose of the SPIRITS protocol is to support services that originate in the cellular or wireline PSTN and necessitate interactions between the PSTN and the Internet. On the PSTN side, the SPIRITS services are most often initiated from the Intelligent Network (IN) entities. Internet Call Waiting and Internet Caller-ID Delivery are examples of SPIRITS services, as are location-based services on the cellular network. The protocol defines the building blocks from which many other services can be built. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3910
- Published
- October 2004
- Authors
- V. Gurbani; A. Brusilovsky; I. Faynberg; J. Gato; H. Lu; M. Unmehopa
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 50
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3976Interworking SIP and Intelligent Network (IN) ApplicationsCurrent
January 2005
- RFC 3578Mapping of Integrated Services Digital Network (ISDN) User Part (ISUP) Overlap Signalling to the Session Initiation Protocol (SIP)Current
August 2003
- RFC 3398Integrated Services Digital Network (ISDN) User Part (ISUP) to Session Initiation Protocol (SIP) MappingCurrent
December 2002
- RFC 3322Signaling Compression (SigComp) Requirements & AssumptionsCurrent
January 2003
- RFC 4825The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)Current
May 2007
- RFC 4826Extensible Markup Language (XML) Formats for Representing Resource ListsCurrent
May 2007
- RFC 3321Signaling Compression (SigComp) - Extended OperationsUpdated
January 2003
- RFC 3320Signaling Compression (SigComp)Updated
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?