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

Document Type Active Internet-Draft (jmap WG)
Last updated 2019-11-21 (latest revision 2019-11-20)
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf htmlized bibtex
Stream WG state In WG Last Call (wg milestone: Dec 2019 - Submit Message Dispo... )
Document shepherd Bron Gondwana
IESG IESG state I-D Exists
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to Bron Gondwana <brong@fastmailteam.com>
JMAP                                                     R. Ouazana, Ed.
Internet-Draft                                                  Linagora
Intended status: Standards Track                       November 20, 2019
Expires: May 23, 2020

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

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 May 23, 2020.

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 May 23, 2020                  [Page 1]
Internet-Draft              JMAP MDN handling              November 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
     2.1.  MDN/set . . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.2.  MDN/parse . . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Samples . . . . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  Sending an MDN for a received email . . . . . . . . . . .   5
     3.2.  Asking for MDN when sending an email  . . . . . . . . . .   6
     3.3.  Parsing a received MDN  . . . . . . . . . . . . . . . . .   7
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
     4.1.  JMAP Capability Registration for "mdn"  . . . . . . . . .   8
   5.  Security considerations . . . . . . . . . . . . . . . . . . .   8
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   9
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   9

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 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 MDN/set 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 [RFC8621] this way.

   3.  When receiving an MDN, the MDN could be related to an existing
       sent mail.  This is already covered by [RFC8621] in the
       EmailSubmission object.  Client could want to display detailed
       information about a received MDN.  This specification defines a
       MDN/parse method to cover this case.

Ouazana                   Expires May 23, 2020                  [Page 2]
Internet-Draft              JMAP MDN handling              November 2019

1.1.  Notational conventions

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.
Show full document text