All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert Steinhäußer" <robert@steinhaeusser.com>
To: linux-hams@vger.kernel.org
Subject: Re: callsign limit
Date: Wed, 31 May 2006 15:15:00 +0200	[thread overview]
Message-ID: <20060531131500.GA16753@hugh.borg> (raw)
In-Reply-To: <1149077523.447d881344509@mgtmail.com>

[-- Attachment #1: Type: text/plain, Size: 1283 bytes --]

Hi! 

We're no longer on a linux subject (linux-hams), but I suppose enough
here are interested.

On Wed, May 31, 2006 at 12:12:03PM +0000, IT3 Stuart Blake Tener wrote:
> Though only Canada has started issuing 2x4's as far as I know.
> 
> While special event stations (even for Packet) are able to get 2x1 callsigns in
> the United States.

2x1 in the US aren't only for special events, see KA9Q etc. But I
haven't seen other countries issuing 2x1 or 1xN (e.g. N9KBK) in the
past. That seems to have changed recently.

> Jordon also issued 1x1 calls too.

Do you mean JY1 etc.? Using this terminology that would be a 2x0 ;-)

These special calls are becoming quite common in many countries now,
also here in Germany, from 2x1s for contest/clubstations (e.g. DR6A)
to the short-time stations during the soccer World Cup with calls like
DR2006N and DQ2006J (which would be "2x1" as well).

Perhaps somebody could check which syntax is valid now? I don't know
where to look. Was there any statement made on how calls longer than
6 chars are to be used on packet? Perhaps just use a different ID 
(which one?) and additionally set a beacon with the correct call in the
data part? How do other modes (was it AMTOR?) handle this?

73, Robert
DL1NC/N9KBK


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2006-05-31 13:15 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-31 12:12 callsign limit IT3 Stuart Blake Tener
2006-05-31 12:41 ` Chuck Hast
2006-05-31 13:15 ` Robert Steinhäußer [this message]
2006-05-31 14:57   ` Bob Nielsen
  -- strict thread matches above, loose matches on Subject: below --
2006-05-31  9:27 stephen
2006-05-31  9:37 ` Hamish Moffatt
2006-05-31 11:03   ` Chuck Hast
2006-05-31 11:19     ` Hamish Moffatt
2006-06-01  1:40       ` Ralf Baechle DL5RB
2006-06-01 12:04         ` David D. Hagood
2006-06-01 13:25           ` Ralf Baechle DL5RB
2006-06-01 14:31           ` Curt, WE7U
2006-06-01 15:08             ` Ralf Baechle DL5RB
2006-06-01 15:15               ` Curt, WE7U
2006-06-01 18:52                 ` Ralf Baechle DL5RB
2006-06-01 19:33                   ` Thomas Sailer
2006-06-02  2:51               ` Kevin Dawson
2006-06-02  3:47                 ` Hamish Moffatt
2006-05-31 13:05     ` Geoff Blake
2006-06-01 10:34   ` stephen
2006-06-01 10:54     ` Chuck Hast
2006-06-01 13:47       ` Hamish Moffatt
2006-06-01 14:00         ` Geoff Blake
2006-05-31 13:02 ` Matti Aarnio
2006-05-31 13:12   ` Thomas Sailer
2006-05-31 14:02     ` Matti Aarnio

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060531131500.GA16753@hugh.borg \
    --to=robert@steinhaeusser.com \
    --cc=linux-hams@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.