On Oct 23, 2012, at 4:44 PM, Warren Kumari wrote: > Not sure I agree with this part -- simply because it can be used in the > decision process doesn't automatically mean it needs to be protected. It (and > med and IGP cost and routerID) "feel" to me like they are low enough down > that they can be (and should be) left alone, to allow operators some > flexibility (Yes, Origin is set by the originator, the rest of these things > are more about the local network, but I still don't think that this > automatically means that it needs to be protected).
Where do you draw that line? Where do you force attackers to move when you draw the line and what's the impact? An origin AS wanting to protect the origin code integrity seems perfectly sensible to me, else upstream ASes can effect not what they meant, but what they said, and drive more traffic across links that they manage, or move traffic, and that's a real problem that exists today that we ought to be able to accommodate. -danny !DSPAM:50870d09120615471543354! _______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
