Skip to main content

Last Call Review of draft-ietf-homenet-front-end-naming-delegation-22
review-ietf-homenet-front-end-naming-delegation-22-artart-lc-miller-2022-11-06-00

Request Review of draft-ietf-homenet-front-end-naming-delegation
Requested revision No specific revision (document currently at 27)
Type Last Call Review
Team ART Area Review Team (artart)
Deadline 2022-10-04
Requested 2022-09-20
Authors Daniel Migault , Ralf Weber , Michael Richardson , Ray Hunter
I-D last updated 2022-11-06
Completed reviews Genart Last Call review of -18 by Christer Holmberg (diff)
Artart Last Call review of -22 by Darrel Miller (diff)
Dnsdir Telechat review of -18 by Matt Brown (diff)
Dnsdir Telechat review of -18 by Anthony Somerset (diff)
Dnsdir Telechat review of -19 by Tim Wicinski (diff)
Dnsdir Telechat review of -25 by Geoff Huston (diff)
Intdir Telechat review of -25 by Tim Chown (diff)
Dnsdir Telechat review of -25 by Geoff Huston (diff)
Dnsdir Last Call review of -26 by Anthony Somerset (diff)
Assignment Reviewer Darrel Miller
State Completed
Request Last Call review on draft-ietf-homenet-front-end-naming-delegation by ART Area Review Team Assigned
Posted at https://mailarchive.ietf.org/arch/msg/art/PDXnM9p_Sgj9Th-1YI_Wp-tgJSs
Reviewed revision 22 (document currently at 27)
Result Ready w/issues
Completed 2022-11-06
review-ietf-homenet-front-end-naming-delegation-22-artart-lc-miller-2022-11-06-00
Summary:

In general, this document was able to communicate its goals and approach, to
someone who is not familiar with the area. There are a number of grammatical
errors that make reading harder than it needs to be.  The biggest concern I
have with the document is that it raises the possibility that the objectives of
the document could be addressed using a "RESTful service" but then provides no
reasoning for why a DNS solution was chosen instead. As the authors noted,
existing DDNS implementations chose to use HTTP APIs rather than use dynamic
DNS update. Understanding the reasons behind this choice seems important before
defining a new mechanism based on DNS.

Major issues: N/A

Minor issues:
Section 1.3.2 says "A good way to provide the parameters would be the home
network be able to copy/paste a JSON object".  This does not seem like a good
experience for a home device.

Nits/editorial comments:

- Abbreviations such as CPE are used before being designed
- The phrase "The use cases are not limitations" in section 1.3 could benefit
from some clarification. - The document would benefit from a thorough editorial
review for language.