Classification: Bug (standards-compliance audit)
ManagementMessage calls setType(subtype.TISB_IDENTIFICATION). The subtype enum (ModeSDownlinkMsg.subtype) has no TISB_MANAGEMENT constant, so DF=18/CF=4 TIS-B/ADS-R management messages are labeled as identification messages; a consumer switching on getType() cannot distinguish a management message from an identification message.
- Code reference:
msgs/tisb/ManagementMessage.java:62 @ 94df15f
- Standard: DO-260B §A.3.3 Table A-36 (Control Field allocation) p.A-88; DF=18 CF=4 = TIS-B/ADS-R Management (Table 2-13, p.50)
Proposed fix: Add a TISB_MANAGEMENT constant to the subtype enum and call setType(subtype.TISB_MANAGEMENT) here.
Filed by the automated lib1090 standards-compliance audit (run 20260715T182455Z, subject commit 94df15f, version 5.0.0-SNAPSHOT). Finding LIB1090-018. Verified against DO-260B / DO-181E / ICAO Doc 9871.
Classification: Bug (standards-compliance audit)
ManagementMessage calls setType(subtype.TISB_IDENTIFICATION). The subtype enum (ModeSDownlinkMsg.subtype) has no TISB_MANAGEMENT constant, so DF=18/CF=4 TIS-B/ADS-R management messages are labeled as identification messages; a consumer switching on getType() cannot distinguish a management message from an identification message.
msgs/tisb/ManagementMessage.java:62@94df15fProposed fix: Add a TISB_MANAGEMENT constant to the subtype enum and call setType(subtype.TISB_MANAGEMENT) here.
Filed by the automated lib1090 standards-compliance audit (run
20260715T182455Z, subject commit94df15f, version5.0.0-SNAPSHOT). FindingLIB1090-018. Verified against DO-260B / DO-181E / ICAO Doc 9871.