Hi Gyan, The dynamic flooding extensions are all new work and they would be optional enabled. We would appreciate your input and especially on applicability to your existing deployed networks. Thanks, Acee
From: Lsr <[email protected]> on behalf of Gyan Mishra <[email protected]> Date: Tuesday, May 14, 2019 at 9:57 PM To: Tony Li <[email protected]> Cc: Huaimo Chen <[email protected]>, "[email protected]" <[email protected]> Subject: Re: [Lsr] Flooding Negotiation bit Is this a new option that does not exist today in OSPFv3 or ISIS. Operators have the ability to mark interfaces as passive so only router stub LSA is generated which helps assist in full SPF calculations flooding. Gyan S. Mishra IT Network Engineering & Technology Verizon Communications Inc. (VZ) 13101 Columbia Pike FDC1 3rd Floor Silver Spring, MD 20904<x-apple-data-detectors://2/0> www..linkedin.com/in/GYAN-MISHRA-RS-SP-MPLS-IPV6-EXPERT<http://www.linkedin.com/in/GYAN-MISHRA-RS-SP-MPLS-IPV6-EXPERT> Phone: 301 502-1347<tel:301%20502-1347> Email: [email protected]<mailto:[email protected]> Sent from my iPhone On May 14, 2019, at 4:31 PM, [email protected]<mailto:[email protected]> wrote: Hi Huaimo, If I understand you correctly, this seems to have almost the same semantics as the Flooding Request TLV (section 5.1.5) or the Flooding Request Bit (section 5.2.7). If I’m not understanding you, could you please clarify the differences and why the current mechanisms are insufficient. Tony On May 14, 2019, at 1:09 PM, Huaimo Chen <[email protected]<mailto:[email protected]>> wrote: Hi Tony, For the case you described below, in order to add one or a limited number of links to the flooding topology temporarily, a new bit, called Flooding Negotiation bit (FN bit for short), should be defined and used. In OSPF, the FN bit is defined in Extended Options and Flag (EOF) TLV in OSPF Hello. In IS-IS, the FN bit is defined in the new TLV used for FR bit. When a node N (with 1000 interfaces/links for example) reboots, , each (node X) of the nodes connected to node N will establish an adjacency with node N. During the process of the adjacency establishment between node X and node N, node X sends a FN-bit set to one in its Hello to node N, node N selects one link/node (or a limited number of links) for temporarily flooding and sends only to this selected node a FN-bit set to one in its Hello. Node N adds the selected link/node to the FT temporarily after receiving the FT bit set to one from the selected node. After receiving the FN bit set to one from node N, the selected node adds the link (connected to node N) to the FT temporarily. In other words, a node Y connected to node N adds the link to node N to the FT temporarily after it sends and receives the FT bit set to one to/from node N; node N adds a selected link to the FT temporarily after it receives and sends the FT bit set to one from/to node Y. Best Regards, Huaimo ==== A case from Tony on 3/6 ==== If the node that rebooted has 1000 interfaces, which interfaces should be temporarily added? Adding all of them is likely to trigger a cascade failure. The TLV allows us to signal which ones should be enabled. _______________________________________________ Lsr mailing list [email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/lsr
_______________________________________________ Lsr mailing list [email protected] https://www.ietf.org/mailman/listinfo/lsr
