ACAP Application Options Dataset Class
draft-ietf-acap-option-05
Document | Type |
Expired Internet-Draft
(acap WG)
Expired & archived
|
|
---|---|---|---|
Authors | Alexey Melnikov , Steve Hole | ||
Last updated | 2004-04-22 (Latest revision 2002-12-02) | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | Proposed Standard | ||
Formats | |||
Additional resources | anonymous%20IMAP%3A%20cyrus.andrew.cmu.edu%3Aarchive.ietf-acap | ||
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 | Ted Hardie | ||
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) is designed to support remote storage and access of application option, configura- tion and preference information. The generalized form of this run- time configuration is called 'options'. Options consist of any type of structured or unstructured data that an application requires to operate in a user specific manner.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)