draft-ietf-jmap-mdn-11.txt   draft-ietf-jmap-mdn-12.txt 
JMAP R. Ouazana, Ed. JMAP R. Ouazana, Ed.
Internet-Draft Linagora Internet-Draft Linagora
Intended status: Standards Track June 22, 2020 Intended status: Standards Track June 25, 2020
Expires: December 24, 2020 Expires: December 27, 2020
Handling Message Disposition Notification with JMAP Handling Message Disposition Notification with JMAP
draft-ietf-jmap-mdn-11 draft-ietf-jmap-mdn-12
Abstract Abstract
JMAP ([RFC8620] - JSON Meta Application Protocol) is a generic JMAP ([RFC8620] - JSON Meta Application Protocol) is a generic
protocol for synchronising data, such as mail, calendars or contacts, protocol for synchronising data, such as mail, calendars or contacts,
between a client and a server. It is optimised for mobile and web between 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)
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 24, 2020. This Internet-Draft will expire on December 27, 2020.
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 6, line 5 skipping to change at page 6, line 5
o accountId: "Id" The id of the account to use. o accountId: "Id" The id of the account to use.
o identityId: "Id" The id of the Identity to associate with these o identityId: "Id" The id of the Identity to associate with these
MDN. The server will use this identity to define the sender of MDN. The server will use this identity to define the sender of
the MDN and to set the finalRecipient field. the MDN and to set the finalRecipient field.
o send: "Id[MDN]" A map of creation id (client specified) to MDN o send: "Id[MDN]" A map of creation id (client specified) to MDN
objects. objects.
o onSuccessUpdateEmail: "Id[PatchObject]|null" A map of creation id o onSuccessUpdateEmail: "Id[PatchObject]|null" A map of id to an
to an object containing properties to update on the Email object object containing properties to update on the Email object
referenced by the "MDN/send" if the sending succeeds. referenced by the "MDN/send" if the sending succeeds. This will
always be a backreference to the creation id (see example below in
Section 3.1).
The response has the following arguments: The response has the following arguments:
o accountId: "Id" The id of the account used for the call. o accountId: "Id" The id of the account used for the call.
o sent: "Id[MDN]|null" A map of creation id to MDN containing any o sent: "Id[MDN]|null" A map of creation id to MDN containing any
properties that were not set by the client. This includes any properties that were not set by the client. This includes any
properties that were omitted by the client and thus set to a properties that were omitted by the client and thus set to a
default by the server. This argument is null if no MDN objects default by the server. This argument is null if no MDN objects
were successfully sent. were successfully sent.
skipping to change at page 9, line 19 skipping to change at page 9, line 22
"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" ],
[ "Email/set", { [ "Email/set", {
"accountId": "ue150411c", "accountId": "ue150411c",
"oldState": "23", "oldState": "23",
"newState": "42", "newState": "42",
"updated": { "updated": {
"Md45b47b4877521042cec0938": { "Md45b47b4877521042cec0938": {}
"keywords": {
"$mdnsent": true
}
}
} }
}, "0" ]] }, "0" ]]
If the "$mdnsent" keyword has already been set, the server can answer If the "$mdnsent" keyword has already been set, the server can answer
an error: an error:
[[ "MDN/send", { [[ "MDN/send", {
"accountId": "ue150411c", "accountId": "ue150411c",
"notSent": { "notSent": {
"k1546": { "k1546": {
 End of changes. 5 change blocks. 
12 lines changed or deleted 10 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/