Hi Folks, I am the assigned DNS Directorate reviewer for this revision of the draft. Please treat these comments like any other IETF Last Call comments. Document: draft-ietf-acme-dns-account-label-04 Reviewer: James Gannon Review Date: 2026-10-31 Review Result: Ready with Nits The document addresses a useful operational problem and the account-specific validation-name construction looks sound. I found no blocking DNS issues. Major issues: None. Minor comments: 1. Sections 3.2, 3.3 and 3.5 — exact hash input. Section 3.5 already says the ACME server MUST NOT apply inconsistent URL normalization. A short clarification covering both sides would help: the ACME client and ACME server should hash the same unchanged account URL string as supplied in the Location header and carried in the JWS kid. 2. Section 3.2 — complete validation-name length. The generated account label is well within the per-label limit, but the two prepended labels add 34 octets to the DNS wire-format name including their length octets. The complete name must still fit within the 255-octet limit in RFC 1035. A short implementation note on checking the complete constructed name, and what to do when it exceeds that limit, would be potnetial useful. Nits: 1. Please qualify "client" and "server" as "ACME client" and "ACME server" where DNS components could also be understood. Same point as Eliot's ARTART terminology comment. 2. A short example showing two account-specific owner names pointing to separate CNAME targets would help operators see the intended deployment. A cross-reference to Section 8 of draft-ietf-dnsop-domain-verification-techniques would also be useful. Thanks for a well written doc.