ACME IP Identifier Validation Extension
draft-ietf-acme-ip-04

Document Type Active Internet-Draft (acme WG)
Last updated 2018-08-27 (latest revision 2018-07-27)
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Stream WG state Submitted to IESG for Publication
Document shepherd Daniel McCarney
Shepherd write-up Show (last changed 2018-08-27)
IESG IESG state Publication Requested
Consensus Boilerplate Yes
Telechat date
Responsible AD Eric Rescorla
Send notices to Daniel McCarney <cpu@letsencrypt.org>
ACME Working Group                                          R. Shoemaker
Internet-Draft                                                      ISRG
Intended status: Standards Track                           July 27, 2018
Expires: January 28, 2019

                ACME IP Identifier Validation Extension
                         draft-ietf-acme-ip-04

Abstract

   This document specifies identifiers and challenges required to enable
   the Automated Certificate Management Environment (ACME) to issue
   certificates for IP addresses.

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 28, 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.

Shoemaker               Expires January 28, 2019                [Page 1]
Internet-Draft                   ACME-IP                       July 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  IP Identifier . . . . . . . . . . . . . . . . . . . . . . . .   2
   4.  Identifier Validation Challenges  . . . . . . . . . . . . . .   3
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   3
     5.1.  Identifier Types  . . . . . . . . . . . . . . . . . . . .   3
     5.2.  Challenge Types . . . . . . . . . . . . . . . . . . . . .   3
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   3
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   4
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .   4
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   The Automatic Certificate Management Environment (ACME)
   [I-D.ietf-acme-acme] only defines challenges for validating control
   of DNS host name identifiers which limits its use to being used for
   issuing certificates for DNS identifiers.  In order to allow
   validation of IPv4 and IPv6 identifiers for inclusion in X.509
   certificates this document specifies how challenges defined in the
   original ACME specification and the TLS-ALPN extension specification
   [I-D.ietf-acme-tls-alpn] can be used to validate IP identifiers.

2.  Terminology

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

3.  IP Identifier

   [I-D.ietf-acme-acme] only defines the identifier type "dns" which is
   used to refer to fully qualified domain names.  If a ACME server
   wishes to request proof that a user controls a IPv4 or IPv6 address
   it MUST create an authorization with the identifier type "ip".  The
   value field of the identifier MUST contain the textual form of the
   address as defined in [RFC1123] Section 2.1 for IPv4 and in [RFC4291]
   Section 2.2 for IPv6.

   An identifier for the IPv6 address 2001:db8::1 would be formatted
   like so:

   {"type": "ip", "value": "2001:db8::1"}

Shoemaker               Expires January 28, 2019                [Page 2]
Internet-Draft                   ACME-IP                       July 2018

4.  Identifier Validation Challenges

   IP identifiers MAY be used with the existing "http-01" and "tls-alpn-
   01" challenges from [I-D.ietf-acme-acme] Section 8.3 and
   [I-D.ietf-acme-tls-alpn] Section 3 respectively.  To use IP
   identifiers with these challenges their initial DNS resolution step
   MUST be skipped and the IP address used for validation MUST be the
   value of the identifier.

   For the "http-01" challenge the Host header MUST be set to the IP
   address being used for validation per [RFC7230].
Show full document text