18-08-2014, 02:33 PM
The protocol will provide a simple reliable distribution system that delivers knowledge, literature, art and music to all. It will do so without need for government subsidies, corporate monopolies or buildings on the high street. There are no central servers. The network is based on peers that cooperate independently to make a library of digital content. As such, this protocol will embody a paradigm shift from a world of cooperate overloads to networked producers and consumers.
The protocol will provide a simple reliable distribution system that delivers knowledge, literature, art and music to all. It will do so without need for government subsidies, corporate monopolies or buildings on the high street. There are no central servers. The network is based on peers that cooperate independently to make a library of digital content. As such, this protocol will embody a paradigm shift from a world of cooperate overloads to networked producers and consumers.
TTL stands for Time to Live. Basically, when a packet (or message in our case) is sent out. It is stamped with a TTL, for each host that receives the packet, they decrement the TTL. If the TTL is zero, the packet is dropped, otherwise it is routed to the next host in the route. Our protocol TTLs work similarly. When a NEW message is sent from your host, the TTL is set to whatever you have set in your config. TTL MY TTL setting. When the packet is received by the next host in line the TTL is decremented. Then that TTL is checked against that host’s Config/TTL/Max TTL setting. The lower of the two numbers is placed in the outgoing TTL field. If the outgoing TTL is zero, the packet is dropped [Capn’s note: I’m not positive about this next part] then the Hops field of the message is incremented and checked. If this number is greater than the Max TTL setting, the packet is dropped [End Capn’s Note]. This method means that even if you set your TTL to 255 (maximum value), odds are the TTL will be set to the default (5) by the next host in your chain.