[nos-bbs] A.X25 then, A.IP now ??? - thinking outloud (fwd)

[Duvall [US], Mike J.]

I had a similar thought years ago. It always seemed like a waste to wrap
x25 around and IP packet. Legally all you need is the call sign to
identify the transmitting station. The payload data could be anything.
With A.X25, source call sign and destination call sign are used like IP
addresses for routing. If you identify the transmitter and IP can take
care of the routing between station then your concept is sound.  

I imagine it would be next to impossible to get the A.X25 standard to
change. Lots of PROM based TNCs out there I am sure. Unless you have
other capabilities in mind, as long as the AX.25 system rejects you're
A.IP protocol I do see the need for the A.X25 protocol to change. 

A simple way to implement it would be to prefix the IP packet with the
transmitting station, SID and a check sum. You just strip these off on
receive and pass the remaining data that is IP packet on for processing.
In a more abstract sense, prefix any network packet with the
transmitting station, SID and a check sum. If this was the standard then
in the future you could replace and IP packet with some other protocol. 


Mike, ac4zq


-----Original Message-----
From: nos-bbs-bounces at lists.tapr.org
[mailto:nos-bbs-bounces at lists.tapr.org] On Behalf Of maiko at pcs.mb.ca
Sent: Thursday, June 22, 2006 12:41 PM
To: TAPR xNOS Mailing List
Subject: [nos-bbs] A.X25 then, A.IP now ??? - thinking outloud (fwd)

{snip}