[Acme] Benjamin Kaduk's Yes on draft-ietf-acme-ip-07: (with COMMENT)

Benjamin Kaduk via Datatracker <noreply@ietf.org> Tue, 01 October 2019 01:06 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: acme@ietf.org
Delivered-To: acme@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 308D1120077; Mon, 30 Sep 2019 18:06:21 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Benjamin Kaduk via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-acme-ip@ietf.org, Daniel McCarney <cpu@letsencrypt.org>, acme-chairs@ietf.org, cpu@letsencrypt.org, acme@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.103.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Benjamin Kaduk <kaduk@mit.edu>
Message-ID: <156989198118.24161.14973758653510180999.idtracker@ietfa.amsl.com>
Date: Mon, 30 Sep 2019 18:06:21 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/8WSoV6KbWjD16R6zLLxjcS0zm58>
Subject: [Acme] Benjamin Kaduk's Yes on draft-ietf-acme-ip-07: (with COMMENT)
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Automated Certificate Management Environment <acme.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/acme>, <mailto:acme-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/acme/>
List-Post: <mailto:acme@ietf.org>
List-Help: <mailto:acme-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/acme>, <mailto:acme-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Oct 2019 01:06:21 -0000

Benjamin Kaduk has entered the following ballot position for
draft-ietf-acme-ip-07: Yes

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-acme-ip/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Section 7

There's perhaps some "action at a distance" going on here, in that we
try to apply normative requirements on unrelated things.  Perhaps it's
safer to just say "this document does not define any usage of the
'dns-01' challenge to validate IP addresses.  But if we can definitively
rule out any future use, then it doesn't really matter.

Section 9

Is there anything to say about issuing certificates for
non-publicly-routable IP addresses in terms of ensuring that the ACME
server and client are in the same administrative domain [and enforcing
that by network topology]?