gzz-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Hermanni Hyytiälä
Subject: [Gzz-commits] storm/doc/pegboard/attacking_gisp--hemppah peg.rst
Date: Fri, 13 Jun 2003 07:51:22 -0400

CVSROOT:        /cvsroot/storm
Module name:    storm
Branch:         
Changes by:     Hermanni Hyytiälä <address@hidden>      03/06/13 07:51:22

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

Log message:
        addition to issue

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/storm/storm/doc/pegboard/attacking_gisp--hemppah/peg.rst.diff?tr1=1.29&tr2=1.30&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.29 
storm/doc/pegboard/attacking_gisp--hemppah/peg.rst:1.30
--- storm/doc/pegboard/attacking_gisp--hemppah/peg.rst:1.29     Fri Jun 13 
03:06:24 2003
+++ storm/doc/pegboard/attacking_gisp--hemppah/peg.rst  Fri Jun 13 07:51:21 2003
@@ -4,8 +4,8 @@
 
 :Authors:  Hermanni Hyytiälä
 :Date-Created: 2003-06-05
-:Last-Modified: $Date: 2003/06/13 07:06:24 $
-:Revision: $Revision: 1.29 $
+:Last-Modified: $Date: 2003/06/13 11:51:21 $
+:Revision: $Revision: 1.30 $
 :Status:   Incomplete
 
 .. :Stakeholders:
@@ -87,9 +87,12 @@
        
        RESOLVED: No, the current GISP implementation does not address 
        "uselessness" properly, since GISP peer only observes reply 
-       timeouts, i.e., the time which has been passed since last
-       reply.
-
+       timeouts for the "seen" messages. Thus, we can implement a "dumb" 
+       peer which answers to the "seen" messages normally but does not
+       perform requested operations, e.g., reply to "query" message. This 
+       behaviour allows other peers to maintain "dumb" peers in their 
+       routing tables while still "dumb" peers are able to cause 
+       problems for the network's operation.
 
 
 Research problems




reply via email to

[Prev in Thread] Current Thread [Next in Thread]