A list of possible PINT functions
draft-conroy-pint-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 is one of a pair 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; the PINT work has similar requirements for a definition of the building blocks that might be used in future services (and so need to be supported by the protocol). This note provides the 'mirror image' of the associated SPIRITS draft, listing functional building blocks that may be executed in response to future PINT protocol requests.
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.)