idnits 2.17.00 (12 Aug 2021) /tmp/idnits20124/draft-melnikov-imap-unselect-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == The page length should not exceed 58 lines per page, but there was 5 longer pages, the longest (page 2) being 60 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 6 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** There is 1 instance of too long lines in the document, the longest one being 2 characters in excess of 72. ** The abstract seems to contain references ([IMAP4]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (May 2003) is 6939 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFC-822' is mentioned on line 105, but not defined ** Obsolete undefined reference: RFC 822 (Obsoleted by RFC 2822) ** Obsolete normative reference: RFC 2060 (ref. 'IMAP4') (Obsoleted by RFC 3501) Summary: 10 errors (**), 0 flaws (~~), 5 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft: IMAP UNSELECT command A. Melnikov 3 Document: draft-melnikov-imap-unselect-01.txt MessagingDirect 4 Expires: November 2003 May 2003 5 Intended category: Standards Track 7 IMAP UNSELECT command 9 Status of this Memo 11 This document is an Internet-Draft and is in full conformance with 12 all provisions of Section 10 of RFC2026. Internet-Drafts are working 13 documents of the Internet Engineering Task Force (IETF), its areas, 14 and its working groups. Note that other groups may also distribute 15 working documents as Internet-Drafts. 17 Internet-Drafts are draft documents valid for a maximum of six months 18 and may be updated, replaced, or obsoleted by other documents at any 19 time. It is inappropriate to use Internet-Drafts as reference 20 material or to cite them other than as "work in progress." 22 The list of current Internet-Drafts can be accessed at 23 . The list of Internet- 24 Draft Shadow Directories can be accessed at 25 . 27 A revised version of this draft document will be submitted to the RFC 28 editor as a Proposed Standard for the Internet Community. Discussion 29 and suggestions for improvement are requested, and should be sent to 30 the IMAPEXT Mailing list . Distribution of this 31 draft is unlimited. 33 Copyright Notice 35 Copyright (C) The Internet Society (2003). All Rights Reserved. 37 Please see the Full Copyright section near the end of this document 38 for more information. 40 Abstract 42 Certain types of IMAP clients need to release resources associated 43 with the selected mailbox without selecting a different mailbox. 44 While [IMAP4] provides this functionality (via a SELECT command with 45 an invalid argument or reselecting the same mailbox with EXAMINE 46 command), a more clean solution is desirable. 48 [IMAP4] defines the CLOSE command that closes the selected mailbox as 49 well as permanently removes all messages with the \Deleted flag set. 51 However [IMAP4] lacks a command that simply closes the mailbox 52 without expunging it. This document defines the UNSELECT command for 53 this purpose. 55 A server which supports this extension indicates this with a 56 capability name of "UNSELECT". 58 Table of Contents 60 1. Conventions Used in this Document............................ 2 61 2. UNSELECT command............................................. 3 62 3. Security Considerations...................................... 3 63 4. Formal Syntax................................................ 3 64 5. Acknowledgments.............................................. 4 65 6. Normative References......................................... 4 66 7. Author's Addresses........................................... 4 68 1. Conventions Used in this Document 70 "C:" and "S:" in examples show lines sent by the client and server 71 respectively. 73 The keywords "MUST", "MUST NOT", "SHOULD", "SHOULD NOT", and "MAY" 74 in this document when typed in uppercase are to be interpreted as 75 defined in "Key words for use in RFCs to Indicate Requirement Levels" 76 [KEYWORDS]. 78 2. UNSELECT Command 80 Arguments: none 82 Responses: no specific responses for this command 84 Result: OK - unselect completed, now in authenticated state 85 BAD - no mailbox selected, or argument supplied but 86 none permitted 88 The UNSELECT command frees server's resources associated with 89 the selected mailbox and returns the server to the authenticated 90 state. This command performs the same actions as CLOSE, except 91 that no messages are permanently removed from the currently 92 selected mailbox. 94 Example: C: A341 UNSELECT 95 S: A341 OK Unselect completed 97 3. Security Considerations 99 It is belived that this extension doesn't raise any additional security 100 concerns not already discussed in [IMAP4]. 102 4. Formal Syntax 104 The following syntax specification uses the augmented Backus-Naur 105 Form (BNF) notation as specified in [RFC-822] as modified by [IMAP4]. 106 Non-terminals referenced but not defined below are as defined by 107 [IMAP4]. 109 Except as noted otherwise, all alphabetic characters are case- 110 insensitive. The use of upper or lower case characters to define 111 token strings is for editorial clarity only. Implementations MUST 112 accept these strings in a case-insensitive fashion. 114 command-select /= "UNSELECT" 116 5. Acknowledgments 118 UNSELECT command was originally implemented by Tim Showalter in 119 Cyrus IMAP server. 121 Also, the author of the document would like to thank Vladimir 122 Butenko and Mark Crispin for reminding that UNSELECT has to be 123 documented. Also thanks to Simon Josefsson for pointing out that 124 there are multiple ways to implement UNSELECT. 126 6. Normative References 128 [KEYWORDS] Bradner, S., "Key words for use in RFCs to Indicate 129 Requirement Levels", RFC 2119, March 1997. 131 [IMAP4] Crispin, M., "Internet Message Access Protocol - Version 132 4rev1", RFC 2060, University of Washington, December 1996. 134 7. Author's Addresses 136 Alexey Melnikov 137 ACI Worldwide/MessagingDirect 138 Address: 59 Clarendon Road, Watford, 139 Hertfordshire, United Kingdom, WD17 1FQ 141 Phone: +44 1923 81 2877 143 Email: mel@messagingdirect.com 145 Intellectual Property Statement 147 The IETF takes no position regarding the validity or scope of any 148 intellectual property or other rights that might be claimed to 149 pertain to the implementation or use of the technology described in 150 this document or the extent to which any license under such rights 151 might or might not be available; neither does it represent that it 152 has made any effort to identify any such rights. Information on the 153 IETF's procedures with respect to rights in standards-track and 154 standards-related documentation can be found in BCP-11. Copies of 155 claims of rights made available for publication and any assurances of 156 licenses to be made available, or the result of an attempt made to 157 obtain a general license or permission for the use of such 158 proprietary rights by implementors or users of this specification can 159 be obtained from the IETF Secretariat. 161 The IETF invites any interested party to bring to its attention any 162 copyrights, patents or patent applications, or other proprietary 163 rights which may cover technology that may be required to practice 164 this standard. Please address the information to the IETF Executive 165 Director. 167 Full Copyright Statement 169 Copyright (C) The Internet Society (2003). All Rights Reserved. 171 This document and translations of it may be copied and furnished to 172 others, and derivative works that comment on or otherwise explain it 173 or assist in its implementation may be prepared, copied, published 174 and distributed, in whole or in part, without restriction of any 175 kind, provided that the above copyright notice and this paragraph are 176 included on all such copies and derivative works. However, this 177 document itself may not be modified in any way, such as by removing 178 the copyright notice or references to the Internet Society or other 179 Internet organizations, except as needed for the purpose of 180 developing Internet standards in which case the procedures for 181 copyrights defined in the Internet Standards process must be 182 followed, or as required to translate it into languages other than 183 English. 185 The limited permissions granted above are perpetual and will not be 186 revoked by the Internet Society or its successors or assigns. 188 This document and the information contained herein is provided on an 189 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 190 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 191 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 192 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 193 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 195 Acknowledgement 197 Funding for the RFC Editor function is currently provided by the 198 Internet Society.