MPLS AND ITS APPLICATION

Real-time and multimedia applications have grown enormously during the last few years. Such applications require guaranteed bandwidth in a packet switched networks. Moreover, these applications require that the guaranteed bandwidth remains available when a node or a link in the network fails. Multiprotocol Label Switching (MPLS) networks cater to these requirements without compromising scalability. Guaranteed service and protection against failures in an MPLS network requires backup paths to be present in the network. Such backup paths are computed and installed at the same time a primary is provisioned. This thesis explains the single-layer restoration routing by placing primary as well as backup paths in MPLS networks. Our focus will be on computing and establishing backup paths, and bandwidth sharing along such backup paths. We will start by providing a quick overview of MPLS routing. We will identify the elements and quantities that are significant to the understanding of MPLS restoration routing. To this end, we will introduce the information locally stored at MPLS nodes and information propagated through routing protocols, in order to assist in efficient restoration routing. L2VPNs and VPLS will also be covered in the end of this thesis. In the end SDN (software defined networks) will be introduced

Análise e otimização da tecnologia MPLS na rede da Universidade do Porto

O presente relatório de projeto foi realizado em ambiente profissional, no âmbito do Mestrado em Tecnologias da Informação, Comunicação e Multimédia do Instituto Universitário da Maia – ISMAI, e teve como principal objetivo o estudo da tecnologia MPLS, e restruturação da mesma, na rede de comunicação de dados da Universidade do Porto. Para tal, a opção metodológica adotada foi a de Action-Research.N/

Performance evaluation of HIP-based network security solutions

Abstract. Host Identity Protocol (HIP) is a networking technology that systematically separates the identifier and locator roles of IP addresses and introduces a Host Identity (HI) name space based on a public key security infrastructure. This modification offers a series of benefits such as mobility, multi-homing, end-to-end security, signaling, control/data plane separation, firewall security, e.t.c. Although HIP has not yet been sufficiently applied in mainstream communication networks, industry experts foresee its potential as an integral part of next generation networks. HIP can be used in various HIP-aware applications as well as in traditional IP-address-based applications and networking technologies, taking middle boxes into account. One of such applications is in Virtual Private LAN Service (VPLS), VPLS is a widely used method of providing Ethernet-based Virtual Private Network that supports the connection of geographically separated sites into a single bridged domain over an IP/MPLS network. The popularity of VPLS among commercial and defense organizations underscores the need for robust security features to protect both data and control information. After investigating the different approaches to HIP, a real world testbed is implemented. Two experiment scenarios were evaluated, one is performed on two open source Linux-based HIP implementations (HIPL and OpenHIP) and the other on two sets of enterprise equipment from two different companies (Tempered Networks and Byres Security). To account for a heterogeneous mix of network types, the Open source HIP implementations were evaluated on different network environments, namely Local Area Network (LAN), Wireless LAN (WLAN), and Wide Area Network (WAN). Each scenario is tested and evaluated for performance in terms of throughput, latency, and jitter. The measurement results confirmed the assumption that no single solution is optimal in all considered aspects and scenarios. For instance, in the open source implementations, the performance penalty of security on TCP throughput for WLAN scenario is less in HIPL than in OpenHIP, while for WAN scenario the reverse is the case. A similar outcome is observed for the UDP throughput. However, on latency, HIPL showed lower latency for all three network test scenarios. For the legacy equipment experiment, the penalty of security on TCP throughput is about 19% compared with the non-secure scenario while latency is increased by about 87%. This work therefore provides viable information for researchers and decision makers on the optimal solution to securing their VPNs based on the application scenarios and the potential performance penalties that come with each approach.HIP-pohjaisten tietoliikenneverkkojen turvallisuusratkaisujen suorituskyvyn arviointi. Tiivistelmä. Koneen identiteettiprotokolla (HIP, Host Identity Protocol) on tietoliikenneverkkoteknologia, joka käyttää erillistä kerrosta kuljetusprotokollan ja Internet-protokollan (IP) välissä TCP/IP-protokollapinossa. HIP erottaa systemaattisesti IP-osoitteen verkko- ja laite-osat, sekä käyttää koneen identiteetti (HI) -osaa perustuen julkisen avainnuksen turvallisuusrakenteeseen. Tämän hyötyjä ovat esimerkiksi mobiliteetti, moniliittyminen, päästä päähän (end-to-end) turvallisuus, kontrolli-informaation ja datan erottelu, kohtaaminen, osoitteenmuutos sekä palomuurin turvallisuus. Teollisuudessa HIP-protokolla nähdään osana seuraavan sukupolven tietoliikenneverkkoja, vaikka se ei vielä olekaan yleistynyt laajaan kaupalliseen käyttöön. HIP–protokollaa voidaan käyttää paitsi erilaisissa HIP-tietoisissa, myös perinteisissä IP-osoitteeseen perustuvissa sovelluksissa ja verkkoteknologioissa. Eräs tällainen sovellus on virtuaalinen LAN-erillisverkko (VPLS), joka on laajasti käytössä oleva menetelmä Ethernet-pohjaisen, erillisten yksikköjen ja yhden sillan välistä yhteyttä tukevan, virtuaalisen erillisverkon luomiseen IP/MPLS-verkon yli. VPLS:n yleisyys sekä kaupallisissa- että puolustusorganisaatioissa korostaa vastustuskykyisten turvallisuusominaisuuksien tarpeellisuutta tiedon ja kontrolliinformaation suojauksessa. Tässä työssä tutkitaan aluksi HIP-protokollan erilaisia lähestymistapoja. Teoreettisen tarkastelun jälkeen käytännön testejä suoritetaan itse rakennetulla testipenkillä. Tarkasteltavat skenaariot ovat verrata Linux-pohjaisia avoimen lähdekoodin HIP-implementaatioita (HIPL ja OpenHIP) sekä verrata kahden eri valmistajan laitteita (Tempered Networks ja Byres Security). HIP-implementaatiot arvioidaan eri verkkoympäristöissä, jota ovat LAN, WLAN sekä WAN. Kaikki testatut tapaukset arvioidaan tiedonsiirtonopeuden, sen vaihtelun (jitter) sekä latenssin perusteella. Mittaustulokset osoittavat, että sama ratkaisu ei ole optimaalinen kaikissa tarkastelluissa tapauksissa. Esimerkiksi WLAN-verkkoa käytettäessä turvallisuuden aiheuttama häviö tiedonsiirtonopeudessa on HIPL:n tapauksessa OpenHIP:iä pirnempi, kun taas WAN-verkon tapauksessa tilanne on toisinpäin. Samanlaista käyttäytymistä havaitaan myös UDP-tiedonsiirtonopeudessa. HIPL antaa kuitenkin pienimmän latenssin kaikissa testiskenaarioissa. Eri valmistajien laitteita vertailtaessa huomataan, että TCP-tiedonsiirtonopeus huononee 19 ja latenssi 87 prosenttia verrattuna tapaukseen, jossa turvallisuusratkaisua ei käytetä. Näin ollen tämän työn tuottama tärkeä tieto voi auttaa alan toimijoita optimaalisen verkkoturvallisuusratkaisun löytämisessä VPN-pohjaisiin sovelluksiin

Next generation control of transport networks

It is widely understood by telecom operators and industry analysts that bandwidth demand is increasing dramatically, year on year, with typical growth figures of 50% for Internet-based traffic [5]. This trend means that the consumers will have both a wide variety of devices attaching to their networks and a range of high bandwidth service requirements. The corresponding impact is the effect on the traffic engineered network (often referred to as the “transport network”) to ensure that the current rate of growth of network traffic is supported and meets predicted future demands. As traffic demands increase and newer services continuously arise, novel network elements are needed to provide more flexibility, scalability, resilience, and adaptability to today’s transport network. The transport network provides transparent traffic engineered communication of user, application, and device traffic between attached clients (software and hardware) and establishing and maintaining point-to-point or point-to-multipoint connections. The research documented in this thesis was based on three initial research questions posed while performing research at British Telecom research labs and investigating control of transport networks of future transport networks: 1. How can we meet Internet bandwidth growth yet minimise network costs? 2. Which enabling network technologies might be leveraged to control network layers and functions cooperatively, instead of separated network layer and technology control? 3. Is it possible to utilise both centralised and distributed control mechanisms for automation and traffic optimisation? This thesis aims to provide the classification, motivation, invention, and evolution of a next generation control framework for transport networks, and special consideration of delivering broadcast video traffic to UK subscribers. The document outlines pertinent telecoms technology and current art, how requirements I gathered, and research I conducted, and by which the transport control framework functional components are identified and selected, and by which method the architecture was implemented and applied to key research projects requiring next generation control capabilities, both at British Telecom and the wider research community. Finally, in the closing chapters, the thesis outlines the next steps for ongoing research and development of the transport network framework and key areas for further study

Teleprotection signalling over an IP/MPLS network

Protection of electricity networks have developed to incorporate communications, referred to as protection signalling. Due to the evolution of the electricity supply system, there are many developments pending within the scope of protection signalling and protection engineering in general. This project investigates the use of current and emerging communications technologies (i.e. packetised networks) being applied and incorporated into current protection signalling schemes and technologies. The purpose of the project is to provide a more cost-effective solution to protection schemes running obsolescent hardware. While the medium-term goal of the industry is to move entirely to IEC 61850 communications, legacy teleprotection relays using non-IP communications will still exist for many years to come. For companies to be ready for an IEC 61850 rollout a fully deployed IP/MPLS network will be necessary and it can be seen that various companies worldwide are readying themselves in this way. However, in the short-term for these companies, this means maintaining their existing TDM network (which runs current teleprotection schemes) and IP/MPLS network. This is a costly business outcome that can be minimised with the migration of services from and decommissioning of TDM networks. Network channel testing was the primary testing focus of the project. The testing proved that teleprotection traffic with correct QoS markings assured the system met latency and stability requirements. Furthermore, MPLS resiliency features (secondary LSPs & Fast-reroute) were tested and proved automatic path failover was possible under fault conditions at sub-30ms speeds

Concepção e implementação de experiências laboratoriais sobre MPLS

Mestrado em Engenharia Electrónica e TelecomunicaçõesO Multiprotocol Label Switching (MPLS) é um mecanismo de transporte de dados, sob a forma de um protocolo agnóstico, com grande potencial de crescimento e adequação. Opera na “Camada 2.5” do modelo OSI e constitui um mecanismo de alto desempenho utilizado nas redes de núcleo para transportar dados de um nó da rede para outro. O sucesso do MPLS resulta do facto de permitir que a rede transporte todos os tipos de dados, desde tráfego IP a tráfego da camada de ligação de dados, devido ao encapsulamento dos pacotes dos diversos protocolos, permitindo a criação de “links virtuais” entre nós distantes. O MPLS pertence à família das “redes de comutação de pacotes”, sendo os pacotes de dados associados a “etiquetas” que determinam o seu encaminhamento, sem necessidade de examinar o conteúdo dos próprios pacotes. Isto permite a criação de circuitos “extremo-aextremo” através de qualquer tipo de rede de transporte e independentemente do protocolo de encaminhamento que é utilizado. O projecto do MPLS considera múltiplas tecnologias no sentido de prestar um serviço único de transporte de dados, tentando simultaneamente proporcionar capacidades de engenharia de tráfego e controlo “out-of-band”, uma característica muito atraente para uma implementação em grande escala. No fundo, o MPLS é uma forma de consolidar muitas redes IP dentro de uma única rede. Dada a importância desta tecnologia, é urgente desenvolver ferramentas que permitam entender melhor a sua complexidade. O MPLS corre normalmente nas redes de núcleo dos ISPs. No sentido de tornar o seu estudo viável, recorreu-se nesta dissertação à emulação para implementar cenários de complexidade adequada. Existem actualmente boas ferramentas disponíveis que permitem a recriação em laboratório de cenários bastante complicados. Contudo, a exigência computacional da emulação é proporcional à complexidade do projecto em questão, tornando-se rapidamente impossível de realizar numa única máquina. A computação distribuída ou a “Cloud Computing” são actualmente as abordagens mais adequadas e inovadoras apara a resolução deste problema. Esta dissertação tem como objectivo criar algumas experiências em laboratório que evidenciam aspectos relevantes da tecnologia MPLS, usando para esse efeito um emulador computacional, o Dynamips, impulsionado por generosas fontes computacionais disponibilizadas pela Amazon ec2. A utilização destas ferramentas de emulação permite testar cenários de rede e serviços reais em ambiente controlado, efectuando o debugging das suas configurações e optimizando o seu desempenho, antes de os colocar em funcionamento nas redes em operação.The Multiprotocol Label Switching (MPLS) is a highly scalable and agnostic protocol to carry network data. Operating at "Layer 2.5" of the OSI model, MPLS is an highperformance mechanism that is used at the network backbone for conveying data from one network node to the next. The success of MPLS results from the fact that it enables the network to carry all kinds of traffic, ranging from IP to layer 2 traffic, since it encapsulates the packets of the diverse network protocols, allowing the creation of "virtual links" between distant nodes. MPLS belongs to the family of packet switched networks, where labels are assigned to data packets that are forwarded based on decisions that rely only on the label contents, without the need to examine the packets contents. This allows the creation of end-to-end circuits across any type of transport medium, using any protocol. The MPLS design takes multiform transport technologies into account to provide a unified data-carrying service, attempting simultaneously to preserve traffic engineering and out-of-band control, a very attractive characteristic for large-scale deployment. MPLS is the way to consolidate many IP networks into a single one. Due to this obvious potential, it is urgent to develop means and tools to better understand its functioning and complexity. MPLS normally runs at the backbone of Service Providers networks, being deployed across an extensive set of expensive equipment. In order to turn the study of MPLS feasible, emulation was considered as the best solution. Currently, there are very good available tools to recreate, in a lab environment, quite complicated scenarios. However, the computational demand of the emulation is proportional to the complexity of the project, becoming quickly unfeasible in a single machine. Fortunately, distributed computing or Cloud computing are suitable and novel approaches to solve this computation problem. So, this work aims to create some lab experiments that can illustrate/demonstrate relevant aspects of the MPLS technology, using the Dynamips emulator driven by the computational resources that were made available by the Amazon ec2 cloud computing facilities. The utilization of these emulation tools allows testing real networks and service scenarios in a controlled environment, being able to debug their configurations and optimize their performance before deploying them in real operating networks

Security Vulnerabilities of the Cisco IOS Implementation of the MPLS Transport Profile

We are interested in the security of the MPLS Transport Profile (MPLS-TP), in the context of smart-grid communication networks. The security guidelines of the MPLS-TP standards are written in a complex and indirect way, which led us to pose as hypothesis that vendor solutions might not implement them satisfactorily. To test this hypothesis, we investigated the Cisco implementation of two MPLS-TP OAM (Operations, Administration, and Maintenance) protocols: bidirectional forwarding detection (BFD), used to detect failures in label-switched paths (LSPs) and protection state coordination (PSC), used to coordinate protection switching. Critical smart grid applications, such as protection and control, rely on the protection switching feature controlled by BFD and PSC. We did find security issues with this implementation. We implemented a testbed with eight nodes that run the MPLS-TP enabled Cisco IOS; we demonstrated that an attacker who has access to only one cable (for two attacks) or two cables (for one attack) is able to harm the network at several points (e.g., disabling both working and protection LSPs). This occurred in spite of us implementing the security guidelines that are available from Cisco for IOS and MPLS-TP. The attacks use forged BFD or PSC messages, which induce a label-edge router (LER) into believing false information about an LSP. In one attack, the LER disables the operational LSP; in another attack, the LER continues to believe that a physically destroyed LSP is up and running; in yet another attack, both operational and backup LSPs are brought down. Our findings suggest that the MPLS-TP standard should be more explicit when it comes to security. For example, to thwart the attacks revealed here, it should mandate either hop by hop authentication (such as MACSec) at every node, or an ad-hoc authentication mechanism for BFD and PSC