Timestamp utilization in Trust-ND mechanism for securing Neighbor Discovery Protocol
Bibliographic record
Abstract
Trust-ND is an alternative lightweight security mechanism based on distributed trust management model to secure IPv6 Neighbor Discovery Protocol. Trust-ND introduced a new NDP option, called Trust option, with three fields: Message Generation Time (or timestamp), Nonce, and Message Authentication Data. A thorough investigation and analysis of the use of timestamp field has identified four scenarios which could result in Denial-of-Service (DoS) as well as a source of inefficiency. DoS is triggered when two or more IPv6 nodes in the same link have unsynchronized clocks with large time difference between them due to the use of local clock, attack on the synchronization mechanism, misconfiguration or faulty clock. DoS could also occurs as the result of faulty validation process caused by the inability of the timestamp to capture and represent two distinct messaging events due to insufficient granularity or lack of precision of the timestamp format. This paper presents measures to overcome the issue of DoS by proposing a change to the reference time to use Coordinated Universal Time (UTC); modification to the Trust-ND validation process to solve the problem of unsynchronized clocks among nodes; and a new timestamp format to increase the precision to correctly represent and distinguish two events occurring in less than hundredths of a second.
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.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.003 | 0.007 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.002 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.002 | 0.004 |
| Open science | 0.002 | 0.003 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.001 | 0.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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".