Peer Routing and Content Routing (DHT) about js-libp2p

[daviddias]

Hi @AlexFreeland, got an update for you :) Check:
https://github.com/libp2p/js-libp2p/tree/master/examples/peer-and-content-routing

Note, consider the current implementation as ⍺ :)

[daviddias]

Hi @AlexFreeland, thank you for your feedback, it is highly appreciated

We know it is a little confusing at the moment, but there is a key reason for it. The simple answer is, the DHT present in go-ipfs, will be available in JavaScript at https://github.com/libp2p/js-libp2p-dht and that is going to be the 'first DHT'.

The 'second DHT', comes from the separation of concerns of Peer Routing and Content Routing, the explanation (and the realization) and can be found described here: ipfs/specs#1

libp2p spec presents some design decisions (https://github.com/libp2p/specs), getting the spec up to date is one of the goals of Q1 this year :)

[AlexFreeland]

Thanks for the response @diasdavid

So to clarify: the "second DHT" will entail separate peer and content routing modules, somewhat analogous to the division of responsibilities between https://github.com/libp2p/js-libp2p-kad-routing and https://github.com/libp2p/js-libp2p-kad-record-store? Is the intention to update or supersede these repositories?

On a related note: I notice that implementations of the first DHT use the "/ipfs/kad/1.0.0" (and historically "/ipfs/dht") protocol; am I correct in assuming that the second DHT will employ separate protocols for peer and content routing?