Distributed Node Consensus Protocol
draft-ietf-homenet-dncp-12

Approval announcement
Draft of message to be sent after approval:

From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Cc: homenet-chairs@ietf.org, mark@townsley.net, "The IESG" <iesg@ietf.org>, draft-ietf-homenet-dncp@ietf.org, homenet@ietf.org, rfc-editor@rfc-editor.org, terry.manderson@icann.org
Subject: Protocol Action: 'Distributed Node Consensus Protocol' to Proposed Standard (draft-ietf-homenet-dncp-12.txt)

The IESG has approved the following document:
- 'Distributed Node Consensus Protocol'
  (draft-ietf-homenet-dncp-12.txt) as Proposed Standard

This document is the product of the Home Networking Working Group.

The IESG contact persons are Brian Haberman and Terry Manderson.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-homenet-dncp/


Technical Summary

This document describes the Distributed Node Consensus Protocol (DNCP), a generic state synchronization protocol which uses Trickle and Merkle trees.  DNCP is transport agnostic and leaves some of the details to be specified in profiles, which define actual implementable DNCP based protocols.

Working Group Summary

The earliest roots of DNCP are in draft-acee-ospf-ospfv3-autoconfig-00 (Oct 2011) which led to draft-acee-ospf-ospfv3-autoconfig-00 and was published as Standards Track RFC 7503,  draft-arkko-homenet-prefix-assignment-00 (April 2012), “Trickle” as defined in Standards Track RFC 6206, and HNCP first defined in draft-stenberg-homenet-hncp-00. DNCP in its current form was split from HNCP for the sake of modularity and reuse. Thus the work that ultimately led to this document evolved roughly through three major iterations before reaching draft-ietf-homenet-dncp-00. Last call had mostly minor issues brought up, which were addressed.

Document Quality

  Are there existing implementations of the protocol? 

Yes, one open source project at https://github.com/sbyx/hnetd/ and project homepage at http://www.homewrt.org/doku.php.

Have a significant number of vendors indicated their plan to implement the specification?

The open source implementation (hnetd daemon) has been a part of routing feed of OpenWrt since Barrier Breaker (14.07) release in July, 2014.

Google Nest, Comcast Xfinity, D-Link, Freebox, Technicolor, and Cisco have all expressed interest in implementing and/or shipping HNCP, which relies upon DNCP. HNCP (and thereby DNCP) is referenced in version 1.0 of the Thread Specification (Nest, Samsung, etc.)

“Homenet” running either the early OSPF version and later HNCP (with DNCP) has been demonstrated publicly at:

8 IETF BnB events
1 CES Event in Las Vegas
3 IPv6 World Congress
1 Cablelabs Meeting

Are there any reviewers that  merit special mention as having done a thorough review, e.g., one that resulted in important changes or a conclusion that the document had no substantive issues? If there was a MIB Doctor, Media Type or other expert review, what was its course (briefly)? In the case of a Media Type review, on what date was the request posted?

No particular Dr. reviews. I believe there has been a special request for review by the newly formed Routing Area Design Team regarding homenet, but have not seen the result. Brian Carpenter reviewed on behalf of Anima. Mikael Abrahamsson and Juliusz Chroboczek provided substantive review and comments as well.

Personnel

Who is the Document Shepherd? 

Mark Townsley

Who is the Responsible Area
  Director?

Terry Manderson


RFC Editor Note

under further review the text of the IANA section needs some improvement by copying and/or moving normative text regarding use of certain ranges of TLV types into section 7 (the TLV definition).

IANA Note

IANA will have one registry to setup for DNCP TLV types as outlined in the IANA Considerations section.

While DNCP is designed to be generally useful, its first usage is within Homenet (specifically HNCP) so any Expert Reviewer should be familiar with the work in the Homenet WG. Either the chairs, or other active and willing participants.