>> If we don't do that, we'll gather a lot of bad press by breaking operational
>> networks when stateful DHCP fails for some reason, with no easy way to
>> work around that.
> Can you elaborate a bit more on the breaking operational network
> parts (not in the RA-sense but for HNCP)? I mean a concrete
> use-case or example of what would break or how?
One of the interfaces, say eth1, is connected to an IPv6-only network that
doesn't do DHCPv6-PD. Another one is connected to an HNCP network, with
some other router publishing an IPv6 prefix delegation.
eth1
IPv6-only network ----- me ----- (HNCP network) ----- HNCP router with PD
Since there's neither DHCPv6-PD nor DHCPv4 on the IPv6-only network, eth1
is detected as internal. Since there's an IPv6 prefix delegation, the
HNCP daemon allocates a /64 to each link connected to each of its internal
interfaces and starts sending RAs on eth1.
I'm now sending RAs on a production network, with no way for the network
administator to prevent that short of either (1) reconfiguring my router
(and any other Homenet routers that might be connected to this network),
or (2) enabling stateful DHCPv4 or DHCPv6-PD.
So please either define a new RA option that triggers HNCP border discovery,
or define a new HNCP-killer TLV:
while(1) {
sendmsg(KILLER)
sleep(random() % 16)
}
-- Juliusz
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
