> On Mar 7, 2015, at 10:44 AM, Juliusz Chroboczek > <[email protected]> wrote: > >>> Homenet --- A ------ B >>> | | >>> | | >>> C ...... D >>> (ZigBee) > >> Why would you even autoconfigure a route at all between C and D? > > I think that you and Mikael expect that the ZigBee link will be designated > as stub, while Brian, ever the pessimist, expects things to go wrong > whenever they can. I happen to agree with Brian. > > (Which, by the way, is the reason why I think that the way networks > containing both IS-IS and Homenet IS-IS will silently break is a major > f*ck up. Section 6.3. Yeah, I was too tired to argue that point.)
The user would have to go out of their way to configure their non-homenet IS-IS router specifically to interoperate with the homenet IS-IS. How would they know how to do this other than to be familiar with the other requirements? It’s not like they would be able to accidentally drop a non-homenet IS-IS router into their network and have it start silently failing. Thanks, Chris. > > -- Juliusz > > _______________________________________________ > homenet mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/homenet _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
