Changes between Version 27 and Version 28 of NetDB/NextBackend


Ignore:
Timestamp:
Jun 2, 2013 12:13:53 PM (6 years ago)
Author:
hottuna
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • NetDB/NextBackend

    v27 v28  
    4848
    4949|| '''Name''' || '''Source''' || '''Description''' ||
    50 || Recursive lookups || R5N[4]|| Make FIND_VALUE request recursive by forwarding the query recursively and (recursively, to the previous requester in the chain of the recursion) returning the answer, a reliability metric of nodes can be obtained.  Which can be used in conjunction with the last_seen attribute of k-bucket entries to create a combined eviction policy. ||
     50|| Recursive lookups || R5N[4]|| Make FIND_VALUE request recursive by forwarding the query recursively and (recursively, to the previous requester in the chain of the recursion) returning the answer, a reliability metric of nodes can be obtained.  Which can be used in conjunction with the last_seen attribute of ''k''-bucket entries to create a combined eviction policy. ||
    5151
    5252
     
    8181 * Investigate the i2p.zzz.kademlia implementation
    8282 * Make sure that i2p.zzz.kademlia implements Kademlia fully
    83    * Implement k-bucket merging
     83   * Implement ''k''-bucket merging
    8484
    8585==== 2: Improve performance ====
     
    9191==== 3: Attack resistance ====
    9292The two main attack resistance methods will be recursive and random recursive lookups.
    93 Recursive lookups are not only fast, but can be be used to provide a lookup success metric that is useful when doing the k-bucket evictions.
     93Recursive lookups are not only fast, but can be be used to provide a lookup success metric that is useful when doing the ''k''-bucket evictions.
    9494Random recursive lookups allows FIND_VALUE requesters to eventually find a path to the data if one exists.
    9595
    9696 * Implement recursive lookup metric
    97    * Change k-bucket eviction policy to also use recursive lookup success metric
     97   * Change ''k''-bucket eviction policy to also use recursive lookup success metric
    9898 * Implement random recursive lookups
    9999
     
    101101
    102102== Unresolved issues ==
    103 ==== K-bucket building for recursive lookups ====
    104 K-buckets need to be continually updated.
    105 In the case of iterative searching, this is not a problem. But when doing recursive searches, the search originator will not get the usual information about nodes that are close to the queried key. [[BR]]
     103==== ''k''-bucket building for recursive lookups ====
     104''k''-buckets need to be continually updated.
     105In the case of iterative searching, this is not a problem. But when doing recursive searches, the search originator will not get the usual information about nodes that are close to the queried key. [[BR]][[BR]]
    106106[6] suggests two solutions to this issue: [[BR]]
    107107'''Source: Direct Mode''': All nodes on the routing path send back ''k'' nodes that are close to ''key'' back to the originator of the query. [[BR]]
    108 '''Source: Source-Routing Mode''': All nodes on the routing path send back ''k'' nodes that are close to ''key'' back to the previous hop on routing path which appends its own ''k'' closest nodes to ''key'' and repeats. [[BR]]
     108'''Source: Source-Routing Mode''': All nodes on the routing path send back ''k'' nodes that are close to ''key'' back to the previous hop on routing path which appends its own ''k'' closest nodes to ''key'' and repeats. [[BR]][[BR]]
     109
     110How
    109111
    110112