Skip to main content

Last Call Review of draft-ietf-homenet-naming-architecture-dhc-options-21
review-ietf-homenet-naming-architecture-dhc-options-21-artart-lc-gondwana-2022-10-04-00

Request Review of draft-ietf-homenet-naming-architecture-dhc-options
Requested revision No specific revision (document currently at 24)
Type Last Call Review
Team ART Area Review Team (artart)
Deadline 2022-10-04
Requested 2022-09-20
Authors Daniel Migault , Ralf Weber , Tomek Mrugalski
I-D last updated 2022-10-04
Completed reviews Opsdir Last Call review of -20 by Al Morton (diff)
Genart Last Call review of -21 by Ines Robles (diff)
Artart Last Call review of -21 by Bron Gondwana (diff)
Secdir Last Call review of -21 by Hilarie Orman (diff)
Opsdir Telechat review of -21 by Al Morton (diff)
Dnsdir Telechat review of -21 by R. (Miek) Gieben (diff)
Assignment Reviewer Bron Gondwana
State Completed
Request Last Call review on draft-ietf-homenet-naming-architecture-dhc-options by ART Area Review Team Assigned
Posted at https://mailarchive.ietf.org/arch/msg/art/HE_gPjbSztuaK4v128p-fCoSIow
Reviewed revision 21 (document currently at 24)
Result Ready w/nits
Completed 2022-10-04
review-ietf-homenet-naming-architecture-dhc-options-21-artart-lc-gondwana-2022-10-04-00
Thanks to the authors for this, and apologies for a slightly delayed review.

I read this document and skim-read the linked
draft-ietf-homenet-front-end-naming-delegation which describes why these fields
might want to be provided by DHCPv6.

I found this document clear and easy to read - there were no nits that stood
out to me other than the double-definition of the "Supported Transport" field. 
While there is a chicken-and-egg problem, the RFC editor and IANA could be
instructed to link things up such that section 4 immediately named the registry
to look up the values in rather than hard-coding an initial table into this
document, and having future readers reach this section without finding the
pointer to IANA in the natural place.

Likewise once the values are assigned by IANA for the DHCP option codes,
putting them directly into this document in the spots where a reader would
naturally be looking would help implementations.

Overall - this document has a very long history - well done for sticking with
it.  I hope one day to buy a product which uses the end result of this work and
transparently configures MY home network!