Re: [44net] What is 44net?

Cory, First, let me say, feel free to have your own opinion. I just wanted to note that technical specifications speak contrary to your point of view. IP allocations follow a system specified in RFC2050; not because there's a majority consensus on the Internet that RIRs possess authority to issue IPs. The current DNS structure exists because of the specifications in RFCs 1034 and 1035, not because people simply agree. If they did not, or there was no global technical standard, there would be no guarantee of unique names and numbers, different networks may reach a different resource depending on their location (or not reach a resource whatsoever). Operating System developers would have no way of programming and configuring defaults for 'standards' such as IPv4, IPv6, DNS, DHCP, etc. 44.0.0.0/8 is, in fact, one network, as specified in RFC1166. Many folk have noted that they don't wish to have their allocation connect to others (or to the Internet for that matter); that's their option and their firewall. In the same token, we have others who come to the mailing list, asking how to get their allocations online. I personally see it as a success that I established connectivity to the rest of AMPRNet; and when I BGP in the future, I intend to maintain a 44GW that will be reachable via tunnel as well. Others are using thier allocations for purposes that would not have thier allocation connected to the rest of AMPRNet, only part time, or in some test/research capacity; that's OK too. Regardless, so long as they are not announcing thier allocation (with permission) from another AS, any Internet traffic destined to that subnet will travel to where 44.0.0.0/8 is announced - your argument that 44/8 is not one network fails on that one notion. Jann, You mentioned spoofing. This is the reason the encap file and route table should be kept private. Only other amateurs would know the location of the other endpoints. Also, thanks for the compliments regarding the aprscode tool. -KB3VWG