Explanation of RBBSIGS
During my foray Amateur Radio, I realized there is a huge gap in the ability of the amateur community to respond to a catastrophe.
The gap is many of the systems rely on the internet for repeater linking, call sign look ups, etc. This works fine as long as one key component is there: The internet.
But what to do when the internet isn't there? If one were to argue that NTS will take care of critical messages, it might. But it might not. You run up against operator fatigue, lack of operators, and pure time constraints.
Now, imagine this: An operator for the NTS system that never sleeps, quickly determines the fastest route for a message to go, and can interface with the internet to send out emails, look up critical website information, etc. We have just easily doubled the utility of the NTS significantly.
Also, packet modes do not apply well to the OSI model. The need for the infrastructure under the common communication systems is of up most importance, as well as the ability for equipment from one operator to the next will and can talk to each other, not caring for the information it's moving, just getting it to the right place.
Goals
- To design a protocol which can route packet information to the internet if need be, and to route NTS messages automatically.
- To be in collusion with the OSI networking model, to allow for vendor compatibility
- To have the protocol open in every way, so any person can pick up the pieces and help improve the system
Collaboration Tools
- This Wiki
- Mailing list (Not established yet)
