Archived criterion

F25-AX: Yes

Archived previous-definition assessment — revision 5.73. Retired in 5.82; excluded from the active matrix and counts. This historical verdict is not a current assessment.

Historical wake-traffic inventory (cutoff retired)

Rationale

The already selected private direct-serial role admits a bounded wake-up witness. Linux 6.12 NET/ROM splits each 256-byte useful message into 236+20-byte fragments; its 15-byte network and 5-byte transport headers keep the larger packet within AX.25 paclen 256. Count fresh AX.25 and NET/ROM connection setup, four data frames for one message in each direction, transport and link acknowledgments, two small announcements and conservative shutdown/maintenance reserves: 32 frames total. A generous 512-byte frame cap, KISS command byte, worst-case doubling by escaping, delimiters and 8N1 start/stop bits yield 41,120 byte-equivalents, below 65,536.

Assessment method

Constructive native fragmentation and complete endpoint byte inventory

Source context

Linux 6.12 NET/ROM, AX.25 and MKISS source; original KISS protocol

Outstanding qualification

Constructive documentary direct-serial configuration, not a runtime measurement or radio-airtime bound. Retained configured callsigns/ports and a locked NET/ROM route (obs_count=0); learned sessions are recreated. One known adjacent peer, no digipeaters, no unrelated traffic or large route announcements, timely loss-free acknowledgments and timers preventing retry/poll bursts. Standard KISS without optional CRC-mode negotiation. No cryptographic authorization is supplied by this plaintext profile; retained labels/configuration do not imply authenticated peer identity. No IP encapsulation or application-layer fragmentation is introduced.

Public sources

Editorial evidence references

The following identifiers refer to research records not included in this public package; they are not public links.