Transitional IMAP capabilities
draft-melnikov-imap-transitional-capa-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Alexey Melnikov | ||
| Last updated | 2004-07-14 | ||
| Stream | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
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
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)