[aprssig] APRS Message Callsign SPEC- Ambiguity

[spam8mybrain]

YAAC currently has this limitation. Should I remove it?
Andrew Pavlin, KA2DDOauthor of YAAC http://www.ka2ddo.org/ka2ddo/YAAC.html

-------- Original message --------
From: Robert Bruninga via aprssig <aprssig at tapr.org> 
Date: 04/25/2016  5:07 PM  (GMT-05:00) 
To: aprssig at tapr.org 
Subject: [aprssig] APRS Message Callsign SPEC- Ambiguity 

There is an unintended ambiguity in the APRS SPEC regarding the addressee in the APRS MESSAGE format. It was intended that the TOCALL of any transmitted message could be sent to ANY 9 character callsign field and this included mixed-case.  Although TNC’s have historically forced callsigns to UPEPRCASE only, this is only a limitation of TNC’s and was not intended to be a limitation of APRS. STATION names, OBJECT names, ITEM names were intended to be a general 9 character mixed case field in APRS padded to 9 with spaces. We just noticed that some radios do not allow sending an APRS message to a mixed case address. Unfortunately, the QIKCOM-2 satellite which does DTMF-to-Voice and APRS-to-voice has a special message address of “QIKCOMsay” for all messages it is expected to speak.  So some people will not be able to exercise this text-to-voice messaging capability. I wont make this mistake in any future satellite, but we are stuck with it.   SO, we might ought-to-identify all APRS radios and APRS clients that have this uppercase-only restriction on MESSAGE Callsigns. I can say the Kenwoods have it.  Others? See http://aprs.org/aprs11.html and specifically, see:See http://aprs.org/aprs11/aprs-names-and-spaces.txt Bob, WB4APR
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20160425/c1e3b579/attachment.html>