-----BEGIN PGP SIGNED MESSAGE----- Curtis Villamizar <curtis@ans.net> writes:
The answer is clearly to number into an aggregate if you are dual homed. Sprint will take the aggregate and at least have one path to your prefix, very likely two if your two providers exchange your more specific route between each other.
We will route long prefixes across customer connections. Therefore, if a customer is dual-homed to another provider and has a long prefix from that other provider, we will listen to that long prefix across the customer connection. When it goes away, we will hear the aggregate, and route towards that. This, as Curtis says, is a clear win. I would note, though, that there is the risk that the other provider has contractual language wrt the non-portability of that provider's addresses that might make this not work. That, as Paul says, might be catch-22. However, I am sure that this would not be an insoluble problem, since, as I said in an earlier note, a price for an exception might be found through negotiation, even though an "official" PIARA experiment has not been started. Sean. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 Comment: PGP Public Key in ftp://ftp.sprintlink.net/engineer/smd/pgpkey iQCVAwUBMhZA+kSWYarrFs6xAQGQHAQAkon2lq0lovouN6IwxMouN1vx2IqXtN2i ZK6N5QF584IcHjyJVVnU5PIrTKytapCDj9hE9Jqd1VuKzepakIuvRM0v4JYbBHXv id8ZqbjFoQTY12etRI7ztXeVTAXNBy01LMKq1NES+S2/CvOhgaAe+rpNCJVuOGfi d0mgbdfALe8= =fUBJ -----END PGP SIGNATURE-----