F25-RI: 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

A configured leaf can meet the approved F25 workload with its adjacent access router/root as the previously authorized peer. Count up to 14 neighbor/registration/RPL control datagrams, seven PSK DTLS handshake messages including optional cookie retry, seven ACK datagrams and two protected messages of 256 useful bytes each. With bounded options/identities every IPv6 datagram fits 640 bytes. Reserve ten 6LoWPAN fragments per datagram and 144 on-air bytes per fragment including PHY and link ACK. The conservative total is 43,200 bytes, below 65,536. Fresh DTLS and repaired network state are counted; no live session is reused.

Assessment method

Constructive documentary byte envelope; no runtime measurement

Source context

Primary protocol formats, radio framing reference and bounded endpoint inventory

Outstanding qualification

Constructive documentary witness only: one stable adjacent root/peer, one prefix/context/parent, provisioned PAN/channel/ULA and valid external PSK. Beaconless link, no MAC security, no unrelated traffic, bounded PSK identity/cookie/options, timely loss-free completion before retry timers and within the stated maintenance allowance. No certificate, CID, ticket, DNS or DHCP is introduced. No compression gain is needed for this upper bound. This is not a bound for arbitrary source-route depth, busy networks or all implementations, nor an energy/runtime/interoperability measurement. Selected psk_ke and its K01 verdict are unchanged.

Public sources

Editorial evidence references

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

round316-budget.json
round316-sources.json