Hello Max, Ad 1 - Apologies for not being clear. I meant the case (pretty common case) where I advertise the same /24 from two distinct sites. The fact that those sites are connected internally on the DMZ side should play no difference to how we attack traffic from outside. Would you agree?
> 2. Are you proposing to make any changes to best path selection based on > > the presence of the specified community ? > > No. The intention is to only allow operators to influence best path > selection by means of import/export policies if they deem that a good > idea. > Oh I see. So essentially you are saying that ANYCAST marked paths should not be suppressed on ingress. If so I am not sure if they are ever suppressed on ingress. Only on egress if they are coming from PA space. But that's not really interesting case since you recommend to mark them with NO-EXPORT anyway. > 4. Or alternatively to #3 are you suggesting to always use ADD-PATHS ALL > > for all prefixes marked with ANYCAST community ? > > In the RR case I presume? If so that could be an option which could > make sense to add to the proposal as one option. I'm not sure if a > general suggestion could be given here. > You could list it in your draft as one possible use case. Which is in the event of no ADD_PATH ALL setting to make them still ALL if marked with ANYCAST community. Cheers, R.
_______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
