Application Access Protocol (ACAP) Numbers (last updated 2008-06-25) Registries included below: - ACAP Capabilities - ACAP Response Codes - Dataset Classes - Vendor Subtree Registry Name: ACAP Capabilities Reference: [RFC2244] Registration Procedures: Recommended working group review Registry: Name Reference ---------------------- --------- STARTTLS [RFC2595] Registry Name: ACAP Response Codes Reference: [RFC2244] Registration Procedures: Recommended working group review Registry: Name Reference ---------------------- --------- None Registry Name: Dataset Classes Reference: [RFC2244] Registration Procedures: Recommended working group review Registry: Name Reference ---------------------- --------- None Registry Name: Vendor Subtrees Reference: [RFC2244] Registration Procedures: First Come First Serve Registry: Name Reference -------------------------------------- --------- vendor.Qualcomm/Eudora [Gellens] vendor.Eudora [Gellens] vendor.ruslan [Shibayev] vendor.Cyrusoft/Mulberry [Daboo] vendor.Cyrusoft/SilkyMail [Daboo] vendor.corvu [Rollo] vendor.kolab [Faure] vendor.cmu/cyrus-imapd [Murchison] vendor.isode [Melnikov] vendor.alu/messaging [Esh] References ---------- [RFC2244] C. Newman and J. G. Myers, "ACAP -- Application Configuration Access Protocol", RFC 2244, November 1997. [RFC2595] Newman, C., "Using TLS with IMAP, POP3 and ACAP", RFC 2595, Innosoft, June 1999. People ------ [Daboo] Cyrus Daboo, , June 2000. [Esh] Thomas D. Esh, , 25 June 2008. [Faure] David Faure, , June 2004. [Gellens] Randall Gellens, , June 1998. [Melnikov] Alexey Melnikov, , 02 January 2008. [Murchison] Ken Murchison, , 15 November 2006. [Rollo] Troy Rollo, , June 2001. [Shibayev] Dmitry Shibayev, , April 1999. []