TL;DR: I do not understand the reason for new text, and would vote against it.
I am probably being thick, but I can see three cases of ULAs in home network: [1] something not from HNCP (e.g. from ISP, from some IoT gateway device, configuration, ..) that are essentially static from HNCP point of view, and just routable to, [2] something not from HNCP (e.g. from ISP, from some IoT gateway device, configuration, ..) that also (partially) delegated to HNCP (also obviously routable to), and [3] HNCP generated (spontaneous) ULA (relatively dynamic), exactly 1 of them (or 0 if you buy the SHOULD argument which I do not). My assertion: Given HNCP generated one spans whole administrative domain, _and_ should not have routing anywhere outside it, it’s uniqueness does not _matter_. Therefore, what is the case for having to deal with ULA changing in case of network split/merge? Case 1: Let us imagine split; I give one of my homenet routers to my neighbor. My neighbor winds up using same ULA. It has different owner, it does not talk with my network devices, and nobody knows they have same ULA nor cares if they do. Case 2: Eventually, my neighbor gives the router back to me. I give it either physical access (wire) or appropriate wireless credentials. Again, it does not matter it has the same ULA, as long as the /64s it has assigned on it’s interfaces do not conflict what is in the rest of the network, and given it is [3] prefix, HNCP should take care of it. (Hell, even [2] type prefix would be fine too in this case). Only case where having same ULA in multiple places would matter, if you plan to route traffic between those places. Due to that, [3] case MUST NOT conflict with whatever comes from [1]/[2], but within [3] type, it does not matter at all. Internal is internal. However, the case 2 looks much different if the ULA prefixes in the merge are different. Then you have to renumber either devices connected to the added router, or to the rest of the homenet. Due to that, I would advocate clearing ULA state before doing the merge to prevent wrong side of the fence winning the ULA allocation arms race. And having 2 ULAs in a home network as result of that is just wrong, from my point of view. Still, renumbering devices connected to router being added to your homenet sounds perfectly acceptable in case the ULA is of type [3]. If it is [1]/[2], just more than one ULA is also fine so it would not be applicable here anyway. I have not looked at the draft text, but expressing these ideas should not be hard. The new text I strongly disagree with. Cheers, -Markus _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
