Doyle Index.Pdf

Total Page:16

File Type:pdf, Size:1020Kb

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, 149 Bachman, Charlie, 20 overloading, 308-312 backbones, 66 partitioned, 179 ABRs, 150 stubs, 234-236 areas not-so-stubby, 238-239 IS-IS, 248-250 totally stubby, 237 OSPF, 224-228 Area Address TLVs, 96, 169 and regional networks, 23 area border routers (ABRs), 149 Backup Designated Router neighbors, 187 area ID (AID), 86 bandwidth multiple, 269 OSPF scalability, 228-233 IS-IS, 88-90 reference, 154 ARPA (Advanced Research Projects banners, login, 349 Agency), 3-8 Baran, Paul, 5, 8 ARPA Network (ARPANET), 4-8, 14-19 batch processing, 2 AS-External LSAs, 165-168, 415 BBN (Bolt Baranek and Newman), 2 ASBRs (autonomous system boundary behavior, default IS-IS area, 256-260 routers), 66, 151 Behavioral Sciences division (DoD), 3 Summary LSAs, 164-165 Bellman, Richard, 15 ASICs (Application-Specific Integrated Bellman-Ford algorithm, 28 Circuits), 373 BFD (bidirectional forwarding detection), AS (autonomous system), 37, 66 340-343 attacks BGP (Border Gateway Protocol), 37 DoS, 67 address summarization, 262 routing protocols, 316-318 area design, 271 authentication, 319-322 bidirectional forwarding detection (BFD), IS-IS, 326-328 340-343 OSPF, 323-325 binding labels, 377 authentication, authorization, and Blitzer, Wolf, 13 accounting. See AAA Bolt Baranek and Newman (BBN), 2 Authority and Format Identifier (AFI), 88 Border Gateway Protocol (BGP), 37 autoconfiguration, stateless addresses, address summarization, 262 398-399 area design, 271 autonomous system (AS), 37, 66 Bradley, Bill, 13 autonomous system boundary routers broadcast networks, 122 (ASBRs), 66, 151 designated routers, 110 Summary LSAs, 164-165 IS-IS adjacencies, 104-107 synchronization, 211 Bush, Vannevar, 3-4 Doyle_Index.indd 440 10/7/05 12:40:56 PM Index 441 C Command and Control Research division (DoD), 3 calculations committees, change management, 355 iSPF, 287-288 comparative terminology, message types, partial routes, 290 65-66 shortest-path routing trees, 51 compatibility of OSPFv3, 404-405 SPF, 51-60 CompleteSNPInterval, 211 Callon, Ross, 22 Complete Sequence Number PDU Canepa, Mike, 20 (CSNP), 148 Carr, Steve, 9 components (flooding), 133-134 Cerf, Vint, 11, 14, 19-20 IS-IS, 142-148 change controllers, 356 OSPF, 134-142 change management, 354-355 configuration characteristics of vector protocols, 28-29 AID, 86-90 checksums, 49, 140 management, 352-358 security, 329-331 NET, 88-90 circuits RIDs, 85 ASICs, 373 stateless address autoconfiguration, demand, 302-303 398-399 VC, 374 connections, OSPF virtual links, 241-248 Circuit Type values, 94 constrained SPF, 383-385 circular sequence number spaces, 48 control packets, BFD, 342 Cisco Systems, 23, 68 conventions, 70, 354 default IS-IS L1 area behavior, 256 convergence, vector protocols, 27-28 NSF, 336 cost of paths, 58 stub areas, 236 CoS (class of service), 68 virtual links, 245 counting to infinity, 32 Clark, Wesley, 7 CRC (cyclical redundancy check), 329 class of service (CoS), 68 Crowther, Will, 15 commands CSNP (Complete Sequence Number ip ospf flood-reduction, 304 PDU), 148 ip ospf retransmit-interval, 295 customization isis lsp-interval, 295 flooding, 292 isis retransmit-interval, 295 demand circuits, 302-303 isis retransmit-throttle-interval, 296 mesh groups, 296-301 lsp-gen-interval, 294 retransmit pacing, 295-296 lsp-interval, 295 transmit pacing, 293-294 overload, 312 neighbors, 187 overload-bit on-startup, 312 SPF, 273 overload timeout, 312 delay, 291-292 retransmit-interval, 295 equal-cost multipath, 274-286 set-overload-bit, 312 iSPF calculations, 287-288 timers pacing flood, 294 partial route calculations, 290 timers pacing lsa-group, 294 cyclical redundancy check (CRC), 329 Doyle_Index.indd 441 10/7/05 12:40:57 PM 442 Index D reliability, 344 domain edge protection, 347 databases redundancy, 344-346 exchanges, 180 router protection, 348-352 management, 188-189 security, 344 OSPF packets used for, 180-183 domain edge protection, 347 interfaces, 124 redundancy, 344-346 IS-IS, 129-131 router protection, 348-352 OSPF, 124-129 sequence counter, 46 IS-IS LS, 74 designated intermediate system (DIS), link state synchronization, 179 115-116 IS-IS, 205-216 designated routers, 77, 109-112 OSPF, 179-189, 190-200, 202-204 IS-IS, 115-116 LSPs, 74 neighbors, 187 RIB, 25 OSPF, 112-115 synchronization, 49-50 detection (BFD), 340-343 TED, 383 development of the Internet, 11-14 Database Description packet, 182 diffusing update algorithm (DUAL), 35 Database Summary List, 187 Dijkstra, Edsger W., 17, 50 datagrams, 12, 66 Dijkstra algorithm, 51 data structures, OSPF neighbors, 186-187 direct acknowledgments, 137 Davies, Donald, 5 disclosure, 316 deception, 316 disruption, 316 Decode-Encode Language (DEL), 10 distance vector protocols, 27 default IS-IS L1 area behavior, 256-260 distribution, MPLS labels, 377-378 default metrics, 156 DIS (designated intermediate systems), defining login banners, 349 115-116 delay documentation, 355 acknowledgments, 136 domains metrics, 156 lookups (names), 100 SPF, 291-292 protecting edges, 347 DEL (Decode-Encode Language), 10 routing, 66 demand circuits, 302-303 DoS (denial-of-service) attacks, 67 demultiplexing, links, 76 DUAL (diffusing update algorithm), 35 denial-of-service (DoS) attacks, 67 duplicate RIDs, troubleshooting, 82-86 dependent functions, subnetworks, 76-78 Dynamic Hostname Exchange Mechanism, design IS-IS, 99-100 areas BGP, 271 IS-IS, 248-258 E OSPF, 224-234 E1 (Type 1 External), 155 reliability, 222-223 E2 (Type 2 External), 155 scalability, 220-221 Doyle_Index.indd 442 10/7/05 12:40:57 PM Index 443 ECMP (equal-cost multipath), 274-280 OSPF, 362-368 pseudonodes and, 282-286 route tagging, 369-371 edges, protecting domains, 347 extensions EIGRP (Enhanced IGRP), 35 IPv6, 391-392 encapsulation, message types, 67-69 address formats, 394-395 end system (ES), 65 address representations, 396-397 Enhanced IGRP (EIGRP), 35 extension headers, 402-403 equal-cost multipath (ECMP), 274-280 features and functions of, 393 pseudonodes and, 282-286 header formats, 400-401 error metrics, 156 IS-IS, 420-422 essential LSAs, 158 Neighbor Discovery Protocol, 397-398 AS-External LSAs, 165-168 stateless address autoconfiguration, ASBR Summary LSAs, 164-165 398-399 Network LSAs, 161 MT-ISIS, 430-434 Network Summary LSAs, 162-164 MT-OSPF, 426-428 Router LSAs, 158-161 OSPFv3, 419 essential TLVs, 168, 169 TE Area Address TLVs, 169 IS-IS, 388-389 Extended IS Reachability TLVs, OSPF, 385-388 173-175 external prefixes IP External Reachability TLVs, 173 IS-IS redistribution, 268-269 IP Interface Addresses TLVs, 171 OSPF scaling, 231-233 IP Internal Reachability TLVs, 172 route prefixes, 369-371 IS Neighbor TLVs, 169, 170 Protocols Supported TLVs, 171 F ES (end system), 65 Ethernet, point-to-point adjacencies feasibility conditions, 35 over, 117 features of IPv6, 393 European Commission, 21 FEC (forwarding equivalence classes), 377 evaluation fields post-change, 357 Link State ID, 139 pre-change, 356 LSA header formats, 138 exchanges (databases), 180 OSPF link state database management, 188-189 synchronization, 184-185 OSPF packets used for, 180-183 filtering packets, 351 excluding links, 430 flags expense metrics, 156 SRM, 208 Extended IP Reachability TLVs, 174-175 SSN, 208 Extended IS Reachability TLVs, 173 Fletcher checksums, 330 extensibility, 361 flooding, 44-48 IS-IS, 368-369 components, 133-134 message architecture, 69 IS-IS, 142-148 OSPF, 134-142 Doyle_Index.indd 443 10/7/05 12:40:57 PM 444 Index optimizing, 292 HDSA (Honeywell Distributed Systems demand circuits, 302-303 Architecture), 20 mesh groups, 296-301 headers retransmit pacing, 295-296 announcements, 49 transmit pacing, 293-294 IPv6, 400-403 Ford, Lester Randolph , 15 LSAs Ford-Fulkerson algorithm, 28 formatting, 138 formatting OSPFv3, 407-417 addresses (IPv6), 394-395 MPLS, 379 headers Heart, Frank, 7 IPv6, 400-403 Hello messages, 41 MPLS, 379 Hello protocol, 90 LSA headers, 138 IS-IS, 93-99 LSPs, 143 OSPF, 91-92 forwarding, 77 history of link state protocols, 1-3 BFD, 340-343 ARPANET, 4-8 LSRs, 375 development
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]
  • 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.
    [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]
  • 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]