Skip to main content

Last Call Review of draft-ietf-homenet-naming-architecture-dhc-options-20

Request Review of draft-ietf-homenet-naming-architecture-dhc-options
Requested revision No specific revision (document currently at 24)
Type Last Call Review
Team Ops Directorate (opsdir)
Deadline 2022-10-04
Requested 2022-09-20
Authors Daniel Migault , Ralf Weber , Tomek Mrugalski
I-D last updated 2022-09-28
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 Al Morton
State Completed
Request Last Call review on draft-ietf-homenet-naming-architecture-dhc-options by Ops Directorate Assigned
Posted at
Reviewed revision 20 (document currently at 24)
Result Ready
Completed 2022-09-28
From the draft:
This document defines DHCPv6 options so an Homenet Naming Authority (HNA) can
automatically proceed to the appropriate configuration and outsource the
authoritative naming service for the home network. In most cases, the
outsourcing mechanism is transparent for the end user. The document describes
how a network can provision the HNA with a specific DOI. This could be
particularly useful for a DOI partly managed by an ISP, or to make home
networks resilient to HNA replacement. The ISP delegates an IP prefix to the
home network as well as the associated reverse zone. It appears that the
document accomplishes these goals (although I'm not an expert in homenet
topics). The Shepherd's form says that this and a companion draft are the last
items to complete before closing homenet (interest is waning). The protocol
details seem to be well-considered.

It appears that the Scenarios were moved to Appendices, rather than as
normative section and subsections:

 Appendix A. Scenarios and impact on the End User

    This *section* details various scenarios and discuss their impact on the
    end user. This section is not normative and limits the description of a
    limited scope of scenarios that are assumed to be representative. Many
    other scenarios may be derived from these.

s/section/Appendix/g   and other fixes.