Skip to main content

Last Call Review of draft-ietf-6man-rfc6724-update-18
review-ietf-6man-rfc6724-update-18-dnsdir-lc-cunat-2025-03-31-00

Request Review of draft-ietf-6man-rfc6724-update
Requested revision No specific revision (document currently at 25)
Type IETF Last Call Review
Team DNS Directorate (dnsdir)
Deadline 2025-04-02
Requested 2025-03-12
Authors Nick Buraglio , Tim Chown , Jeremy Duncan
I-D last updated 2026-05-20 (Latest revision 2025-08-11)
Completed reviews Tsvart IETF Last Call review of -18 by Michael Tüxen (diff)
Dnsdir IETF Last Call review of -18 by Vladimír Čunát (diff)
Opsdir IETF Last Call review of -19 by Niclas Comstedt (diff)
Genart IETF Last Call review of -18 by Elwyn B. Davies (diff)
Secdir IETF Last Call review of -18 by Ned Smith (diff)
Dnsdir Telechat review of -20 by Jim Reid (diff)
Intdir Telechat review of -23 by Timothy Winters (diff)
Dnsdir Telechat review of -21 by Jim Reid (diff)
Dnsdir Telechat review of -22 by Jim Reid (diff)
Assignment Reviewer Vladimír Čunát
State Completed
Request IETF Last Call review on draft-ietf-6man-rfc6724-update by DNS Directorate Assigned
Posted at https://mailarchive.ietf.org/arch/msg/dnsdir/tkbIySCe6TY9y_YYe8nyoF3sLTM
Reviewed revision 18 (document currently at 25)
Result Ready
Completed 2025-03-31
review-ietf-6man-rfc6724-update-18-dnsdir-lc-cunat-2025-03-31-00
Review assigned by dnsdir.  My thoughts are more like "no objection".

I've read through the whole document but not in too much depth and - more
importantly - I don't feel like an expert on this particular topic, though this
draft does make sense to me.  I wanted to focus on DNS aspects here, but there
are basically none: while IP(v6) addresses are very often retrieved from DNS,
in this case the separation seems pretty high.

- - -
A loosely related DNS consideration did came to mind - as DNS resolvers very
often have to choose which IP address to ask from a particular set (which could
be spread across multiple NS names).  But in this case, I don't think that ULAs
are expected to be special-cased, except maybe ignored if appearing in public
DNS as nameserver addresses.  In public DNS ULAs aren't expected/recommended
anywhere (as restated here in 9.2) and in case they're locally configured for
some DNS subtree, I believe the resolver operator chooses by hand.  In any
case, resolvers tend to have resilience by design for cases when some
nameserver IPs are inaccessible or significantly slower than others.