RFC 3136 on The SPIRITS Architecture
RFC Editor <rfc-ed@ISI.EDU> Sat, 30 June 2001 00:04 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27835; Fri, 29 Jun 2001 20:04:39 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id TAA03431 for ietf-123-outbound.10@ietf.org; Fri, 29 Jun 2001 19:35:01 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id TAA03327 for <all-ietf@loki.ietf.org>; Fri, 29 Jun 2001 19:15:50 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA27007 for <all-ietf@ietf.org>; Fri, 29 Jun 2001 19:15:47 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.11.2/8.11.2) with ESMTP id f5TNGPG29943; Fri, 29 Jun 2001 16:16:25 -0700 (PDT)
Message-Id: <200106292316.f5TNGPG29943@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 3136 on The SPIRITS Architecture
Cc: rfc-ed@ISI.EDU, spiritis@lists.bell-lab.com
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 29 Jun 2001 16:16:25 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
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 Mailbox: faynberg@lucent.com, huilanlu@lucent.com, maw1@lucent.com, lslutsman@att.com Pages: 10 Characters: 19241 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-spirits-architecture-03.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3136.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 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 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. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.
- RFC 3136 on The SPIRITS Architecture RFC Editor