>> It's not. The AS Path is to prove the path is loop free. It was never >> intended to prove where the update went in the network. > > ok, so what other tool do we have today that does this? (can tell us > that an path is not fictitious)
There never was a tool intended to solve that problem --from a routing perspective, it doesn't matter where I get the information from, only that the path is actually loop free. BGP cares about policy as well, but only the policy between me and my peer, never a peer several hops away. Let me ask this --do you care if you get the certificate showing AS x is able to originate prefix y from a server in AS x, or off a web site someplace? Or are you more concerned about the certificates/etc being right --that the information is true? :-) Russ
signature.asc
Description: OpenPGP digital signature
_______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
