Re: [44net] routable or private?

I would like to chime in here with a couple points. 1. Not all 44-net traffic is routed over the air. This address space is indeed reserved for the amateur radio community, but that doesn't mean that it's routed over the air and is necessarily subject to the content rules the FCC has laid out for our wireless communications. In such situations, it makes little sense to restrict to only 44/8 space unless that is the only community you're serving. As bill said, there are certainly things that would be of interest to the outside world, and are part of the ham community so shouldn't be restricted. 2. For the traffic that does go over the air, consider the case of a repeater operator/owner, and say that repeater has a phone patch. The FCC has laid out rules that the operator of the repeater is not liable for the content of other's transmissions, provided they take reasonable corrective action to prevent abuse. Specifically in the case of a phone patch, in most cases, this means configuring it for only outgoing calls, however, it is permissible to receive a phone call from the outside provided it is expected by a licensed operator. If we apply this to IP space, this would translate in my mind to generally firewalling incoming traffic, allowing for exceptions in the firewall rules as desired for ham services that are compatible with the wireless nature of the path, and in my opinion, I'd prefer to not restrict other licensed users of a network. They're responsible for their own transmissions, and if it comes to be a problem, as in the case of a repeater, steps can be tak! en to limit or stop the abuse. So, in agreement with Bill, it's going to very much depend on your situation, as is the case with all internet connected systems, you need to protect it in the way that makes most sense for your applications of it. Nigel K7NVH On Apr 1, 2014, at 5:23 PM, Paula <g8pzt(a)blueyonder.co.uk> wrote: