Hey Brian,
So I logged into the portal and I see:
--------------------------------------------------------------------- Network Type Description Actions 44.4.10.40/32 user KI6ZHD Edit | Release 44.4.128.0/22 user KJ6VU Edit | Release
Pending Requests
You have no pending requests. ---------------------------------------------------------------------
The top entry is seemingly incomplete as I've been previously granted and DNS resolution confirms I have (had?):
$ host 44.4.10.39 39.10.4.44.in-addr.arpa domain name pointer ki6zhd-5.ampr.org. <------- This is what I actively use on RF $ host 44.4.10.40 40.10.4.44.in-addr.arpa domain name pointer ki6zhd.ampr.org. <------- for special projects right now $ host 44.4.10.41 41.10.4.44.in-addr.arpa domain name pointer ki6zhd-dgw.ampr.org. <--------- This is what I use when the IPIP tunnel is up
Are these missing entries something I missed or something my local coordinator missed? Depending on your answer here, I imagine this will be the same reasoning for my other fellow HAMs being on the "to-be-deleted.txt" list.
Btw, the second entry is for the local HAM club that I've been working on their IP segment in their behalf.
--David
On 02/06/2016 12:41 PM, Brian Kantor wrote:
(Please trim inclusions from previous messages) _______________________________________________ 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