Securing Phoenix Network Coordinate System: Difference between revisions

From NET Wiki
Jump to navigation Jump to search
Line 17: Line 17:


== Reference ==
== Reference ==
[http://www.springerlink.com/content/20qt876131833081/]
* [http://www.springerlink.com/content/20qt876131833081/]
[http://planete.inria.fr/dabbous/publis/lsad06.pdf]
* [http://planete.inria.fr/dabbous/publis/lsad06.pdf]
[http://portal.acm.org/ft_gateway.cfm?id=1368453&type=pdf]
* [http://portal.acm.org/ft_gateway.cfm?id=1368453&type=pdf]
[http://micah.cis.upenn.edu/papers/veracity-usenix-atc09.pdf]
* [http://micah.cis.upenn.edu/papers/veracity-usenix-atc09.pdf]
[http://www.springerlink.com/index/f348530225120185.pdf]
* [http://www.springerlink.com/index/f348530225120185.pdf]

Revision as of 16:32, 22 February 2010

Details

Supervisor: Yang Chen
Duration: 6 months
Type: Master Thesis or Student Project
Status: open


Description

Phoenix [1] is an accurate and decentralized Network Coordinate (NC) system. It can be used to predict the distance (latency) between two Internet hosts without performing directly measurement. We have demonstrated and evaluated Phoenix through Internet traces.

In this project, we are going to consider the security issues in Phoenix NC. There are different kinds of attacks [2] [3] in NC systems, and we are going to design and deploy some security method in Phoenix NC. Finally, we will use typical attacks with real measured Internet data sets to evaluate our design.

There are some existing NC security solutions [4][5] proposed in Vivaldi NC system, which could be our good reference.

Good understanding of C/C++ is necessary for this project.

Reference