Handling Message Disposition Notification with JMAP
draft-ietf-jmap-mdn-01

The information below is for an old version of the document
Document Type Active Internet-Draft (jmap WG)
Last updated 2019-03-07
Stream IETF
Intended RFC status (None)
Formats pdf htmlized bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
JMAP                                                     R. Ouazana, Ed.
Internet-Draft                                                  Linagora
Intended status: Standards Track                           March 7, 2019
Expires: September 8, 2019

          Handling Message Disposition Notification with JMAP
                         draft-ietf-jmap-mdn-01

Abstract

   This document specifies a data model for handling [RFC8098] MDN
   messages with a server using JMAP.

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 September 8, 2019.

Copyright Notice

   Copyright (c) 2019 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 September 8, 2019               [Page 1]
Internet-Draft              JMAP MDN handling                 March 2019

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Methods added to the EmailSubmission object . . . . . . . . .   4
     3.1.  EmailSubmission/sendMDN . . . . . . . . . . . . . . . . .   4
     3.2.  EmailSubmission/parseMDN  . . . . . . . . . . . . . . . .   5
   4.  Samples . . . . . . . . . . . . . . . . . . . . . . . . . . .   6
     4.1.  Sending an MDN for a received email . . . . . . . . . . .   6
     4.2.  Asking for MDN when sending an email  . . . . . . . . . .   7
     4.3.  Parsing a received MDN  . . . . . . . . . . . . . . . . .   8
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
     5.1.  JMAP Capability Registration for "mdn"  . . . . . . . . .   8
     5.2.  Registration of JMAP keyword '$MDNSent' . . . . . . . . .   9
   6.  Security considerations . . . . . . . . . . . . . . . . . . .   9
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  10
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  10
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   JMAP ([I-D.ietf-jmap-core] - 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 aims to provide a consistent interface to
   different data types.

   MDN are defined in [RFC8098] and are used as "read receipts",
   "acknowledgements", or "receipt notifications".

   A client can have to deal with MDN in different ways:

   1.  When receiving an email, an MDN can be sent to the sender.  This
       specification defines an EmailSubmission/sendMDN method to cover
       this case.

   2.  When sending an email, an MDN can be requested.  This must be
       done with the help of a header, and is already specified by
       [RFC8098] and can already be handled by [I-D.ietf-jmap-mail] this
       way.

   3.  When receiving an MDN, the MDN could be related to an existing
       sent mail.  This is already covered by [I-D.ietf-jmap-mail] in
       the EmailSubmission object.  Client could want to display

Ouazana                 Expires September 8, 2019               [Page 2]
Internet-Draft              JMAP MDN handling                 March 2019

       detailed information about a received MDN.  This specification
       defines a EmailSubmission/parseMDN method to cover this case.

1.1.  Notational conventions

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
Show full document text