The Application Configuration Access Protocol in the Context of Other Internet Protocols
draft-wall-acap-vsothers-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Matt Wall | ||
| Last updated | 1996-09-12 | ||
| 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
The Application Configuration Access Protocol (ACAP) provides a client/server-based mechanism for remote access of structured list information appropriate to common uses by internet clients. This document contrasts the approach ACAP takes to the problem of remote storage of client information to the possible use of existing protocols for this same purpose.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)