This Working Group did not meet
NOTE: This charter is a snapshot of the 54th IETF Meeting in Yokohama, Japan. It may now be out-of-date.
Last Modifield: 07/31/2001
The Application Configuration Access Protocol is a proposed solution to the problems of client configuration for users of the internet.
Given the increasing prevalence of network access points and rapidly increasing numbers of users with diverse needs and settings, there is a phenomenon of internet application users who typically connect from more than one physical location and/or operating system to use the same set of internet services and applications. These users must recreate sets of personal configuration information for each system, session, and location that they use. This may include information such as application options and preferences; personal or shared user data such as addressbooks, bookmarks, or subscription lists; or shared data for internal client use, such as authorization group lists. The products of this working group will be: * a formal specification for the protocol * formal specifications of datasets used by the protocol and related extensions to the protocol * an RFC intended to move to a Standard in a timely manner * a specification for extensibility of the protocol in the form of a framework document * additional informational and/or experimental RFCs as necessary to amplify and/or extend ACAP.
Note on goals and milestones: because the work of the ACAP WG is based on the previous work done on IMSP, there is justification for a somewhat more aggressive schedule than is customary.
| Done | Submission of 'ACAP vs. Other Protocols' Informational Document for discussion | |
| Done | Second internet-draft of ACAP protocol specification | |
| Done | Submission of 'ACAP vs. Other Protocols' as Internet Draft | |
| Done | Submission of revised proposed WG charter to area directors | |
| Done | working group meeting at San Jose IETF | |
| Done | Working implementations of client and server library | |
| Done | Additional dataset specifications defined as directed by WG. | |
| Done | Final internet-draft of ACAP protocol submitted to IESG for consideration as Proposed Standard | |
| Done | Meet at Munich IETF. Discussion to include language-based orderings. | |
| Done | Submit remaining dataset class definitions I-D to IESG for considertation as a Proposed Standard. | |
| DEC 00 | Submit Final drafts of options, personal addressbook and mediatype dataset classes | |
| FEB 01 | Proposed standard recycle of ACAP base spec with bugfixes and possible change to mandatory-to-implement auth mechanism | |
| MAY 01 | Conclude WG. |
| RFC | Status | Title |
|---|---|---|
| RFC2244 | PS | ACAP -- Application Configuration Access Protocol |
| RFC2245 | PS | Anonymous SASL Mechanism |