F22-BP: No
Rationale
BP endpoints can contain multiple nodes under one EID, and the selected profile already credits locally agreed collective names and static forwarding fanout. However, RFC 9171 defines registrations as local state and explicitly provides no mechanism for distributing registration information. Delivery to the preconfigured collective therefore does not expose independently identified participant candidates through that shared reference. BPSec and transport authentication do not supply this missing discovery operation. A request/reply discovery application or an added membership protocol could do so, but neither is selected. This No leaves collective delivery and DTN capabilities unchanged.
Assessment method
Selected composition and RFC 9171 analysis; no execution
Source context
RFC 9171 section 3.1: bundle endpoint and registration