The SPIRITS Architecture

The information below is for an old version of the document that is already published as an RFC
Document Type RFC Internet-Draft (spirits WG)
Authors Mark Weissman  , Lev Slutsman  , Igor Faynberg 
Last updated 2013-03-02 (latest revision 2001-05-09)
Stream Internet Engineering Task Force (IETF)
Formats plain text pdf htmlized bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state RFC 3136 (Informational)
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
A new Request for Comments is now available in online RFC libraries.

        RFC 3136

        Title:      The SPIRITS Architecture
        Author(s):  L. Slutsman, Editor, I. Faynberg, H. Lu,
                    M. Weissman 
        Status:     Informational
        Date:       June 2001
        Pages:      10
        Characters: 19241
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-spirits-architecture-03.txt


This document describes the architecture for supporting SPIRITS
services, which are those originating in the PSTN (Public Switched
Telephone Network)and necessitating the interactions between the PSTN
and the Internet.  (Internet Call Waiting, Internet Caller-ID
Delivery, and Internet Call Forwarding are examples of SPIRIT
services.)  Specifically, it defines the components constituting the
architecture and the interfaces between the components.

This document is a product of the Service in the PSTN/IN Requesting
InTernet Service Working Group of the IETF.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.