F36-BP: No
Rationale
The selected basic BPv7/TCPCLv4 service accepts messages with lifetimes and can retain, forward or expire them. RFC 9171 leaves forwarding decisions to routing policy; it supplies no application-requested service allocation mechanism. This column selects aggregate gateway exits and optional AQM/DiffServ, not CGR/SABR contact-volume admission. ION classOfService priority and lifetime parameters alone do not establish that additional allocation behavior.
Assessment method
Documentary plausibility with selected-version source corroboration
Source context
BPv7; CCSDS SABR 734.3-B-1; ION selected pin; GNUnet 0.20 ATS
Outstanding qualification
No applies to this declared basic BP composition, not all BP routing implementations. The CG and LT columns explicitly add SABR and are assessed separately. Expiration, storage acceptance, transport flow control and queue priority are not by themselves F36 service allocation. No new runtime test.
Public sources
- https://www.rfc-editor.org/rfc/rfc9171.html#section-5.4
- https://github.com/nasa-jpl/ION-DTN/blob/154a4cc7354b26661169f8d8b75a4002cd509a9f/bpv7/library/libbp.c
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round705.html