The issue is not that it is readily decodable, it is more along the line of having a publicly documented protocol. One might wonder why the DSTAR protocol is published at the ARRL site(http://www.arrl.org/FandES/field/regulations/techchar/ ). It is my understanding that the protocol is published to make sure that it fits FCC 97.309(a)(4).
Ed WA4YIH From: dstar_digital@yahoogroups.com [mailto:dstar_digi...@yahoogroups.com] On Behalf Of k7ve Sent: Tuesday, May 19, 2009 6:56 PM To: dstar_digital@yahoogroups.com Subject: [DSTAR_DIGITAL] U.S. Only - Re: Tactical Call indication --- In dstar_digital@yahoogroups.com<mailto:dstar_digital%40yahoogroups.com>, "Woodrick, Ed" <ewoodr...@...> wrote: > If you stick to the specifics of the protocol, then if you put something > besides your callsign in the field, then it wouldn't be in accordance with > the protocol. If it isn't in accordance with the protocol, then you will need > to follow the requirements of utilization of a non-published protocol. This > would require, among other things, that the station identification be done in > a standard protocol such as FM or CW. (For US rules) > > So I guess if you want to get down to nitpicking, if the callsign is not in > the field then you need to make sure to switch your radio to FM and identify > appropriately. > > Ed WA4YIH Though I am of the school that the "MY" field should contain one's own callsign, I don't think your argument about having to ID using FM or CW is correct. The "standard protocol" includes AMBE encoded voice, which can be readily deciphered by anyone with a D-STAR radio and giving a "voice" ID over AMBE, I believe, would constitute a legal identification within the US rules. -- John, K7VE [Non-text portions of this message have been removed]
