Re: [Lsr] "Prefix Unreachable Announcement" and "IS-IS and OSPF Extension for Event Notification"

Hi Enke Because MED is non transitive it is only propagated to adjacent AS, so only in unique situations where the path attribute does not need to be propagated multiple hops is MED utilized. I was thinking of AS level not prefix level symmetry. So for AS level symmetry exporting IGP metric

[Lsr] Francesca Palombini's Discuss on draft-ietf-lsr-isis-srv6-extensions-17: (with DISCUSS)

Francesca Palombini has entered the following ballot position for draft-ietf-lsr-isis-srv6-extensions-17: Discuss When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.)

Re: [Lsr] "Prefix Unreachable Announcement" and "IS-IS and OSPF Extension for Event Notification"

Hi, Gyan: I am not sure what you meant by "non-deterministic" behavior. If you referred to dampening the IGP metric export, there is this knob "bgp dynamic-med-interval". If one wants symmetric routing with scale at the prefix-level, "exporting IGP metric as MED" is the best option. Thanks.

Re: [Lsr] "Prefix Unreachable Announcement" and "IS-IS and OSPF Extension for Event Notification"

Hi Enke Understood. Sending IGP metric into BGP can have unwanted consequences as MED is higher up in BGP path selection and so can cause much non deterministic behavior. It is better to not match internal but rather do set metric to set higher MED on all prefix to make the path preferred. Or

[Lsr] LSR Presentation Slot Requests - IETF 112

Hi all, The IETF 112 Final Agenda is now available: https://datatracker.ietf.org/meeting/112/agenda.html We will have one LSR session: Thursday, November 11, 2021 12:00-14:00 UTC Thursday Session I Please send slot requests to

Re: [Lsr] "Prefix Unreachable Announcement" and "IS-IS and OSPF Extension for Event Notification"

Hi, Gyan: > IGP metric exported to BGP as MED does not come into play here as we are not redistribution ISIS into BGP. > We are doing next hop self on egress PE and it’s the PE loopback next hop attribute that is flooded. "Exporting IGP metric to BGP" (also discussed in Sect. 1.1, RFC 5302) is