RFC 2244: ACAP -- Application Configuration Access Protocol
In plain English — editorial summary, not part of the RFC
The Application Configuration Access Protocol (ACAP) is designed to support remote storage and access of program option, configuration and preference information. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2244
- Published
- November 1997
- Authors
- C. Newman; J. G. Myers
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 71
- Also known as
- —
- Updated by:
- RFC 6075
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2392Content-ID and Message-ID Uniform Resource LocatorsCurrent
August 1998
- RFC 3510Internet Printing Protocol/1.1: IPP URL SchemeCurrent
April 2003
- RFC 3421Select and Sort Extensions for the Service Location Protocol (SLP)Current
November 2002
- RFC 2295Transparent Content Negotiation in HTTPCurrent
March 1998
- RFC 2296HTTP Remote Variant Selection Algorithm -- RVSA/1.0Current
March 1998
- RFC 2369The Use of URLs as Meta-Syntax for Core Mail List Commands and their Transport through Message Header FieldsCurrent
July 1998
- RFC 2111Content-ID and Message-ID Uniform Resource LocatorsObsoleted
March 1997
- RFC 2079Definition of an X.500 Attribute Type and an Object Class to Hold Uniform Resource Identifiers (URIs)Current
January 1997
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?