[Acme] Paul Wouters' No Objection on draft-ietf-acme-integrations-13: (with COMMENT)

Paul Wouters via Datatracker <noreply@ietf.org> Thu, 02 March 2023 02:59 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 399AEC14CEE5; Wed, 1 Mar 2023 18:59:23 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Paul Wouters via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-acme-integrations@ietf.org, acme-chairs@ietf.org, acme@ietf.org, decoole@radium.ncsc.mil, decoole@radium.ncsc.mil
X-Test-IDTracker: no
X-IETF-IDTracker: 9.12.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Paul Wouters <paul.wouters@aiven.io>
Message-ID: <167772596322.21739.9689242730499702095@ietfa.amsl.com>
Date: Wed, 01 Mar 2023 18:59:23 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/F_eLHaJ3j-ixaIbW60qM30gzhB0>
Subject: [Acme] Paul Wouters' No Objection on draft-ietf-acme-integrations-13: (with COMMENT)
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.39
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: Thu, 02 Mar 2023 02:59:23 -0000

Paul Wouters has entered the following ballot position for
draft-ietf-acme-integrations-13: No Objection

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/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


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



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

The document is a good read, and the figures in it make the process very clear.
Thanks for that work.

Just some minor comments:

       |                      | Publish DNS TXT      |           |
       |                      | "example.com"        |           |

       |                      | Delete DNS TXT       |           |
       |                      | "example.com"        |           |

This reads a little as if a TXT record with the content "example.com"
needs to be published and deleted. Maybe use 'Publish ACME DNS challange
in "example.com"' ?

        This ownership proof could have been by fulfilling an
        authorization challenge against the explicit identifier
        "pledge.example.com",

Where does "pledge" come from? Is this a normative reference to something?

If it is made up here, add some "for example" text to clarify this. And
use at least "_pledge" to avoid clashing with potential real hostnames
called pledge ?

NITS:

        which it will issue certificates.

s/\.$/ for./