Abstract

On the one hand, the correctness of routing protocols in networks is an issue of utmost importance for guaranteeing the delivery of messages from any source to any target. On the other hand, a large collection of routing schemes have been proposed during the last two decades, with the objective of transmitting messages along short routes, while keeping the routing tables small. Regrettably, all these schemes share the property that an adversary may modify the content of the routing tables with the objective of, e.g., blocking the delivery of messages between some pairs of nodes, without being detected by any node. In this paper, we present a simple certification mechanism which enables the nodes to locally detect any alteration of their routing tables. In particular, we show how to locally verify the stretch-3 routing scheme by Thorup and Zwick [SPAA 2001] by adding certificates of $\widetilde{O}(\sqrt{n})$ bits at each node in $n$-node networks, that is, by keeping the memory size of the same order of magnitude as the original routing tables. We also propose a new name-independent routing scheme using routing tables of size $\widetilde{O}(\sqrt{n})$ bits. This new routing scheme can be locally verified using certificates on $\widetilde{O}(\sqrt{n})$ bits. Its stretch is3 if using handshaking, and 5 otherwise.

Highlights

  • It serves as recalling basic notions that will be helpful for the design of our new name-independent routing scheme

  • √ We have shown that it is possible to verify routing schemes based on tables of size O( n) bits using certificates with sizes of the same order of magnitude as the space consumed by the routing tables

  • Our new routing scheme, which is verifiable with certificates on O( n), has stretch 3 only if using handshaking

Read more

Summary

Introduction

A routing scheme is a mechanism enabling to deliver messages from any source to any target in a network. A routing scheme consists of a way of assigning a routing table to every node of the given network. These tables should contain enough information so that, for every target node t, each node is able to compute the port number of the incident edge through which it should forward a message of destination t. One scenario allows the routing scheme to assign names to the nodes, and each target is identified by its given name. The nodes are not provided with sufficient information to detect such an issue locally, that is, by having each node inspecting only the network structure and the tables assigned to nodes in its vicinity

Objective
Definitions
Name-dependent routing scheme
Name-independent Routing Scheme
A New Name-Independent Routing Scheme
Conclusion and Further

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.