Participant Relationship Protocol

Back to matrix

E04-AX: Yes

Rationale

Zielinski (Silesian University of Technology, 2013) measures AX.25 throughput using existing commercial TNC hardware and firmware. Section 3 specifies computers, controllers, serial and link rates, windows, payload sizes and timing boundaries; figures report executed measurements alongside a separate analytical model. The university evaluator is distinct from the identified vendors and firmware authors. AX.25 is an explicit component of the selected AX.25/NET-ROM stack. Revised E04 accepts a measured relevant component: the earlier demand for NET/ROM measurements as well was stricter than this definition.

Assessment method

Revised E04 component-scoped documentary assessment; earlier full-stack requirement corrected

Source context

Zielinski, Effective throughput of AX.25 protocol (2013)

Outstanding qualification

Credit applies only to AX.25 frame exchange and throughput. NET/ROM route selection, transport circuits and the selected Linux implementation were not measured. Controllers were connected by wire to approximate error-free radio conditions; no over-the-air range or interference result is inferred. Hardware and firmware differences prevent transfer of numerical performance to current systems. The study’s analytical curves are not counted as measurements. No new experiment, ranking or exhaustive contributor audit was performed.

Public sources

Editorial evidence references

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