2,795 research outputs found
Implementation and Deployment of a Distributed Network Topology Discovery Algorithm
In the past few years, the network measurement community has been interested
in the problem of internet topology discovery using a large number (hundreds or
thousands) of measurement monitors. The standard way to obtain information
about the internet topology is to use the traceroute tool from a small number
of monitors. Recent papers have made the case that increasing the number of
monitors will give a more accurate view of the topology. However, scaling up
the number of monitors is not a trivial process. Duplication of effort close to
the monitors wastes time by reexploring well-known parts of the network, and
close to destinations might appear to be a distributed denial-of-service (DDoS)
attack as the probes converge from a set of sources towards a given
destination. In prior work, authors of this report proposed Doubletree, an
algorithm for cooperative topology discovery, that reduces the load on the
network, i.e., router IP interfaces and end-hosts, while discovering almost as
many nodes and links as standard approaches based on traceroute. This report
presents our open-source and freely downloadable implementation of Doubletree
in a tool we call traceroute@home. We describe the deployment and validation of
traceroute@home on the PlanetLab testbed and we report on the lessons learned
from this experience. We discuss how traceroute@home can be developed further
and discuss ideas for future improvements
Proof-of-Concept Implementation of the Ahoy Discovery Protocol for Ad-hoc Networks
The context discovery protocol Ahoy has been proposed ear- lier for resource-limited fully-distributed ad-hoc networks. Ahoy has been proven as an efficient context discovery pro- tocol, which generates only little network traffic, in both static and dynamic ad-hoc networks. In this report, we im- plement the prototype of Ahoy and test it on UNIX-like platforms. We show the possibility to implement Ahoy in the real world
Evolving SDN for Low-Power IoT Networks
Software Defined Networking (SDN) offers a flexible and scalable architecture
that abstracts decision making away from individual devices and provides a
programmable network platform. However, implementing a centralized SDN
architecture within the constraints of a low-power wireless network faces
considerable challenges. Not only is controller traffic subject to jitter due
to unreliable links and network contention, but the overhead generated by SDN
can severely affect the performance of other traffic. This paper addresses the
challenge of bringing high-overhead SDN architecture to IEEE 802.15.4 networks.
We explore how traditional SDN needs to evolve in order to overcome the
constraints of low-power wireless networks, and discuss protocol and
architectural optimizations necessary to reduce SDN control overhead - the main
barrier to successful implementation. We argue that interoperability with the
existing protocol stack is necessary to provide a platform for controller
discovery and coexistence with legacy networks. We consequently introduce
{\mu}SDN, a lightweight SDN framework for Contiki, with both IPv6 and
underlying routing protocol interoperability, as well as optimizing a number of
elements within the SDN architecture to reduce control overhead to practical
levels. We evaluate {\mu}SDN in terms of latency, energy, and packet delivery.
Through this evaluation we show how the cost of SDN control overhead (both
bootstrapping and management) can be reduced to a point where comparable
performance and scalability is achieved against an IEEE 802.15.4-2012 RPL-based
network. Additionally, we demonstrate {\mu}SDN through simulation: providing a
use-case where the SDN configurability can be used to provide Quality of
Service (QoS) for critical network flows experiencing interference, and we
achieve considerable reductions in delay and jitter in comparison to a scenario
without SDN
Case Study - IPv6 based building automation solution integration into an IPv4 Network Service Provider infrastructure
The case study presents a case study describing an Internet Protocol (IP) version 6 (v6) introduction to an IPv4 Internet Service Provider (ISP) network infrastructure. The case study driver is an ISP willing to introduce a new âkillerâ service related to Internet of Things (IoT) style building automation. The provider and cooperation of third party companies specialized in building automation will provide the service. The ISP has to deliver the network access layer and to accommodate the building automation solution traffic throughout its network infrastructure. The third party companies are system integrators and building automation solution vendors. IPv6 is suitable for such solutions due to the following reasons. The operator canât accommodate large number of IPv4 embedded devices in its current network due to the lack of address space and the fact that many of those will need clear 2 way IP communication channel.
The Authors propose a strategy for IPv6 introduction into operator infrastructure based on the current network architecture present service portfolio and several transition mechanisms. The strategy has been applied in laboratory with setup close enough to the current operatorâs network. The criterion for a successful experiment is full two-way IPv6 application layer connectivity between the IPv6 server and the IPv6 Internet of Things (IoT) cloud
IETF standardization in the field of the Internet of Things (IoT): a survey
Smart embedded objects will become an important part of what is called the Internet of Things. However, the integration of embedded devices into the Internet introduces several challenges, since many of the existing Internet technologies and protocols were not designed for this class of devices. In the past few years, there have been many efforts to enable the extension of Internet technologies to constrained devices. Initially, this resulted in proprietary protocols and architectures. Later, the integration of constrained devices into the Internet was embraced by IETF, moving towards standardized IP-based protocols. In this paper, we will briefly review the history of integrating constrained devices into the Internet, followed by an extensive overview of IETF standardization work in the 6LoWPAN, ROLL and CoRE working groups. This is complemented with a broad overview of related research results that illustrate how this work can be extended or used to tackle other problems and with a discussion on open issues and challenges. As such the aim of this paper is twofold: apart from giving readers solid insights in IETF standardization work on the Internet of Things, it also aims to encourage readers to further explore the world of Internet-connected objects, pointing to future research opportunities
- âŠ