On Fri, 9 Jun 2023, Matthew Petach wrote:
Hi Mike,
In general, no, there's nothing that prevents you from doing that.
...
Now, from a network reachability perspective, you should also think about your own internal network connectivity. If you're using the same ASN in California and Makati, you'll need redundant internal network connections between the two countries to ensure you don't end up with a partitioned ASN. Remember, California won't accept the advertisements from Makati over the external Internet, as AS-PATH loop detection will drop the announcements; likewise, Makati won't hear the advertisements of the California IP space.
Every platform I've used has a knob for turning off / relaxing as-path loop detection. Note, for some platforms (at least Juniper), you may also have to have your upstream provider "advertise-peer-as", though I suspect it's highly unlikely you'd have BGP service from the same upstream in both CA and PH...so this won't likely be an issue. At one point, ARIN manufactured a policy that out of region use of IP resources didn't count toward utilization calculations, but I think that was fixed...not that it likely matters in general at this point. As someone mentioned, you will have IP Geo issues to resolve. Other than that, IPs are IPs, and as long as your upstreams accept your routes, it shouldn't matter if the IPs came from / are registered by ARIN/RIPE/APNIC, etc. In fact, it was suggested to me at one point by an IP broker that we move all of our ARIN IP assets to one of our RIPE LIRs due to much better pricing re annual fees from RIPE vs ARIN. We have POPs pretty much everywhere, and have IPs/accounts/memberships with ARIN/RIPE/APNIC/Registro.br. ---------------------------------------------------------------------- Jon Lewis, MCP :) | I route StackPath, Sr. Neteng | therefore you are _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________