## 7 Experimental Results
The algorithm, as shown in the flowchart of Figure 4, comprises four main parts: preparation of the benchmarking environment, initiation of remote MQTT over TLS instances on the broker with TLS dumps, execution of the client for data transmission, and summary of data collection at session conclusion. During the message relay process, the \"mqtt_pub_base-qos\" routine captures sending and receiving statistics using the measurement utility. Simultaneously, it establishes a connection as a distant log monitor to access the Mosquito event records stored on the broker system. The process is divided into four primary stages: initial setup of the performance evaluation environment, remote activation of MQTT over TLS on the broker with TLS activity monitoring, client execution for data transmission, and final compilation of gathered information upon session completion. The mqtt_pub_base-qos routine establishes a link as a distant log observer to the broker's Mosquito event records. It employs a metric collection utility to record sending and receiving statistics throughout the message relay process. The client initiates the remote broker on the server via SSH commands, cycling through each supported encryption protocol in OpenSSL 1.x libraries. The server monitors a designated port (1866/TCP in this instance) for one encryption protocol at a time while the client creates connections and verifies server responsiveness. It is interesting to see the statistical distribution of delays illustrated in Figure 6 using a boxplot representation. The results presented in the figure exclude the IEEE 802.3 ab channel, but similar trends were observed in the IEEE 802.11n/ac and 3 GPP-4G configurations. In each boxplot, the 25 th and 75 th percentiles are represented visually by the box boundaries, the 5 th and  
Figure 6: Latency Patterns Analysis for MQTT V3.11 over IEEE 802.3 ab Connection: Examining TLS v1.2 Encryption Protocols at QoS0 Priority Level. The \(\times\) represents the median value. 95 th percentiles by the whiskers, and the median is indicated by an 'X'. Outlier values beyond these percentiles are included to augment the previously reported average values and show the range of delay variance. The ordinate axis is scaled to properly represent the boxplot's general range while improving the visibility of outlier values. As seen in Figure 6, the majority of delay samples fall into a constant range, with a few studies above the 95 th percentile in delay time and outliers offering insights into observed variances in average delay. Figure 7 depicts the comparative bandwidth utilization between standard internet and TOR network communications using TLSv1.2 encryption protocols. The analysis covers all quality of service tiers on an IEEE 802.3 ab connection, employing MQTT V3.11 with a constant payload of 1 Mb. The figure reveals that in the case of the DHE-RSA-AES128-SHA cipher suite, the measured bandwidth percentage difference is the highest at around 13%, while in all other cases, a percentage difference of around 4% is measured. This graph helps us understand the overhead introduced into communication measured in terms of bandwidth loss. We conducted another relevant analysis comparing the percentage difference in bandwidth between messages of 1 MB and 500 KB in size. This analysis helps us understand how message length affects bandwidth utilization. The results, as shown in Figure 8, indicate that doubling the message length results in a bandwidth reduction of approximately 6 percentage points. Figure 8: Percentage difference in bandwidth used to transmit a 1 Mb payload versus a 5 Kb payload over an IEEE 802.3 ab link on the Dark Web with the TLSv1.2 cipher suite for all levels of QoS and MQTT V3.11. Figure 7: The percentage difference in bandwidth between the dark web and the web using TLSv1. With MQTT V3.11 and IEEE 802.3 ab Link, two cipher suites and all QoS levels are supported with a fixed payload size of 1 MB. This analysis helps us understand how the length of a message affects bandwidth.