Hi Walter.
>>> To be honest, the AX.25 specification needs SERIOUS revision
>>> in this area, to allow for callsigns of any length or pattern
>>> to be used.
> No. It is IMO not necessary to put your whole callsign into the
> address fields.
Please advise how one would put the callsign GB50BOB into a packet
radio transceiver then? I have so far seen NO indication of how that
could be validly used, even though it was a valid callsign when it was
issued - which was back in 1990 if my memory is correct, so calls such
as that have been around for at least that long.
Other Here's the UK examples from my QSL card collection that can not
be used in the current AX.25 specification:
1. GB50BOB Special event station commemorating the 50th
anniversary of the Battle of Britain.
2. GB50CAN/AM Special event station commemorating the 50th
anniversary of the first flight of the Canberra
with the Royal Air Force. This is the ONLY valid
/AM callsign ever issued in the UK, and was done
live from an active RAF Canberra whilst the said
aeroplane was airborne.
3. GB50RAF Special event station commemorating the 50th
anniversary of the founding of the Royal Air
Force.
4. GB500KCA Special event station commemorating the 500th
anniversary of the founding of King's College,
University of Aberdeen, Scotland.
5. GB400MCA Special event station commemorating the 400th
anniversary of the founding of Marischal College,
University of Aberdeen, Scotland.
6. GB200USA Special event station commemorating the 200th
anniversary of the laying of Union Street,
Aberdeen, Scotland.
In each case, please advise how they can validly be used on packet
radio with the current AX.25 standard.
> Exactly as dl1nc wrote:
>> just using DL1NC and (just in case) sending a beacon every 10
>> minutes containing my complete callsign and QTH. If anybody
>> wants to know more, they can connect me and ask.
> it is nonsense to change a protocol for a minor "problem".
Since that does NOT work for ANY of the callsigns in question, I would
consider your argument to be irrelevant, and I would also consider the
problem to be rather more than minor...
> If you *really* need this "feature" (because your PTT *really*
> requested it literally) there is a simple solution. Just take as
> much callsign fields as you need for the long callsign, and
> protect it with the heard-flag. It may looks like:
> AX25: DC/->DB0IZ-11 v /W0RLI*, /MM, DB0IZ-9 <C C P>
> Of course you have to change your local soft; but all other
> existing nodes needs no changes.
> This looks like complete nonsense? Yes, it does. It _is_
> nonsense. A solution can't be more sensefull than the
> "problem" :->
Since the proposed solution just doesn't work, I see no reason to
describe it other than as nonsense, but the problem definately isn't
nonsense, as was quite evident prior to your missive !!!
Best wishes from Riley.
+----------------------------------------------------------------------+
| There is something frustrating about the quality and speed of Linux |
| development, ie., the quality is too high and the speed is too high, |
| in other words, I can implement this XXXX feature, but I bet someone |
| else has already done so and is just about to release their patch. |
+----------------------------------------------------------------------+
* ftp://ftp.MemAlpha.cx/pub/rhw/Linux
* http://www.MemAlpha.cx/kernel.versions.html
