7 Apr
2021
7 Apr
'21
12:46 a.m.
Chris, what's the use of this?
Now, instead of one invalid subnet (44.128.0.0/16) that we should
ignore, we get three of them?
The new "documentation" subnet has exactly the same issues like the ones
described for the initial one, nothing is solved.
Worse, one can not even exemplify a simple clearly visible /16 /24
sub-netting with clear numbers using 44.128.252.0/22, for people to
understand netmasks.
And all of this just because some worry the address space will run out
sometimes in the future, so we get to subnet it further? C'mon...
Either choose one OUTSIDE the address space, or leave it as it is.
In the mean time: Everybody please update your RIP filters to include
44.128.252.0/22 as well. And your blackhole routes too. Oh, and some
scripts and daemons maybe....
Yes, and instead of one iptables rule, you need 3 of them.
At least make it half/half: 44.128.0.0/17 for documentation,
44.128.128.0/17 for those worrying data could show up in some readme and
magically trash their tests.
Marius, YO2LOJ
On 06/04/2021 20:26, G1FEF via 44Net wrote:
Ok, to avoid any confusion Jann (chair of the TAC) and
I have had a chat about this today. We agreed that it would make sense to reserve a small
part of the address space specifically for documentation relating to 44net. I have updated
the Portal to reflect this:
44.128.0.0/17
This is reserved for testing. Anyone may use this address space for private testing
purposes, it will never be allocated to anyone, it will never be advertised on the
Internet at large.
44.128.128.0/17
This is reserved for future testing. It also will never be allocated to anyone, nor will
it ever be advertised on the Internet. Within this address space we have allocated:
44.128.252.0/22
This is reserved specifically for documentation.
Anyone implementing filtering may safely route 44.128.0.0/16 to /dev/null
73,
Chris
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net