214 |
|
|
215 |
Problem description Solutions Comments/Status |
Problem description Solutions Comments/Status |
216 |
Routing: Incorrect forwarding (hostile), Query monitoring, cross check |
Routing: Incorrect forwarding (hostile), Query monitoring, cross check |
217 |
incorrect routing (hostile) routing tables, verify routing tables |
incorrect routing (hostile) routing tables, verify routing tables, |
218 |
|
invariants |
219 |
|
|
220 |
DoS attack Distributed, controlled burden againts Client puzzles, load balancing, traffic |
DoS attack Distributed, controlled burden againts Client puzzles, load balancing, traffic |
221 |
specific computer(s) measurements, traffic models |
specific computer(s) measurements, traffic models |
222 |
|
|
223 |
Sybil attack: Single hostile entity present multiple Resource demanding mechanisms for Not practically realizable, |
Sybil attack: Single hostile entity present multiple Identify all nodes simultaneously Not practically realizable, |
224 |
entities validating identities research focused on persistence, |
entities across the system, collect pool of nodes research focused on persistence, |
225 |
not on distincn |
which are validated, distributed not on distinction |
226 |
|
node ID creation |
227 |
|
|
228 |
Spam attack: Hostile entity creates false versions Do not trust to single entity, |
Spam attack: Hostile entity creates false versions Do not trust to single entity, |
229 |
of data get information from multiple entities, |
of data get information from multiple entities, |
230 |
trust on majority |
trust on majority's opinion |
231 |
|
|
232 |
Resource spoofing: Hostile entity gives wrong information Do not trust to single entity, |
Resource spoofing: Hostile entity gives wrong information Do not trust to single entity, |
233 |
about the data which entity is responsible get information from multiple entities, |
about the data which entity is responsible get information from multiple entities, |
234 |
for/knows about trusy on majority |
for/knows about trust on majority's opinion |
235 |
|
|
236 |
Sudden network partition: Sub network is isolated from other network Self-tuning, environment observatorion, |
Sudden network partition: Sub network is isolated from other network Self-tuning, environment observatorion, |
237 |
because of network disconnection backup connections |
because of network disconnection backup connections |
240 |
of previous queries |
of previous queries |
241 |
|
|
242 |
Efficient data discovery: Find resources efficiently, if resource Super nodes, node clusters, |
Efficient data discovery: Find resources efficiently, if resource Super nodes, node clusters, |
243 |
exists (broadcasting) caching |
exists (broadcasting) caching techiques |
244 |
|
|
245 |
Entity identification: Identify participating entities reliably Digital signatures Research focused on persistence, |
Entity identification: Identify participating entities reliably Digital signatures Research focused on persistence, |
246 |
and efficiently not on disti |
and efficiently not on distiinction of identity |
247 |
|
|
248 |
Fail Stop: A specific faulty nodes is deleted/isolated |
Fail Stop: A faulty node stops working Environment observatorion, informing |
249 |
from the system |
protocols |
250 |
|
|
251 |
Byzantine faults: Faulty nodes may behave arbitrarily |
Byzantine faults: Faulty nodes may behave arbitrarily Byzantine agreement protocols, |
252 |
|
trust on majority's opinion |
253 |
|
|
254 |
Richness of queries: Query languages should be more powerful |
Richness of queries: Query languages should be more powerful SQL-like queries |
255 |
|
|
256 |
Robustness: How well system performs under hostile Form of connectivity graph, |
Robustness: How well system performs under hostile Self-tuning, backup links, use |
257 |
attacks/in the case of severe failure ? backup links |
attacks/in the case of severe failure ? diverse routing paths |
258 |
|
|
259 |
Quality of Service, QoS: The system cannot promise the quality of |
Quality of Service, QoS: The system cannot promise the quality of |
260 |
service in all cases |
service in all cases |
261 |
|
|
262 |
Data availability: Data might be temporary unavailable, or lost |
Data availability: Data might be temporary unavailable, or lost Data caching, data replication |
263 |
permanently |
permanently |
264 |
|
|
265 |
Data integrity/authenticity: Integrity/originality of data is unknown |
Data integrity/authenticity: Integrity/originality of data is unknown Cryptographic content hashes |
266 |
|
|
267 |
Anonymity: Anonymity cannot be provided in all |
Anonymity: Anonymity cannot be provided in all Remailers |
268 |
cases |
cases |
269 |
|
|
270 |
Malicious nodes: There are malicious nodes in the system. |
Malicious nodes: There are malicious nodes in the system, Detect |
271 |
How we are able to discover them ? |
how we are able to discover them ? |
272 |
|
|
273 |
Mutual distrust: Nobody trust anybody, this is a problem |
Mutual distrust: Nobody trust anybody, this is a problem |
274 |
|
|
276 |
like they should be, instead they go for |
like they should be, instead they go for |
277 |
own profit |
own profit |
278 |
|
|
279 |
Heterogeneity: There are different kind of nodes |
Heterogeneity: There are different kind of nodes |
280 |
in the system, in light of bandwidth |
in the system, in light of bandwidth |
281 |
and computing power |
and computing power |
282 |
|
|
283 |
Network proximity: Can we take account the underlying |
Network proximity: Can we take account the underlying Global Network Positioning, Lighthouse |
284 |
network's properties better when forming |
network's properties better when forming technique, trianqulated heuristics |
285 |
overlay network (network-awareness for |
overlay network (network-awareness for |
286 |
performance) ? |
performance) ? |
287 |
|
|
288 |
Locality: In the case on DHTs, can we take account |
Locality: In the case on DHTs, can we take account Constrained Load Balancing, using |
289 |
locality ? |
locality ? network proximity for nearest |
290 |
|
neighbor selection |
291 |
|
|
292 |
Hotspots: What will happen if some resource |
Hotspots: What will happen if some resource Caching, multisource downloads |
293 |
is extremely popular and only |
is extremely popular and only |
294 |
one node is hosting it ? |
one node is hosting it ? |
295 |
|
|
296 |
Scalability: Broadcasting doesn't scale when performing |
Scalability: Broadcasting doesn't scale when performing Super peers, peer clusters, mutual |
297 |
searches |
searches index caching |
298 |
|
|
299 |
Programming guidelines: Set of programming guidelines/frameworks |
Programming guidelines: Set of programming guidelines/frameworks Common frameworks and APIs |
300 |
is needed for better interoperability between |
is needed for better interoperability between |
301 |
different systems |
different systems |
302 |
|
|
303 |
Access Control: Can we define access control levels |
Access Control: Can we define access control levels |
304 |
in peer-to-peer network ? |
in peer-to-peer network ? |
305 |
|
|
306 |
System in flux: Nodes join and leave system constantly: |
System in flux: Nodes join and leave system constantly: Half-life phenomenon |
307 |
load balancing, efficiency ? |
load balancing, efficiency ? |
308 |
|
|
309 |
Inconsistent behaviour: Hostile node could act correctly with |
Inconsistent behaviour: Hostile node could act correctly with |
314 |
|
|
315 |
External threats: Viruses, troijans, sniffers |
External threats: Viruses, troijans, sniffers |
316 |
|
|
317 |
Overlay construction: Hostile node controls the construction Cryptography |
Overlay construction: Hostile node controls the construction Cryptography |
318 |
of the network |
of the network |
319 |
|
|
320 |
at each hop, querier knows that the lookup is supposed to get "closer". The querier should check this so that |
at each hop, querier knows that the lookup is supposed to get "closer". The querier should check this so that |
1240 |
-some research has been done on on-line identities for humans. However, they often has a direct relation to phychical world |
-some research has been done on on-line identities for humans. However, they often has a direct relation to phychical world |
1241 |
|
|
1242 |
|
|
1243 |
|
Udi Wieder's important statement: |
1244 |
|
"By the way, as I think I stated in the paper, I believe that when it |
1245 |
|
comes to security and byzantine faults in p2p there should be a |
1246 |
|
distinction between attacks on the protocols assuming the construction |
1247 |
|
is correct, and attacks on the construction itself" |
1248 |
|
|
1249 |
|
|
1250 |
|
|
1251 |
6. Proposed frameworks |
6. Proposed frameworks |
1252 |
|
|