[FADCA] Use of ESATCOM for TCP/IP

[Doug Christ]

Hopefully everyone has got the "flames" out of their emails in reference to
SEDAN. Lets concentrate on what we do have available for us to use.

In John Fleming's email to me, he explained that bandwidth was limited and
if we hog too much that they will have to pull the plug on us during
emergencies. I think, as Chuck stated, that a multi-protocol stack at each
site is the proper approach. As of right now, anyone, through my local LAN
frequency, can connect to my BBS, FPAC or WinLink. My WinLink connects
directly to the T1 line here at my office. Why would I need to pump it
anywhere else on a normal basis?

 Do we need to have WinLink run through  ESATCOM?  I would hate to have
critical links reliant on a path that could be turned off on us.

As someone else stated, WinLink and Airmail is developing into a very robust
package. My EM Director (thirty years of experience) really likes the fact
that we can send and receive emails from anyone. Last year during a drill, I
sat up a laptop, TNC and HT at the scene and was sending emails back and
forth to the EM office.  I got a paper trail with time stamps that can be
printed out which makes all of the big cheeses happy.



Doug/KN4YT