< draft-melnikov-imap-unselect-00.txt		draft-melnikov-imap-unselect-01.txt >
	Internet Draft: IMAP UNSELECT command A. Melnikov		Internet Draft: IMAP UNSELECT command A. Melnikov
	Document: draft-melnikov-imap-unselect-00.txt MessagingDirect		Document: draft-melnikov-imap-unselect-01.txt MessagingDirect
	Expires: April 2003		Expires: November 2003 May 2003
	Intended category: Standards Track		Intended category: Standards Track
	October 2002
	IMAP UNSELECT command		IMAP UNSELECT command
	Status of this Memo		Status of this Memo
	This document is an Internet-Draft and is in full conformance with		This document is an Internet-Draft and is in full conformance with
	all provisions of Section 10 of RFC2026. Internet-Drafts are working		all provisions of Section 10 of RFC2026. Internet-Drafts are working
	documents of the Internet Engineering Task Force (IETF), its areas,		documents of the Internet Engineering Task Force (IETF), its areas,
	and its working groups. Note that other groups may also distribute		and its working groups. Note that other groups may also distribute
	working documents as Internet-Drafts.		working documents as Internet-Drafts.
	skipping to change at page 1, line 37 ¶		skipping to change at page 1, line 36 ¶
	<http://www.ietf.org/shadow.html>.		<http://www.ietf.org/shadow.html>.
	A revised version of this draft document will be submitted to the RFC		A revised version of this draft document will be submitted to the RFC
	editor as a Proposed Standard for the Internet Community. Discussion		editor as a Proposed Standard for the Internet Community. Discussion
	and suggestions for improvement are requested, and should be sent to		and suggestions for improvement are requested, and should be sent to
	the IMAPEXT Mailing list <ietf-imapext@imc.org>. Distribution of this		the IMAPEXT Mailing list <ietf-imapext@imc.org>. Distribution of this
	draft is unlimited.		draft is unlimited.
	Copyright Notice		Copyright Notice
	Copyright (C) The Internet Society (2002). All Rights Reserved.		Copyright (C) The Internet Society (2003). All Rights Reserved.
	Table of Contents
	0. To do.........................................................1		Please see the Full Copyright section near the end of this document
	1. Abstract......................................................2		for more information.
	2. Conventions Used in this Document.............................2
	3. UNSELECT command..............................................3
	4. Security Considerations.......................................3
	5. Formal Syntax.................................................3
	6. Acknowledgments...............................................4
	7. References....................................................4
	8. Author's Addresses............................................4
	9. Full Copyright Statement......................................5
	1. Abstract		Abstract
	Certain types of IMAP clients need to release resources associated		Certain types of IMAP clients need to release resources associated
	with the selected mailbox without selecting a different mailbox.		with the selected mailbox without selecting a different mailbox.
	While [IMAP4] provides this functionality (via a SELECT command with		While [IMAP4] provides this functionality (via a SELECT command with
	an invalid argument), a more clean solution is desirable.		an invalid argument or reselecting the same mailbox with EXAMINE
			command), a more clean solution is desirable.
	[IMAP4] defines the CLOSE command that closes the selected mailbox as		[IMAP4] defines the CLOSE command that closes the selected mailbox as
	well as permanently removes all messages with the \Deleted flag set.		well as permanently removes all messages with the \Deleted flag set.
	However [IMAP4] lacks a command that simply closes the mailbox		However [IMAP4] lacks a command that simply closes the mailbox
	without expunging it. This document defines the UNSELECT command for		without expunging it. This document defines the UNSELECT command for
	this purpose.		this purpose.
	A server which supports this extension indicates this with a		A server which supports this extension indicates this with a
	capability name of "UNSELECT".		capability name of "UNSELECT".
	2. Conventions Used in this Document		Table of Contents
			1. Conventions Used in this Document............................ 2
			2. UNSELECT command............................................. 3
			3. Security Considerations...................................... 3
			4. Formal Syntax................................................ 3
			5. Acknowledgments.............................................. 4
			6. Normative References......................................... 4
			7. Author's Addresses........................................... 4
			1. Conventions Used in this Document
	"C:" and "S:" in examples show lines sent by the client and server		"C:" and "S:" in examples show lines sent by the client and server
	respectively.		respectively.
	The keywords "MUST", "MUST NOT", "SHOULD", "SHOULD NOT", and "MAY" in		The keywords "MUST", "MUST NOT", "SHOULD", "SHOULD NOT", and "MAY"
	this document when typed in uppercase are to be interpreted as		in this document when typed in uppercase are to be interpreted as
	defined in "Key words for use in RFCs to Indicate Requirement Levels"		defined in "Key words for use in RFCs to Indicate Requirement Levels"
	[KEYWORDS].		[KEYWORDS].
	3. UNSELECT Command		2. UNSELECT Command
	Arguments: none		Arguments: none
	Responses: no specific responses for this command		Responses: no specific responses for this command
	Result: OK - unselect completed, now in authenticated state		Result: OK - unselect completed, now in authenticated state
	BAD - no mailbox selected, or argument supplied but		BAD - no mailbox selected, or argument supplied but
	none permitted		none permitted
	The UNSELECT command frees server's resources associated with		The UNSELECT command frees server's resources associated with
	the selected mailbox and returns the server to the authenticated		the selected mailbox and returns the server to the authenticated
	state. This command performs the same actions as CLOSE, except		state. This command performs the same actions as CLOSE, except
	that no messages are permanently removed from the currently		that no messages are permanently removed from the currently
	selected mailbox.		selected mailbox.
	Example: C: A341 UNSELECT		Example: C: A341 UNSELECT
	S: A341 OK Unselect completed		S: A341 OK Unselect completed
	4. Security Considerations		3. Security Considerations
	It is belived that this extension doesn't raise any additional		It is belived that this extension doesn't raise any additional security
	security concerns not already discussed in [IMAP4].		concerns not already discussed in [IMAP4].
	5. Formal Syntax		4. Formal Syntax
	The following syntax specification uses the augmented Backus-Naur		The following syntax specification uses the augmented Backus-Naur
	Form (BNF) notation as specified in [RFC-822] as modified by [IMAP4].		Form (BNF) notation as specified in [RFC-822] as modified by [IMAP4].
	Non-terminals referenced but not defined below are as defined by		Non-terminals referenced but not defined below are as defined by
	[IMAP4].		[IMAP4].
	Except as noted otherwise, all alphabetic characters are case-		Except as noted otherwise, all alphabetic characters are case-
	insensitive. The use of upper or lower case characters to define		insensitive. The use of upper or lower case characters to define
	token strings is for editorial clarity only. Implementations MUST		token strings is for editorial clarity only. Implementations MUST
	accept these strings in a case-insensitive fashion.		accept these strings in a case-insensitive fashion.
	command-select /= "UNSELECT"		command-select /= "UNSELECT"
	6. Acknowledgments		5. Acknowledgments
	UNSELECT command was originally implemented in CMU IMAP server.		UNSELECT command was originally implemented by Tim Showalter in
			Cyrus IMAP server.
	Also, the author of the document would like to thank Vladimir Butenko		Also, the author of the document would like to thank Vladimir
	and Mark Crispin for reminding that UNSELECT has to be documented.		Butenko and Mark Crispin for reminding that UNSELECT has to be
			documented. Also thanks to Simon Josefsson for pointing out that
			there are multiple ways to implement UNSELECT.
	7. References		6. Normative References
	[KEYWORDS] Bradner, S., "Key words for use in RFCs to Indicate		[KEYWORDS] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", RFC 2119, March 1997.		Requirement Levels", RFC 2119, March 1997.
	[IMAP4] Crispin, M., "Internet Message Access Protocol - Version		[IMAP4] Crispin, M., "Internet Message Access Protocol - Version
	4rev1", RFC 2060, University of Washington, December 1996.		4rev1", RFC 2060, University of Washington, December 1996.
	8. Author's Addresses		7. Author's Addresses
	Alexey Melnikov		Alexey Melnikov
	ACI Worldwide/MessagingDirect		ACI Worldwide/MessagingDirect
	Address: 59 Clarendon Road, Watford, Hertfordshire, United Kingdom, WD17 1FQ		Address: 59 Clarendon Road, Watford,
			Hertfordshire, United Kingdom, WD17 1FQ
	Phone: +44 1923 81 2877		Phone: +44 1923 81 2877
	Email: mel@messagingdirect.com		Email: mel@messagingdirect.com
	9. Full Copyright Statement		Intellectual Property Statement
	Copyright (C) The Internet Society (2002). All Rights Reserved.		The IETF takes no position regarding the validity or scope of any
			intellectual property or other rights that might be claimed to
			pertain to the implementation or use of the technology described in
			this document or the extent to which any license under such rights
			might or might not be available; neither does it represent that it
			has made any effort to identify any such rights. Information on the
			IETF's procedures with respect to rights in standards-track and
			standards-related documentation can be found in BCP-11. Copies of
			claims of rights made available for publication and any assurances of
			licenses to be made available, or the result of an attempt made to
			obtain a general license or permission for the use of such
			proprietary rights by implementors or users of this specification can
			be obtained from the IETF Secretariat.
			The IETF invites any interested party to bring to its attention any
			copyrights, patents or patent applications, or other proprietary
			rights which may cover technology that may be required to practice
			this standard. Please address the information to the IETF Executive
			Director.
			Full Copyright Statement
			Copyright (C) The Internet Society (2003). All Rights Reserved.
	This document and translations of it may be copied and furnished to		This document and translations of it may be copied and furnished to
	others, and derivative works that comment on or otherwise explain it		others, and derivative works that comment on or otherwise explain it
	or assist in its implementation may be prepared, copied, published		or assist in its implementation may be prepared, copied, published
	and distributed, in whole or in part, without restriction of any		and distributed, in whole or in part, without restriction of any
	kind, provided that the above copyright notice and this paragraph are		kind, provided that the above copyright notice and this paragraph are
	included on all such copies and derivative works. However, this		included on all such copies and derivative works. However, this
	document itself may not be modified in any way, such as by removing		document itself may not be modified in any way, such as by removing
	the copyright notice or references to the Internet Society or other		the copyright notice or references to the Internet Society or other
	Internet organizations, except as needed for the purpose of		Internet organizations, except as needed for the purpose of
End of changes. 21 change blocks.
	35 lines changed or deleted		63 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/