Hi Chris,
In the end, I think 'bgpsec suggests' that the operator would make some decision... ideally the same decision across the network.
Such decision is inherently per prefix. So even assuming ideal case and such policy like in your example would be the same across given AS how would you see such policy to be the same across the entire path given update traverses ?
Aren't you afraid about swiss cheese effect for end-to-end connectivity if some ASes prefer signed and some other non signed paths ?
What happens in your example if singed comes with PATH_SIG listing 4 ASes (pCount=1 of each) and real AS_PATH is length of 3 ?
If you set local pref on inbound (just like shipping code allows for origin validation) you will deliberately choose longer path as best since LOC_PREF is checked much earlier in BGP Best path then AS_PATH length (even assuming those would be comparable across two attributes).
Thx, R. _______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
