On selection of IN parameters for the SPIRITS Protocol
draft-ietf-spirits-in-03
| Document | Type |
Expired Internet-Draft
(spirits WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Kumar Vemuri | ||
| Last updated | 2005-05-26 (Latest revision 2002-07-01) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Action Holders |
(None)
|
||
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | Jon Peterson | ||
| IESG note | |||
| Send notices to | <smb@research.att.com>, <abrusilovsky@ieee.org> |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes INAP parameters (IN information and its encoding) which the SPIRITS protocol can transport from the PSTN into the IP network. The SPIRITS protocol is a protocol through which PSTN can request actions (services) to be carried out in the IP network in response to events occurring within the PSTN/IN. These services include, but are not limited to: Incoming Call Notification (Internet Call Waiting), Internet Caller-Id Delivery, and Internet Call Forwarding ('Follow Me'). This draft outlines, what INAP parameters are of immediate interest to SPIRITS, how they may be extracted and encoded for use within the SPIRITS domain. INAP is used as an example protocol to clarify the SPIRITS message encoding process. This Internet-Draft has been written in response to the SPIRITS WG Chairs' call for SPIRITS Protocol proposals. It may be viewed as being a direct contribution to the Informational RFC on the SPIRITS protocol parameters. Among other contributions, this I-D is based on: o Informational RFC2995, 'Pre-SPIRITS implementations' o SPIRITS Architecture, presented in draft-ietf-spirits-architecture-02, RFC 3136 o SPIRITS Protocol Requirements, presented in draft-ietf-spirits-reqs-04, current candidate for Informational RFC.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)