QUIC, a general-purpose transport protocol, is receiving growing interest in the context of the Internet of Things (IoT), as researchers have mapped various IoT applications over to QUIC transport. In this paper, we aim to show that since QUIC is so feature-rich on its own, uper-layer complexities of traditional protocols can be greatly reduced or even eliminated. A technology's simplicity and resource frugality are critical for IoT devices. To exemplify this, we have designed a publish-subscribe 'thin-app' for IoT, relying almost entirely on QUIC's specification. We achieved comparable functionality to MQTT, doing away with the need for much of its control messaging. Furthermore, experimentation with our solution against MQTTv5 shows significant reductions in signaling overhead while maintaining comparable CPU and memory utilization.

In this paper, we investigate the Domain Name System (DNS) over QUIC (DoQ) and propose a non-disruptive extension, which can greatly reduce DoQ’s resource consumption. This extension can benefit all DNS clients – especially Internet of Things (IoT) devices. This is important because even resource-constrained IoT devices can generate dozens of DNS requests every hour. DNS is a crucial service that correlates IP addresses and domain names. It is traditionally sent as plain-text, favoring low-latency results over security and privacy. The repercussion of this can be eavesdropping and information leakage about IoT devices. To address these concerns, the newest and most promising solution is DoQ. QUIC offers features similar to TCP and TLS while also supporting early data delivery and stream multiplexing. DoQ’s specification requires that DNS exchanges occur over independent streams in a long-lived QUIC connection. Our hypothesis is that due to DNS’s typically high transaction volume, managing QUIC streams may be overly resource intensive for IoT devices. Therefore, we have designed and implemented a data delivery mode for DoQ using QUIC datagrams, which we believe to be more preferable than stream-based delivery. To test our theory, we analyzed the memory, CPU, signaling, power, and time of each DoQ delivery mode in a setup generating real queries and network traffic. Our novel datagram-based delivery mode proved to be decisively more resource-friendly with little compromise in terms of functionality or performance. Furthermore, our paper is the first to investigate multiple queries over DoQ, to our knowledge.

There has been growing interest in using the QUIC transport protocol for the Internet of Things (IoT). In lossy and high-latency networks, QUIC outperforms TCP and TLS. Since IoT greatly differs from traditional networks in terms of architecture and resources, IoT specific parameter tuning has proven to be of significance. While RFC 9006 offers a guideline for tuning TCP within IoT, we have not found an equivalent for QUIC. This article is the first of our knowledge to contribute empirically based insights toward tuning QUIC for IoT. We improved our pure HTTP/3 publish–subscribe architecture and rigorously benchmarked it against an alternative: MQTT-over-QUIC. To investigate the impact of transport-layer parameters, we ran both applications on Raspberry Pi Zero hardware. Eight metrics were collected while emulating different network conditions and message payloads. We enumerate the points we experimentally identified (notably, relating to authentication, MAX_STREAM messages, and timers) and elaborate on how they can be tuned to improve resource consumption and performance. Our application offered lower latency than MQTT-over-QUIC with slightly higher resource consumption, making it preferable for reliable time-sensitive dissemination of information.

Google’s QUIC (GQUIC) is an emerging transport protocol designed to reduce HTTP latency. Deployed across its platforms and positioned as an alternative to TCP+TLS, GQUIC is feature rich: offering reliable data transmission and secure communication. It addresses TCP+TLS’s (i) Head of Line Blocking (HoLB), (ii) excessive round-trip times on connection establishment, and (iii) entrenchment. Efforts by the IETF are in progress to standardize the next generation of HTTP’s (HTTP/3, or H3) delivery, with their own variant of QUIC. While perfor-mance benchmarks have been conducted between GQUIC and HTTP/2-over-TCP (H2), few analyses, to our knowledge, have taken place between H2 and H3. In addition, past studies rely on Page Load Time as their main, if not only, metric. The purpose of this article is to benchmark the latest draft specification of H3 and dig into a user’s Quality of Experience (QoE) by using Lighthouse: an open-source (and metric diverse) auditing tool. Our findings show that, for one of H3’s early implementations, H3 is mostly worse but achieves a higher average throughput.

Scan based Design for Test (DfT) schemes have been in wide use to increase the testability of digital circuits. The main objective is to ensure that nodes in the Circuit Under Test (CUT) are controllable and observable. While such comprehensive access is highly desirable for testing, it is not acceptable for secure chips as it is subject to exploitation. In this work, a new method is presented to protect the sensitive information from attackers using scan chains. The access through the scan chain to the circuit containing the secret information has been severely limited to reduce the risk of a scan-based attack. To ensure the testability of the circuit, a built-in self-test utilizing an LFSR is considered. The proposed scheme can be used as countermeasure against side channel attacks with a low area overhead as compared to the reported solutions.