GhostNet 1.5, page 36

36 Expectation Management: Even considering the widespread implementation of the GhostNet plan, it’s astronomically unlikely for anyone to actually make contact with another human being via the use of these shared frequencies. Contact may be made in more populated areas, but the utility and usefulness of such link-ups is debatable. Nevertheless, having a freq or two stored in a radio’s codeplug may provide piece of mind for those who want to have some sort of last-ditch plan, even if it’s very unlikely to be helpful. However, care must be taken to not rely on these specific procedures to the point of gaining a false sense of security. What would be extraordinarily ill-advised would be for someone to program in these freqs, and think they’re all set with a solid plan that needs no additional work. This is the reasoning as to why these freqs are included in the GhostNet only hesitantly, and with much warning. This LoS plan was created solely for those who only have a Baofeng or other low-cost handheld radio. These tools can provide a lot of capability for some people in certain situations, however the vulnerabilities and trade-offs should be known, planned for, and mitigated wherever and whenever possible. The digital portions of this plan serve to help users move towards these ends, and encourage the adoption of digital radio use on a more widespread scale. Line-of-Sight Concerns Meshtastic Integration While Meshtastic can be a helpful tool for many, it's best served when used by small groups that are within Line-of-Sight of each other. Using Meshtastic in this role does not make use of most of it's benefits. However, there may be some use in establishing a dedicated Meshtastic channel for those who already use Meshtastic. Meshtastic itself makes use of what is essentially a national calling frequency (i.e. - the default "Long Fast" channel), so the implementation of such for GhostNet users may be of some benefit as well. At minimum, it doesn't take much effort to add to a user's channel list, so even if it's never used it won't be a burden. This integration also lays the groundwork for additional features and support as the Meshtastic project develops. Expediency vs Security...and Risk Management As with most ideas in the world of communications, the balance of security versus capability must be considered for each specific situation. It is very hard to create a communications plan with both ideas in mind. For the most part, many communications plans are either based on military doctrine, or emergency management doctrine, with very little crossover between the two communities on even the most basic features that are needed. Almost all military doctrine, for instance, assumes that most radio communica- tions will be encrypted by default...non-encrypted comms are usually not even discussed at great length. On the other hand, encrypted comms are not only rare to see in the world of emergency management, but also illegal for non-professionals to use in many cases (such as in the world of amateur radio). So, the conundrum becomes apparent...relying on emergency management comms doctrine in a warzone might summon an artillery strike within 60 seconds of transmitting, but on the other hand using encrypted comms during a widespread hurricane disaster response might also not be super effective. Everything is a balance, and every risk that appears, has a mitigation technique. The use of radios in war relies on the Emissions Control (EMCON) doctrine to ensure that comms can occur, and be as safe as possible considering the overall risk. Disaster communications usually require more open communication techniques, but also may consider the need for increased security in some situations. Sometimes, even a di- saster response is not entirely a permissive environment, and thus transmitting one's Personally Identifiable Information (PII) over the airwaves for anyone to see is probably not the best idea in all circumstances. Though very challenging to incorporate into real-world practice and use, the entire GhostNet idea intends to bridge this unique gap: To allow for a common standard to be adopted by those who need it during peace- time conditions, but also leave the door open for more security-conscious use if it's needed at some point. The VHF/UHF options provided are intended to achieve this effect, albeit due to the nature of LoS comms, the practicality of such may be questionable over long distances. Where this plan may be of some value is the expediency that comes with a predetermined plan. In short, a group of people can rapidly get together, and already have their radios speaking the same language. When seconds count, this will save precious time if/when it's needed. When you need to grab a rucksack and go at a moment's notice, having the ability to not worry about what frequencies to use will be helpful. Since this plan isn't too complicated, and backwards compatible with most radios that are in common use, it is also easy to incorporate comms with a variety of users. This allows for a rapid, ad hoc, comms hierarchy to stand up really quickly. For example, a team leader/radioman can have a digital radio to work with other teams, and individual team members can still use their Baofengs amongst themselves as needed.