22 Feb
2020
22 Feb
'20
12:06 p.m.
Hi,
Just to clarify on the fees, the RIPE NCC charges nothing for ASN
sponsorships however the LIR may often charge administrative and
maintenance fees.
- Cynthia
On Fri, Feb 21, 2020 at 12:41 PM Toussaint OTTAVI via 44Net <
44net(a)mailman.ampr.org> wrote:
Hi William, and many thanks for your detailed answer.
Le 21/02/2020 à 12:02, William Waites a écrit :
Currently, we are using a private ASN given by Vultr. They have a good
howto. Several of us are using Vultr services, both for the ease of use
and tiny prices :
https://www.vultr.com/docs/configuring-bgp-on-vultr
The howto says I can use a public ASN if I have one.
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.
Sorry for the confusion. RIPE is our contact in Europe, of course.
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.
That's still not decided yet :-) The idea would be to have redundant
announcement with two providers, so that our network still works in case
of Vultr failure (this morning, Paris data center has been down during
an hour). I planned to use a French telco operator to which I am in
contact for my business. The guy is a friend, and he'll be able to
manage BGP HAM stuff for just a few bucks more.
Anyway, it was still unclear how I could achieve redundant BGP routing
in such a setup (Vultr + business telco). And I didn't have time to
investigate yet. But you gave me a nice clue :-)
Will you maintain direct
(maybe tunneled) peering relationships with other networks in AMPR
space?
For now, we are using BGP only for our 44.190 subnet (things that need
to be connected to public Internet, such as Echolink, XLX, etc...).
According to DG8NGN specs, this subnet has been designed to be routed
only to Internet.
We also have "pure" hamnet subnets in 44.168. It's a Work in Progress...
Final routing policy is still undefined for now. But I think I may
follow DG8NGN advice : use only HamNet routing rules (iBGP with European
HamNet, and IP-IP tunnels to the rest of the world). I do not see any
need to announce those on public Internet. And this may/will cause
routing problems with AMPRNet / HamNet partners.
Then, keeping things separated, and use Internet BGP only for 44.190,
may be the solution.
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.
That's what I missed. And that's why I need a public ASN.
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.
Thank you. I thought it was required to be a LIR to get an ASN. Becoming
a LIR was not an option for me, because it's over-priced, and I
absolutely do not need it for my business. But $50/year is something I
can afford, and offer to my radio-club :-)
Thank you again for your detailed explanation.
73 de TK1BI
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net