<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.melnikov-imap-transitional-capa" target="https://datatracker.ietf.org/doc/html/draft-melnikov-imap-transitional-capa-00">
   <front>
      <title>Transitional IMAP capabilities</title>
      <author initials="A." surname="Melnikov" fullname="Alexey Melnikov">
         <organization>Isode Ltd.</organization>
      </author>
      <date month="July" day="14" year="2004" />
      <abstract>
	 <t>   Software releases can&#x27;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.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-melnikov-imap-transitional-capa-00" />
   
</reference>
