draft-ietf-acme-ip-03.txt   draft-ietf-acme-ip-04.txt 
ACME Working Group R. Shoemaker ACME Working Group R. Shoemaker
Internet-Draft ISRG Internet-Draft ISRG
Intended status: Standards Track July 25, 2018 Intended status: Standards Track July 27, 2018
Expires: January 26, 2019 Expires: January 28, 2019
ACME IP Identifier Validation Extension ACME IP Identifier Validation Extension
draft-ietf-acme-ip-03 draft-ietf-acme-ip-04
Abstract Abstract
This document specifies identifiers and challenges required to enable This document specifies identifiers and challenges required to enable
the Automated Certificate Management Environment (ACME) to issue the Automated Certificate Management Environment (ACME) to issue
certificates for IP addresses. certificates for IP addresses.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 32 skipping to change at page 1, line 32
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 26, 2019. This Internet-Draft will expire on January 28, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 15 skipping to change at page 2, line 15
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. IP Identifier . . . . . . . . . . . . . . . . . . . . . . . . 2 3. IP Identifier . . . . . . . . . . . . . . . . . . . . . . . . 2
4. Identifier Validation Challenges . . . . . . . . . . . . . . 3 4. Identifier Validation Challenges . . . . . . . . . . . . . . 3
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
5.1. Identifier Types . . . . . . . . . . . . . . . . . . . . 3 5.1. Identifier Types . . . . . . . . . . . . . . . . . . . . 3
5.2. Challenge Types . . . . . . . . . . . . . . . . . . . . . 3 5.2. Challenge Types . . . . . . . . . . . . . . . . . . . . . 3
6. Security Considerations . . . . . . . . . . . . . . . . . . . 3 6. Security Considerations . . . . . . . . . . . . . . . . . . . 3
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 3 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 4
8. Normative References . . . . . . . . . . . . . . . . . . . . 4 8. Normative References . . . . . . . . . . . . . . . . . . . . 4
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction 1. Introduction
The Automatic Certificate Management Environment (ACME) The Automatic Certificate Management Environment (ACME)
[I-D.ietf-acme-acme] only defines challenges for validating control [I-D.ietf-acme-acme] only defines challenges for validating control
of DNS host name identifiers which limits its use to being used for of DNS host name identifiers which limits its use to being used for
issuing certificates for DNS identifiers. In order to allow issuing certificates for DNS identifiers. In order to allow
validation of IPv4 and IPv6 identifiers for inclusion in X.509 validation of IPv4 and IPv6 identifiers for inclusion in X.509
skipping to change at page 3, line 17 skipping to change at page 3, line 17
IP identifiers MAY be used with the existing "http-01" and "tls-alpn- 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 01" challenges from [I-D.ietf-acme-acme] Section 8.3 and
[I-D.ietf-acme-tls-alpn] Section 3 respectively. To use IP [I-D.ietf-acme-tls-alpn] Section 3 respectively. To use IP
identifiers with these challenges their initial DNS resolution step identifiers with these challenges their initial DNS resolution step
MUST be skipped and the IP address used for validation MUST be the MUST be skipped and the IP address used for validation MUST be the
value of the identifier. value of the identifier.
For the "http-01" challenge the Host header MUST be set to the IP For the "http-01" challenge the Host header MUST be set to the IP
address being used for validation per [RFC7230]. address being used for validation per [RFC7230].
For the "tls-alpn-01" challenge the SNI value MUST be set to the IP For the "tls-alpn-01" the subjectAltName extension in the validation
address being used for validation and the subjectAltName extension in certificate MUST contain a single iPAddress which matches the address
the validation certificate MUST contain a single iPAddress which being validated. As [RFC6066] does not permit IP addresses to be
matches the address being validated. used in the SNI extension the server MUST instead use the IN-
ADDR.ARPA [RFC1034] or IP6.ARPA [RFC3596] reverse mapping of the IP
address as the SNI value instead of the literal IP address.
The existing "dns-01" challenge MUST NOT be used to validate IP The existing "dns-01" challenge MUST NOT be used to validate IP
identifiers. identifiers.
5. IANA Considerations 5. IANA Considerations
5.1. Identifier Types 5.1. Identifier Types
Adds a new type to the Identifier list defined in Section 9.7.7 of Adds a new type to the Identifier list defined in Section 9.7.7 of
[I-D.ietf-acme-acme] with the label "ip" and reference I-D.ietf-acme- [I-D.ietf-acme-acme] with the label "ip" and reference I-D.ietf-acme-
skipping to change at page 5, line 5 skipping to change at page 5, line 9
<https://www.rfc-editor.org/info/rfc3596>. <https://www.rfc-editor.org/info/rfc3596>.
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, DOI 10.17487/RFC4291, February Architecture", RFC 4291, DOI 10.17487/RFC4291, February
2006, <https://www.rfc-editor.org/info/rfc4291>. 2006, <https://www.rfc-editor.org/info/rfc4291>.
[RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data [RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data
Encodings", RFC 4648, DOI 10.17487/RFC4648, October 2006, Encodings", RFC 4648, DOI 10.17487/RFC4648, October 2006,
<https://www.rfc-editor.org/info/rfc4648>. <https://www.rfc-editor.org/info/rfc4648>.
[RFC6066] Eastlake 3rd, D., "Transport Layer Security (TLS)
Extensions: Extension Definitions", RFC 6066,
DOI 10.17487/RFC6066, January 2011,
<https://www.rfc-editor.org/info/rfc6066>.
[RFC7230] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer [RFC7230] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
Protocol (HTTP/1.1): Message Syntax and Routing", Protocol (HTTP/1.1): Message Syntax and Routing",
RFC 7230, DOI 10.17487/RFC7230, June 2014, RFC 7230, DOI 10.17487/RFC7230, June 2014,
<https://www.rfc-editor.org/info/rfc7230>. <https://www.rfc-editor.org/info/rfc7230>.
Author's Address Author's Address
Roland Bracewell Shoemaker Roland Bracewell Shoemaker
Internet Security Research Group Internet Security Research Group
 End of changes. 6 change blocks. 
9 lines changed or deleted 16 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/