No, expectation is that people getting AMPR address space should have the subnet they're in registered with the portal. That includes non-connected hosts and /32s.
What we did was to extract from the portal all the allocations which were listed as an end-user or which had one of the three connection types checked, or which were in a subnet from the encap list, or which were in one of the BGP-routed subnets.
Do those you spotted fit any of those criteria?
If they do, we have a bug in our process and we'll have to fix it. Please let me know. - Brian
On Sat, Feb 06, 2016 at 11:36:55AM -0800, David Ranch wrote:
I looked over this list and recognized several IPs of local HAMs (including my IPs in the 44.4 class-B). Many of these entries are /32s and though they might not be actively routing their traffic to the Internet-enabled AMPR network today, it doesn't mean they won't be in the future. Is it the expectation with this move that if people request AMPR address space, they *must* have them pointing to a gateway that's operational *and* their IPs are pingable by some date? In my specific case, I have my address space active on RF but the local 44.4.10.1 gateway has been down for some time.
--David KI6ZHD