[Acme] Erik Kline's No Objection on draft-ietf-acme-subdomains-06: (with COMMENT)

Erik Kline via Datatracker <noreply@ietf.org> Tue, 17 January 2023 02:55 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 B3AF2C14CE2C; Mon, 16 Jan 2023 18:55:50 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Erik Kline via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-acme-subdomains@ietf.org, acme-chairs@ietf.org, acme@ietf.org, debcooley1@gmail.com, debcooley1@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 9.5.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Erik Kline <ek.ietf@gmail.com>
Message-ID: <167392415071.3889.3988254701134024292@ietfa.amsl.com>
Date: Mon, 16 Jan 2023 18:55:50 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/T5P4qjY8CUj5IGIykUkes9rty5s>
Subject: [Acme] Erik Kline's No Objection on draft-ietf-acme-subdomains-06: (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: Tue, 17 Jan 2023 02:55:50 -0000

Erik Kline has entered the following ballot position for
draft-ietf-acme-subdomains-06: 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-subdomains/



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

# Internet AD comments for draft-ietf-acme-subdomains-06
CC @ekline

## Comments

### S4.3

* At the end of this section discussion switches from "ancestorDomain" to
  "parentDomain".  I think this makes sense in the context of the 2nd
  example (foo.bar.example.org and {bar.,}example.org) where the parent
  domain is not necessarily the same as the ancestor domain. Nevertheless,
  some text highlighting the distinction between ancestor and parent domains
  might be helpful.  (Or just describe it in the context of the example;
  I assume bar.example.org is the parent in the case where example.org is
  the ancestor?)