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

Robert Wilton via Datatracker <noreply@ietf.org> Thu, 19 January 2023 12:07 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 D5AB0C14F72D; Thu, 19 Jan 2023 04:07:15 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Wilton 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: Robert Wilton <rwilton@cisco.com>
Message-ID: <167413003586.18236.3769672968410087796@ietfa.amsl.com>
Date: Thu, 19 Jan 2023 04:07:15 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/YHZKaOtDt25JSFfe7xDMlqYkDKM>
Subject: [Acme] Robert Wilton'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: Thu, 19 Jan 2023 12:07:15 -0000

Robert Wilton 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:
----------------------------------------------------------------------

Hi,

Thanks for this document.

One minor nit on the definition of subdomain and ancestor domain:

Subdomain has been clarified in this document to remove the ambiguity of
whether a given domain is a subdomain of itself.

However, looking at the definition of ancestor domain:

   *  Ancestor Domain: a domain is an ancestor domain of a subdomain if
      it contains that subdomain, as per the [RFC8499] definition of
      subdomain.  For example, for the host name "nnn.mmm.example.com",
      both "mmm.example.com" and "example.com" are ancestor domains of
      "nnn.mmm.example.com".  Note that the comparisons here are done on
      whole labels; that is, "oo.example.com" is not an ancestor domain
      of "ooo.example.com"

It specifically references the RFC8499 definition of subdomain rather than the
one clarified in the document, raising the question whether a domain is also an
ancestor of itself, and whether that ambiguity is intentional for some reason. 
Hence, I would propose that the definition of ancestor domain is tied back to
the definition of subdomain in this document rather than RFC8499.

Regards,
Rob