Back to matrix

F33-I2: No

Rationale

The selected I2P composition specifies NTCP2 links and destination tunnels, not a contact-aware reliable-transfer layer. NTCP2 uses TCP for an adjacent connection; tunnel rebuilding restores paths but does not preserve a checkpointed transfer across prolonged loss of communication opportunities. No contact schedule, timer suspension or equivalent recovery contract is selected.

Assessment method

Primary specification and pinned code review; no runtime experiment

Source context

I2P transport layering and GNUnet CADET recovery

Outstanding qualification

I2P also documents an application-layer Streaming library with acknowledgements, retransmission and RTT/congestion behavior. That optional layer is not silently added to the column, and ordinary streaming retries alone would not establish F33. The finding does not deny I2P reliability under normal operating conditions or prohibit application-level deferred delivery. No outage-duration measurement or universal timeout bound is claimed.

Public sources

• https://i2p.net/en/docs/api/streaming/
• https://i2p.net/en/docs/specs/tunnel-implementation/

Editorial evidence references

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

• round511.html
• round511-sources.json