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

Document Type Active Internet-Draft (acme WG)
Last updated 2017-09-18
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)
ACME Working Group                                          R. Shoemaker
Internet-Draft                                                      ISRG
Intended status: Standards Track                      September 18, 2017
Expires: March 22, 2018

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

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 http://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 March 22, 2018.

Copyright Notice

   Copyright (c) 2017 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
   (http://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 March 22, 2018                 [Page 1]
Internet-Draft                   ACME-IP                  September 2017

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  IP Identifier . . . . . . . . . . . . . . . . . . . . . . . .   2
   4.  Identifier Validation Challenges  . . . . . . . . . . . . . .   3
     4.1.  Reverse DNS . . . . . . . . . . . . . . . . . . . . . . .   3
     4.2.  Existing Challenges . . . . . . . . . . . . . . . . . . .   5
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
     5.1.  Identifier Types  . . . . . . . . . . . . . . . . . . . .   5
     5.2.  Challenge Types . . . . . . . . . . . . . . . . . . . . .   5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
     6.1.  Certificate Lifetime  . . . . . . . . . . . . . . . . . .   5
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   6
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   7

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 these identifiers.  In order to allow
   validation of IPv4 and IPv6 identifiers for inclusion in X.509
   certificates this document defines a new challenge type and specifies
   how challenges defined in the original ACME specification 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, RFC 2119
   [RFC2119].

3.  IP Identifier

   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
   RFC 1123 [RFC1123] Section 2.1 for IPv4 and in RFC 4291 [RFC4291]
   Section 2.2 for IPv6.

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

Shoemaker                Expires March 22, 2018                 [Page 2]
Internet-Draft                   ACME-IP                  September 2017
Show full document text