Skip to main content

IETF Last Call Review of draft-davids-forsalereg-18
review-davids-forsalereg-18-genart-lc-housley-2025-12-04-00

Request Review of draft-davids-forsalereg
Requested revision No specific revision (document currently at 21)
Type IETF Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2025-12-29
Requested 2025-12-01
Authors Marco Davids
I-D last updated 2026-06-12 (Latest revision 2026-02-05)
Completed reviews Dnsdir Early review of -09 by James Gannon (diff)
Dnsdir IETF Last Call review of -18 by James Gannon (diff)
Intdir IETF Last Call review of -18 by Tim Wicinski (diff)
Genart IETF Last Call review of -18 by Russ Housley (diff)
Artart IETF Last Call review of -18 by Takahiro Nemoto (diff)
Secdir IETF Last Call review of -18 by Watson Ladd (diff)
Opsdir IETF Last Call review of -18 by Chongfeng Xie (diff)
Artart Telechat review of -19 by Takahiro Nemoto (diff)
Assignment Reviewer Russ Housley
State Completed
Request IETF Last Call review on draft-davids-forsalereg by General Area Review Team (Gen-ART) Assigned
Posted at https://mailarchive.ietf.org/arch/msg/gen-art/8JznYA33oQPPxaJkXE7X51Mstpo
Reviewed revision 18 (document currently at 21)
Result Almost ready
Completed 2025-12-04
review-davids-forsalereg-18-genart-lc-housley-2025-12-04-00
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/