28 Jul
2021
28 Jul
'21
6:10 p.m.
Hello Janko, thanks for the comment! Please find my response below:
On 28 Jul 2021, at 12:56, Janko Mivšek via 44Net
<44net(a)mailman.ampr.org> wrote:
Hello everyone,
Rob PE1CHL via 44Net je 28. 07. 21 ob 11:33 napisal:
If you are mostly on the Intranet what you can do it keep your 44.150/16 prefix as is, and
don’t renumber. For the few hosts or ranges you need to support with Internet access you
can get allocated e.g. a /22 or /20, or whatever else you think is enough and then netmap
specific regions:
44.0.0.0/24 -> 44.150.17.0/24
44.0.1.0/28 -> 44.150.100.192/28
44.0.1.16/32 -> 44.150.0.1/32
If you think this is hard to maintain and more difficult, you can of course request a /16
in 44.0/10, or e.g. a /18 if you only use the first 1/4 of your space so far. We always
appreciate people that take only what they need plus a bit for future growth, but as
discussed earlier, we do not foresee problems of running out of IPv4 space in the near
future.
I hope this addresses your concerns!
Antonis
However, what we have here in the Netherlands is
a combination of the two. It is a radio
network, with additional internet tunnels to join areas without radio links between them
(at least
as an interim measure), but also it is internet routed and announced as a /16. We do
not
want to become an intranet!
I think that use case has to remain, and has to be detailed more in the proposal.
We in S5-Slovenia are also going the similar way as Netherlands - to use an 44.150/16
mostly as 'Intranet' but few of those IPs will be reachable from public Internet.
By BGP announcing the whole /16, then selectively filtering traffic on the firewall.
We see this way the simplest for both ARDC and our end users, who make their allocated
IPs publicly accessible by a simple click on the forthcoming web application.