P2P Filesharing Population Tracking Based on ... - ETH Zürich

More documents

Recommendations

Info

Polling Remarks Delay to polling < 10 Minutes About 50% unreachable via TCP and port seen by PeerTracker⇒likely behind NAT Other errors: Peer variation (esp. Gnutella), classification into wrong network, tracker error BitTorrent not really pollable Arno Wagner, ETH Zurich, ICISP 2006 – p.15
Legal Aspects (Warning: I am no legal expert) Flow data likely not subject to privacy laws (unless attempts to identify people are made) PeerTracker does not identify content shared ⇒ output unproblematic, no action needs to be taken Identification of heavy hitters unproblematic, since payloads (shared contents) not identified Polling is unproblematic, since similar to running a peer (some users get nervous though...) Arno Wagner, ETH Zurich, ICISP 2006 – p.16
Page 1 and 2: P2P Filesh
Page 3 and 4: Contributors Philipp Jardas, ”<st
Page 5 and 6: The DDoSVax Project http://www.tik.
Page 7 and 8: What is a ”Flow”? In the DDoSVa
Page 9 and 10: PeerTracker Algorithm Idea: ”Trav
Page 11 and 12: PeerTracker: Hosts State Diagram Ar
Page 13 and 14: Validation The PeerTracker does not
Page 15: Polling Results P2P</strong
Page 19 and 20: Conclusion, Remarks Peer identifica

P2P Filesharing Population Tracking Based on ... - ETH Zürich

Create successful ePaper yourself

Delete template?

Save as template?