Re: [Acme] Genart last call review of draft-ietf-acme-subdomains-04

Reese Enghardt <ietf@tenghardt.net> Tue, 29 November 2022 23:10 UTC

Return-Path: <ietf@tenghardt.net>
X-Original-To: acme@ietfa.amsl.com
Delivered-To: acme@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1344C1526E8; Tue, 29 Nov 2022 15:10:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=tenghardt.net
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kn3EQDTH2v6T; Tue, 29 Nov 2022 15:10:15 -0800 (PST)
Received: from mail.hemio.de (mail.hemio.de [136.243.12.180]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BEB1EC14CF06; Tue, 29 Nov 2022 15:10:14 -0800 (PST)
Received: from user.client.invalid (localhost [136.243.12.180]) by mail.hemio.de (Postfix) with ESMTPSA id C3B58B4; Wed, 30 Nov 2022 00:10:10 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tenghardt.net; s=20170414; t=1669763412; bh=np0eWEUPFH7qyfANSH0vGYO3HExNFmvbTor1QIzb310=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=pbBmAb3KX4gj9LrHZlaEgBkjagXXQYg/6iWftNEnn8lfBEJXf85txJ/79su4FDzIl 5mHccHikoTrshPeOMepZF4N0pjUSJhL7Y8KCQMykckjXYBM5ycJ9phJx2NWF7/Kbc3 dzRFTL7almBZI1MM5Jl92VbNiyDAN+GEELz2/8qQiBwFCILwjJmNsisBfZwVuex+mg BBpt8YWOiXqP+E3B4SaIvZBh0oqTYYbE3yw3AerXQVXihZkOKyqraUOJyDrto/wZ/D 2oLBxJgw6JYJw/uUuQUvF8/bzciS589hEpwM8jKeTWXU33ckkKlfmIa69zolC9G+KU fJuODLduX+k0w==
Message-ID: <7a3aa201-bd91-8d25-866a-b017dee06ace@tenghardt.net>
Date: Tue, 29 Nov 2022 15:10:08 -0800
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2
To: "Owen Friel (ofriel)" <ofriel@cisco.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Cc: "acme@ietf.org" <acme@ietf.org>, "draft-ietf-acme-subdomains.all@ietf.org" <draft-ietf-acme-subdomains.all@ietf.org>, "last-call@ietf.org" <last-call@ietf.org>
References: <166864821687.27396.11214608162761711249@ietfa.amsl.com> <DS0PR11MB6445B8186657989F14FDA7D4DB0E9@DS0PR11MB6445.namprd11.prod.outlook.com>
Content-Language: en-US
From: Reese Enghardt <ietf@tenghardt.net>
In-Reply-To: <DS0PR11MB6445B8186657989F14FDA7D4DB0E9@DS0PR11MB6445.namprd11.prod.outlook.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/P6LQTKadcA-qM2hAe7dnYcLfqeQ>
Subject: Re: [Acme] Genart last call review of draft-ietf-acme-subdomains-04
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
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, 29 Nov 2022 23:10:19 -0000

Hi Owen,

Thanks for committing the fixes.

To the one inline comment:

On 11/25/22 10:39, Owen Friel (ofriel) wrote:
> Section 2:
>
> " Fully-Qualified Domain Name (FQDN): This is often just a clear way
>            of saying the same thing as "domain name of a node", as outlined
>            above.  However, the term is ambiguous."
>
> These two sentences appear to contradict each other - Is the term clear or ambiguous? I suggest removing the word "clear" to simply state how the term is commonly used, and then point out the ambiguity.
>
> [ofriel] The section starts with stating:
>
> " The following terms are defined in DNS Terminology [RFC8499] and are
>     reproduced here"
>
> The definition is an exact quote from RFC8499. Do we need to get the definition in RFC8499 updated? I am unsure if I should change the definition of FQDN in this ACME document and would prefer to change the definition in the common source of these DNS terms. What does IESG recommend?

Oh, I see. Agreed, there's no need to change the definition of FQDN in 
this document.

I find it strange phrasing, but it's still clear enough, and I'll defer 
to the DNS folks on whether anything needs to be updated here.

Best,
Reese