packet 360 does not have to be done in stages as described the above description is just a useful heuristic for describing the final product namely the tarp packet note that tarp header ip t could be a completely custom header configuration with no similarity to a normal ip header except that it contain the information identified above this is so since this header is interpreted by only tarp routers the above scheme may be implemented entirely by processes operating between the data link layer and the network layer of each server or terminal participating in the tarp system referring to fig4 a tarp transceiver 405 can be an originating terminal 100 a destination terminal 110 or a tarp router 122 127 in each tarp transceiver 405 a transmitting process is generated to receive normal packets from the network ip layer and generate tarp packets for communication over the network a receiving process is generated to receive normal ip packets containing tarp packets and generate from these normal ip packets which are u201c passed up u201d to the network ip layer note that where the tarp transceiver 405 is a router the received tarp packets 140 are not processed into a stream of ip packets 415 because they need only be authenticated as proper tarp packets and then passed to another tarp router or a tarp destination terminal 110 the intervening process a u201c tarp layer u201d 420 could be combined with either the data link layer 430 or the network layer 410 in either case it would intervene between the data link layer 430 so that the.