I have read this draft. It looks very good.
I have the following questions:
1. What are the interoperability considerations if the node also
contains (historical) configuration for acting as an RFC7084 router?
Especially with respect to requirement L2 and L8.
I came across this whilst testing the openwrt hnet package, where some
interfaces where configured with 'proto hnet', whilst other interfaces
still had vanilla openwrt config "option ip6assign '64'".
SHOULD nodes when performing draft-ietf-homenet-prefix-assignment-03
take historical RFC7084 assignments into account as being statically
configured with a certain priority?
Also
2. may/should/must a Homenet router that participates in the
draft-ietf-homenet-prefix-assignment-03.txt also act as a proxy for an
old RFC7084 router connected to one interface?
[ref: RFC 7368 3.9]
Some of the hardest problems in developing solutions for home
networking IPv6 architectures include discovering the right borders
where the 'home' domain ends and the service provider domain begins,
deciding whether some of the necessary discovery mechanism extensions
should affect only the network infrastructure or also hosts, and the
ability to turn on routing, prefix delegation, and other functions in
a backwards-compatible manner.
I could imagine the homenet router grabbing a bunch of prefixes on
behalf of the 7084 router, when it detects an inbound DHCP PD request on
one of its interfaces, and then issuing a DHCP PD reply to the 7084
router based on these prefixes, and also advertising a local route to
the downstream router.
[email protected] wrote:
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Home Networking Working Group of the IETF.
Title : Distributed Prefix Assignment Algorithm
Authors : Pierre Pfister
Benjamin Paterson
Jari Arkko
Filename : draft-ietf-homenet-prefix-assignment-03.txt
Pages : 18
Date : 2015-02-08
Abstract:
This document specifies a distributed algorithm for automatic prefix
assignment. Given a set of delegated prefixes, it ensures that at
most one prefix is assigned from each delegated prefix to each link.
Nodes may assign available prefixes to the links they are directly
connected to, or for other private purposes. The algorithm
eventually converges and ensures that all assigned prefixes do not
overlap.
The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-homenet-prefix-assignment/
There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-homenet-prefix-assignment-03
A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-homenet-prefix-assignment-03
Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.
Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/
--
Regards,
RayH
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
