>> I don't think inventing yet another protocol makes sense here. >> What is your usecase here? > Remember all the trouble we had with rogue RAs? An RA-killer protocol > built-in from the start would have avoided all of that, so I'm thinking of > an HNCP-killer protocol. Nothing complicitated, just react to any HNCP > packet by unicasting an HNCP packet with a KILLER TLV. Periodic KILLER > multicasts might be a good idea. > > 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? In general auto border discovery is a heuristic to increase user-friendliness, and it uses protocols that ISPs usually speak with us. At the moment it is also decoupled from HNCP in a sense that HNCP is only enabled after the interface category is determined to be internal. Cheers, Steven _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
