2 Mar
2017
2 Mar
'17
10:35 a.m.
On Thu, Mar 02, 2017 at 08:14:28AM -0800, Michael Fox - N6MEF wrote:
If such a document truly doesn't exist, then
perhaps we should document it
somewhere. It should be as simple as a cut and paste the language of RFC
1226, substituting "UDP" for "IP" where appropriate, and
substituting
"default port number of 93" instead of "protocol number of 93".
Unfortunately, there are problems with AXIP and AXUDP ever since the
revisions of AX.25 were published - the AX.25 frames may get too big
to encapsulate in unfragmented IP and UDP frames. Any new document
would have to discuss the fragmentation issues, and I'll bet they're
not defined. (As far as I know, the same issue applies to ROSE, KISS,
and Net/Rom encapsulation too.)
Do any of the various implementations of AX.25 encompass v2.0 et seq as
published by TAPR? Ie, is anyone actually implementing jumbo frames,
expanded frame sequence numbers, etc? Or should we just treat it as a
bad idea that should be buried and go on with the old protocol?
- Brian