IN- and PINT-related Requirements for SPIRITS Protocol
draft-faynberg-spirits-inpintreqs-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Igor Faynberg , Jorge Gato , Hui-Lan Lu , Lev Slutsman | ||
| Last updated | 2000-11-10 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This Internet-Draft is written in response to the SPIRITS WG chairs' call for contributions to the future RFC on the SPIRITS protocol requirements. The goal of this document is to introduce the requirements pertinent to Intelligent Network (IN) and the (future) work of PSTN/Internet iNTernetworking (PINT) WG. To this end, the SPIRITS architecture has been slightly augmented to demonstrate the relation of PINT to SPIRITS as discussed at the Adelaide meeting.
Authors
Igor Faynberg
Jorge Gato
Hui-Lan Lu
Lev Slutsman
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)