19 Jun
2019
19 Jun
'19
11:33 a.m.
IIRC Vultr registers your prefix with the RADb as "Vultr Customer Route" or
something alike. That will make your asn/prefix pair work with most
providers. On the other hand, I met some providers completely ignores the
RADb and/or LoA, and do their own due diligence, I believe there are good
stories behind these practices.
Cheers,
Quan
On Wed, Jun 19, 2019 at 11:55 PM Toussaint OTTAVI <t.ottavi(a)bc-109.com>
wrote:
Le 19/06/2019 à 14:51, Brian Kantor a écrit :
--
Regards,
Quan Zhou
F2999657195657205828D56F35F9E5CDBD86324B
quanzhou822(a)gmail.com
I believe it depends mainly on whether your ISP
or its upstreams
are building their BGP filter lists from the routing object databases.
Many in Europe are. Most in the USA aren't. So whether it's needed
or not is dependent upon your network service provider's internal
policies.
Thank you for your answer. For now, we are using Vultr (via a VPS hosted
in Paris, and a GRE tunnel to Corsica). And we didn't notice any problem
about that.
Anyway, as I'm planning to expand my local data center capabilities, I'm
negociating with a new French operator, so that it can manage BGP
announcement for us, and deliver 44.x traffic directly on our fiber
router here in Ajaccio, for just a few bucks more.
Thank you for making us aware about that. I'll ask if they need this IRR
object or not.
73 de TK1BI
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net