The Internet of Things (IoT) is expanding rapidly with billions of connected devices worldwide, necessitating robust security solutions to protect these systems. This paper proposes a comprehensive and adaptive security framework called Enhanced Secure Channel Authentication using random forests and software-defined networking (SCAFFOLD), tailored for IoT environments. The framework establishes secure communication channels between IoT nodes using software-defined networking (SDN) and machine learning techniques. The key components include encrypted channels using session keys, continuous traffic monitoring by the SDN controller, ensemble machine-learning for attack detection, precision mitigation via SDN reconfiguration, and periodic reauthentication for freshness. A mathematical model formally defines the protocol. Performance evaluations via extensive simulations demonstrate Enhanced SCAFFOLD’s ability to reliably detect and rapidly mitigate various attacks with minimal latency and energy consumption overheads across diverse IoT network scenarios and traffic patterns. The multidimensional approach combining encryption, intelligent threat detection, surgical response, and incremental hardening provides defense-in-depth to safeguard availability, integrity, and privacy within modern IoT systems while preserving quality of service.

In this research paper, the spatial distributions of five different services—Voice over Internet Protocol (VoIP), Video Conferencing (VC), Hypertext Transfer Protocol (HTTP), and Electronic Mail—are investigated using three different approaches: circular, random, and uniform approaches. The amount of each service varies from one to another. In certain distinct settings, which are collectively referred to as mixed applications, a variety of services are activated and configured at predetermined percentages. These services run simultaneously. Furthermore, this paper has established a new algorithm to assess both the real-time and best-effort services of the various IEEE 802.11 technologies, describing the best networking architecture as either a Basic Service Set (BSS), an Extended Service Set (ESS), or an Independent Basic Service Set (IBSS). Due to this fact, the purpose of our research is to provide the user or client with an analysis that suggests a suitable technology and network configuration without wasting resources on unnecessary technologies or requiring a complete re-setup. In this context, this paper presents a network prioritization framework for enabling smart environments to determine an appropriate WLAN standard or a combination of standards that best supports a specific set of smart network applications in a specified environment. A network QoS modeling technique for smart services has been derived for assessing best-effort HTTP and FTP, and the real-time performance of VoIP and VC services enabled via IEEE 802.11 protocols in order to discover more optimal network architecture. A number of IEEE 802.11 technologies have been ranked by using the proposed network optimization technique with separate case studies for the circular, random, and uniform geographical distributions of smart services. The performance of the proposed framework is validated using a realistic smart environment simulation setting, considering both real-time and best-effort services as case studies with a range of metrics related to smart environments.

The Web of Things (WoT) is a concept that aims to create a network of intelligent devices capable of remote monitoring, service provisioning, and control. Virtual and Physical Internet of Things (IoT) gateways facilitate communication, processing, and storage among social nodes that form the social Web of Things (SWoT). Peripheral IoT services commonly use device data. However, due to the limited bandwidth and processing power of edge devices in the IoT, they must dynamically alter the quality of service provided to their connected clients to meet each user's needs while also meeting the service quality requirements of other devices that may access the same data. Consequently, deciding which transactions get access to which Internet of Things data is a scheduling problem. Edge-cloud computing requires transaction management because several Internet of Things transactions may access shared data simultaneously. However, cloud transaction management methods cannot be employed in edge-cloud computing settings. Transaction management models must be consistent and consider ACIDity of transactions, especially consistency. This study compares three implementation strategies, Edge Host Strategy (EHS), Cloud Host Strategy (CHS), and Hybrid BHS (BHS), which execute all IoT transactions on the Edge host, the cloud, and both hosts, respectively. These transactions affect the Edge hosts as well. An IoTT framework is provided, viewing an Internet of Things transaction as a collection of fundamental and additional subtransactions that loosen atomicity. Execution strategy controls essential and additional subtransactions. The integration of edge and cloud computing demonstrates that the execution approach significantly affects system performance. EHS and CHS can waste wireless bandwidth, while BHS outperforms CHS and EHS in many scenarios. These solutions enable edge transactions to complete without restarting due to outdated IoT data or other edge or cloud transactions. The properties of these approaches have been detailed, showing that they often outperform concurrent protocols and can improve edge-cloud computing.

The impending exhaustion of internet protocol (IP) version four (IPv4) addresses necessitates a transition to the more expansive IP version six (IPv6) protocol. However, this shift faces challenges due to the widespread legacy of IPv4 infrastructure and resistance among organizations to overhaul networks. Host-based translators offer a critical bridging solution by enabling IPv6-only devices to communicate with IPv4-only devices through software-level protocol translation. This paper comprehensively evaluates four pivotal host-based translator mechanisms—bump-in-the-stack (BIS), bump-in-the-application programming interface (API) (BIA), BIA version 2 (BIAv2), and bump-in-the-host (BIH). Using simulated networks with diverse configurations of IPv4/IPv6 applications, hosts, and routing protocols, the authors assessed performance through metrics including packet loss, convergence time, traffic throughput, and overhead. The results reveal variability in effectiveness across both translators and scenarios. BIAv2 demonstrated advantages in throughput and overhead due to stateless mapping. The research underscores the importance of selecting the optimal translation approach for specific network environments and goals. It guides smoother IPv6 adoption by demonstrating how host-based translators can facilitate coexistence during transition. Further exploration of performance tradeoffs can continue guiding effective deployment strategies.

This document specifies a new mechanism called D4across6, which stands for Deploying IPv4-only Connectivity across Local IPv6-only Access Networks. This protocol could be used to ease the process of transition to IPv6 protocol, particularly in the ISPs’ access networks. This protocol allows legacy IPv4-only devices to communicate with IPv4-only content providers over an IPv6-only infrastructure. The main part is an application level tunnelling protocol that allows IPv6-only ISPs to provide IPv4 connectivity in addition to IPv6 connectivity across IPv6-only access networks. It carries IPv4 packets and routing information of the IPv4 protocol over an IPv6-only network infrastructure. The features of the proposed protocol are: offers IPv4 connectivity across IPv6-only access networks, stateless operation, cost-effective solution, and requires simple and automatic configuration at customers’ hosts. D4across6 requires installing an application and a pseudo network driver at the IPv4-only hosts in order to allow them to communicate with IPv4-only content providers. The configured IPv4-only hosts will be able to auto-detect the ISP available connectivity in the following precedence: native IPv6, IPv4-in-IPv6, or no IPv4 connectivity. The protocol does not require replacing or upgrading customer edges. Thus, a minimal cost is expected in providing IPv4-only connectivity after successfully deploying of IPv6 service to subscribers. The simulation analysis showed that the performance metrics of D4across6 is pretty near to those of native IPv6 and IPv4 protocols. Additionally, the performance of D4across6 is better than that of all (A+P), DS-Lite and 4rd protocols.