A list of possible SPIRITS functions
draft-conroy-spirits-act-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Lawrence W. Conroy , Jeremy R. Buller | ||
Last updated | 2000-08-11 | ||
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 has been written at the request of one of the SPIRITS Working Group co-chairs in order to elicit discussion on what extended functionality SPIRITS may be used to provide. It has been requested that mapping to any specific protocol is not undertaken at this juncture. As such, only 'possible' functionality is identified and no mapping to existing protocol methods is given. This document is only intended to provide a basis for discussion and would be expected to form one aspect of the requirements for SPIRITS. As such the terminology used is deliberately and (we hope) suitably ambiguous.
Authors
Lawrence W. Conroy
Jeremy R. Buller
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)