From: Jon Roland <jroland@linux-migration.net>
To: b.a.t.m.a.n@lists.open-mesh.net
Subject: [B.A.T.M.A.N.] Digital Comm on Version of Mesh Potato
Date: Thu, 03 Dec 2009 20:57:00 -0600 [thread overview]
Message-ID: <4B187A7C.3020200@linux-migration.net> (raw)
Mesh networking for analog phones is a good concept, but to be broadly
useful it also needs to support digital communications, with computers
or smart phones as the client devices. It would seem what while
developing them, you ought to go ahead and enable them for broader uses.
My concern is emergency disaster situations, and here in the U.S., as
elsewhere, emergency response will require the conveyance of data as
well as voice. I have been involved in some disasters and data
communications proved to actually be more important than voice
communication. From maps to inventories, logistic control to medical
imaging, ground-penetrating radar to biometric identification. The list
goes on. We can use CB or handheld shortwave for voice. Data is the main
need.
-- Jon
-------------------------------------------------------------------
Constitution Society 2900 W Anderson Ln C-200-322, Austin, TX 78757
512/299-5001 www.constitution.org jon.roland@constitution.org
-------------------------------------------------------------------
--
----------------------------------------------------------------------
Linux Migration Network 2900 W Anderson Ln C-200-322, Austin, TX 78757
512/299-5001 www.linux-migration.net jroland@linux-migration.net
----------------------------------------------------------------------
reply other threads:[~2009-12-04 2:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B187A7C.3020200@linux-migration.net \
--to=jroland@linux-migration.net \
--cc=b.a.t.m.a.n@lists.open-mesh.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox