From: Ralf Baechle DL5RB <ralf@linux-mips.org>
To: "Mike McCarthy, W1NR" <lists@w1nr.net>
Cc: Bernard Pidoux <bernard.pidoux@upmc.fr>,
linux-hams <linux-hams@vger.kernel.org>,
Ray Wells <vk2tv@exemail.com.au>,
Charlie k4gbb <k4gbb1@earthlink.net>,
Jerry DeLong <KD4YAL@tampabay.rr.com>, F1TE <f1te@f1te.org>,
f8arr <f8arr@f8arr.org>
Subject: Re: BUGs into libax25
Date: Mon, 2 Jun 2008 10:16:02 +0100 [thread overview]
Message-ID: <20080602091601.GC997@linux-mips.org> (raw)
In-Reply-To: <4843579E.8030003@w1nr.net>
On Sun, Jun 01, 2008 at 10:14:54PM -0400, Mike McCarthy, W1NR wrote:
> As I recall, there is a limit to the size of a callsign in the AX.25
> protocol specification. Will changing it create an incompatibility with
> standard TNC protocol stacks?
Afaik the currently only user of 6-letter callsigns aside of special
event stations are Australien foundation license which look like VK3FABC
so 4-letter suffix and those are not permitted to use packet radio anyway.
I was wondering if Swaziland which only has a half-series assignment is
possibly using 3+3 calls.
Anyway, the maximum callsign length in the AX.25 spec is 6 characters and
(I looked into that ...) there is no way of extending that without causing
large scale software breakage :-( It's almost like retrofitting 128-bit
addresses into IPv4 - it took a new protocol.
Ralf
next prev parent reply other threads:[~2008-06-02 9:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-01 22:26 BUGs into libax25 Bernard Pidoux
2008-06-02 2:14 ` Mike McCarthy, W1NR
2008-06-02 6:49 ` Robin Gilks
2008-06-02 9:16 ` Ralf Baechle DL5RB [this message]
2008-06-02 17:16 ` Dave Platt
2008-06-02 8:49 ` Ralf Baechle DL5RB
-- strict thread matches above, loose matches on Subject: below --
2008-06-02 9:36 DL5DI
2008-06-02 10:41 ` Matti Aarnio
2008-06-02 16:28 ` Bernard Pidoux
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=20080602091601.GC997@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=KD4YAL@tampabay.rr.com \
--cc=bernard.pidoux@upmc.fr \
--cc=f1te@f1te.org \
--cc=f8arr@f8arr.org \
--cc=k4gbb1@earthlink.net \
--cc=linux-hams@vger.kernel.org \
--cc=lists@w1nr.net \
--cc=vk2tv@exemail.com.au \
/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.