Global reachability is not in conflict
with autonomy. Achieving both simultaneously just requires
careful design of HamWAN network services. If the HamWAN internet
feed drops off, the routing, DNS and other services need to
continue working. The first word in ASN is Autonomous after all.
:)
I consider NAT and Proxies as old crusty hacks from the age of
ISPs giving out just 1 IP/customer. It's time to put these ideas
to rest. IPv6 will do this on the commercial internet in the
coming years, and AMPRnet will allow us to do it immediately
here. For the cases where communication is to be restricted due
to user preference, we can push filtering rules to firewalls at
the edges of the network, and at the HamWAN <-> user site
interface. In short, firewalls: yes, nat+gateways: no.
If a user wants to make a service running on one of his servers
public, he just needs to push an ACL update to HamWAN and it'll be
opened up. No need to re-IP, update DNS, change NICs, whatever
else. And most importantly, it makes everyone equal. Your subnet
allocation has the same powers as mine. There is no special
ground to fight over, such as space on a public subnet, or access
to some officially sanctioned gateway servers that are allowed to
do special things.
If you want though, you can of course live in the world of private
IPs and NAT. Just configure your LAN router that way.
Complete freedom of configuration. This is the way the internet
should have evolved for geeks!
--Bart
On 2/13/2013 8:30 AM, Cory (NQ1E) wrote:
Unless I've misunderstood the point of this network
all together, there shouldn't be a case where we want the entire
network address space to be reachable from the global internet.
It's much more likely that the network will remain as
autonomous as possible and any connections to the internet will
be for connecting specific services through a gateway of some
sort.
A subnet of at least /23 (typical minimum for
global BGP announcements) should be reserved for the purpose
of being globally routable in the future, if/when HamWAN
decides to peer with one or more ISPs. An address in the /23
can be given to each service gateway for connecting to the
internet.
The rest of the 44-net allocation can be treated
as private address space, except that it's
essentially guaranteed not to cause conflicts with the
user-level networks since it's still globally unique.
_______________________________________________
PSDR mailing list
PSDR@hamwan.org
http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org