MétaCan
Menu
Back to cohort
Record W2613257643

A Detailed Classification of Routing Attacks Against RPL in Internet of Things

2017· article· en· W2613257643 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueInternational journal of advance research, ideas and innovations in technology · 2017
Typearticle
Languageen
FieldComputer Science
TopicSecurity in Wireless Sensor Networks
Canadian institutionsHorizon College and Seminary
Fundersnot available
KeywordsComputer scienceComputer networkRouting protocolWireless sensor networkSoftware deploymentRouting (electronic design automation)Computer security
DOInot available

Abstract

fetched live from OpenAlex

With the advancement in mobile computing and wireless communications, a new paradigm called Internet of Things is generating a lot of research interest and the industrial revolution. The increasing interest for this paradigm has resulted in the large-scale deployment of Low power and Lossy Networks (LLN), such as wireless sensor networks and home automation systems. These networks are typically composed of many embedded devices with limited power, memory, and processing resources interconnected by a variety of links, such as IEEE 802.15.4 or low-power Wi-Fi. These networks have a wide scope of applications such as industrial monitoring, connected home, healthcare, environmental monitoring, urban sensor networks, energy management, and assets tracking etc.RFC 7228. In order to address the specific properties and constraints of these networks, RPL (Routing Protocol for low power Lossy network) has been developed by the IETF working group [ROLL WG]. RPL is a lightweight, rank based routing protocol. However, this routing protocol is exposed to various attacks which can significantly impact the network resources and its performance. This paper presents an elaborate classification of the possible attacks against RPL in IoT network. Further, we have analyzed and compared the severity of these attacks.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.002
metaresearch head score (Gemma)0.003
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: Theoretical or conceptual
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.229
Threshold uncertainty score0.410

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.003
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0020.001
Science and technology studies0.0000.001
Scholarly communication0.0000.001
Open science0.0020.001
Research integrity0.0000.001
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.044
GPT teacher head0.387
Teacher spread0.343 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it