<div dir="ltr"><div class="gmail_default" style="font-size:small">Why has this been cross posted to the OpenWrt <u><b>Development</b></u> List?</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">I fail to see any relevance to the usual and prevailing use of this list.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Dec 8, 2015 at 10:52 AM, Dave Taht <span dir="ltr"><<a href="mailto:dave.taht@gmail.com" target="_blank">dave.taht@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">While I'm dreaming of steadier funding for things I care about,<br>
ietf homenet wg's work is nearly complete.<br>
<br>
*most* of the work is already done in openwrt to make all the ietf<br>
homenet proposed standards work, and indeed, be the default in<br>
openwrt. However nobody is funded anymore to take it further, and it<br>
would be nice to see builds taking place and tested automagically - to<br>
finally bring the dream of always interoperable, ipv6 capable cpe and<br>
home routers, plugged in, every which way - a reality.<br>
<br>
There are still many details left to make it happen well and be a<br>
truly usable set of interoperable standards - I have a huge list of<br>
things still not encapsulated or negotiated right within the hncp<br>
stack, such as wifi channel selection and uplink bandwidth, and babel<br>
is in need of some love, there are some state machine bugs that need<br>
squashing.....<br>
<br>
---------- Forwarded message ----------<br>
From: The IESG <<a href="mailto:iesg-secretary@ietf.org">iesg-secretary@ietf.org</a>><br>
Date: Tue, Dec 8, 2015 at 3:09 PM<br>
Subject: [homenet] Protocol Action: 'Home Networking Control Protocol'<br>
to Proposed Standard (draft-ietf-homenet-hncp-10.txt)<br>
To: IETF-Announce <<a href="mailto:ietf-announce@ietf.org">ietf-announce@ietf.org</a>><br>
Cc: <a href="mailto:homenet-chairs@ietf.org">homenet-chairs@ietf.org</a>, <a href="mailto:mark@townsley.net">mark@townsley.net</a>,<br>
<a href="mailto:draft-ietf-homenet-hncp@ietf.org">draft-ietf-homenet-hncp@ietf.org</a>, The IESG <<a href="mailto:iesg@ietf.org">iesg@ietf.org</a>>,<br>
<a href="mailto:homenet@ietf.org">homenet@ietf.org</a>, <a href="mailto:terry.manderson@icann.org">terry.manderson@icann.org</a>, <a href="mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a><br>
<br>
<br>
The IESG has approved the following document:<br>
- 'Home Networking Control Protocol'<br>
(draft-ietf-homenet-hncp-10.txt) as Proposed Standard<br>
<br>
This document is the product of the Home Networking Working Group.<br>
<br>
The IESG contact persons are Brian Haberman and Terry Manderson.<br>
<br>
A URL of this Internet Draft is:<br>
<a href="https://datatracker.ietf.org/doc/draft-ietf-homenet-hncp/" rel="noreferrer" target="_blank">https://datatracker.ietf.org/doc/draft-ietf-homenet-hncp/</a><br>
<br>
<br>
<br>
<br>
<br>
Technical Summary<br>
<br>
This document describes the Home Networking Control Protocol (HNCP),<br>
an extensible distributed configuration protocol for “unmanaged”<br>
(e.g., functions that are not configured manually or by a central<br>
management server of some kind) home network devices. The intent is to<br>
provide a distributed protocol for flooding of basic configuration<br>
state essential to IP network functionality.<br>
<br>
HNCP is described as a profile of and extension to the Distributed<br>
Node Consensus Protocol (DNCP). HNCP enables discovery of network<br>
topology and borders, automated configuration of addresses (using the<br>
algorithm defined in draft-ietf-homenet-prefix-assignment-08), name<br>
resolution, and service discovery.<br>
<br>
Working Group Summary<br>
<br>
The earliest roots of HNCP are in draft-acee-ospf-ospfv3-autoconfig-00<br>
(Oct 2011) which was eventually published as Standards Track RFC 7503,<br>
with the expectation that other documents would define<br>
HOMENET-specific TLVs to be carried inside OSPFv3.<br>
<br>
Strong resistance from the WG (as well as open source router software<br>
developers) to this tight coupling between a specific routing protocol<br>
and network configuration led to the split of HNCP as a standalone<br>
protocol first defined in draft-stenberg-homenet-hncp-00.<br>
<br>
Later, DNCP (generic aspects of HNCP concerning synchronization of<br>
state among a set of nodes using Trickle[RFC6206]) were split from the<br>
main HNCP document to allow for modularity and potential reuse. After<br>
this final split, the HNCP document describes the HOMENET-specific<br>
TLVs and the DNCP profile used to synchronize them across the home<br>
network.<br>
<br>
Document Quality<br>
<br>
Are there existing implementations of the protocol?<br>
<br>
The reference “hnetd” implementation is at<br>
<a href="https://github.com/sbyx/hnetd/" rel="noreferrer" target="_blank">https://github.com/sbyx/hnetd/</a> (project homepage at<br>
<a href="http://www.homewrt.org/doku.php" rel="noreferrer" target="_blank">http://www.homewrt.org/doku.php</a>).<br>
<br>
There is a second (fully independent and interoperable) implementation<br>
available at <a href="https://github.com/jech/shncpd" rel="noreferrer" target="_blank">https://github.com/jech/shncpd</a> developed entirely from<br>
the specification documents without referal to the reference<br>
implementation.<br>
<br>
There is a partial third implementation, though not fully independent,<br>
available here: <a href="https://github.com/fingon/pysyma" rel="noreferrer" target="_blank">https://github.com/fingon/pysyma</a><br>
<br>
<br>
Have a significant number of vendors indicated their plan to<br>
implement the specification?<br>
<br>
<br>
The reference implementation has been a part of routing feed of<br>
OpenWrt since Barrier Breaker (14.07) release in July, 2014.<br>
<br>
Google Nest, Comcast Xfinity, D-Link, Freebox, Technicolor, and Cisco<br>
have all expressed interest in implementing and/or shipping HNCP. HNCP<br>
is referenced in version 1.0 of the Thread Specification (Nest,<br>
Samsung, etc.)<br>
<br>
“Homenet” running either the early OSPF version and later HNCP (with<br>
DNCP) has been demonstrated publicly at 9 IETF BnB events (every BnB<br>
since BnB began, plus at least one “pre BnB” event), HNCP split off<br>
from OSPF has been demontrated at the last 5 IETF BnB events. In<br>
addition to IETF, Homenet Implementations have been presented at:<br>
<br>
3 IPv6 World Congress events in Paris<br>
1 CES Event in Las Vegas<br>
1 Cablelabs Meeting in Denver, Co<br>
<br>
Are there any reviewers that merit special mention as having done a<br>
thorough review, e.g., one that resulted in important changes or a<br>
conclusion that the document had no substantive issues? If there was a<br>
MIB Doctor, Media Type or other expert review, what was its course<br>
(briefly)? In the case of a Media Type review, on what date was the<br>
request posted?<br>
<br>
Thomas Clausen provided an exhaustive review on behalf of Routing Area<br>
resulting in a number of changes to the document. Review (and coding<br>
effort) by Juliusz Chroboczek indicated that a second interoperable<br>
implementation was doable, and he provided only some minor<br>
clarifications that were incorporated later on. A number of other<br>
people have also reviewed the document.<br>
<br>
Personnel<br>
<br>
Who is the Document Shepherd?<br>
<br>
Mark Townsley<br>
<br>
Who is the Responsible Area Director?<br>
<br>
Terry Manderson<br>
<br>
RFC-Editor Note<br>
<br>
It would be helpful if this document was clustered with the<br>
publication of draft-ietf-homenet-dncp-12<br>
<br>
IANA Note<br>
<br>
Document requests one IANA registry for TLV-types with action “RFC required”,<br>
initial contents and policies are given. Furthermore allocation of two<br>
UDP ports and a well-known IPv6 link-local multicast group are<br>
requested, the purpose of the allocation is mentioned.<br>
<br>
<br>
_______________________________________________<br>
homenet mailing list<br>
<a href="mailto:homenet@ietf.org">homenet@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/homenet" rel="noreferrer" target="_blank">https://www.ietf.org/mailman/listinfo/homenet</a><br>
_______________________________________________<br>
openwrt-devel mailing list<br>
<a href="mailto:openwrt-devel@lists.openwrt.org">openwrt-devel@lists.openwrt.org</a><br>
<a href="https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel" rel="noreferrer" target="_blank">https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel</a><br>
</blockquote></div><br></div>