Skip to main content

Telechat Review of draft-ietf-homenet-hncp-09

Request Review of draft-ietf-homenet-hncp
Requested revision No specific revision (document currently at 10)
Type Telechat Review
Team Ops Directorate (opsdir)
Deadline 2015-11-17
Requested 2015-10-09
Authors Markus Stenberg , Steven Barth , Pierre Pfister
I-D last updated 2015-10-26
Completed reviews Genart Last Call review of -09 by Francis Dupont (diff)
Secdir Telechat review of -09 by Yoav Nir (diff)
Opsdir Telechat review of -09 by Sheng Jiang (diff)
Rtgdir Early review of -04 by Thomas H. Clausen (diff)
Assignment Reviewer Sheng Jiang
State Completed
Request Telechat review on draft-ietf-homenet-hncp by Ops Directorate Assigned
Reviewed revision 09 (document currently at 10)
Result Has nits
Completed 2015-10-26
Hi, OPS-DIR, Authors,

I have reviewed this document as part of the Operational directorate's ongoing
effort to review all IETF documents being processed by the IESG. These comments
were written with the intent of improving the operational aspects of the IETF
drafts. Comments that are not addressed in last call may be included in AD
reviews during the IESG review. Document editors and WG chairs should treat
these comments just like any other last call comments.

This Standards Track document describes the Home Networking Control Protocol
(HNCP), an extensible configuration protocol and a set of requirements for home
network devices. HNCP is described as a profile of and   extension to the
Distributed Node Consensus Protocol (DNCP), which is another document in
progress. This document is well written. I don't see any major issues from the
operations and management perspective. It is almost ready to be published.

I have some comments as follow:

1. HNCP describes Prefix and Naming configuration. But it is not very clear how
they are matched in the DNCP architecture. It would be help to understand if
some description using DNCP architecture, like node state and network state,
etc., could be added. 2. It would be very useful to add a bootstrap and
configuration procedure of HNCP. So far, this is not clear. 3. Section 6.5
"only the one published by the node with the highest node identifier". It is
not very clear how to compare the value against node identifier. 4. Section 1.1
"Ideally, the routing protocol is also zero-configuration (e.g., no need to
configure identifiers or metrics) although HNCP can be used also with a
manually configured routing protocol." It is not very clear how or what routing
protocol is zero configuration. My guess is this refers to RFC 7503 "OSPFv3
Auto-Configuration" and ongoing work of draft-liu-isis-auto-conf "ISIS
Auto-Configuration". Informational references to them should be added.