THE MPFS PROTOCOL

Specifications:
We create a x packet that contains the following informations, base64 encrypted:
tracker_list = “tcp://tracker.site.net::tcp://tracker.anothersite.net:81::tcp://109.108.95.02:6965”^1,
peer_list = “udp://109.108.58.01:40::udp://98.108.73.24:4545::udp://45.18.78.01:4545”^2,
seed_list = “tcp://109.108.58.01:40::tcp://98.108.73.24:4545::tcp://45.18.78.01:4545”^3,
webseed_list = “http://tracker.site.net::http://tracker.anothersite.net:81::http://109.108.95.02:6965”^4,
file_name = “quantal-ubuntu-gnome-i386-20120902.iso”^5,
file_hash = “d701639597670b7498327787abcbd3649ccd526b”^6,
unique_hash = “9b54ada7928b1e90d2c280a0a9938c0a9da250d9”^7,
full_download = 1^8

_____________________________________________________________________

1: Tracker sends peer_list, seed_list like in the torrent protocol plus tracker_list and webseed_list.
2: Where we can send file parts from UDP connections. No more than 1Mb/sec.
3: Where we can receive file parts from TCP connections. No more than 1Mb/sec.
4: Like the seed_list, but HTTP protocol and more than 1Mb/sec.
5: The file name, for displaying.
6: File hash, for verification purpose (sha1(file_name)).
7: Unique hash, again, for verification purpose (sha1(file_name + ‘.’ + size + ‘.’ timestamp)).
8: If 1: we don’t need to ask for seeds nor webseeds anymore, else yes.