From: Ralf Baechle DL5RB <ralf@linux-mips.org>
To: "Curt, WE7U" <archer@eskimo.com>
Cc: "David D. Hagood" <wowbagger@sktc.net>, linux-hams@vger.kernel.org
Subject: Re: callsign limit
Date: Thu, 1 Jun 2006 16:08:54 +0100 [thread overview]
Message-ID: <20060601150854.GA19527@linux-mips.org> (raw)
In-Reply-To: <Pine.SUN.4.58.0606010723410.10879@eskimo.com>
On Thu, Jun 01, 2006 at 07:31:54AM -0700, Curt, WE7U wrote:
> Are we still talking about AX.25 here? This is from the AX.25
> version 2.0 spec, published in 1984:
May it rest in peace. V2.2 dated 1997 is the latest.
> "The characters of the call sign should be standard seven-bit ASCII
> (upper case only) placed in the leftmost seven bits of the octet to
> make room for the address extension bit. If the call sign contains
> fewer than six characters, it should be padded with ASCII spaces
> between the last call sign character and the SSID octet."
>
> So... We only have 7 bits to play with, not 8. I suspect that we
> could still play some games though and compress the callsign into
> the 42 bits available, plus up to 4 more bits for the SSID if we
> wanted to mess with that. Many people like to have more than one
> station on the same frequency though (as I do with APRS), so messing
> with the SSID too much would be problematic. Perhaps one bit could
> be borrowed from there leaving 8 possible SSID's per station instead
> of 16?
>
> There are also two reserved bits in the SSID byte. I didn't check
> the later version 2.2 spec (which isn't implemented anywhere as far
> as I know) to see if they decided to use those two bits. There may
> be some other reserved bits further down the header to use as well.
DAMA packs some information into the the unused bits of the SSID field.
73 de DL5RB op Ralf
--
Loc. JN47BS / CQ 14 / ITU 28 / DOK A21
next prev parent reply other threads:[~2006-06-01 15:08 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-31 9:27 callsign limit 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2006-05-31 12:12 IT3 Stuart Blake Tener
2006-05-31 12:41 ` Chuck Hast
2006-05-31 13:15 ` Robert Steinhäußer
2006-05-31 14:57 ` Bob Nielsen
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=20060601150854.GA19527@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=archer@eskimo.com \
--cc=linux-hams@vger.kernel.org \
--cc=wowbagger@sktc.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox