In message <8031f94c-66bf-4748-aa97-5efa12bb8...@fugue.com> Ted Lemon writes: > If you autoconfigure a routing topology, you have to make sure that > you don't accidentally autoconfigure it to include routers that > weren't intended to have been included. > > The concern is not for grandma running Windows 98, and the whole hard > shell/gooey center debate is completely beside the point.
You've said what the problem *isn't*, so what *is* the problem on a homenet? Surely the provider is not going to accept a unauthenticated auto-config hello request and start peering, nor will it accept a hello from a legacy router configured with router-id and a "be adjacent to anything" policy. If the electric meter wants to be a router with a slow link on the power line, then it needs to act like a provider router, but perhaps only advertising reachability to the electric utility, not the whole Internet. The more specific prefix (than default) should get the attention of the water heater if it has to try to reach the electric utility. Curtis _______________________________________________ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet
