ACAP Datatyping and Datatyping Discovery
draft-ietf-acap-dewinter-dtype-00
| Document | Type |
Expired Internet-Draft
(acap WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Jack De Winter | ||
| Last updated | 1997-04-25 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| 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 | |
| Consensus boilerplate | Unknown | ||
| 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) is designed to support remote storage and access of program option, configuration and preference information. In certain circumstances, it is desirable or necessary to deal with information that has a limit imposed on it. While the general ACAP specification does provide for a (SYNTAX) alert to inform the submittor that the stored information was not in a valid syntax for that field, there is no generic method to discover that syntax. There is strong feeling in the ACAP working group that variable length strings should be used for data where possible, but there is also the knowledge that ACAP will be used to configure and access existing systems where the use of such variable length strings may be difficult or impossible.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)