Practical Evaluation of a Network Mobility Solution

IFIP International Workshop on Networked Applications, Colmenarejo, Madrid/Spain, 6–8 July, 2005As the demand of ubiquitous Internet access and the current trend of all-IP communications keep growing, the necessity of a protocol that provides mobility management increases. The IETF has specified protocols to provide mobility support to individual nodes and networks. The Network Mobility (NEMO) Basic Support protocol is designed for providing mobility at IP level to complete networks, allowing a Mobile Network to change its point of attachment to the Internet, while maintaining ongoing sessions of the nodes of the network. All the mobility management is done by the mobile router whilst the nodes of the network are not even aware of the mobility. The main aim of this article is evaluating the performance of the NEMO Basic Support protocol by using our implementation. We also discuss the design of an implementation of the NEMO Basic Support protocol.Publicad

End-Site Routing Support for IPv6 Multihoming

Multihoming is currently widely used to provide fault tolerance and traffic engineering capabilities. It is expected that, as telecommunication costs decrease, its adoption will become more and more prevalent. Current multihoming support is not designed to scale up to the expected number of multihomed sites, so alternative solutions are required, especially for IPv6. In order to preserve interdomain routing scalability, the new multihoming solution has to be compatible with Provider Aggregatable addressing. However, such addressing scheme imposes the configuration of multiple prefixes in multihomed sites, which in turn causes several operational difficulties within those sites that may even result in communication failures when all the ISPs are working properly. In this paper we propose the adoption of Source Address Dependent routing within the multihomed site to overcome the identified difficulties.Publicad

Preserving Established Communications in IPv6 Multi-homed Sites with MEX

This research was supported by the SAM (Advanced Mobility Services) project, funded by the Spanish National R&D Programme under contract MCYT TIC2002-04531-C04-03.A proper support for multimedia communications transport has to provide fault tolerance capabilities such as the preservation of established connections in case of failures. While multi-homing addresses this issue, the currently available solution based in massive BGP route injection presents serious scalability limitations, since it contributes to the exponential growth of the BGP table size. Alternative solutions proposed for IPv6 fail to provide equivalent facilities to the current BGP based solution. In this paper we present MEX (Muti-homing through EXtension header) a novel proposal for the provision of IPv6 multi-homing capabilities. MEX preserves overall scalability by storing alternative route information in end-hosts while at the same time reduces packet loss by allowing routers to re-route in-course packets. This behavior is enabled by conveying alternative route information within packets inside a newly defined Extension Header. The resulting system provides fault tolerance capabilities and preserves scalability, while the incurred costs, namely deployment and packet overhead, are only imposed to those that benefit from it. An implementation of the MEX host and router components is also presented.Publicad

Técnicas para el despliegue de IPv6 en redes LAN

El crecimiento de Internet registrado a lo largo de los, aproximadamente, últimos 20 años trajo consigo el problema del agotamiento de las direcciones IPv4 (Internet Protocol versión 4). Como solución a este problema, el IETF (Internet Engineering Task Force) propuso la adopción de un nuevo protocolo al que se denominó IPv6 (Internet Protocolo versión 6). Lentamente, desde hace varios años, IPv6 está reemplazando a IPv4 en Internet mediante la aplicación de variadas técnicas de transición. Hoy coexisten en Internet ambos protocolos. El avance del despliegue de IPv6 en Internet no es uniforme a nivel mundial y existen regiones en las cuales todavía este no es importante. Este es el caso de la Argentina. Este trabajo tiene como propósito principal aportar información que facilite e incentive el despliegue de IPv6 en redes de área local (LAN – Local Area Network) como forma de mejorar la penetración del nuevo protocolo tanto en ámbitos académicos, pequeñas organizaciones en general y en el hogar. La poca comprensión del nuevo protocolo y su tardía adopción en nuestras redes podría traer como consecuencia elevados costos derivados de apresurados despliegues y, en el peor de los casos, pérdidas de conectividad a sitios de Internet que solo operen con IPv6.Eje: Arquitecturas, Redes y Sistemas Operativos.Red de Universidades con Carreras en Informátic

Técnicas para el despliegue de IPv6 en redes LAN

El crecimiento de Internet registrado a lo largo de los, aproximadamente, últimos 20 años trajo consigo el problema del agotamiento de las direcciones IPv4 (Internet Protocol versión 4). Como solución a este problema, el IETF (Internet Engineering Task Force) propuso la adopción de un nuevo protocolo al que se denominó IPv6 (Internet Protocolo versión 6). Lentamente, desde hace varios años, IPv6 está reemplazando a IPv4 en Internet mediante la aplicación de variadas técnicas de transición. Hoy coexisten en Internet ambos protocolos. El avance del despliegue de IPv6 en Internet no es uniforme a nivel mundial y existen regiones en las cuales todavía este no es importante. Este es el caso de la Argentina. Este trabajo tiene como propósito principal aportar información que facilite e incentive el despliegue de IPv6 en redes de área local (LAN – Local Area Network) como forma de mejorar la penetración del nuevo protocolo tanto en ámbitos académicos, pequeñas organizaciones en general y en el hogar. La poca comprensión del nuevo protocolo y su tardía adopción en nuestras redes podría traer como consecuencia elevados costos derivados de apresurados despliegues y, en el peor de los casos, pérdidas de conectividad a sitios de Internet que solo operen con IPv6.Eje: Arquitecturas, Redes y Sistemas Operativos.Red de Universidades con Carreras en Informátic

A Repeater Encryption Unit for IPv4 and IPv6

IPsec is a powerful mechanism for protecting network communications. However, it is often viewed as difficult to use due to the elaborate configuration that is needed to ensure correct (and secure) operation. In this paper, we seek to answer the question of how to build IPsec VPNs without affecting the network assets. We exploit "repeater-encryption", which is similar to the IPsec bump-in-the-wire mode of operation. Our IPsec encryption unit works at Layer-2 of the network stack and does not encrypt control packets that are used for routing, address resolution and resource reservation. Although this is fairly straightforward for IPv4 networks, IPv6 introduces several new features and messages that complicate the operation of such a box. We report our findings of implementing transparent, repeater-based IPsec protection for IPv4 and IPv6. Our approach requires no configuration changes to other devices in the network, making it an attractive mechanism for security network traffic. We discuss the features of our IPsec encryption unit and show how it adapts to IPv4 and IPv6 networks. We also implement our approach on the OpenBSD IPsec stack to demonstrate its feasibility. We show that our transparent IPsec box can easily support speeds in excess of 100 Mbps

Checking-in on Network Functions

When programming network functions, changes within a packet tend to have consequences---side effects which must be accounted for by network programmers or administrators via arbitrary logic and an innate understanding of dependencies. Examples of this include updating checksums when a packet's contents has been modified or adjusting a payload length field of a IPv6 header if another header is added or updated within a packet. While static-typing captures interface specifications and how packet contents should behave, it does not enforce precise invariants around runtime dependencies like the examples above. Instead, during the design phase of network functions, programmers should be given an easier way to specify checks up front, all without having to account for and keep track of these consequences at each and every step during the development cycle. In keeping with this view, we present a unique approach for adding and generating both static checks and dynamic contracts for specifying and checking packet processing operations. We develop our technique within an existing framework called NetBricks and demonstrate how our approach simplifies and checks common dependent packet and header processing logic that other systems take for granted, all without adding much overhead during development.Comment: ANRW 2019 ~ https://irtf.org/anrw/2019/program.htm

Técnicas para el despliegue de IPv6 en redes LAN

El crecimiento de Internet registrado a lo largo de los, aproximadamente, últimos 20 años trajo consigo el problema del agotamiento de las direcciones IPv4 (Internet Protocol versión 4). Como solución a este problema, el IETF (Internet Engineering Task Force) propuso la adopción de un nuevo protocolo al que se denominó IPv6 (Internet Protocolo versión 6). Lentamente, desde hace varios años, IPv6 está reemplazando a IPv4 en Internet mediante la aplicación de variadas técnicas de transición. Hoy coexisten en Internet ambos protocolos. El avance del despliegue de IPv6 en Internet no es uniforme a nivel mundial y existen regiones en las cuales todavía este no es importante. Este es el caso de la Argentina. Este trabajo tiene como propósito principal aportar información que facilite e incentive el despliegue de IPv6 en redes de área local (LAN – Local Area Network) como forma de mejorar la penetración del nuevo protocolo tanto en ámbitos académicos, pequeñas organizaciones en general y en el hogar. La poca comprensión del nuevo protocolo y su tardía adopción en nuestras redes podría traer como consecuencia elevados costos derivados de apresurados despliegues y, en el peor de los casos, pérdidas de conectividad a sitios de Internet que solo operen con IPv6.Eje: Arquitecturas, Redes y Sistemas Operativos.Red de Universidades con Carreras en Informátic

A Repeater Encryption Unit for IPv4 and IPv6

IPsec is a powerful mechanism for protecting network communications. However, it is often viewed as difficult to use due to the elaborate configuration that is needed to ensure correct (and secure) operation. In this paper, we seek to answer the question of how to build IPsec VPNs without affecting the network assets. We exploit "repeater-encryption", which is similar to the IPsec bump-in-the-wire mode of operation. Our IPsec encryption unit works at Layer-2 of the network stack and does not encrypt control packets that are used for routing, address resolution and resource reservation. Although this is fairly straightforward for IPv4 networks, IPv6 introduces several new features and messages that complicate the operation of such a box. We report our findings of implementing transparent, repeater-based IPsec protection for IPv4 and IPv6. Our approach requires no configuration changes to other devices in the network, making it an attractive mechanism for security network traffic. We discuss the features of our IPsec encryption unit and show how it adapts to IPv4 and IPv6 networks. We also implement our approach on the OpenBSD IPsec stack to demonstrate its feasibility. We show that our transparent IPsec box can easily support speeds in excess of 100 Mbps