draft-ietf-jmap-mdn-12.txt		draft-ietf-jmap-mdn-13.txt
	JMAP R. Ouazana, Ed.		JMAP R. Ouazana, Ed.
	Internet-Draft Linagora		Internet-Draft Linagora
	Intended status: Standards Track June 25, 2020		Intended status: Standards Track July 2, 2020
	Expires: December 27, 2020		Expires: January 3, 2021
	Handling Message Disposition Notification with JMAP		Handling Message Disposition Notification with JMAP
	draft-ietf-jmap-mdn-12		draft-ietf-jmap-mdn-13
	Abstract		Abstract
	JMAP ([RFC8620] - JSON Meta Application Protocol) is a generic		JMAP (RFC8620 - JSON Meta Application Protocol) is a generic protocol
	protocol for synchronising data, such as mail, calendars or contacts,		for synchronising data, such as mail, calendars or contacts, between
	between a client and a server. It is optimised for mobile and web		a client and a server. It is optimised for mobile and web
	environments, and aims to provide a consistent interface to different		environments, and aims to provide a consistent interface to different
	data types.		data types.
	JMAP for Mail ([RFC8621] - The JSON Meta Application Protocol (JMAP)		JMAP for Mail (RFC8621 - The JSON Meta Application Protocol (JMAP)
	for Mail) specifies a data model for synchronising email data with a		for Mail) specifies a data model for synchronising email data with a
	server using JMAP. Clients can use this to efficiently search,		server using JMAP. Clients can use this to efficiently search,
	access, organise, and send messages.		access, organise, and send messages.
	MDN are defined in [RFC8098] and are used as "read receipts",		MDN are defined in RFC8098 and are used as "read receipts",
	"acknowledgements", or "receipt notifications".		"acknowledgements", or "receipt notifications".
	MDN have a specific format that must be parsed or generated. The		MDN have a specific format that must be parsed or generated. The
	goal of this document is to specify a data model for handling MDN		goal of this document is to specify a data model for handling MDN
	messages with a server using JMAP.		messages with a server using JMAP.
	Status of This Memo		Status of This Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	skipping to change at page 1, line 46 ¶		skipping to change at page 1, line 46 ¶
	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 December 27, 2020.		This Internet-Draft will expire on January 3, 2021.
	Copyright Notice		Copyright Notice
	Copyright (c) 2020 IETF Trust and the persons identified as the		Copyright (c) 2020 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 8, line 40 ¶		skipping to change at page 8, line 40 ¶
	"forEmailId": "Md45b47b4877521042cec0938",		"forEmailId": "Md45b47b4877521042cec0938",
	"subject": "Read receipt for: World domination",		"subject": "Read receipt for: World domination",
	"textBody": "This receipt shows that the email has been		"textBody": "This receipt shows that the email has been
	displayed on your recipient's computer. There is no		displayed on your recipient's computer. There is no
	guaranty it has been read or understood.",		guaranty it has been read or understood.",
	"reportingUA": "linagora.com; OpenPaaS",		"reportingUA": "linagora.com; OpenPaaS",
	"disposition": {		"disposition": {
	"actionMode": "manual-action",		"actionMode": "manual-action",
	"sendingMode": "mdn-sent-manually",		"sendingMode": "mdn-sent-manually",
	"type": "displayed"		"type": "displayed"
	}		},
	"extension": {		"extension": {
	"X-EXTENSION-EXAMPLE": "example.com"		"X-EXTENSION-EXAMPLE": "example.com"
	}		}
	}		}
	},		},
	"onSuccessUpdateEmail": {		"onSuccessUpdateEmail": {
	"#k1546": {		"#k1546": {
	"keywords/$mdnsent": true		"keywords/$mdnsent": true
	}		}
	}		}
	skipping to change at page 11, line 19 ¶		skipping to change at page 11, line 19 ¶
	"forEmailId": "Md45b47b4877521042cec0938",		"forEmailId": "Md45b47b4877521042cec0938",
	"subject": "Read receipt for: World domination",		"subject": "Read receipt for: World domination",
	"textBody": "This receipt shows that the email has been		"textBody": "This receipt shows that the email has been
	displayed on your recipient's computer. There is no		displayed on your recipient's computer. There is no
	guaranty it has been read or understood.",		guaranty it has been read or understood.",
	"reportingUA": "linagora.com; OpenPaaS",		"reportingUA": "linagora.com; OpenPaaS",
	"disposition": {		"disposition": {
	"actionMode": "manual-action",		"actionMode": "manual-action",
	"sendingMode": "mdn-sent-manually",		"sendingMode": "mdn-sent-manually",
	"type": "displayed"		"type": "displayed"
	}		},
	"finalRecipient": "rfc822; john@example.com",		"finalRecipient": "rfc822; john@example.com",
	"originalMessageId": "<1521557867.2614.0.camel@apache.org>"		"originalMessageId": "<1521557867.2614.0.camel@apache.org>"
	}		}
	}		}
	}, "0" ]]		}, "0" ]]
	In case of a not found blobId, the server would respond:		In case of a not found blobId, the server would respond:
	[[ "MDN/parse", {		[[ "MDN/parse", {
	"accountId": "ue150411c",		"accountId": "ue150411c",
End of changes. 8 change blocks.
	11 lines changed or deleted		11 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/