Back to matrix

F21-BP: Yes

Rationale

The newer pinned ION API returns bundleSourceEid, primaryIntegrityVerified and payloadAuthVerified together with the ADU. Native BIB verification sets the indicators after successful processing of the corresponding target; receiver rules select keys using the bundle source EID. With exact source-specific rules and distinct sender/receiver-only keys, protected primary and payload, and the application using the source as authenticated only when both indicators are true, this supplies native final-source provenance without another authentication exchange. Unlike F16, F21 does not require all unauthenticated payloads to be stopped before the API. The previous mandatory-delivery-gate blocker conflated those criteria. Unflagged deliveries remain unauthenticated. This is shared-key peer authentication, not civil identity, nonrepudiation or replay prevention.

Assessment method

Pinned implementation/API analysis; no protocol experiment

Source context

ION native BPSec verifier, source-key policy selection and BpDelivery API

Outstanding qualification

Exercise valid, absent, corrupted, wrong-key and source-substitution cases through bp_receive; verify paired flags and source/ADU association, including restart. Use only the declared exact-origin keys and primary-inclusive payload coverage. No execution, complete TCPCL deployment, or interoperability certification is claimed.

Public sources

Editorial evidence references

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