Extensions to Automatic Certificate Management Environment for email TLS
draft-ietf-acme-email-tls-05

Document Type Active Internet-Draft (acme WG)
Last updated 2018-07-25
Replaces draft-melnikov-acme-email-tls
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html 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)
Network Working Group                                        A. Melnikov
Internet-Draft                                                 Isode Ltd
Intended status: Informational                             July 25, 2018
Expires: January 26, 2019

Extensions to Automatic Certificate Management Environment for email TLS
                      draft-ietf-acme-email-tls-05

Abstract

   This document specifies identifiers and challenges required to enable
   the Automated Certificate Management Environment (ACME) to issue
   certificates for use by TLS email services.

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 January 26, 2019.

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 January 26, 2019                [Page 1]
Internet-Draft         ACME for email TLS services             July 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions Used in This Document . . . . . . . . . . . . . .   2
   3.  Use of ACME for use by TLS-protected SMTP, IMAP and POP3
       services  . . . . . . . . . . . . . . . . . . . . . . . . . .   2
     3.1.  "service" field in JSON payload . . . . . . . . . . . . .   3
     3.2.  "port" field in JSON payload  . . . . . . . . . . . . . .   4
     3.3.  DNS challenge for email services  . . . . . . . . . . . .   4
     3.4.  CAPABILITY challenge for email services . . . . . . . . .   4
       3.4.1.  Registration of the ACME SMTP extension . . . . . . .   6
   4.  Open Issues . . . . . . . . . . . . . . . . . . . . . . . . .   6
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   7.  Normative References  . . . . . . . . . . . . . . . . . . . .   7
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   [I-D.ietf-acme-acme] is a mechanism for automating certificate
   management on the Internet.  It enables administrative entities to
   prove effective control over resources like domain names, and
   automates the process of generating and issuing certificates.

   This document describes extensions to ACME for use by email services.
   Section 3 defines extensions for how email services (such as SMTP,
   IMAP and POP3) can get certificates for use with TLS.

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.  Use of ACME for use by TLS-protected SMTP, IMAP and POP3 services

   SMTP [RFC5321] (including SMTP Submission [RFC6409]), IMAP [RFC3501]
   and POP3 [RFC2449] servers use TLS [RFC5246] to provide server
   identity authentication, data confidentiality and integrity services.
   Such TLS protected email services either use STARTTLS command or run
   on a separate TLS-protected port [RFC8314].

   [I-D.ietf-acme-acme] defines several challenge types that can be
   extended for use by email services.  This document also defines some
   new challenge types specific to SMTP, IMAP and POP3.

   In order to use these challenges JWS [RFC7515] object used by
   [I-D.ietf-acme-acme] is extended.  The following extra requirements

Melnikov                Expires January 26, 2019                [Page 2]
Internet-Draft         ACME for email TLS services             July 2018

   are in addition to requirements on JWS objects sent in ACME defined
   in Section 6.2 of [I-D.ietf-acme-acme]:

   1.  "service" JWS header parameter MUST be included.  See Section 3.1
       for more details.
Show full document text