Subject: Protocol Action: 'Distributed Prefix Assignment Algorithm' to Proposed Standard (draft-ietf-homenet-prefix-assignment-08.txt)

From: The IESG <[email-masked]>
Date: Thu, 10 Sep 2015 07:47:13 -0700

The IESG has approved the following document:
- 'Distributed Prefix Assignment Algorithm'
  (draft-ietf-homenet-prefix-assignment-08.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-prefix-assignment/

Technical Summary

This document specifies a distributed algorithm for prefix assignment within a site. While developed primarily for IPv6, it is generic enough to be used for any prefix-based numbering space such as IPv4. In order to run, the algorithm requires that participating nodes share information through a flooding mechanism of some kind.  If the flooding mechanism ensures that all messages are propagated to all nodes faster than a given timing upper bound, the algorithm also ensures that all assigned prefixes used for networking operations (e.g., host configuration) remain unchanged, unless another node assigns an overlapping prefix with a higher assignment priority, or the topology changes and renumbering cannot be avoided.

Working Group Summary

This algorithm began as an extension to OSPF as, at the time, the Homenet WG was heading down the path of using OSPF as a monolithic home network routing and configuration protocol. There was strong consensus against using OSPF in this manner in the WG, leading to the the standalone prefix-assignment document. As a modular piece of work, the algorithm has now been applied to OSPF, IS-IS, and HNCP.

RFC 7503 includes this text:

   “This new LSA is designated for information related to OSPFv3
   autoconfiguration and, in the future, could be used for other
   autoconfiguration information, e.g., global IPv6 prefixes.  However,
   this is beyond the scope of this document.”

While this document is not referenced directly above, the work in this document is what was in mind when RFC 7503 was written.

Document Quality

Open source implementation: http://github.com/sbyx/hnetd, 

Personnel

 Mark Townsley is the document shepherd
 Terry Manderson is the responsible AD