It can be inferred from the traces and the node graphs constructed by optimizing these node traces, that a “threeway handshake” aided by a synchronized set of clock-based sequential numbers is used to establish a connection. Even in the absence of significant bandwidth consuming applications, the observations seem to indicate that this procedure is normally initiated by one TCP (in the presence of a real-time application, by the end user and in the case of a streaming application, by the client server, also known as the host server, after the initial request has been communicated to the server without the requirement of a packet confirmation, i.e. for instance, some applications start communicating with the user as soon as the application is streamlined to the internet connection to establish a steady stream of data. This request is verified; the node making the request identified, recorded and then responded to by the other TCP (in this case, the client of the essential processes receives a request upon startup and thereby initiates the connection, which must then be received by the end-user, without the need for acknowledgment.
It has been observed that processes requiring acknowledgment form the majority of the essential applications that are still running on the computer, indicating that the collision between two parallel, oppositely oriented streams of data is also a significant factor in determining the network performance. Similar to such collision studies performed on MAC and ALOHA, these collision traces were observed on Wireshark and the results quantified.
An additional observation from this experiment, which is of vital consequence to the experiments following it, is that the procedure is also found to be working if both the TCPs involved in the exchange simultaneously initiate the request and acknowledgement procedures. As in the case of a Gtalk application during startup, when such a simultaneous attempt occurs between the TCPs allotted to two different network nodes, each of the two TCPs receives a “SYN” segment (corresponding to the response to a request). This request is usually a ping from one IP to the other, and its reply carries no acknowledgement after it has sent a “SYN” to the requester in response.