Huaimo wrote: > > Tony wrote: > > > >There is no need for a backup leader. If the area leader is partitioned > >from the topology, then > > leader election is repeated, resulting in a new leader. Again, no > > configuration is required. > > The above does not talk about topology split, but about the leader down. > After a user/operator has configured some things on the leader, and the > leader has got them and distributed them in some form, and then some time > later, the leader goes down, a new leader is selected. In this case, will the > new leader take and maintain the configurations or the information derived > from the configurations done on the old leader.I
Operators configure their routers using their management systems. When an operator chooses a distributed algorithm they SHOULD configure that choice consistently in their network if they don't expect changes based on leader election. This is something that can be stated in the document if it must be. Yes, misconfiguration is possible due to NMS bugs, in which case it may be reasonable for the LSR protocol to detect and signal this misconfiguration. We do not want to build a bunch of complexity into LSR protocols to treat misconfigurations as the normal state of things, as it is not. Thanks, Chris. > Best Regards, > Huaimo >
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ Lsr mailing list [email protected] https://www.ietf.org/mailman/listinfo/lsr
