[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/06 07:56:25

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

Log message:
        twid

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/storm/storm/doc/pegboard/attacking_gisp--hemppah/peg.rst.diff?tr1=1.11&tr2=1.12&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.11 
storm/doc/pegboard/attacking_gisp--hemppah/peg.rst:1.12
--- storm/doc/pegboard/attacking_gisp--hemppah/peg.rst:1.11     Fri Jun  6 
07:45:05 2003
+++ storm/doc/pegboard/attacking_gisp--hemppah/peg.rst  Fri Jun  6 07:56:24 2003
@@ -5,8 +5,8 @@
 
 :Authors:  Hermanni Hyytiälä
 :Date-Created: 2003-06-05
-:Last-Modified: $Date: 2003/06/06 11:45:05 $
-:Revision: $Revision: 1.11 $
+:Last-Modified: $Date: 2003/06/06 11:56:24 $
+:Revision: $Revision: 1.12 $
 :Status:   Incomplete
 
 .. :Stakeholders:
@@ -63,27 +63,28 @@
 to use GISP's native code as much as possible. We start our 
 simulation process by creating simple scenarios in which:
 
-- A hostile (or faulty) peer(s) doesn't reply to queries (a "dumb" peer)*
+- A hostile peer(s) doesn't reply to queries (a "dumb" peer)*
 
-- A hostile (or faulty) peer(s) tries to drop certain packets/queries wilfully*
+- A hostile peer(s) tries to drop certain packets/queries wilfully*
   
-- A hostile (or faulty) peer(s) forwards queries to incorrect destination peers
+- A hostile peer(s) forwards queries to incorrect destination peers
 
-- A hostile (or faulty) peer(s) gives false information during queries
+- A hostile peer(s) gives false information during queries
 
-- A hostile (or faulty) peer(s)'s queries/replies include loads of rubbish, 
i.e., 
+- A hostile peer(s)'s queries/replies include loads of rubbish, i.e., 
   wrong XML-scheme, wrong string/text encoding, or doesn't otherwise follow 
the protocol
   
-- A hostile (or faulty) peer(s) performs many queries randomly
+- A hostile peer(s) performs many queries randomly
 
-- A hostile (or faulty) peer(s) performs many queries wilfully with a certain 
key
+- A hostile peer(s) performs many queries wilfully with a certain key
 
-- A hostile (or faulty) peer(s) stores lot of dummy random key-value-pairs
+- A hostile peer(s) stores lot of dummy random key-value-pairs
 
-- A hostile (or faulty) peer(s) stores lot of dummy key-value-pairs with a 
certain key
+- A hostile peer(s) stores lot of dummy key-value-pairs with a certain key
 
-During the simulation process we will use a single hostile (or faulty) peer
-or a group of hostile/faulty peers (fraction of all peers) in the test 
network. 
+During the simulation process we will use a single hostile  peer
+or a group of hostile peers (fraction of all peers) in the test network.
+We assume that hostile peer(s) takes part in forming of the network normally. 
 
 By using above scenarios, we want to clarify GISP's properties with regard to 
research 
 questions.
@@ -93,9 +94,9 @@
 Issues
 ======
 
-.. Is there any issues ?
 
-None, yet.
+ISSUE: When should we discuss this with the author of GISP?      
+
 
 Changes
 =======