-
Notifications
You must be signed in to change notification settings - Fork 238
Open
Labels
P1High: Likely tackled by core team if no one steps upHigh: Likely tackled by core team if no one steps updif/expertExtensive knowledge (implications, ramifications) requiredExtensive knowledge (implications, ramifications) required
Description
We have various routing types, and no high level spec + specific routing types also lack basic specs.
Routing specs we should have:
- High level overview of types of routing, poitning at sub-specs for specific types / implementations / standards
- DHT (peer / content / ipns records + put/get strategies and defaults - when to expire, how many copies to put/get etc)
- Pubsub (IPNS over Pubsub example, but fleshed out as a generic protocol)
- content routing over Bitswap: https://research.protocol.ai/publications/accelerating-content-routing-with-bitswap-a-multi-path-file-transfer-protocol-in-ipfs-and-filecoin/delarocha2021.pdf
- sub-quest: improve bitswap specs themselves based on the above paper.
- IPNI router (tbd, depends on IPIP-342: Ambient Discovery of Content Routers #342)
guillaumemichel
Metadata
Metadata
Assignees
Labels
P1High: Likely tackled by core team if no one steps upHigh: Likely tackled by core team if no one steps updif/expertExtensive knowledge (implications, ramifications) requiredExtensive knowledge (implications, ramifications) required