Samantha Lo wrote:
What would you suggest?
I suggest that we can have multiple RRCs with different upstream providers (better no overlaps).
This is possible: we can set up multiple IBGP peerings to multiple RRCs and have those RRCs provide transit. For determining which RRCs are best to use in order not to have overlap between upstreams, perhaps you could use the RIS looking glass to see who provides transit for the beacon prefix of each RRC. That gives you an easy way to check who provides transit for each RRC and thus who would provide transit for your prefix if you were to announce it from that RRC. A list of the beacon prefixes announced by each RRC is here: http://www.ripe.net/projects/ris/docs/beaconlist.html Here you can also see where each RRC is located.
We can further investigate the response of the upstreams to the prepending in different situations, e.g. locations (but I don't think location would have any effect to the response. Instead, the policies of the upstreams would be affected. That's why I would like to know the policies of your upstreams.)
As far as I know, when we request transit for a beacon prefix, the agreement is "treat this prefix exactly as though we were a stub customer of yours". The routing policies of our upstreams are another matter, but perhaps once you know better which RRCs and thus which upstreams you will be using you can look up this information in the RIPE routing database (Or perhaps we can try to confirm this with them directly. Note, however, that this is likely proprietary information that cannot be published.)
So, your announcer would be perfectly fit in our measurement. But I am still not very sure how to set up an iBGP section from my university network to the RRCs.Would you give me more details?
Once we know more about the setup you want to use, e.g. which RRCs you want to use, which prefixes you want to announce and where, I can configure IBGP sessions between an IP address you give me and the RRCs and give you the info you need to set up the peering on your side. Depending on the RRC, we might need to do other things like open the firewall. Cheers, Lorenzo -- Lorenzo Colitti lorenzo@ripe.net Network Engineer +31-20-5354471 RIPE NCC www.ripe.net