21 Feb
2020
21 Feb
'20
5:02 a.m.
Toussaint OTTAVI via 44Net <44net(a)mailman.ampr.org> writes:
Is an ARIN ASN number mandatory in such a situation ?
No. TK1 is not in the ARIN region. ARIN is for networks in North
America. In RIPE region you should normally have a RIPE-assigned ASN.
If not mandatory, would it be a good practice to have
one ?
It's not completely clear from your description of your situation. You
said that you speak iBGP with a provider. What ASN are you using for
this? What happens when you decide to change providers? How will that
transition work? Will you end up announcing your addresses with
inconsistent origins? That is to be avoided. Will you maintain direct
(maybe tunneled) peering relationships with other networks in AMPR
space?
It's important to think through what you want the routing policy to be
for your network, now and in the forseeable future. The point of an ASN
is basically to give an identifier to a network with a distinct routing
policy.
If so, would RIPE deliver ASN numbers to people or
companies that do
not own any IPv4 range (I am not the owner of my 44 subnet, ARDC just
grants me the right to announce it) ?
Yes but you have to justify it. This means explaining how your routing
policy is different from your upstream provider's. The questions above
will help you articulate that. The barrier is fairly low and essentially
designed to check that you know what you're doing and that what you're
doing makes sense. The procedure is similar in other regions.
For RIPE region, you will need to get a member (LIR) to ask for the ASN
on your behalf. Only LIRs can get number resources from RIPE. The LIR
might be but does not have to be your provider. There is a fee from
RIPE, I think it's something like EUR50/year. The LIR may or may not
charge a fee on top of this, depending on how friendly they are.
73s VE3HW