Request for comments:
New variable:
Peak Specialization (PS)
Nodes look for a peak in their datastore around a certain key and store its position as their Peak Specialization (PS) which is advertised to other nodes whenever a connection is made and stored in routing tables. This way each node knows the PS of every node connecting to it and every node in its routing table.
It would be easier to make nodes announce their PS from the start. Of course nodes must not be able to choose their specializations in the announcement protocol. With unobtanium routing the specialization of a node becomes public anyways (http://article.gmane.org/gmane.network.freenet.devel/8219).
New Communication:
Similar node discovery
Nodes with similar PS regularly connect and exchange lists of other nodes that have a similar PS.
Don't reinvent the wheel! Please take a look at kademlia: http://kademlia.scs.cs.nyu.edu/kpres.ps.gz http://kademlia.scs.cs.nyu.edu/kpos_iptps.pdf It works like a DHT. But it is not fragile. Load balancing and optimization for low latency can be easily added.
DigitalE wrote in another mail: > Instead of hoping we stumble onto the key by following estimators, each > hop will bring the request closer to where the data really is, and where nodes > specialise in routing this request.
Kademlia does exactly that in a well-thought out way.
The problem is to make publishing and reading anonymous. This may require mixmaster prerouting. The announcement protocol must also be changed so that nodes can not choose their own specializations.
-- Thomas Leske
_______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
