Wow... that's very bad news Thomas and I can only imagine the amount of work required that it will be to request new netblocks, coordination, and implement the technical changes on multiple layers (network, firewalls, documentation, etc).
To the larger topic, I don't understand how such a huge netblock could have been overlooked by the ARDC! It was specifically mentioned from one of the board members that this was a critical criteria for him to approve. This conflicting address space even publicly published on the AMPR web pages (even as of 7/19/19 @ 9:35am PST)! I have to imagine that there will be other amateur radio operators that use this 44.192.0.0 - 44.255.255.255 aka 44.192.0.0/10 address range on a non-registered basis that will be impacted. That's a risk those people took when not properly registering their uses BUT, in theory, their were protected from major changes by the ARDC with what I would assume would have been an open and public dialog before any changes were made.
A public discussion of this sale would have at least given those operators a chance to speak up or at least have some warning.
--David KI6ZHD
On 07/19/2019 12:46 AM, Thomas Osterried wrote:
I was assured that this block was not actively allocated to any hams. Is
it possible they're using it unofficially?
No. https://portal.ampr.org/networks.php
44.224.0.0 / 15 GERMANY
..with currently ~9500 assignments.
But that's no unresolvable problem. Just answering here to state that there is a large allocation and we do our best to move.
There's no direct bgp announcement for 44.224/15, and connectivity is done ampr-internal via ipip-mesh. Thus except for the dns reverse resolution, we expect no impact and can move step by step to 44.148/15.
The sold of the /10 netblock we are in is not a showstepper, it just makes (a lot of) work. But we also see the chance to configure things better during the renumbering.
vy 73,
- Thomas dl9sau IP coordination team DL
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net