I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at
<https://wiki.ietf.org/en/group/gen/GenArtFAQ>.

Document: draft-davids-forsalereg-18
Reviewer: Russ Housley
Review Date: 2025-12-04
IETF LC End Date: unknown
IESG Telechat date: unknown


Summary: Almost Ready


Major Concerns:

Section 2.2 says:

   Content tags are optional.  Providing a minimum set to allow
   interested parties to engage is RECOMMENDED.

The specification does not define the "minimal set".  Without a
definition, the RECOMMENDED phrase is not actionable by an
implementer.


Minor Concerns:

Section 2.1 says:

   If no TXT records at a leaf node contain a valid version tag,
   processors MUST consider the node name invalid and MUST discard it.

Discard seems like the wrong action here.  I think that you want 
processors to ignore such TXT records.

Sections 2.2.1 and 2.5 use "ACME" as an example.  I suspect this has nothing
to do with RFC 8555.  If that suspicion is correct, using a different
example string would probably be helpful.  If that suspicion is not
correct, please add a reference to RFC 8555 and provide a sentence or
two of explanation.


Nits:

Footer: s/_for-sale DNS/_for-sale DNS Node Name/

Section 1: s/mean it is unavailable/mean it is unavailable for purchase/

Section 1: s/domain name for availability/domain name for purchasability/

Section 2.6: s/can essentially be/can be/