An ACME Profile for Generating Delegated Certificates
draft-ietf-acme-star-delegation-07

Document Type Active Internet-Draft (acme WG)
Authors Yaron Sheffer  , Diego Lopez  , Antonio Pastor  , Thomas Fossati 
Last updated 2021-04-08 (latest revision 2021-03-26)
Replaces draft-sheffer-acme-star-delegation
Stream Internet Engineering Task Force (IETF)
Intended RFC status Proposed Standard
Formats plain text html xml pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication (wg milestone: Jan 2021 - Profile for delegate... )
Document shepherd Rich Salz
Shepherd write-up Show (last changed 2021-01-19)
IESG IESG state IESG Evaluation::Revised I-D Needed
Action Holders
Consensus Boilerplate Yes
Telechat date
Has 3 DISCUSSes. Needs one more YES or NO OBJECTION position to pass.
Responsible AD Roman Danyliw
Send notices to ynir.ietf@gmail.com, rsalz@akamai.com
IANA IANA review state IANA - Not OK
IANA expert review state Issues identified
IANA expert review comments Authors: A couple of points for you: 1. The "delegation" field is currently attached to the "identifier" object, which is a bad semantic fit in a few ways. ACME orders can have multiple identifiers, and delegations can describe multiple SAN values, yet this design assumes singularity on both sides. This field should be moved to the order object; in fact, if you wanted to be more radical, you could even use it to replace the "identifiers" field in the newOrder request. 2. The "allow-certificate-get" field is listed as configurable. It seems like this is a matter of CA policy, so it should either be non-configurable, or if you allow the client to request a value for it, there should be a clear specification that the server is allowed to ignore the client's preference.
ACME                                                          Y. Sheffer
Internet-Draft                                                    Intuit
Intended status: Standards Track                                D. López
Expires: 27 September 2021                             A. Pastor Perales
                                                          Telefonica I+D
                                                              T. Fossati
                                                                     ARM
                                                           26 March 2021

         An ACME Profile for Generating Delegated Certificates
                   draft-ietf-acme-star-delegation-07

Abstract

   This memo defines a profile of the Automatic Certificate Management
   Environment (ACME) protocol by which the owner of an identifier
   (e.g., a domain name) can allow a third party to obtain an X.509
   certificate such that the certificate subject is the delegated
   identifier while the certified public key corresponds to a private
   key controlled by the third party.  A primary use case is that of a
   Content Delivery Network (CDN, the third party) terminating TLS
   sessions on behalf of a content provider (the owner of a domain
   name).  The presented mechanism allows the owner of the identifier to
   retain control over the delegation and revoke it at any time.  A key
   property of this mechanism is it does not require any modification to
   the deployed TLS ecosystem.

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 27 September 2021.

Sheffer, et al.         Expires 27 September 2021               [Page 1]
Internet-Draft               ACME Delegation                  March 2021

Copyright Notice

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   4
     1.2.  Conventions used in this document . . . . . . . . . . . .   5
   2.  Protocol Flow . . . . . . . . . . . . . . . . . . . . . . . .   5
     2.1.  Preconditions . . . . . . . . . . . . . . . . . . . . . .   5
     2.2.  Overview  . . . . . . . . . . . . . . . . . . . . . . . .   6
     2.3.  Delegated Identity Profile  . . . . . . . . . . . . . . .   8
       2.3.1.  Delegation Configuration  . . . . . . . . . . . . . .   8
       2.3.2.  Order Object Transmitted from NDC to IdO and to ACME
               Server (STAR) . . . . . . . . . . . . . . . . . . . .  10
       2.3.3.  Order Object Transmitted from NDC to IdO and to ACME
               Server (non-STAR) . . . . . . . . . . . . . . . . . .  13
       2.3.4.  Capability Discovery  . . . . . . . . . . . . . . . .  16
       2.3.5.  Terminating the Delegation  . . . . . . . . . . . . .  16
     2.4.  Proxy Behavior  . . . . . . . . . . . . . . . . . . . . .  17
   3.  CSR Template  . . . . . . . . . . . . . . . . . . . . . . . .  18
     3.1.  Template Syntax . . . . . . . . . . . . . . . . . . . . .  19
     3.2.  Example . . . . . . . . . . . . . . . . . . . . . . . . .  20
   4.  Further Use Cases . . . . . . . . . . . . . . . . . . . . . .  21
     4.1.  CDN Interconnection (CDNI)  . . . . . . . . . . . . . . .  21
       4.1.1.  Multiple Parallel Delegates . . . . . . . . . . . . .  22
       4.1.2.  Chained Delegation  . . . . . . . . . . . . . . . . .  22
     4.2.  Secure Telephone Identity Revisited (STIR)  . . . . . . .  25
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  26
     5.1.  New ACME Identifier Object Fields . . . . . . . . . . . .  26
     5.2.  New Fields in the "meta" Object within a Directory
           Object  . . . . . . . . . . . . . . . . . . . . . . . . .  27
Show full document text