Hi Robert.
>> Also note that the following is a perfectly valid callsign which
>> also doesn't fit in the AX.25 spcification:
>> PA/GM7GOD/MM
>> That is the callsign that *I* would have to use if operating from
>> a ship sailing in tidal waters claimed by the Netherlands.
> AFAIK, this callsign is *not* valid.
I've had reason to use it in compliance with my licence, so I can
confirm that it is indeed valid.
> If the waters are claimed by a country (xx mile zone), you are
> IN that country an *not* /MM. So it's either GM7GOD/MM *or*
> PA/GM7GOD/p or /m or whatever.
Under MOST (but not all) ham radio licences, the term "Maritime
Mobile" is defined as meaning that one is located on "tidal waters".
The UK licence terms and conditions booklets can be read online as
follows:
Q> Full: http://www.open.gov.uk/radiocom/br68.htm
Q> Novice: http://www.open.gov.uk/radiocom/br68anht.htm
Here's the relevant sections extracted from the former. The latter
differs only in section numbers.
1.11 Subject to clause 11, the Licencee shall operate the
station only:
:
d. while Maritime Mobile ("Maritime Mobile" means
located on any Vessel At Sea).
:
1.12 Interpretation:
:
d. "At Sea" means in the Tidal Waters or territorial
sea of the United Kingdom, or in international
waters.
:
l. "Tidal Water" means any part of the sea or a river
within the ebb and flow of the tide at ordinary
spring tides.
:
7 Identification:
:
7.4 When Mobile, the Licencee shall use the suffix '/M' and
when Maritime Mobile the suffix '/MM'.
That looks clear enough to me. One obvious example of this would be to
note that a ham sailing in the River Severn downstream of the Severn
Bridge is technically "At Sea" as the river is tidal at that point, so
would be required to operate /MM when doing so.
> It's pretty vague, but I remember some line requiring every
> valid callsign to follow this scheme: one letter or number, then
> one letter, then one number and following it 2 or 3 letters (or
> was is 1..3 letters?). Anyway, by this rule most US callsigns
> would be invalid (e.g. N9KBK), but would anybody care?
That's actually in the ITU regulations, or at least, the correct
specification is. I donn't have it to hand, but memory states that all
amateur callsigns are required to consist of:
1. The designated country prefix for the country and region in
question.
2. A numerical separator, consisting of (normally) one digit,
although two or more digits may be used fr special occasions.
3. One or more letters to distinguish the individual stations.
Let's analyse a few that I am aware of:
A. GM7GOD = GM 7 GOD - Complies with the rules.
B. W1AW = W 1 AW - Complies with the rules.
C. 2M1ABC = 2M 1 ABC - Complies with the rules.
D. A22XE = A2 2 XE - Complies with the rules.
E. GB50BOB = GB 50 BOB - Complies with the rules - special event
station that commemorated the 50th
anniversary of the Battle of Britain
in 1995.
F. JY1 = JY 1 ? - Does not comply with the rules !!!
As you can see, the majority of amateur callsigns do indeed comply
with the ITU regulations.
>> 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. However, it needs to be done in a manner compatible with the
>> current standard.
> Not only this are needs revision...
True...
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
