-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Michael K. Smith - Adhost wrote:
...snip...snip... > > The answer to this may be "no way". :-) If you have a peering session > with the customer, why not only announce your routes from your two other > providers so that the customer doesn't see the routes from the one they > want to avoid? Wouldn't that accomplish the same thing? You could tag > your transit routes with a community, add the two you want to transit to > a community-list and then announce only the routes that match the list. > > Thinking out loud, but not necessarily well. :-) > And when the packets reach his routers that have all 3 provider exit points available, how is he going to prevent those packets from choosing the "undesired" exit point? It's not a question of what he advertises to his customer, but rather how the forwarding decision is modified for just this customer. - -- ========= bep -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFH6rJdE1XcgMgrtyYRAqiUAJ9WrZEqdo3wvfHIECABL/1lumg4gACgvb2F 0ohoY6gFi5RWdjyEv86KT7Y= =2oTl -----END PGP SIGNATURE----- _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
