On Tue, Jul 16, 2013 at 10:59 PM, Lin Holcomb LHolcomb@clearqualitygroup.com wrote:
Well no it is not necessary as we are using the space alocated to ham radio for ham radio use these will be APs and clients that are operating on ham radio frequencies.
Ok, so wouldn't it be great if those clients could access services within other amprnet sites in addition to the Internet (assuming that some cool services would exist)? And that your local services could be accessed from other radio-based networks, not just from the rest of the Internet? For now, you'll need to have tunnel routing in addition to the BGP announcement to be able to have that. Without tunnel routing you only have access to the Internet and other BGP-enabled sites.
As for as use of the 44net I guess one could ask the same of you. If your project is not routable to the internet why not use 10/8? Answer on both counts because it is allocated for ham radio use.
Cut-n-pasting the answer from my previous email:
I always thought that the cool thing about using 44/8 with BGP announcements would be that [services in the network would] be accessible over both the normal Internet routing infrastructure *and* over radio from various Amprnet gateway sites. And that whenever a 44/8 source address would be seen at my service, I could tell that it would be originated by an amateur radio operator.
Interoperability with the Internet, thanks to the BGP announcements and not using 10/8, *and* at the same time, access to the same services from ham radio networks which are not allowed to access the Internet over ham radio due to local regulations. That'd be cool. Run a nice web service having a net-44 address, but when the visitor comes from within the amprnet with a net-44 address, allow extra features like being able to key a transmitter.
- Hessu