order error:
likewise to prefer invalid over not found customer prefixes.
Sorry,
R.
so, your programatically generated template for a customer peering
could be something such as the following pretty strict policy:
if p in custs-pfxs
community add ExportToPeersCustsAndUpstreams
if p is marked valid
set local-pref 120
elif p is marked notfound
set local-pref 100
elif p is marked invalid # layer nine attack
set local-pref 120 # maintain g-r fantasy
that seems really like a brilliant idea to set same local pref of 120 to
both valid and invalid customer prefixes. likewise to prefer not found
(where 100 would be applied anyway as this is local pref's default
value) over invalid customer prefixes.
r.
_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr
