DOCSLIB.ORG

Intent NBI for Software Defined Networking

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Intent NBI for Software Defined Networking Intent NBI for Software Defined Networking Intent NBI for Software Defined Networking 1 SDN NBI Challenges According to the architecture definition in Open Networking Foundation (ONF), a Software Defined Network (SDN) includes three vertically separated layers: infrastructure, control and application. The North-Bound Interface (NBI), located between the control plane and the applications, is essential to enable the application innovations and nourish the eco-system of SDN by abstracting the network capabilities/information and opening the abstract/logic network to applications. Traditional NBI used to pay more attention on the function layer. The Functional NBI is usually designed by the network domain experts from the network system point of view. The network capabilities are abstracted and encapsulated from bottom up. This kind of design does not take care of the requirement from user side, but expose network information and capability as much as possible. In this way, applications can get maximum programmability from the functional NBI. The examples of functional NBI include: device and link discovery, ID assignment for network interfaces, configuration of forwarding rules, and management of tens of thousands of network state information. However, let’s look from the application developer’s point of view, and assume that they are not familiar with the complex network concepts and configurations. The application developers want to focus on the functionality of the application and the friendly interaction with application users. The network service is required to be used as easy and automatic as the cloud services. The network function is required to be flexible, available and scalable. All this requires the network to have a set of service oriented, declarative, and intent based NBI. For instance, “create a connection between site A and B”, “provide the Service Level Agreement (SLA) for my Data Center Interconnection (DCI)”, “apply a Service Function Chain (SFC) for my internet access from my Virtual Data Center (vDC)”. The complexity of the network service interface is the pain point of the application developers. Complexity is the enemy of the scalability. Complexity makes the interface not easy to use. Intent NBI for Software Defined Networking Complexity makes the application development error-prone. Complexity blocks the innovation of network service related applications. The way to solve the complexity is to add a declarative network middle-ware on top of the controller platform, and tell the controller what the application want but not how to do by using the Intent NBI. It captures the application intent, converts to the domain and dedicated technique specific configuration details, while concealing the complex translation. Application Application Application Application Application Application Application Application Intent … … Declarative Network Middleware Specific Domain Controller Platform Controller Platform Details Data path Data path Data path Data path Data path Data path 2 What’s Intent NBI? In order to simplify the interaction between the network service consuming application and the controller, the control plane should provide an Intent NBI level. Intent NBI is independent with specific network technology, while providing application related terms and vocabulary, so that users do not see VPN, MPLS, and any other routing protocols. Intent NBI abstracts the network objects and capabilities, and expresses the user’s intent on what to do declaratively, but not how to do. Intent NBI express the expected service that the controller delivers. The SDN controller is a “black box” for resource allocation and management. Let’s take the taxi service in real life for example. One passenger wants to take the taxi from A place to B place. He does not have to know how to go there, but to tell the driver: “Hey, I want to go to B.” That’s it. The message only carries what the passenger want. The passenger also does not have to tell the driver why he wants to go to B, because this is not the passenger’s intent. We Intent NBI for Software Defined Networking can also find similar examples in network domain. Intent NBI benefits applications and the development. • Intent description is declarative, not designates the way for execution. The SDN controller can calculate the optimal result to fulfill the intent request. • Intent request is independent of the controller platforms and implementations. It only expresses the requirements for the application layer, and uses application related vocabulary and information. One intent request can be implemented on different controller with various algorithms. This enables portable applications. • Intent NBI helps applications to reduce conflict on higher level, so that increases the success of requests. For example, a typical connection needs to assign the network elements on the connection path. And then, the SDN controller sets associated network elements with configurations. However, if there are some governance rules that limit the application to touch one element, the deployment will fail. If we apply intent, the application only express the requirement to create a connection between site A and site B, the SDN controller can automatically calculate an optimal path to avoid the network element. The deployment succeeds! 3 Intent Expression Modeling In order that the SDN controller can understand the intent requests, formalize models are required for intent expression. Let’s firstly conclude the intent expression from our real life. There will be two expression patterns: • The Operation expression, expresses what I want to do. • The Result expression, expresses the expected final state. We can also find the following network domain intents: • I want to CREATE a Network for HR (Customer Facing Node) • I want to BLOCK the http flow (Flow) • I want to ADJUST the bandwidth (Connection) to 10G • I want to AVOID the bandwidth utilization on the connection greater than 80%. (Result) Intent NBI for Software Defined Networking We can generate the following OOR (Object-Operation-Result) model for the intent expression according to above network examples. Intent CFN (Customer Facing Node) Expect State Connection Object Operation Result ServiceFlow Avoid State Condition Action Constraint There are two patterns for intent expression: the Object+Operation and the Object+Result. On the network service layer: • Object, includes: Customer Facing Node (CFN), Connection, and Service Flow. • Operation, describes the expected behavior. It can be generally formalized with “on condition, do action, with the constraint”. • Result, describes the expected state. We can use the clause “expect to achieve the state” or “avoid the state”. 4 Huawei Practice on Intent NBI The NEMO project initiated by Huawei and leading operators keeps leading the Intent NBI practice. It provides life cycle solutions for the intent implementation. NEMO project developed a network service oriented programming language as a novel SDN NBI fashion. It breaks the “funnel” like scenario based NBI by a set of network service oriented primitives based on the above intent expression model. The NEMO language includes 15 simple statements instead of thousands of API, and can flexibly compose most scenarios. NEMO language expresses the user intent with a more intuitive way, so that application developers can only tell the SDN controller what to do, rather than how to do. The NEMO execution engine implements an intelligent network service middleware by concealing the complexity of network implementation and deployment. It translates the high level Intent NBI for Software Defined Networking service intent into the real network deployments, and solves the network conflict on resource and policy. The three layer translation framework innovation simplifies the mapping from intent to deployment. The mapping on each layer is clear, so that third party and new functions and algorithms can be easily integrated into the framework. Moreover, NEMO provides a set of supporting tools, e.g. the sandbox, facilitating testing, simulation, and deployment. Service customization and innovation is one pain point from operators. Based on the generic network operation pattern, NEMO project provides operator business designer with an easy to use network service template functionality. The NEMO language captures the customer intent from various domains, and describes the network requirements. While leaving all the complexities to the SDN controller, NEMO simplifies network design and expedites the service innovation and deployment by optimized software system, automatic resource allocation, network performance monitoring, and conflict solving for both resource and policy. Huawei is working with standard development organizations, e.g., IETF, ONF, and open-source communities to design and development the Intent NBI, intent model, NEMO language syntax, and intent execution engine. .
Load more

Recommended publications
  • Genomics As a Service: a Joint Computing and Networking Perspective
    1 Genomics as a Service: a Joint Computing and Networking Perspective G. Reali1, M. Femminella1,4, E. Nunzi2, and D. Valocchi3 1Dept. of Engineering, University of Perugia, Perugia, Italy 2Dept. of Experimental Medicine, University of Perugia, Perugia, Italy 3Dept. of Electrical and Electronic Engineering, UCL, London, United Kingdom 4Consorzio Interuniversitario per le Telecomunicazioni (CNIT), Italy Abstract—This paper shows a global picture of the deployment intense research. At that time, although the importance of of networked processing services for genomic data sets. Many results was clear, the possibility of handling the human genome current research and medical activities make an extensive use of as a commodity was far from imagination due to costs and genomic data, which are massive and rapidly increasing over time. complexity of sequencing and analyzing complex genomes. They are typically stored in remote databases, accessible by using Internet connections. For this reason, the quality of the available Today the situation is different. The progress of DNA network services could be a significant issue for effectively (deoxyribonucleic acid) sequencing technologies has reduced handling genomic data through networks. A first contribution of the cost of sequencing a human genome, down to the order of this paper consists in identifying the still unexploited features of 1000 € [2]. Since the decrease of these costs is faster that the genomic data that could allow optimizing their networked Moore’s law [4], two main consequences are expected. First, it management. The second and main contribution is a is easy to predict that in few years a lot of applicative and methodological classification of computing and networking alternatives, which can be used to deploy what we call the societal fields, including academia, business, and public health Genomics-as-a-Service (GaaS) paradigm.
    [Show full text]
  • Architecture Overview
    ONAP Architecture Overview Open Network Automation Platform (ONAP) Architecture White Paper 1 Introduction The ONAP project addresses the rising need for a common automation platform for telecommunication, cable, and cloud service providers—and their solution providers—to deliver differentiated network services on demand, profitably and competitively, while leveraging existing investments. The challenge that ONAP meets is to help operators of telecommunication networks to keep up with the scale and cost of manual changes required to implement new service offerings, from installing new data center equipment to, in some cases, upgrading on-premises customer equipment. Many are seeking to exploit SDN and NFV to improve service velocity, simplify equipment interoperability and integration, and to reduce overall CapEx and OpEx costs. In addition, the current, highly fragmented management landscape makes it difficult to monitor and guarantee service-level agreements (SLAs). These challenges are still very real now as ONAP creates its fourth release. ONAP is addressing these challenges by developing global and massive scale (multi-site and multi-VIM) automation capabilities for both physical and virtual network elements. It facilitates service agility by supporting data models for rapid service and resource deployment and providing a common set of northbound REST APIs that are open and interoperable, and by supporting model-driven interfaces to the networks. ONAP’s modular and layered nature improves interoperability and simplifies integration, allowing it to support multiple VNF environments by integrating with multiple VIMs, VNFMs, SDN Controllers, as well as legacy equipment (PNF). ONAP’s consolidated xNF requirements publication enables commercial development of ONAP-compliant xNFs. This approach allows network and cloud operators to optimize their physical and virtual infrastructure for cost and performance; at the same time, ONAP’s use of standard models reduces integration and deployment costs of heterogeneous equipment.
    [Show full text]
  • ISTORE: Introspective Storage for Data-Intensive Network Services
    ISTORE: Introspective Storage for Data-Intensive Network Services Aaron Brown, David Oppenheimer, Kimberly Keeton, Randi Thomas, John Kubiatowicz, and David A. Patterson Computer Science Division, University of California at Berkeley 387 Soda Hall #1776, Berkeley, CA 94720-1776 {abrown,davidopp,kkeeton,randit,kubitron,patterson}@cs.berkeley.edu Abstract ware [8][9][10][19]. Such maintenance costs are inconsis- Today’s fast-growing data-intensive network services place tent with the entrepreneurial nature of the Internet, in heavy demands on the backend servers that support them. which widely utilized, large-scale network services may be This paper introduces ISTORE, a novel server architecture operated by single individuals or small companies. that couples LEGO-like plug-and-play hardware with a In this paper we turn our attention to the needs of the generic framework for constructing adaptive software that providers of new data-intensive services, and in particular leverages continuous self-monitoring. ISTORE exploits to the need for servers that overcome the scalability and introspection to provide high availability, performance, manageability problems of existing solutions. We argue and scalability while drastically reducing the cost and that continuous monitoring and adaptation, or introspec- complexity of administration. An ISTORE-based server tion, is a crucial component of such servers. Introspective monitors and adapts to changes in the imposed workload systems are naturally self-administering, as they can moni- and to unexpected system events such as hardware failure. tor for exceptional situations or changes in their imposed This adaptability is enabled by a combination of intelligent workload and immediately react to maintain availability self-monitoring hardware components and an extensible and performance goals.
    [Show full text]
  • Framework for Path Finding in Multi-Layer Transport Networks
    UvA-DARE (Digital Academic Repository) Framework for path finding in multi-layer transport networks Dijkstra, F. Publication date 2009 Document Version Final published version Link to publication Citation for published version (APA): Dijkstra, F. (2009). Framework for path finding in multi-layer transport networks. General rights It is not permitted to download or to forward/distribute the text or part of it without the consent of the author(s) and/or copyright holder(s), other than for strictly personal, individual use, unless the work is under an open content license (like Creative Commons). Disclaimer/Complaints regulations If you believe that digital publication of certain material infringes any of your rights or (privacy) interests, please let the Library know, stating your reasons. In case of a legitimate complaint, the Library will make the material inaccessible and/or remove it from the website. Please Ask the Library: https://uba.uva.nl/en/contact, or a letter to: Library of the University of Amsterdam, Secretariat, Singel 425, 1012 WP Amsterdam, The Netherlands. You will be contacted as soon as possible. UvA-DARE is a service provided by the library of the University of Amsterdam (https://dare.uva.nl) Download date:29 Sep 2021 Frame Framework for w ork f or Path Finding in Multi-La Path Finding in Multi-Layer Transport Networks Quebec Amsterdam y er T ranspor StarLight t Netw orks CAnet StarLight MAN LAN NetherLight Fr eek Dijkstra Freek Dijkstra Framework for Path Finding in Multi-Layer Transport Networks Academisch Proefschrift ter verkrijging van de graad van doctor aan de Universiteit van Amsterdam op gezag van de Rector Magnificus Mw.
    [Show full text]
  • The Network Access Machine
    NAT'L INST . OF STAND 4 TECH AlllOS T73fl?b ference National Bureau of Standards MBS Library, E-01 Admin. Bidg. Publi - cations JUN 13 1979 Q1"7 CO 186377 -&f. NBS TECHNICAL NOTE 51 I / US163 U.S. DEPARTMENT OF COMMERCE/ National Bureau of Standards A Review of Network Access Techniques with a Case Study: The Network Access Machine r~- NATIONAL BUREAU OF STANDARDS 1 The National Bureau of Standards was established by an act of Congress March 3, 1901. The Bureau's overall goal is to strengthen and advance the Nation's science and technology and facilitate their effective application for public benefit. To this end, the Bureau conducts research and provides: (1) a basis for the Nation's physical measurement system, (2) scientific and technological services for industry and government, (3) a technical basis for equity in trade, and (4) technical services to promote public safety. The Bureau consists of the Institute for Basic Standards, the Institute for Materials Research, the Institute for Applied Technology, the Institute for Computer Sciences and Technology, and the Office for Information Programs. THE INSTITUTE FOR BASIC STANDARDS provides the central basis within the United States of a complete and consistent system of physical measurement; coordinates that system with measurement systems of other nations; and furnishes essential services leading to accurate and uniform physical measurements throughout the Nation's scientific community, industry, and commerce. The Institute consists of the Office of Measurement Services, the Office of Radiation Measurement and the following Center and divisions: Applied Mathematics — Electricity — Mechanics — Heat — Optical Physics — Center " for Radiation Research: Nuclear Sciences; Applied Radiation — Laboratory Astrophysics " " = — Cryogenics — Electromagnetics — Time and Frequency .
    [Show full text]
  • Designing Cisco Network Service Architectures (ARCH)
    Data Sheet Learning Services Cisco Training on Demand Designing Cisco Network Service Architectures (ARCH) Overview Designing Cisco® Network Service Architectures (ARCH) Version 3.0 is a Cisco Training on Demand course. It enables you to perform the conceptual, intermediate, and detailed design of a network infrastructure that supports desired network solutions over intelligent network services to achieve effective performance, scalability, and availability. It also enables you to provide viable, stable enterprise internetworking solutions by applying solid Cisco network solution models and recommended design practices. By building on the Designing for Cisco Internetwork Solutions (DESGN) Version 3.0 course, you learn additional aspects of modular campus design, advanced addressing and routing designs, WAN service designs, enterprise data center, and security designs. Interested in purchasing this course in volume at discounts for your company? Contact [email protected]. Duration The ARCH Training on Demand is a self-paced course based on the 5-day instructor-led training version. It consists of 40 sections of instructor video and text totaling more than 28 hours of instruction along with interactive activities, 7 hands-on lab exercises, content review questions, and challenge questions. Target Audience This course is designed for network engineers and those preparing for the 300-320 ARCH exam. © 2016 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 1 of 4 Objectives After completing
    [Show full text]
  • Doyle Index.Pdf
    INDEX A AID (area ID), 86 multiple, 269 AAA (authentication, authorization, and IS-IS, 88-90 accounting), 315 algorithms Abramson, Norman, 11 Bellman-Ford, 15, 28 ABRs (area border routers), 149 Dijkstra, 17, 51 accessing policies, 348 DUAL, 35 acknowledgments Ford-Fulkerson, 28 LSAs, 136 metric calculation, 18 LSPs, 148 SPF, 17, 273 Acknowledgment packet, 182 delay, 291-292 acquiring RIDs, 82 equal-cost multipath, 274-286 addresses iSPF calculations, 287-288 BGP summarization, 262 partial route calculations, 290 IPv6 announcement headers, 49 formats, 394-395 ANSI (American National Standards representations, 396-397 Institute), 20 IS-IS summarization, 261 Anycast addresses, 394 NSAP, 88 Application-Specific Integrated Circuits OSPF summarization, 240-241 (ASICs), 373 stateless autoconfiguration, 398-399 applications, virtual links, 241-248 adjacencies, 41, 101 architecture, message types, 69 IS-IS, 103 archives, 355 broadcast networks, 104-107 areas, 61-62, 149 point-to-point networks, 107-109 backbones, 66 neighbors, 103 design OSPF, 101-102 BGP, 271 point-to-point over Ethernet, 117 IS-IS, 248-258 routers, 77 OSPF, 224-234 administration (RIDs), 81-86 reliability, 222-223 Advanced Research Projects Agency scalability, 220-221 (ARPA), 3-8 fragmentation, 304-308 Advertising Routers, 140 Inter-Area Prefix LSAs, 414 AFI (Authority and Format Identifier), 88 Inter-Area Router LSAs, 414 age of the LSA in seconds, 140 Intra-Area Prefix LSAs, 410 aging, 45 IS-IS, 151-153 439 Doyle_Index.indd 439 10/7/05 12:40:56 PM 440 Index nonbackbone, 66 B OSPF,
    [Show full text]
  • Cloud and Network Infrastructures
    EIT Digital Master School What can I study at the entry and exit points? Cloud and Network Infrastructures FOR A STRONG DIGITAL EUROPE EIT Digital Master School Cloud and Network Infrastructures (CNI) ENTRY - 1ST YEAR, COMMON COURSES 2 Aalto University (Aalto), Finland 2 Technical University of Berlin (TUB), Germany 3 University of Rennes 1 (UR1), France 4 Sorbonne University (SU), France 5 KTH Royal Institute of Technology (KTH), Sweden 7 University of Trento (UNITN), Italy 7 EXIT - 2ND YEAR, SPECIALISATION 9 Aalto University (Aalto), Finland 9 Technical University of Berlin (TUB), Germany 10 University of Rennes 1 (UR1), France 11 Sorbonne University (SU), France 13 KTH Royal Institute of Technology (KTH), Sweden 14 University of Trento (UNITN), Italy 15 1 EIT Digital Master School Cloud and Network Infrastructures (CNI) Entry - 1st year, common courses Aalto University (Aalto), Finland Visit University website. Programme Contact: Jukka Manner; [email protected] Common Core (10 ECTS) • ELEC-7320 Internet Protocols (5 ECTS) • CS-E4100 Mobile Cloud Computing (5 ECTS) Compulsory courses (6 ECTS) • LC-xxxx Language course: Compulsory degree requirement, both oral and written requirements (3 ECTS) • ELEC-E0110 Academic skills in master's studies (3 ECTS) Electives (20 ECTS) • CS-C3130 Information Security (5 ECTS) • ELEC-E712 Wireless Systems (5 ECTS) • ELEC-E7130 Internet Traffic Measurements and Analysis (5 ECTS) • ELEC-E7310 Routing and SDN (5 ECTS) • ELEC-E7330 Laboratory Course in Internet Technologies (5 ECTS) • ELEC-E7210 Communication
    [Show full text]
  • White Paper: Network Transformation
    ETSI White Paper No. #32 Network Transformation; (Orchestration, Network and Service Management Framework) 1st edition – October-2019 ISBN No. 979-10-92620-29-0 Authors: Chairmen of ISG ENI, MEC, NFV and ZSM ETSI 06921 Sophia Antipolis CEDEX, France Tel +33 4 92 94 42 00 [email protected] www.etsi.org Contents Contents 3 1 Executive Summary 4 2 The need for network transformation 5 3 Steps towards autonomous network management 6 3.1 NFV (Network Functions Virtualization) 6 3.2 MEC (Multi-access Edge Computing) 8 3.3 ENI 10 3.4 ZSM (Zero-touch Network and Service Management) 12 4 A common way forward 14 References 15 Network Transformation; (Orchestration, Network and Service Management Framework) 3 1 Executive Summary The telecommunication industry is in the middle of a significant transformation. Driven by the needs of 5G networks and applications and enabled by transformative technologies such as NFV and cloud-native deployment practices, this is likely to be the single biggest technological and business transformation of the telecom industry since the consolidation of mobile communication infrastructures. The telecom networks that will emerge from this transformation are going to be highly distributed and fully software-defined, running primarily on homogeneous cloud resources. The flexibility that these characteristics bring will allow mobile operators to address the heterogeneous and divergent needs of 5G applications in a highly efficient manner (e.g. through the use of techniques like network slicing) – but only if the overall network services can be properly managed. The issue of management is perhaps the most critical challenge facing the telecom industry as it moves into 5G.
    [Show full text]
  • P4xos: Consensus As a Network Service
    This article has been accepted for inclusion in a future issue of this journal. Content is final as presented, with the exception of pagination. IEEE/ACM TRANSACTIONS ON NETWORKING 1 P4xos: Consensus as a Network Service Huynh Tu Dang, Pietro Bressana, Han Wang, Member, IEEE,KiSuhLee , Noa Zilberman, Senior Member, IEEE, Hakim Weatherspoon, Marco Canini, Member, IEEE, ACM, Fernando Pedone, and Robert Soulé Abstract— In this paper, we explore how a programmable Leveraging this trend, several recent projects have explored forwarding plane offered by a new breed of network switches ways to improve the performance of consensus protocols by might naturally accelerate consensus protocols, specifically focus- folding functionality into the network. Consensus protocols ing on Paxos. The performance of consensus protocols has long been a concern. By implementing Paxos in the forwarding plane, are a natural target for network offload since they are both we are able to significantly increase throughput and reduce essential to a broad range of distributed systems and services latency. Our P4-based implementation running on an ASIC in (e.g., [7], [8], [54]), and widely recognized as a performance isolation can process over 2.5 billion consensus messages per sec- bottleneck [16], [23]. ond, a four orders of magnitude improvement in throughput Beyond the motivation for better performance, there is over a widely-used software implementation. This effectively removes consensus as a bottleneck for distributed applications also a clear opportunity. Since consensus protocols critically in data centers. Beyond sheer performance, our approach offers depend on assumptions about the network [28], [34], [44], several other important benefits: it readily lends itself to formal [45], they can clearly benefit from tighter network integration.
    [Show full text]
  • Reflections on Network Architecture: an Active Networking Perspective
    Reflections on Network Architecture: an Active Networking Perspective Ken Calvert∗ Laboratory for Advanced Networking University of Kentucky [email protected] ABSTRACT years. As such, the work on active networking represents one of After a long period when networking research seemed to be fo- the few recent research efforts that considered network architecture cused mainly on making the existing Internet work better, inter- as something other than a solved problem. est in “clean slate” approaches to network architecture seems to be This note is an attempt to present some observations based on growing. Beginning with the DARPA program in the mid-1990’s, the author’s experiences, in the hope of extracting some insight into researchers working on active networks explored such an approach, network architecture. It is neither an attempt to make a case for ac- based on the idea of a programming interface as the basic interoper- tive or programmable networking, nor to claim that experience with ability mechanism of the network. This note draws on the author’s active networks (AN) architecture necessarily transfers to other any experiences in that effort and attempts to extract some observations other kind of network architecture. The AN effort, after all, focused or “lessons learned” that may be relevant to more general network on solving a particular problem—the difficult and lengthy process architecture research. of standardizing and deploying new protocols and services—using a particular technology: programmable network nodes. Neverthe- less, there may be some general lessons here. The reader will judge Categories and Subject Descriptors whether that is the case.
    [Show full text]
  • Quality of Service Routing in the Internet
    Quality of Service Routing in the Internet Theory, Complexity and Algorithms Quality of Service Routing in the Internet Theory, Complexity and Algorithms Proefschrift terverkrijgingvandegraadvandoctor aan de Technische Universiteit Delft, op gezag van de Rector Magnificus Prof.dr.ir. J.T. Fokkema, voorzitter van het College voor Promoties, in het openbaar te verdedigen op dinsdag 14 september 2004 om 15.30 uur door Fernando Antonio KUIPERS elektrotechnisch ingenieur geborente’sGravenhage. Dit proefschrift is goedgekeurd door de promotor: Prof.dr.ir. P.F.A. Van Mieghem Samenstelling promotiecommissie: Rector Magnificus, Voorzitter Prof.dr.ir. P.F.A. Van Mieghem, Technische Universiteit Delft, promotor Prof.dr.ir. I.G.M.M. Niemegeers, Technische Universiteit Delft Prof.dr.ir. N.H.G. Baken, Technische Universiteit Delft Prof.dr.ir. C. Roos, Technische Universiteit Delft Prof.dr. J. Domingo-Pascual, Universitat Politècnica de Catalunya Prof. Ing. G. Ventre, Università di Napoli Federico II Dr.ir. H. De Neve, Alcatel Belgium Published and distributed by: DUP Science DUP Science is an imprint of Delft University Press P.O. Box 98 2600 MG Delft The Netherlands Telephone:+31152785678 Telefax:+31152785706 E-mail: [email protected] ISBN 90-407-2523-3 Keywords: QoS routing, algorithm, complexity Copyright c 2004 by F.A. Kuipers ° All rights reserved. No part of the material protected by this copyright notice may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying, recording or by any information storage and retrieval system, without written permission from the publisher: Delft University Press Printed in The Netherlands to Theo, Maria and Carolina vi Contents 1Introduction 1 1.1RoutingintheInternet..........................
    [Show full text]