--- Nick Tarleton <[EMAIL PROTECTED]> wrote: > Maybe just XOR with a randomly chosen node-private > value. But won't this fubar > routing and specialization, if each node has a > different ordering in its > routing? Or do I misunderstand what is meant by > "estimator keyspace"? > --
Since the ordering of keys in the estimator keyspace is completely arbitrary anyway the answer is no, but with some caveats: 1) A current node's routing would be screwed up if this was implemented all at once (this would probably screw up the entire network if enough nodes did this at the same time). An existing node would have to be converted slowly. Not a problem with a new node (with the exception of #2 below). 2) I believe NGR allows this information to be shared with a new node to help them integrate into the network. This would cause a problem because either the estimators would be scrambled (and therefore useless) or you would have to reveal the mapping function (which a cancer node could use to DoS a key). So each node would have to keep some unscrambled references to pass on to other nodes. Actually, I withdraw my last proposal. I think this one would work much better. So the two proposals for thwarting Toad's key DoS scenario are: 1) Hash-cash - works by making requesters pay a price for each request. 2) Estimator keyspace reordering - works by scattering requests across the entire estimator keyspace. I think either solution would do the job. Any other suggestions? __________________________________ Do you Yahoo!? Exclusive Video Premiere - Britney Spears http://launch.yahoo.com/promos/britneyspears/ _______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
