This is a read-only archive. Find the latest Linux articles, documentation, and answers at the new Linux.com!

Linux.com

Feature

Concerned hams question amateur radio choice of closed code and controller

By Jay Lyman on June 07, 2004 (8:00:00 AM)

Share    Print    Comments   

Amateur emergency radio is all about helping out, quickly, dependably, and without charging fees, in a time of need such as terrorist incidents and natural disasters. Now some ham radio operators, who have evolved from a network of high-tech hobbyists to a Federal Communications Commission-regulated radio service, are worried that a recommendation for proprietary software and hardware for the Amateur Radio Emergency Service (ARES) may close out communications and communicators.

An American Radio Relay League (ARRL) ad-hoc committee on ARES has recommended the adoption of two proprietary technologies -- Winlink 2000 software to bridge radio frequency and Internet connectivity and the Pactor II and III controllers -- as standard for the national public service and emergency radio organization.

The ARES Communications Ad Hoc Committee (ARESCOM) argues that to provide a means of quickly moving high volumes of radio email traffic across the nation, the Winlink 2000 system (WL2K) and Pactor II/III is the most feasible and can be combined with existing resources or deployed as new.

"The WL2K system provides for the movement of radio email with multiple addressees, multiple copies, blind copies, and encoded binary attachments between all client email applications," said the ARESCOM recommendation. "Compression is used to conserve valuable spectrum."

ARESCOM claims the move is an efficient use of spectrum that will allow more simultaneous access and provide room for the growth of data rates to better align with wired networks and future commercial wireless networks. The main idea behind the recommendation is to digitally complement existing voice communication.

"It is not meant to be a replacement for such longstanding and proven services," ARESCOM's documentation says, referring to current technologies of ARES and the National Traffic System (NTS), which is used to systemize amateur radio traffic.

However, some higher-up hams say that while the committee may not be going entirely pro-proprietary -- or at least they deeply hope not -- the ARESCOM committee does not realize the problems of proprietary software and hardware. The individuals, who have asked to remain anonymous to avoid loss of access and influence, say amateur radio and open source are aligned in community spirit, as well as technical symmetry.

After the committee recommendation, hams looking into the matter have have reportedly uncovered limitations to only NTS and ARES communications in the Winlink documentation, limiting ham freedom. There are also concerns about the price of the personal mailbox station (PMBO) with the recommended hardware and software, which takes the average price of a ham setup from a few hundred dollars up to around $3,000, according to one ham who is concerned.

Another issue with the recommendation from ARESCOM, which will consider finalization of the move at its board of directors meeting in July, is that ARES communications are not normally conducted through formal messages, instead relying on voice communication coming into an Emergency Operations Center (EOC), which is better served with a "chat" mode and phone patching.

"Most of the local EOC emergency coordinators don't feel that Winlink will be of much benefit," says a source with ARRL.

A third issue involves the manufacturer of the Pactor II and III units. Some question whether it can keep up with hardware demand, and wonder what the results would be if it exits from the business or existence.

"These questions need to be answered and considered by the committee members, and the ARRL directors need good answers before they proceed," the source says.

Yet another issue arises from the fact that -- as is often the case with proprietary solutions and people's positions -- two of the ARRL committee members are also on the Winlink Development Team.

"The ARRL ARESCOM is a work-in-process and I have been asked not to provide details until they have been made officially public by the ARRL," said the ARRL's Steve Waterman, who is also a Winlink 2000 developer. "I can tell you that the objective is meant to provide seamless, end-to-end email from the desktops of the offices in the served agencies with no invasive software behind the agency firewall. It is meant to do this using the existing email agents on the desktops.

"Further the objective is to accomplish this with no Internet available," Waterman added. "Incidentally, Pactor plays a minor role, if any at all, in this scenario."

The ARESCOM committee did leave the door cracked open with its reference to Winlink's binary B2F protocol. B2F purportedly delivers 44 percent compression and "excellent error correction," making it a good means to link radio and Internet communications. A FAQ document notes that "Nothing has yet been discovered that is more robust, and should it be found, it will be used. Likewise, should a more robust or efficient mode be discovered to wrap around the B2F protocol, we will certainly be using it."

Hams with open source sympathies have put out a call for papers or proposals on an alternative, preferably open source and inexpensive.

"Certainly amateur radio would welcome any and all open source [ideas]; we do 802.11a/b/g and are really interested in high-speed, robust data on HF as well as 56 Kbps and higher data on VHF and UHF frequencies," says an ARRL source.

Waterman said proposed solutions should go to Dick Mondro, vice director for the ARRL Great Lakes Division and chairman of ARESCOM.

Share    Print    Comments   

Comments

on Concerned hams question amateur radio choice of closed code and controller

Note: Comments are owned by the poster. We are not responsible for their content.

Is it possible...

Posted by: The Spoonman on June 07, 2004 10:03 PM
...I mean there IS a chance...however slim...that the proprietary software is...dare I say it?...BETTER?



No mention is made in the article about which open source alternatives exist, nor a comparison of the differences between said alternatives and the proposed solutions. That would be helpful information to make this article useful. Also, it would be useful to know if the comittee reviewed any open source alternatives before making their decision, as well as their reasons for rejecting them. It could well be that the feature-set delta between the open source alternatives and the proprietary software was large enough to justify paying for the software. Also, how often are these decisions going to be reviewed? Unless they're going to use this software until the end of time, then alternatives have time to make up any deficiencies.

#

Specify Interface, Not Applications

Posted by: Anonymous Coward on June 08, 2004 02:05 AM
As long as the interface protocol is open and the comittee uses laguage like "stations should use the winlink protocol", or "stations should use hardware and software compatilble with winlink and pactor" then this shouldn't be a problem.



Looks like AirMail users are capable of retreiving email from xfbb under certain conditions:



Here's the initial post with the problem:



http://cbgw.remsnet.de/cgi-bin/dpcmd?R%20FBB%2042<nobr> <wbr></nobr>



Here's the post with the solution:



http://cbgw.remsnet.de/cgi-bin/dpcmd?R%20FBB%2043<nobr> <wbr></nobr>



It also looks like a program called MailGW can interface smtp and fbb:



http://radio.linux.org.au/pkgdetail.phtml?sectpat<nobr>=<wbr></nobr> All&ordpat=title&descpat=&pkgid=86



These links should be a good starting point for building a Linux based version of winlink.



73

#

Re:Specify Interface, Not Applications

Posted by: Anonymous Coward on June 08, 2004 09:25 AM
As long as the software interfaces and hardware specifications are available, then thats great.

What Linux/OpenSource/non-proprietary advocates worry about is a closed/proprietary interface being adopted in such a crucial place as the low-level message handling infrastructure of a service such as ARES.

Is the B2F compression algorythm freely implementable, or do Linux/OSS developers have to license it from Winlink or others?

Can anyone build Pactor II/III compatible hardware, or are those specifications closed, or otherwise burdened with restrictive licensing.

Public services, from freely available/open technologies allow everyone to contribute, not just those who follow some inflexibly designed agenda designed to marketize then prey upon an otherwise freely provided service.

Beware any specification based on a named piece of hardware or software application!

If you can't freely create your own version of something from the specification, then you should seriously question whether or not that specification is worth adopting.

Then again, Linux folks are used to this sort of abuse from closed vendor moves... and know how to undermine them.

As your post shows, there are already alternatives that could be built into a viable alternative.

#

B2F Compression

Posted by: Anonymous Coward on June 08, 2004 10:41 AM
Wouldn't the B2F Compression protocol have to be published in order to avoid violating the FCC rules against using secret codes or ciphers on amateur radio frequencies?

#

Expensive Installation

Posted by: Anonymous Coward on July 22, 2004 12:09 AM
Since you must use a computer hooked up to your radio, why pay $$$$$ for the PTCII modems? Also, why should I have a pc running at 250mhz running WinME (groan..), or WinXP (slowwwww)...I can easily have Linux running with Fluxbox that can zing along and do everything that they want done without buying the modem and M$ OS. Don't get this at all.

#

This story has been archived. Comments can no longer be posted.



 
Tableless layout Validate XHTML 1.0 Strict Validate CSS Powered by Xaraya