For AX.25 version 2.0, the maximum frame size expected is 330 bytes and implementations MUST be prepared to handle frames of this size. Higher frame sizes can be negotiated by AX.25 version 2.2 and so this is a minimum requirement and not a limit.
It is ok. For IPv6, the minimum MTU (minimum Maximum Transmission Unit) is 1280 bytes.
For IPv4, it is not worth mentioning. One, including myself, would go as far as suggesting to remove the IPv4 keyword from the draft altogether.
A packet dump, or an illustration diagram, showing an AX.25 carried in IPv6 would be helpful.
AX.25 is related to X.25 but remark: X.25 might carry IP packets, whereas IP packets might carry AX.25. If I understand correctly.
Alex Le 21/05/2020 à 09:25, Iain R. Learmonth a écrit :
Hi All, I have just submitted a draft containing a refresh for RFC1226, "AX.25 over IP". URL: https://www.ietf.org/internet-drafts/draft-learmonth-intarea-rfc1226-bis-00.txt Status: https://datatracker.ietf.org/doc/draft-learmonth-intarea-rfc1226-bis/ Htmlized: https://tools.ietf.org/html/draft-learmonth-intarea-rfc1226-bis-00 Htmlized: https://datatracker.ietf.org/doc/html/draft-learmonth-intarea-rfc1226-bis I am happy to receive any comments you may have. This draft has been discussed within the TAPR APRSSIG mailing list, and that thread can be found here: http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/2020-May/048579.html I plan to survey existing implementations to see whether or not they are currently interoperable, and will be producing an implementation for HamBSD (https://hambsd.org/). Currently this is specified for unicast IP, however I can see benefits to enabling multicast use. I would like to have multicast use covered in this update. There is also the question of UDP encapsulated AX.25 which currently seems to have been made up by every implementation. I will include that in my survey, and see if there can be some consensus drawn there. I'm not sure if it is appropriate to add the UDP encapsulation details to this draft, or if it would be preferred to make that a separate draft, maybe even in a different area/WG. Thanks, Iain. -------- Forwarded Message -------- Subject: New Version Notification for draft-learmonth-intarea-rfc1226-bis-00.txt Date: Thu, 21 May 2020 00:14:45 -0700 From: [email protected] To: Iain Learmonth <[email protected]>, Iain R. Learmonth <[email protected]> A new version of I-D, draft-learmonth-intarea-rfc1226-bis-00.txt has been successfully submitted by Iain R. Learmonth and posted to the IETF repository. Name: draft-learmonth-intarea-rfc1226-bis Revision: 00 Title: Internet Protocol Encapsulation of AX.25 Frames Document date: 2020-05-21 Group: Individual Submission Pages: 6 Abstract: This document describes a method for the encapsulation of AX.25 Link Access Protocol for Amateur Packet Radio frames within IPv4 and IPv6 packets. Obsoletes RFC1226. Note Comments are solicited and should be addressed to the author(s). The sources for this draft are at: https://github.com/irl/draft-rfc1226-bis Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat _______________________________________________ Int-area mailing list [email protected] https://www.ietf.org/mailman/listinfo/int-area
_______________________________________________ Int-area mailing list [email protected] https://www.ietf.org/mailman/listinfo/int-area
