draft-ietf-extra-imap-replace-01.txt		draft-ietf-extra-imap-replace-02.txt
	Network Working Group S. Brandt		Network Working Group S. Brandt
	Internet-Draft Verizon		Internet-Draft Verizon
	Intended status: Standards Track October 1, 2018		Intended status: Standards Track October 12, 2018
	Expires: April 4, 2019		Expires: April 15, 2019
	IMAP REPLACE Extension		IMAP REPLACE Extension
	draft-ietf-extra-imap-replace-01		draft-ietf-extra-imap-replace-02
	Abstract		Abstract
	This document defines an IMAP extension which can be used to replace		This document defines an IMAP extension which can be used to replace
	an existing message in a message store with a new message. Message		an existing message in a message store with a new message. Message
	replacement is a common operation for clients that automatically save		replacement is a common operation for clients that automatically save
	drafts or notes as a user composes them.		drafts or notes as a user composes them.
	Status of This Memo		Status of This Memo
	skipping to change at page 1, line 33 ¶		skipping to change at page 1, line 33 ¶
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at https://datatracker.ietf.org/drafts/current/.		Drafts is at https://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	This Internet-Draft will expire on April 4, 2019.		This Internet-Draft will expire on April 15, 2019.
	Copyright Notice		Copyright Notice
	Copyright (c) 2018 IETF Trust and the persons identified as the		Copyright (c) 2018 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(https://trustee.ietf.org/license-info) in effect on the date of		(https://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	skipping to change at page 9, line 20 ¶		skipping to change at page 9, line 20 ¶
	capability =/ "REPLACE"		capability =/ "REPLACE"
	command-select =/ replace		command-select =/ replace
	replace = "REPLACE" SP seq-number SP mailbox append-message		replace = "REPLACE" SP seq-number SP mailbox append-message
	uid = "UID" SP (copy / fetch/ search / store / move /		uid = "UID" SP (copy / fetch/ search / store / move /
	replace)		replace)
	6. Security Considerations		6. Security Considerations
	This document is believed to add no security problems beyond those		This document is believed to add no security problems beyond those
	that may already exist with the base IMAP specificaiton.		that may already exist with the base IMAP specification. The REPLACE
			command may actually prevent some potential security problems because
			it avoids intermediate message states that could possibly be
			exploited by an attacker.
	7. IANA Considerations		7. IANA Considerations
	The IANA is requested to add REPLACE to the "IMAP 4 Capabilities"		The IANA is requested to add REPLACE to the "IMAP 4 Capabilities"
	registry, http://www.iana.org/assignments/imap4-capabilities.		registry, http://www.iana.org/assignments/imap4-capabilities.
	8. Acknowledgements		8. Acknowledgements
	The author would like to thank the participants of IMAPEXT with		The author would like to thank the participants of IMAPEXT with
	particular thanks to Arnt Gulbrandsen, Alexey Melkinov, Chris Newman,		particular thanks to Arnt Gulbrandsen, Alexey Melkinov, Chris Newman,
End of changes. 4 change blocks.
	5 lines changed or deleted		8 lines changed or added
This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/