[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gzz-commits] gzz/Documentation/misc/hemppah-progradu prograd...
From: |
Hermanni Hyytiälä |
Subject: |
[Gzz-commits] gzz/Documentation/misc/hemppah-progradu prograd... |
Date: |
Thu, 06 Feb 2003 04:39:22 -0500 |
CVSROOT: /cvsroot/gzz
Module name: gzz
Changes by: Hermanni Hyytiälä <address@hidden> 03/02/06 04:39:21
Modified files:
Documentation/misc/hemppah-progradu: progradu.bib
research_problems
Log message:
Added problems description into problem table
CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/gzz/Documentation/misc/hemppah-progradu/progradu.bib.diff?tr1=1.65&tr2=1.66&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/gzz/Documentation/misc/hemppah-progradu/research_problems.diff?tr1=1.46&tr2=1.47&r1=text&r2=text
Patches:
Index: gzz/Documentation/misc/hemppah-progradu/progradu.bib
diff -u gzz/Documentation/misc/hemppah-progradu/progradu.bib:1.65
gzz/Documentation/misc/hemppah-progradu/progradu.bib:1.66
--- gzz/Documentation/misc/hemppah-progradu/progradu.bib:1.65 Wed Feb 5
07:51:44 2003
+++ gzz/Documentation/misc/hemppah-progradu/progradu.bib Thu Feb 6
04:39:18 2003
@@ -1764,6 +1764,7 @@
pages = {173--186},
location = {New Orleans, Louisiana, United States},
publisher = {USENIX Association},
+ url = {http://www.pmg.lcs.mit.edu/papers/osdi99.pdf}
}
@inproceedings{juels99clientpuzzles,
Index: gzz/Documentation/misc/hemppah-progradu/research_problems
diff -u gzz/Documentation/misc/hemppah-progradu/research_problems:1.46
gzz/Documentation/misc/hemppah-progradu/research_problems:1.47
--- gzz/Documentation/misc/hemppah-progradu/research_problems:1.46 Wed Feb
5 09:32:01 2003
+++ gzz/Documentation/misc/hemppah-progradu/research_problems Thu Feb 6
04:39:18 2003
@@ -212,35 +212,89 @@
3) p2p open problems table:
- Problem description
Solutions Comments/Status
-Routing:
-DDos:
-Sybil:
-Spam:
-Resource spoofing:
-Sudden network partition:
-Searching:
View trees, bloom filters
-Efficient Resource discovery:
-Entity identification:
-Fail Stop:
-Byzantine problem:
-Richness of queries:
-Robustness:
-Quality of Service, QoS:
-Data availability:
-Data integrity/authenticity:
-Anonymity:
-Attack resistance:
-Malicious nodes:
-Mutual distrust:
-Lack of motivation to cooperate:
-Heterogeneity:
-Network proximity:
-Load Balancing:
-Locality:
-Hotspots:
-Scalability:
-Programming guidelines:
+ Problem description
Solutions Comments/Status
+Routing: Incorrect forwarding (hostile),
Query monitoring, crossc heck
+ incorrect routing (hostile)
routing tables
+
+DoS: Distributed, controlled burden of a
Client puzzles
+ computer(s)
+
+Sybil: Single hostile entity present multiple
Resource demanding mechanisms for Not practically realizable
+ entities
validating identities
+
+Spam: Hostile entity creates false versions
+ of data
+
+Resource spoofing: Hostile entity gives wrong information
+ about the data which entity is
responsible
+ for
+
+Sudden network partition: Sub network is isolated from other
network
+ because of disconnection
+
+Searching: Efficient searching exploiting previous
+ queries
View trees, bloom filters
+
+Efficient Resource discovery: Find resources efficiently, if resource
+ exists (broadcasting)
+
+Entity identification: Identify participating entities reliably
+ and efficiently
+
+Fail Stop: A specific faulty nodes is
deleted/isolated
+ from the system
+
+Byzantine faults: Faulty nodes may behave arbitrarily
+
+Richness of queries: Queries should be more powerful
+
+Robustness: How well system performs under hostile
+ attacks
+
+Quality of Service, QoS: The system cannot promise the quality
of
+ service in all cases
+
+Data availability: Data might be temporary unavailable, or
lost
+ permanently
+
+Data integrity/authenticity: Integrity/originality of data is unknown
+
+Anonymity: Anonymity cannot be provided in all
+ cases
+
+Malicious nodes: There are malicious nodes in the system.
+ How we are able to discover them ?
+
+Mutual distrust: Nobody trust anybody
+
+Lack of motivation to cooperate: All participants do not behave
+ like they should be, instead they go
for
+ own profit
+
+Heterogeneity: There are different kind of nodes
+ in the system, in light of bandwidth
+ and computing power.
+
+Network proximity: Can we take account the underlying
+ network's properties better when forming
+ overlay network ?
+
+Locality: In the case on DHTs, can we take account
+ locality ?
+
+Hotspots: What will happen if some resource
+ is extremely popular and only
+ one node is hosting it
+
+Scalability: Broadcasting doesn't scale when
performing
+ searches
+
+Programming guidelines: Set of programming
guidelines/frameworks
+ is needed for better combatibility
between
+ different systems
+
+Access Control Can we define access control levels
+ in peer-to-peer network ?
* = In Kademlia, there is no action required when nodes leaves the system
- [Gzz-commits] gzz/Documentation/misc/hemppah-progradu prograd..., Hermanni Hyytiälä, 2003/02/05
- [Gzz-commits] gzz/Documentation/misc/hemppah-progradu prograd..., Hermanni Hyytiälä, 2003/02/05
- [Gzz-commits] gzz/Documentation/misc/hemppah-progradu prograd...,
Hermanni Hyytiälä <=
- [Gzz-commits] gzz/Documentation/misc/hemppah-progradu prograd..., Hermanni Hyytiälä, 2003/02/06
- [Gzz-commits] gzz/Documentation/misc/hemppah-progradu prograd..., Hermanni Hyytiälä, 2003/02/07
- [Gzz-commits] gzz/Documentation/misc/hemppah-progradu prograd..., Hermanni Hyytiälä, 2003/02/10
- [Gzz-commits] gzz/Documentation/misc/hemppah-progradu prograd..., Hermanni Hyytiälä, 2003/02/14
- [Gzz-commits] gzz/Documentation/misc/hemppah-progradu prograd..., Hermanni Hyytiälä, 2003/02/17
- [Gzz-commits] gzz/Documentation/misc/hemppah-progradu prograd..., Hermanni Hyytiälä, 2003/02/19