Thanks a lot Robert,
Cheers!! Girish Pattanaik *From:* Robert Raszuk [mailto:[email protected]] *Sent:* Thursday, December 20, 2018 3:04 AM *To:* Girish Pattanaik *Cc:* SPRING WG List *Subject:* Re: [spring] Will CSPF be affected by ISIS Overload bit ...? Girish, Overload bit or max metric router LSA indicate that given node should be removed from topology calculations so by default it applies to both SFP and constrained SPF. However some vendors have knobs to still allow such nodes to be included into CSPF if you configure so explicitly. Example: *mpls traffic-eng path-selection overload allow <https://www.cisco.com/c/en/us/td/docs/ios/12_0s/feature/guide/fs_isovr.html#wp1032917>* So IMO by default you should not consider this transit router for both SPF & CSPF, but it will rather not be set hard in stone in the draft/RFC as there are obviously use cases to allow to override this default behavior. Thx R. On Wed, Dec 19, 2018 at 10:23 PM Girish Pattanaik < [email protected]> wrote: Hi All, My self Girish Pattanaik, am working as a Techlead in IPI India. As we know Today, the use cases of the O bit in ISIS have evolved beyond its original meaning and intention. Its widely used by administrators .As per understanding setting overload bit on transit will only affect the SPF calculation on head end, So now point is, will it also affect the *CSPF* calculation?, And if not then how will we handle this overload bit scenario for CSPF.? I didn’t find this any such scenario has mentioned in your current draft, so mailing you to get the appropriate answer for this. *Cheers!!* *Girish Pattanaik* ..._______________________________________________ spring mailing list [email protected] https://www.ietf.org/mailman/listinfo/spring -- ..
_______________________________________________ spring mailing list [email protected] https://www.ietf.org/mailman/listinfo/spring
