[Gzz-commits] storm/doc/pegboard/attacking_gisp--hemppah peg.rst

[Hermanni Hyytiälä]

CVSROOT:        /cvsroot/storm
Module name:    storm
Branch:         
Changes by:     Hermanni Hyytiälä <address@hidden>      03/06/16 04:49:08

Modified files:
        doc/pegboard/attacking_gisp--hemppah: peg.rst 

Log message:
        cache info

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/storm/storm/doc/pegboard/attacking_gisp--hemppah/peg.rst.diff?tr1=1.34&tr2=1.35&r1=text&r2=text

Patches:
Index: storm/doc/pegboard/attacking_gisp--hemppah/peg.rst
diff -u storm/doc/pegboard/attacking_gisp--hemppah/peg.rst:1.34 
storm/doc/pegboard/attacking_gisp--hemppah/peg.rst:1.35
--- storm/doc/pegboard/attacking_gisp--hemppah/peg.rst:1.34     Fri Jun 13 
09:12:32 2003
+++ storm/doc/pegboard/attacking_gisp--hemppah/peg.rst  Mon Jun 16 04:49:08 2003
@@ -4,8 +4,8 @@
 
 :Authors:  Hermanni Hyytiälä
 :Date-Created: 2003-06-05
-:Last-Modified: $Date: 2003/06/13 13:12:32 $
-:Revision: $Revision: 1.34 $
+:Last-Modified: $Date: 2003/06/16 08:49:08 $
+:Revision: $Revision: 1.35 $
 :Status:   Incomplete
 
 .. :Stakeholders:
@@ -168,7 +168,9 @@
 - The current implementation does not support "free choice"
 - Future versions may include "peer strength" feature (a peer decides 
   whether to put it an another peer in its routing table or not)  
-
+- GISP maintains cache information about 10000 peers (max) whereas Chord
+  caches information about 1000 peers (max)
+  
 The assumption for the results above is that the system is "in the steady 
state", 
 according to the authors.
 
@@ -230,9 +232,9 @@
 
 Hypothesis:
 
-- GISP has an obvious exploit, if a hostile peer is able to behave like "dumb"
-  peer. More specifically, a hostile peer answers to "SEEN" messages in the
-  network, but no dot perform requested operations, e.g., do not provide
+- GISP has a exploit, if a hostile peer is able to behave like "dumb"
+  peer easily. More specifically, a hostile peer answers to "SEEN" messages in 
+  the network, but no dot perform requested operations, e.g., do not provide
   a "RESULT" message for a "QUERY" message. This behaviour allows other peers 
   to maintain hostile peers in their routing tables while still hostile
   peers are able to cause problems to the network's operation. "SEEN", "RESULT"
@@ -243,10 +245,10 @@
 - In the GISP overlay, the average routing hop length is proportional to 
   O(log n).
   
-- In a GISP network, when fraction f of the peers are "dumb" and a "dumb"
-  peer do not provide a "RESULT" message for a "QUERY" message, the 
-  probability of routing successfully "QUERY" message between two regular 
-  peers is (1-f)^h-1, where h is the routing hops used in the overlay. 
+- In a GISP network, when fraction f of the peers are "dumb" and a "dumb" peer 
+  do not provide a "RESULT" message for a "QUERY" message, the probability of 
+  routing successfully "QUERY" message between two regular peers is (1-f)^h-1, 
+  where h is the routing hops used in the overlay.