Lessons Learned from IMSP
draft-newman-acap-imsp-lessons-02

Document Type Expired Internet-Draft (individual)
Author Chris Newman 
Last updated 1996-12-23 (latest revision 1996-12-24)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-newman-acap-imsp-lessons-02.txt

Abstract

IMSP (Internet Message Support Protocol) [IMSP] was designed and implemented to supply the support functions necessary for a large scale IMAP4 based infrastructure with highly mobile users. Although the protocol was successful in its mission, it was realized that a slightly different approach could achieve more for the Internet Standards community. Thus was born the idea for ACAP (Application Configuration Access Protocol) [ACAP].

Authors

Chris Newman (chris.newman@sun.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)