The current Internet was designed in the 1970s to allow researchers to access remote computers. Since then, the Internet has grown tremendously, both in number of users as well as in number of supported services. Some of the architectural choices made in the 1970s for a small research network are not optimised for today's global commercial Internet. The IP Networking Lab participates actively in the development of the architecture of the future Internet.

The architecture of today's Internet was mainly designed together with the TCP and IP protocols in the 1970s and early 1980s. During the last years, researchers and funding organisations in America, Europa, Asia have started to work on different alternative architectures for the Internet. Some consider an evolutionnary approach where the Internet architecture would be incrementally modified in a backward compatible manner while other consider that a completely new architecture should be developped to take into account the requirements of today's and tomorrow's Internet.

Overview

Today, most IP networks are still configured manually on a router-by-router basis. This is error-prone and often leads to misconfiguration.

NCGuard is a tool that allows a network architect to apply a safer methodology by generating validated network configuration. NCGuard relies heavily on software engineering techniques.

The source code is available below. Unfortunately, the manual is not yet finished and it may be difficult for you to use this tool without it. I'll do my best to publish it as soon as possible.

To do, describe multipath measurements

Overview

The Internet topology discovery at the IP interface level is mostly based on traceroute. Traceroute servers are located around the world and, based on a large destinations list, probe the network. It has been demonstrated that probing the network in such a way causes redundancy.

In this work, we propose to reduce the amount of required probes by triggering a traceroute based on BGP information. Our BGP guided probing software, once connected to a BGP feed, is able to decide whether a traceroute towards a given prefix must be launched or not.