On Tue, Jul 16, 2013 at 9:45 PM, Lin Holcomb LHolcomb@clearqualitygroup.com wrote:
I just think the deal is we really should not be required to do something that we dont have as a project goal. If a BGP site wants to play in the amprgw world great if not then then no.
It is not necessary for the packets to route back and forth. It just adds an extra level of complexity that is not needed for our project goals of hosting radio projects that are fully rotatable to the internet.
Hmm, just checking, if I understand right:
Your project is about hosting radio projects that are fully routable to the Internet. You do not wish to be accessible from the rest of Amprnet, over amateur radio for example.
Why do you need to use 44/8 addresses then, if not for being available on the Amprnet?
I always thought that the cool thing about using 44/8 with BGP announcements would be that they'd 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.
- Hessu