Re: [HamWAN PSDR] "How To Integrate HamWAN Into Your EOC ".
Re-directing email with questions to the mailing list. --Bart On 03/12/2014 03:43 AM, Keith wrote:
BART,
I see the need for a policy that would provide node information that will be needed by first responders and others.
I want guarantee that any information will be used appropriately and for the best interest of the Emergency and Amateur Radio community.
First I am not putting any node information up on the web for general public access.
However, I would like to put up a site with the nodes that is accessible by the people that should have this information for planning.
Different groups need different information for example, the short list below is to help define the need.
All nodes available to the ARES/RACES community. Trustee nodes and connected nodes available to trustees Open Mesh nodes would be visible to Hams.
So my goal with this particular question is to find out what groups will have a use for such information and how to provide it. Providing auxiliary information such as the contact person, trustee, etc. To provide a location to support emergency connections.
The general goal is to form a 'good practices' policy for this type of information. I could draw a loose parallel to Domain Server management with the addition that geographic information is needed.
So I would like for BRATS and myself to work out a policy that would provide the information that will be needed in an emergency for others to use the facilities.
Keith KB3TCB
I have attached my provisional map of the BCWARN system.
On 3/4/2014 9:57 PM, Bart Kus wrote:
For any of your left-over questions, please address them to the mailing list. I need to focus on other things and cannot keep going with this thread.
--Bart
How apropo given last night's meeting topic. :) On Wed, Mar 12, 2014 at 1:30 PM, Bart Kus <me@bartk.us> wrote:
Re-directing email with questions to the mailing list.
--Bart
On 03/12/2014 03:43 AM, Keith wrote:
BART,
I see the need for a policy that would provide node information that will be needed by first responders and others.
I want guarantee that any information will be used appropriately and for the best interest of the Emergency and Amateur Radio community.
First I am not putting any node information up on the web for general public access.
However, I would like to put up a site with the nodes that is accessible by the people that should have this information for planning.
Different groups need different information for example, the short list below is to help define the need.
All nodes available to the ARES/RACES community. Trustee nodes and connected nodes available to trustees Open Mesh nodes would be visible to Hams.
So my goal with this particular question is to find out what groups will have a use for such information and how to provide it. Providing auxiliary information such as the contact person, trustee, etc. To provide a location to support emergency connections.
The general goal is to form a 'good practices' policy for this type of information. I could draw a loose parallel to Domain Server management with the addition that geographic information is needed.
So I would like for BRATS and myself to work out a policy that would provide the information that will be needed in an emergency for others to use the facilities.
Keith KB3TCB
I have attached my provisional map of the BCWARN system.
On 3/4/2014 9:57 PM, Bart Kus wrote:
For any of your left-over questions, please address them to the mailing list. I need to focus on other things and cannot keep going with this thread.
--Bart
_______________________________________________ PSDR mailing list PSDR@hamwan.org http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org
-- Benjamin
participants (2)
-
Bart Kus -
Benjamin Krueger