The sync protocol (Section 6.2) assumes bilateral connection between peers. It does not address store-and-forward transit across partitioned networks: connect to an access point in one part of the city → sync a subset → physically move → connect to another network segment → sync the rest.
This is distinct from multi-device sync — it's relay through mobile intermediaries across disconnected network islands.
Proposal: define a DTN extension to the sync protocol:
Bundle format: serialized DAG subgraph with referenced content, signed by original authors
Relay semantics: any node carries bundles without reading encrypted content
Priority mechanism for senders (emergency coordination vs. media)
TTL / size limits on carried bundles
Deduplication: content-addressed messages deduplicate naturally on import
The bundle format should be shared between sneakernet export/import and DTN relay.
The sync protocol (Section 6.2) assumes bilateral connection between peers. It does not address store-and-forward transit across partitioned networks: connect to an access point in one part of the city → sync a subset → physically move → connect to another network segment → sync the rest.
This is distinct from multi-device sync — it's relay through mobile intermediaries across disconnected network islands.
Proposal: define a DTN extension to the sync protocol:
Bundle format: serialized DAG subgraph with referenced content, signed by original authors
Relay semantics: any node carries bundles without reading encrypted content
Priority mechanism for senders (emergency coordination vs. media)
TTL / size limits on carried bundles
Deduplication: content-addressed messages deduplicate naturally on import
The bundle format should be shared between sneakernet export/import and DTN relay.