It seems to me that with the creation of this new 44.190.0.0/16 network, there is now a new workflow. If I'm incorrect, could someone please set me strait?
- If a new HAM desires to get and advertise an AMPR prefix via BGP w/o any IPIP encaps support, they should request a 44.190/16 block. If this is correct, the AMPR portal should be enhanced to send this request off to whomever is this new 44.190/16 coordinator. Until this portal changes occur, who should we forward the AMPR allocation requests to?
- If a new HAM doesn't intend to advertise their block via BGP, they should request a netblock via the current IP coordinators workflow
--David KI6ZHD
On 05/10/2018 10:13 AM, Rob Janssen wrote:
Each 44.190.x.0/24 subnet arranges its own BGP advertising, so there isn't just one point. They are spread all over the world. - Brian
Note that due to this, the approximate location in IP geolocation databases has to be set for each of the /24 subnets. The default location for 44.0.0.0/8 is San Diego, California, USA. I have set the location for 44.137.0.0/16 to Amsterdam, Netherlands and other country ip coordinators have done similar for their countries. And of course an individual amateur can set a more accurate location for their smaller subnet.
It comes into play for some services that use IP location aware DNS to direct users to a geographically closest (and hopefully this translates to closest in network topology) service. With all the 44.190.0.0/16 networks located in San Diego this of course isn't going to work. Echolink is such a service that users IP geolocation.
You can enter an address from your subnet in lookup services like this: https://www.iplocation.net/
It shows what some of the more important services return for your location. And when clicking on the link for each service it is usually easy to submit location data for a subnet to that service provider.
Rob