Transitional IMAP capabilities
draft-melnikov-imap-transitional-capa-00

Document Type Expired Internet-Draft (individual)
Last updated 2004-07-14
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html 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-melnikov-imap-transitional-capa-00.txt

Abstract

Software releases can't always wait for some document to become an RFC. As the result some software products are released when they implement a non-final version of an IMAP [IMAP4] extension. This may cause substantial interoperability problems between clients and servers that implement different revisions of the same document, as syntax and semantics of operations may change substantially between revisions of the same IMAP extension draft.

Authors

Alexey Melnikov (alexey.melnikov@isode.com)

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