S/MIME signature verification extension to JMAP
draft-ietf-jmap-smime-01

The information below is for an old version of the document
Document Type Active Internet-Draft (jmap WG)
Last updated 2020-02-10
Stream IETF
Intended RFC status Proposed Standard
Formats pdf htmlized (tools) htmlized bibtex
Stream WG state WG Document (wg milestone: Aug 2020 - Submit JMAP S/MIME s... )
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                        A. Melnikov
Internet-Draft                                                 Isode Ltd
Intended status: Informational                         February 10, 2020
Expires: August 13, 2020

            S/MIME signature verification extension to JMAP
                        draft-ietf-jmap-smime-01

Abstract

   This document specifies an extension to JMAP for returning S/MIME
   signature verification status.

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 13, 2020.

Copyright Notice

   Copyright (c) 2020 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.

Melnikov                 Expires August 13, 2020                [Page 1]
Internet-Draft          JMAP extension for S/MIME          February 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions Used in This Document . . . . . . . . . . . . . .   2
   3.  Addition to the capabilities object . . . . . . . . . . . . .   2
   4.  Extension to Email/get for S/MIME signature verification  . .   2
   5.  Open Issues . . . . . . . . . . . . . . . . . . . . . . . . .   5
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
     6.1.  JMAP capability registration for "smime"  . . . . . . . .   5
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   [RFC8621] is a JSON based application protocol for synchronising
   email data between a client and a server.

   This document describes an extension to JMAP for returning S/MIME
   [RFC8551] signature verification status, without requiring a JMAP
   client to download the signature body part and all signed body parts
   (when multipart/signed media type is used) or to download and decode
   CMS (when application/pkcs7-mime media type is used).

2.  Conventions Used in This Document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

3.  Addition to the capabilities object

   The capabilities object is returned as part of the standard JMAP
   Session object; see the JMAP spec.  Servers supporting _this_
   specification MUST add a property called "urn:ietf:params:jmap:smime"
   to the capabilities object.

   The value of this property is an empty object in both the JMAP
   session _capabilities_ property and an account's
   _accountCapabilities_ property.

4.  Extension to Email/get for S/MIME signature verification

   [RFC8621] defines Email/get method for retrieving message specific
   information.  This document defines the following pseudo values in
   the _properties_ argument:

Melnikov                 Expires August 13, 2020                [Page 2]
Internet-Draft          JMAP extension for S/MIME          February 2020

   o *smimeStatus*: If "smimeStatus" is included in the list of
   requested properties, it MUST be interpreted by the server as a
   request to return "smimeStatus" response property.
   o *smimeErrors*: If "smimeErrors" is included in the list of
   requested properties, it MUST be interpreted by the server as a
   request to return "smimeErrors" response property.

   The "smimeStatus" response property is defined as follows:

   smimeStatus: "String|null". null signifies that the message doesn't
   contain any signature.  This property contains the S/MIME signature
   and certificate verification status calculated according to [RFC8551]
   and [RFC8550].  Possible string values of the property are listed
Show full document text