Handling Message Disposition Notification with JMAP
draft-ietf-jmap-mdn-17
Document | Type | Active Internet-Draft (jmap WG) | ||
---|---|---|---|---|
Author | Raphaƫl Ouazana | |||
Last updated | 2021-02-01 (latest revision 2021-01-28) | |||
Stream | Internent Engineering Task Force (IETF) | |||
Intended RFC status | Proposed Standard | |||
Formats | plain text xml pdf htmlized (tools) htmlized bibtex | |||
Reviews | ||||
Stream | WG state | Submitted to IESG for Publication (wg milestone: Jun 2020 - Submit Message Dispo... ) | ||
Document shepherd | Bron Gondwana | |||
Shepherd write-up | Show (last changed 2020-07-03) | |||
IESG | IESG state | RFC Ed Queue | ||
Action Holders |
(None)
|
|||
Consensus Boilerplate | Yes | |||
Telechat date | ||||
Responsible AD | Barry Leiba | |||
Send notices to | Bron Gondwana <brong@fastmailteam.com> | |||
IANA | IANA review state | Version Changed - Review Needed | ||
IANA action state | RFC-Ed-Ack | |||
IANA expert review state | Expert Reviews OK | |||
RFC Editor | RFC Editor state | EDIT | ||
Details |
JMAP R. Ouazana, Ed. Internet-Draft Linagora Intended status: Standards Track January 28, 2021 Expires: August 1, 2021 Handling Message Disposition Notification with JMAP draft-ietf-jmap-mdn-17 Abstract This document specifies a data model for handling Message Disposition Notifications (MDNs, RFC 8098) in the JSON Meta Application Protocol (JMAP, RFCs 8620 and 8621). Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on August 1, 2021. Copyright Notice Copyright (c) 2021 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Ouazana Expires August 1, 2021 [Page 1] Internet-Draft JMAP MDN handling January 2021 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Notational conventions . . . . . . . . . . . . . . . . . 3 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.3. Addition to the capabilities object . . . . . . . . . . . 3 2. MDN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2.1. MDN/send . . . . . . . . . . . . . . . . . . . . . . . . 5 2.2. MDN/parse . . . . . . . . . . . . . . . . . . . . . . . . 7 3. Samples . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 3.1. Sending an MDN for a received email message . . . . . . . 8 3.2. Asking for MDN when sending an email message . . . . . . 9 3.3. Parsing a received MDN . . . . . . . . . . . . . . . . . 10 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 4.1. JMAP Capability Registration for "mdn" . . . . . . . . . 11 4.2. JMAP Error Codes Registry . . . . . . . . . . . . . . . . 12 5. Security considerations . . . . . . . . . . . . . . . . . . . 12 6. Normative References . . . . . . . . . . . . . . . . . . . . 12 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 13 1. Introduction JMAP ([RFC8620] - JSON Meta Application Protocol) is a generic protocol for synchronising data, such as mail, calendars or contacts, between a client and a server. It is optimised for mobile and web environments, and provides a consistent interface to different data types. JMAP for Mail ([RFC8621] - The JSON Meta Application Protocol (JMAP) for Mail) specifies a data model for synchronising email data with a server using JMAP. Clients can use this to efficiently search, access, organise, and send messages. Message Disposition Notifications (MDNs) are defined in [RFC8098] and are used as "read receipts", "acknowledgements", or "receipt notifications". A client can come across MDNs in different ways: 1. When receiving an email message, an MDN can be sent to the sender. This specification defines an MDN/send method to cover this case. 2. When sending an email message, an MDN can be requested. This must be done with the help of a header field, and is already specified by [RFC8098] and can already be handled by [RFC8621] this way. Ouazana Expires August 1, 2021 [Page 2] Internet-Draft JMAP MDN handling January 2021 3. When receiving an MDN, the MDN could be related to an existing sent message. This is already covered by [RFC8621] in the EmailSubmission object. A client might want to display detailed information about a received MDN. This specification defines an MDN/parse method to cover this case.Show full document text