Network Working Group A. Melnikov Internet-Draft Isode Ltd Intended status: Informational March 5, 2018 Expires: September 6, 2018 Extensions to JMAP for S/MIME signature verification draft-ietf-jmap-smime-00 Abstract This document specifies 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 September 6, 2018. Copyright Notice Copyright (c) 2018 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 September 6, 2018 [Page 1] Internet-Draft JMAP extension for S/MIME March 2018 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Conventions Used in This Document . . . . . . . . . . . . . . 2 3. Extension to getMessages for S/MIME signature verification . 2 4. Open Issues . . . . . . . . . . . . . . . . . . . . . . . . . 3 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 6. Security Considerations . . . . . . . . . . . . . . . . . . . 4 7. Normative References . . . . . . . . . . . . . . . . . . . . 4 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction JMAP [I-D.ietf-jmap-core] 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. [I-D.ietf-jmap-mail] builds on top of JMAP and defines how to perform email synchronization. This document describes an extension to JMAP Mail for returning S/MIME [RFC5751] signature verification status, without requiring a JMAP client to download the signature and all signed body parts. 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. Extension to getMessages for S/MIME signature verification [I-D.ietf-jmap-mail] defines getMessages method for retrieving message specific information. This document defines the following pseudo values in the _properties_ argument: 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"" property. *smimeStatus*: "String|null". null signifies that the message doesn't contain any signature. Possible string values of the property are listed below. Servers MAY return other values not defined below. Client MUST treat unrecognized values as "unknown": unknown - S/MIME message, but it is neither signed, nor encrypted. This can also be returned for a multipart/signed message which contains unrecognized signing protocol (for example OpenPGP). Melnikov Expires September 6, 2018 [Page 2] Internet-Draft JMAP extension for S/MIME March 2018 signed - S/MIME signed message, but the signature was not yet verified. Some servers might not attempt to verify signature until a particular message is requested by the client. signed/verified - S/MIME signed message and the sender's signature was successfully verified, sender matches the From header field and the sender's certificate (and the certificate chain) is trusted for signing. signed/failed - S/MIME signed message, but the signature failed to verify. This might be a policy related decision (message signer doesn't match the From header field), message was modified, etc. The following example demonstrates a request for S/MIME status. ["getMessages", { "ids": [ "f123u987" ], "properties": [ "mailboxIds", "from", "subject", "date", "smimeStatus" ] }, "#1"] This will result in the following response: ["messages", { "accountId": "abc", "state": "41234123231", "list": [ { id: "f123u457", mailboxIds: { "f123": true }, from: [{name: "Joe Bloggs", email: "joe@bloggs.com"}], subject: "Dinner on Thursday?", date: "2013-10-13T14:12:00Z", smimeStatus: "signed/verified" } ] }, "#1"] Example 4. Open Issues [[This section should be empty before publication]] Melnikov Expires September 6, 2018 [Page 3] Internet-Draft JMAP extension for S/MIME March 2018 5. IANA Considerations TBD. 6. Security Considerations TBD. 7. Normative References [I-D.ietf-jmap-core] Jenkins, N., "JSON Meta Application Protocol", draft-ietf- jmap-core-04 (work in progress), March 2018. [I-D.ietf-jmap-mail] Jenkins, N., "JMAP for Mail", draft-ietf-jmap-mail-04 (work in progress), March 2018. [RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies", RFC 2045, DOI 10.17487/RFC2045, November 1996, . [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC5751] Ramsdell, B. and S. Turner, "Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Message Specification", RFC 5751, DOI 10.17487/RFC5751, January 2010, . Author's Address Alexey Melnikov Isode Ltd 14 Castle Mews Hampton, Middlesex TW12 2NP UK EMail: Alexey.Melnikov@isode.com Melnikov Expires September 6, 2018 [Page 4]