>>>> The point is you've gone beyond the existence of the path here to the >>>> rightful use of the path --and that is policy. >> >>> don't think so. >> >> Yes, you have. >> >> Because you've insisted on making the solution work per prefix, you've >> moved the problem out of the realm of path validation and into the realm >> of per prefix policy. Paths don't exist per prefix. Paths either exist >> or don't. Only policies can tell you whether or not a particular path is >> available for a particular prefix. > > clearly there's something I'm missing... if we remove the ideas of > SIDR form the table, how does your picture change? how does the > outcome change? it SEEMS (to me) that the situation is exactly the > same... there's no idea of policy in protocol, there is only bgp, and > the local decision by B to NOT send a route to E.
But D has no way of knowing this in band without SIDR. With SIDR, it's a matter of looking at the signatures --by the design specs of SIDR itself. When you provide information about who should be advertising to whom across multiple hops, rather than who is connected to whom, then you've moved from existence proofs to policy implementation. Russ _______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
