From: Matti Aarnio <matti.aarnio@zmailer.org>
To: DL5DI <dl5di@prgm.org>
Cc: linux-hams@vger.kernel.org
Subject: Re: BUGs into libax25
Date: Mon, 2 Jun 2008 13:41:49 +0300 [thread overview]
Message-ID: <20080602104149.GS3700@mea-ext.zmailer.org> (raw)
In-Reply-To: <1K36Sn-0OkOu00@fwd26.aul.t-online.de>
On Mon, Jun 02, 2008 at 11:36:25AM +0200, DL5DI wrote:
> This special event station callsign that we sometimes find like
> DQ2008ANYEVENT will never work in packet radio.
> The protocol header of ax25 frames only allows 6 bytes of callsign and 1
> halfbyte of SSID.
> Not only for the destiantion, also for all digipeaters inbetween.
> We would need to change the whole protocol and all digipeaters and stations
> using it worldwide to get that covered.
> I expect that packet radio will be dead before that happens. :-)
Arbitrary long callsigns... Only OSI stack can handle that, and even it
has some upper limits on address lengths.
On IPv6 the addresses are 16 bytes long, and low 8 bytes (64 bits) of them
are reserved for "link local" use. Considering that.. one can encode
any callsign with 38 characters, add couple codes for things like
"no character here", and "next is ssid", that would be 40 codes.
Using 6 bits per character one could encode 10 characters + 4 bits on IPv6-
address "local half". With arithmetic encoding (see APRS mic-e) maybe
17 code bytes.
Would that be AX.25 ? Definitely not. That would be IPv6.
On IPv6 the basic assumption is that link local area is /64 size slice,
and thus "AX.25 space" would be something smaller.. like /32.
How could we implement smooth transition from AX.25 to IPv6 on data links ?
Very good question... old legacy junk will want to live a long time.
(we are way too willing to recycle obsolete hardware...)
> 73 de Hans, DL5DI
73 de Matti, OH2MQK
next prev parent reply other threads:[~2008-06-02 10:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-02 9:36 BUGs into libax25 DL5DI
2008-06-02 10:41 ` Matti Aarnio [this message]
2008-06-02 16:28 ` Bernard Pidoux
-- strict thread matches above, loose matches on Subject: below --
2008-06-01 22:26 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
2008-06-02 17:16 ` Dave Platt
2008-06-02 8:49 ` Ralf Baechle DL5RB
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=20080602104149.GS3700@mea-ext.zmailer.org \
--to=matti.aarnio@zmailer.org \
--cc=dl5di@prgm.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox