F25-BP: 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 compact configured BPv7/BPSec transfer can meet F25 after fresh TCP/TLS1.3/TCPCLv4 setup. The inventory includes both contact headers, mutual certificate authentication and NODE-ID checking, SESS_INIT, two protected bundles carrying 256 useful bytes each, transfer acknowledgments and conservative shutdown/keepalive reserves. Bounded standard BPSec blocks fit a 2,048-byte bundle. At MSS 1,024, 32 data-bearing segments plus ACK, connection control, IPv4/Ethernet overhead and fresh ARP total at most 41,314 byte-times.

Assessment method

Constructive documentary byte envelope

Source context

Primary BP/BPSec/TCPCL/TLS formats and complete endpoint inventory

Outstanding qualification

Conditional documentary bound: compact numeric EIDs, locally trusted certificate chains <=2,048 bytes each, bounded TLS messages and <=32 data-segment packetization. Retain BPSec keys and authorization but establish a new transport session. No DNS, OCSP, resumption, optional TLS padding, bundle reports, retransmission or arbitrary extensions. All selected security layers remain; this is not a generic bound for every certificate/bundle or implementation. Exact executable BPv7/BPSec/TCPCL and SABR integration remains separately unqualified. No runtime, energy or throughput claim.

Public sources

Editorial evidence references

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

round320-budget.json
round320-sources.json