Hello Jeff, Yes, and not only for the backup paths, we also have options for marking non-selected paths and their churn might be even worse.
We know that this might be complicated for the devices. Section 3. explains that the reason code should be optional, and devices should provide options for enable or disable the reason code. Do you think there are other implementation guidelines that we can consider that would facilitate this on the devices? Thanks, Camilo C On 21/3/25, 18:17, "Jeffrey Haas" <[email protected] <mailto:[email protected]>> wrote: Authors, As the active route churns, the reason why backup paths may lose vs. it may change. Was the intention in this specification that each time route selection changes the active path that we get a new rib-in message with new markings? -- Jeff _______________________________________________ GROW mailing list -- [email protected] To unsubscribe send an email to [email protected]
