DOCSLIB.ORG

Segment Routing for Ipv6 Networks (Srv6)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Segment Routing for Ipv6 Networks (Srv6) Segment Routing for IPv6 Networks (SRv6) Stefano Previdi Distinguished Engineer BRKRST-3123 Agenda • Introduction to Segment Routing • Segment Routing and the IPv6 Source Routing Model • IPv6 Segment Routing Header (SRH) • SRH Procedures • SR-IPv6 Examples • Use Cases • Standardization • Conclusion 3 Introduction to Segment Routing 4 What is Segment Routing ? • An architecture that seeks the right balance between distributed intelligence and centralized optimization and programming. • simplifies operation (lower opex) • enables application-based service creation (new revenue) • allows for better utilization of the installed infrastructure (lower capex) • Applies to both IPv6 and MPLS dataplanes with wide application • (SP, OTT/Web, GET) across (WAN, Metro/Agg, DC) • SDN controller • An architecture designed with SDN in mind • Segment Routing technology is extensively explained in • http://www.segment-routing.net (includes all published IETF drafts) 5 Segment Routing • Source Routing • the source chooses a path and encodes it in the packet header as an ordered list of segments • the rest of the network executes the encoded instructions without any further per-flow state • SR-IPv6: the list of segment is encoded into a new (and secure) Routing Header called the “Segment Routing Header” • Segment: an identifier for any type of instruction • forwarding or service • Segment Routing leverages the benefit of IPv6 • Source routing capability through the use of extension headers • Full interoperability with non-source routing nodes (with no signaling) 6 Segment Routing – Scalability and Virtualization • Each engineered application flow is mapped on a path Millions of Application • millions of paths flow paths • A path is expressed as an ordered list of segments A path is mapped on a • The network maintains segments list of segments • thousands of segments • completely independent of application size/frequency The network only maintains • Excellent scaling and virtualization segments No per-flow • the application state is no longer within the router but application within the packet state 7 Segment Routing - Strong Operator Partnership • Fundamental to the velocity and success • Significant commitment • technical transparency • multi-vendor commitment • Many more operators now involved • Segment Routing MPLS now standardized and (almost) deployed… • Segment Routing IPv6 is getting up to speed • Open and standardized technology • More than 25 drafts under standardization process in IETF WGs: • SPRING, 6MAN, IS-IS, IDR, OSPF, PCE • For both MPLS and IPv6 dataplanes 8 Segment Routing and the IPv6 Source Routing model 9 Segment Routing and the Source Based Routing Model • By combining type of segments (i.e.: instructions) Segment Routing allows to address a variety of use cases from edge to edge Controller AS W Ap SR DC SR WAN BR AS p Z AS Fwrdr TOR Leaf Spine DCI BR core X Ap p BR AS Y Top Segment provides Next segments implement WAN Policy: Last segment Classify flow and ECMP-path to selected . Cost vs Latency Disjointness selects egress push SR segment list DCI . Select egress BR peer 10 Segment Routing and the Source Based Routing Model Wait a Moment !! • There are two ways of using Segment Routing on v6 networks • IPv6 control plane with a MPLS dataplane • IPv6 control plane with a IPv6 dataplane • This presentation covers Segment Routing for IPv6 control & data planes i.e.: no MPLS dataplane is involved… but interop is granted 11 Segment Routing and the Source Based Routing Model • SR-IPv6 allows IPv6 dataplane networks to benefit from all features deployed over the years on MPLS network: • Traffic Engineering • VPNs • Fast Reroute • … • As well as new features such as • Conduit • Service Chaining • BGP Traffic Engineering • BGP Peer Engineering • Application Engineered Routing 12 Segment Routing IPv6 and the Source Based Routing Model • In the source based routing model the source chooses a path and encodes it in the packet header as an ordered list of segments • A new type of the existing IPv6 Routing Extension Header is used for Segment Routing: SRH • The Segment Routing Header (SRH) contains the list of segments • Path state in the packet, not in the network • The segment identifier (SID) is a 128-bit IPv6 address • The Segment List expressing the source routed path is a list of IPv6 addresses 13 Segment Routing IPv6 and the Source Based Routing Model • A segment is an instruction applied to the packet: • IGP-based forwarding construct • BGP-based forwarding construct • local adjacency • service/application • location, • context, … 14 Segment Routing and the IPv6 Dataplane • Segment Routing applies to both IPv6 and MPLS dataplanes • Difference is in the bits encoded in the packet not in the architecture • Enabling SR-IPv6, means that ONLY the nodes that have to process the packet header must have SR-IPv6 dataplane support • All other nodes in the infrastructure are just plain IPv6 nodes IPv6 Hdr Label(C) Label(F) SR Header B C D Label(H) Segments: C,F,H A H IPv4 or IPv6 hdr E F G PAYLOAD PAYLOAD SR-IPv6 SR-MPLS 15 Example of Segments Service Segment to S1 S1 Node segment to C Node segment to C Peer Segment A B C D 1 Adj Segment Z M N O P 2 Peer Segment Node segment to Z • Examples: • Go to this node using shortest path (Node-SID) • Go to this prefix using shortest path (Prefix-SID) • Go through this specific link (no matter what SPT says, Adj-SID) • Go through this egress interface / peering AS (Adj-SID, Peer-SID) • Etc. • Simple protocol extensions allowing advertisement of segments • IGP, BGP, BGPLS, PCEP, … 16 Segment Routing and the Source Based Routing Model • Segment Routing IPv6: • The notion of a “segment” is not new in IPv6 • Routing Extension Header has been defined in RFC 2460 and defines the “segment” • In both RFC 2460 and Segment Routing a segment is identified by an IPv6 address • Segment Routing leverages RFC 2460 Routing Header by defining a new type • Improves Routing Header • Enhance the source routing model • Introduces security • Segment Routing does NOT require a forklift upgrade of the network • SR and non-SR nodes can co-exist • Gradual deployment • Full interoperability • Backward compatibility 17 The Segment Routing Header Insertion Vs. Encapsulation 18 Segment Routing Header and encapsulation • While not explicitly mentioned, RFC2460 assumes only the source is allowed to insert a routing header – Remember: the SRH is a type of routing header • Segment Routing for IPv6 allows multiple operational modes – All compliant to base IPv6 specification 19 Insertion Vs. Encapsulation • Header Insertion at the Source: – Source originates the packet with the SRH – SRH is kept and used along the path – Packet is delivered to destination with the SRH (plain IPv6 operations) > Optionally, the SRH may be removed prior to deliver the packet to destination – Use case: source is SRv6 capable Source C D IPv6 Hdr: SA=A, DA=D A IPv6 Hdr: SA=A, DA=G IPv6 Hdr: SA=A, DA=B SR Hdr: SL= B, D, G, Z Destination SR Hdr: SL= B, D, G, Z SR Hdr: SL= B, D, G, Z B PAYLOAD PAYLOAD Z PAYLOAD Ingress E F G IPv6 Hdr: SA=A, DA=Z Egress SR Hdr: SL= B, D, G, Z PAYLOAD SR domain 20 Insertion Vs. Encapsulation • Header Insertion at Ingress: – Source originates the packet without any SRH – SRH is inserted at ingress – SRH is removed prior to deliver the packet to the destination – Use case: source is not SRv6 capable Source C D IPv6 Hdr: SA=A, DA=D A IPv6 Hdr: SA=A, DA=G SR Hdr: SL= D, G, Z Destination IPv6 Hdr: SA=A, DA=Z B SR Hdr: SL= D, G, Z PAYLOAD PAYLOAD Z Ingress PAYLOAD E F G IPv6 Hdr: SA=A, DA=Z PAYLOAD Egress SR domain 21 Insertion Vs. Encapsulation • Encapsulation at Ingress : – Source originates the packet without any SRH – Ingress encapsulates the incoming packet into a new outer IPv6 header followed by the SRH – Packet is decapsulated at egress (both outer IPv6 header and SRH are removed) – Use Case: Source B C IPv6 Hdr: SA=A, DA=C A IPv6 Hdr: SA=A, DA=E IPv6 Hdr: SA=A, DA=Z SR Hdr: SL= C, E Destination A SR Hdr: SL= C, E PAYLOAD IPv6 Hdr: SA=A, DA=Z IPv6 Hdr: SA=A, DA=Z Z Ingress PAYLOAD PAYLOAD B D IPv6 Hdr: SA=A, DA=Z E PAYLOAD Egress SR domain 22 Segment Routing Example 23 Example of Explicit Path • How to express an explicit (source routed) path knowing that: • Nodes may represent routers, hosts, servers, application instances, services, chains of services, etc. • A path is encoded into the packet by the originator (or ingress) node using a list of IPv6 addresses • The network may have plurality of nodes not all supporting Segment Routing • A path can be “loose” or “strict” • Likely to be loose… • A single mechanism, a single placeholder where the “path” of the packet is expressed 24 SR-IPv6 Explicit Path Example • In following topology: B C D – Q: How to best express path: [A, B, C, F, G, H] A H • Note well: node A has two shortest E F G paths to C (ECMP) • A: Source rooted path with segments: [C,F,H] First segment: set of shortest paths from A to C (ECMP aware) Second segment: adjacency/link from C to F Third segment: shortest path from F to H • Loose Source Routing B C D A H E F G 25 SR-IPv6 Explicit Path Example Interoperability B C D A H E F G • Not all nodes needs to be SR capable • Example: – Traffic Engineering from A to H through path ABCFGH – Nodes A, C and F are SR capable – Nodes B, D, E, G and H are plain ipv6 forwarders 26 SR-IPv6 Explicit Path Example B C IPv6 Hdr: SA=A, DA=C SR Hdr: SL= C, F, H A PAYLOAD • At node A: – Path is computed or received by a controller (e.g.: SDN Controller) – Path is instantiated
Load more

Recommended publications
  • Routing and Congestion Control in Datagram Networks
    Routing and Congestion Control in Datagram Networks Zheng Wang Submitted for the degree of PhD at University College London January 1992 ProQuest Number: 10608852 All rights reserved INFORMATION TO ALL USERS The quality of this reproduction is dependent upon the quality of the copy submitted. In the unlikely event that the author did not send a com plete manuscript and there are missing pages, these will be noted. Also, if material had to be removed, a note will indicate the deletion. uest ProQuest 10608852 Published by ProQuest LLC(2017). Copyright of the Dissertation is held by the Author. All rights reserved. This work is protected against unauthorized copying under Title 17, United States C ode Microform Edition © ProQuest LLC. ProQuest LLC. 789 East Eisenhower Parkway P.O. Box 1346 Ann Arbor, Ml 48106- 1346 ABSTRACT Routing and congestion control can be viewed as two closely related processes in a resource control system which manages the network resources. One of the basic prob­ lems is to adapt to changing conditions. Our analysis shows that inadequate information and delayed feedback can cause oscillation and instability. In this dissertation we exam­ ine the problems in routing and congestion control in a datagram environment and pro­ pose a number of solutions. The essence of the ideas is to deal with momentary fluctua­ tions and average steady trends separately. The behavior of shorest-path routing algorithms is investigated. A new approach for dynamic routing based on the concept of decentralized decision making is introduced. A dynamic routing algorithm based on this new approach, Shortest Path First with Emer­ gency Exits (SPF-EE)y is developed, which eliminates many of the problems that the Shortest Path First (SPF) algorithm exhibits under heavy and dynamic traffic.
    [Show full text]
  • Segment Routing: a Comprehensive Survey of Research Activities, Standardization Efforts and Implementation Results
    SUBMITTED TO IEEE COMMUNICATIONS SURVEYS & TUTORIALS 1 Segment Routing: a Comprehensive Survey of Research Activities, Standardization Efforts and Implementation Results Pier Luigi Ventre, Stefano Salsano, Marco Polverini, Antonio Cianfrani, Ahmed Abdelsalam, Clarence Filsfils, Pablo Camarillo, Francois Clad Revision R2 - June 2020 Abstract—Fixed and mobile telecom operators, enterprise net- APIs, Northbound APIs, Open Source, Software Defined Net- work operators and cloud providers strive to face the challenging working, SDN, Service Function Chaining, SFC, Standards demands coming from the evolution of IP networks (e.g. huge bandwidth requirements, integration of billions of devices and millions of services in the cloud). Proposed in the early 2010s, I. INTRODUCTION Segment Routing (SR) architecture helps face these challenging demands, and it is currently being adopted and deployed. SR Egment Routing (SR) is based on the loose Source architecture is based on the concept of source routing and S Routing concept. A node can include an ordered list of has interesting scalability properties, as it dramatically reduces instructions in the packet headers. These instructions steer the the amount of state information to be configured in the core forwarding and the processing of the packet along its path in nodes to support complex services. SR architecture was first implemented with the MPLS dataplane and then, quite recently, the network. with the IPv6 dataplane (SRv6). IPv6 SR architecture (SRv6) The single instructions are called segments, a sequence of has been extended from the simple steering of packets across instructions can be referred to as a segment list or as an SR nodes to a general network programming approach, making it Policy.
    [Show full text]
  • Source Routing 2.0
    Source Routing 2.0 Why Now? Why Again? Nick Slabakov [email protected] ‹#› v3 Outline Source Routing • Historical Notes SPRING • Principles of operation • Why it has motivated new discussions on source routing SPRING Inspirations • SPRING-inspired second look at existing problems Conclusions ‹#› Terminology Level-Set • Source Routing • Explicit definition of a packet path within the packet header by the source. • Source Routing is a generic term, there are many methods of doing it. • Segment Routing • Emergent network architecture based on the distribution of label (and IPv6 segment) info in the IGP. • Segment Routing is one specific way of doing Source Routing. • SPRING (Source Packet Routing In NetworkinG) • IETF working group tasked with standardizing the architecture and protocols associated with Segment Routing. ‹#› Source Routing – Short History Key idea • Prescribe the path of the packet in its header at the source; the source has unique knowledge about the desired path. • A nice side-effect is that loops can be avoided. • Reduce/remove forwarding state in the network, put it in the packet instead. Examples • Niche high-performance interconnects • Myrinet, SpaceWire, etc. • Token Ring, APPN, ANR (IBM), … • IP • IPv4 – LSRR and SRRR options. • IPv6 – Extension header of routing type. ‹#› IP Header-Based Source Routing Security Concerns and Solutions IPv4 options and IPv6 header extensions • Treated as easily spoof-able and prone to amplification attacks. • Generally disabled on all Internet-connected routers. • RFC5095 actually deprecates Type 0 routing extension header: • “An IPv6 node that receives a packet with a destination address assigned to it and that contains an RH0 extension header MUST NOT execute the algorithm specified in the latter part of Section 4.4 of [RFC2460] for RH0 …”.
    [Show full text]
  • Multiprotocol Label Switching (MPLS)
    Multiprotocol Label Switching (MPLS) Definition Multiprotocol label switching (MPLS) is a versatile solution to address the problems faced by present-day networks—speed, scalability, quality-of-service (QoS) management, and traffic engineering. MPLS has emerged as an elegant solution to meet the bandwidth-management and service requirements for next- generation Internet protocol (IP)–based backbone networks. MPLS addresses issues related to scalability and routing (based on QoS and service quality metrics) and can exist over existing asynchronous transfer mode (ATM) and frame-relay networks. Overview This tutorial provides an in-depth look at the technology behind MPLS, with an emphasis on the protocols involved. The tutorial also discusses why MPLS is an important component in the deployment of converged networks. Topics 1. Introduction 2. Traditional Routing and Packet Switching 3. MPLS and Its Components 4. MPLS Operation 5. MPLS Protocol Stack Architecture 6. MPLS Applications 7. Standards Groups Self-Test Correct Answers Glossary 1. Introduction Over the last few years, the Internet has evolved into a ubiquitous network and inspired the development of a variety of new applications in business and Web ProForum Tutorials Copyright © 1/24 http://www.iec.org The International Engineering Consortium consumer markets. These new applications have driven the demand for increased and guaranteed bandwidth requirements in the backbone of the network. In addition to the traditional data services currently provided over the Internet, new voice and multimedia services are being developed and deployed. The Internet has emerged as the network of choice for providing these converged services. However, the demands placed on the network by these new applications and services, in terms of speed and bandwidth, have strained the resources of the existing Internet infrastructure.
    [Show full text]
  • MPLS Segment Routing Driving a Modern Approach to MPLS Transport
    White Paper MPLS Segment Routing Driving a modern approach to MPLS transport For many years, one of the biggest challenges in network design has been effectively managing traffic flow end-to- end across the network. Stated more specifically: How is traffic intelligently classified and path engineered throughout the network? Furthermore, how can this traffic be classified into differentiated levels of service, without adding unnecessary complication to management, control plane, or data plane state in this critically important part of the network? Now, modern cloud and service provider networks in the SDN era require even more flexible control on steering of their traffic flows, at a much greater scale. With globally optimized SDN controllers utilizing parameters like distance, available bandwidth, latency, cost of long-haul links and business logic into their path computation algorithms, there is an increased need for flexible, intelligent source routing solutions. More and more operators have made a concerted effort to simplify their networks and eliminate the dependency on a wide set of protocols to achieve their goals. As native IPv6 deployments increase, there is a need for a native solution for IPv6 networks and IP backbones that provides the same capabilities as current MPLS networks. This seems like an impossible set of opposing requirements to reconcile. Traditional MPLS implementations did address some of the original challenges, but they came with a complex array of protocols, suffered from scaling challenges and had rigid vendor specific path computation algorithms for Traffic Engineering (TE). They also did not provide native IPv6 support across the protocol stack. Segment routing is the technology that elegantly addresses this varied set of requirements across many different networking domains: datacenter, content delivery networks and metro networks, to name a few.
    [Show full text]
  • Application of Asynchronous Transfer Mode (Atm) Technology to Picture Archiving and Communication Systems (Pacs): a Survey
    UNLV Retrospective Theses & Dissertations 1-1-1996 Application of Asynchronous Transfer Mode (Atm) technology to Picture Archiving and Communication Systems (Pacs): A survey Sridharan R Madabhushanam University of Nevada, Las Vegas Follow this and additional works at: https://digitalscholarship.unlv.edu/rtds Repository Citation Madabhushanam, Sridharan R, "Application of Asynchronous Transfer Mode (Atm) technology to Picture Archiving and Communication Systems (Pacs): A survey" (1996). UNLV Retrospective Theses & Dissertations. 3249. http://dx.doi.org/10.25669/vpsr-biak This Thesis is protected by copyright and/or related rights. It has been brought to you by Digital Scholarship@UNLV with permission from the rights-holder(s). You are free to use this Thesis in any way that is permitted by the copyright and related rights legislation that applies to your use. For other uses you need to obtain permission from the rights-holder(s) directly, unless additional rights are indicated by a Creative Commons license in the record and/ or on the work itself. This Thesis has been accepted for inclusion in UNLV Retrospective Theses & Dissertations by an authorized administrator of Digital Scholarship@UNLV. For more information, please contact [email protected]. INFORMATION TO USERS This manuscript has been reproduced from the microfilm master. UMI films the text directly fiom the original or copy submitted. Thus, some thesis and dissertation copies are in typewriter face, while others may be from any type of computer printer. The quality of this reproduction is dependent upon the quality of the copy submitted. Broken or indistinct print, colored or poor quality illustrations and photographs, print bleedthrough, substandard margins, and improper alignment can adversely affect reproduction.
    [Show full text]
  • Configuring Static MPLS
    Configuring Static MPLS This chapter contains information on how to configure static multiprotocol label switching (MPLS). • About Static MPLS, on page 1 • Licensing Requirements, on page 4 • Prerequisites for Static MPLS, on page 4 • Guidelines and Limitations for Static MPLS, on page 4 • Configuring Static MPLS, on page 6 • Verifying the Static MPLS Configuration, on page 9 • Displaying Static MPLS Statistics, on page 11 • Clearing Static MPLS Statistics, on page 12 • Configuration Examples for Static MPLS, on page 12 • Additional References, on page 13 About Static MPLS Generally, label switching routers (LSRs) use a label distribution protocol to dynamically learn the labels that they should use to label-switch packets. Examples of such protocols include: • Label Distribution Protocol (LDP), the Internet Engineering Task Force (IETF) standard that is used to bind labels to network addresses • Resource Reservation Protocol (RSVP), which is used to distribute labels for traffic engineering (TE) • Border Gateway Protocol (BGP), which is used to distribute labels for MPLS virtual private networks (VPNs) To use a learned label to label-switch packets, an LSR installs the label into its Label Forwarding Information Base (LFIB). The static MPLS feature enables you to statically configure the following: • The binding between a label and an IPv4 or IPv6 prefix • The action corresponding to the binding between a label and an IPv4 or IPv6 prefix (label swap or pop) • The contents of an LFIB cross-connect entry Configuring Static MPLS 1 Configuring Static MPLS Label Swap and Pop Label Swap and Pop As a labeled packet traverses the MPLS domain, the outermost label of the label stack is examined at each hop.
    [Show full text]
  • Chapter 14 in Stallings 10Th Edition
    The Internet Protocol Chapter 14 in Stallings 10th Edition CS420/520 Axel Krings Page 1 Sequence 14 Table 14.1 Internetworki ng Terms (Table is on page 429 in the textbook) Page 2 Sequence 14 1 Host A Host B App X App Y App Y App X Port 1 2 3 2 4 6 Logical connection (TCP connection) TCP TCP Global internet IP address IP Network Access Network Access Protocol #1 Protocol #2 Logical connection Physical Subnetwork attachment (e.g., virtual circuit) Physical point address Router J IP NAP 1 NAP 2 Network 1 Network 2 Physical Physical Figure 14.1 TCP/IP Concepts CS420/520 Axel Krings Page 3 Sequence 14 Why we do not want Connection Oriented Transfer CS420/520 Axel Krings Page 4 Sequence 14 2 Connectionless Operation • Internetworking involves connectionless operation at the level of the Internet Protocol (IP) IP •Initially developed for the DARPA internet project •Protocol is needed to access a particular network CS420/520 Axel Krings Page 5 Sequence 14 Connectionless Internetworking • Advantages —Flexibility —Robust —No unnecessary overhead • Unreliable —Not guaranteed delivery —Not guaranteed order of delivery • Packets can take different routes —Reliability is responsibility of next layer up (e.g. TCP) CS420/520 Axel Krings Page 6 Sequence 14 3 LAN 1 LAN 2 Frame relay WAN Router Router End system (X) (Y) End system (A) (B) TCP TCP IP IP IP IP t1 t6 t7 t10 t11 t16 LLC LLC LLC LLC t2 t5 LAPF LAPF t12 t15 MAC MAC MAC MAC t3 t4 t8 t9 t13 t14 Physical Physical Physical Physical Physical Physical t1, t6, t7, t10, t11, t16 IP-H TCP-H Data t2,
    [Show full text]
  • Will Segment Routing Deliver on Its Promise? a Heavy Reading White Paper Produced for Juniper Networks
    Independent market research and competitive analysis of next-generation business and technology solutions for service providers and vendors Will Segment Routing Deliver on Its Promise? A Heavy Reading white paper produced for Juniper Networks AUTHOR: STERLING PERRIN, PRINCIPAL ANALYST, HEAVY READING INTRODUCTION Segment routing (SR) was introduced to the market just a few years ago with a promise that it would greatly simplify the control plane in IP networks. It promised to move state information from the network to the packet header and provide an end-to-end transport architecture that spans multiple network domains. Service provider support of SR is growing, but work remains in advance of broad industry adoption. In this white paper, Heavy Reading explores the state of SR today: What is working and what’s not? What is the industry doing to ensure broad, reliable adoption at scale for this promising new technology? Topics addressed include the following: • The current state of SR in service provider networks • Challenges to broader adoption • Future use case cases • Proposed path forward for SR STATE OF SEGMENT ROUTING TODAY, CURRENT ADOPTION, USE CASES "Segment routing" and "source routing" are two terms that describe a routing technique in which the source (or ingress) router specifies the route that the packet will take through the network, rather than the path being chosen based on the packet's destination only. SR was officially introduced within the Internet Engineering Task Force (IETF) in 2013 when the Source Packet Routing in Networking (SPRING) Working Group was formed. SR’s primary differentiation from legacy traffic engineering protocols – such as RSVP-TE, LDP, and MPLS-TP* – is in its implementation and operational simplicity.
    [Show full text]
  • Segment Routing
    Application Engineered Routing: Allowing Applications to Program the Network BRKSPG-2066 Rob Piasecki, Solutions Architect, Services, [email protected] Agenda • AER: Industry Drivers & Overview • AER: Architecture & Technical Concepts . Segment Routing . Intelligent SDN Controller • Use Cases & Implementation . Purpose Built Applications . Demo • Conclusion AER: Industry Drivers & Overview The Problem The Network is facing new challenges Cloud Services IoE Mobility Dynamic and changing traffic patterns UHD Increasingly diverse applications with application-specific transport requirements Other End-to-End control required IPv6 EVOLVED PROGRAMMABLE NETWORK5 Networks Need to be Rethought Applications and Network interaction is key IP APPLICATIONS Core Edge EVOLVED SERVICES PLATFORM Acce ss/ Agg IPv6 EVOLVED PROGRAMMABLE NETWORK IP NGN Era Designed to support a set of services Designed to support any kind of services Static traffic patterns Dynamic traffic patterns Manual configuration (CLI) Automation (APIs, Controllers, …) Apps Independent of Network App & Network Interaction 6 Specific Approaches to the Problem A continuum of enhanced solutions Hosts DC Core Agg Hosts DC Core Agg Hosts DC Core Agg One device, single domain Many devices, single domain Many devices, across domains IP NGN Era EPN Era Policy-Based routing MPLS TE . Scalable Evolution required Effective solutions with some caveats: . Stateless to address the . Little or no application / network interaction new paradigm . Scalability . Programmable . Configuration & troubleshooting complexity . States to be maintained in each network node . Ease of configuration & troubleshooting 7 Applications & Network Interaction Implications for the Network Fabric Many applications with dynamic and changing traffic patterns IP Networks IP Networks & Traffic Engineering Limitations . Limited to a single network Impediment to service domain creation . Scalability . Configuration & Major scalability issues troubleshooting complexity .
    [Show full text]
  • Traffic Engineering with Multi-Protocol Label Switching
    Master Thesis Computer Science Thesis no: MCS-2008-32 August 2008 Traffic Engineering with Multi-Protocol Label Switching Performance Comparison with IP networks By MUHAMMAD NAEEM ASLAM YASSAR AZIZ Department of Interaction and System Design School of Engineering Blekinge Institute of Technology Box 520 SE – 372 25 Ronneby Sweden This thesis is submitted to the Department of Interaction and System Design, School of Engineering at Blekinge Institute of Technology in partial fulfillment of the requirements for the degree of Master of Science in Computer Science. The thesis is equivalent to 20 weeks of full time studies. Contact Information: Yassar Aziz Folkparksvagen 10, Room 10 Ronneby, 37240 [email protected] Muhammad Naeem Aslam [email protected] Studentvagen 01, Room 37 Ronneby, 37240 University advisor(s): Dr. Lawrence Edward Henesey Department of System and Software Engineering Department of Systems and Software Engineering Blekinge Institute of Technology Internet : www.bth.se/tek Box 520 Phone : +46 457 38 50 00 SE – 372 25 Ronneby Fax : + 46 457 102 45 Sweden ii ABSTRACT Traffic Engineering (TE) is the stage which deals with geometric design planning and traffic operation of networks, network devices and relationship of routers for the transportation of data. TE is that feature of network engineering which concentrate on problems of performance optimization of operational networks. It involves techniques and application of knowledge to gain performance objectives, which includes movement of data through network, reliability, planning of network capacity and efficient use of network resources. This thesis addresses the problems of traffic engineering and suggests a solution by using the concept of Multi-Protocol Label Switching (MPLS).
    [Show full text]
  • MPLS Multiprotocol Label Switching
    MPLS Multiprotocol Label Switching Prof. Rami Langar LIGM/UPEM [email protected] http://perso.u-pem.fr/~langar 1 Outline o Routing vs. switching o Label Switching properties o IPOA o IP switching o Multi Protocol Label Switching (MPLS) o Label Distribution Protocol o Traffic Engineering 2 Two forwarding paradigms o Station breaks long message into packets o Packets sent one at a time to the network o Packets handled in two ways n Datagram (e.g., IP routing) n Virtual Circuit (e.g., ATM) 3 Datagram (e.g., IP routing) o Each packet treated independently o Packets can take any practical route o Packets may arrive out of order o Packets may go missing o Up to receiver to re-order packets and recover from missing packets 4 Conventional IP routing o Router have to execute a forwarding decision for every received IP packet : n Routing algorithm execution (performed in advance), n Packet reception from the input queue, n Header analysis (Checksum, TTL, @IP, …), n Access control (optional), n Send the packet to the output queue. => Important queue congestion if all packets are routed in the same way. 5 Conventional IP routing 1. Remove a packet 2. Check for sanity, 4. Place packet on from an input decrement TTL correct output queue field queue Forwarding Process 3. Match packet’s If queues If queues destination to get full, just get full, just a table entry drop packets! drop packets! IP Forwarding Table Router 6 Conventional IP routing o Advantages: n IP is the first defined and used protocol, n IP is the only protocol for global Internet working o Deployed in all machines since mid 90’s n Connectionless: Simplicity, no need for signalization n Flexibility (adaptive routing), o Disadvantages: n No QoS support, n High routing table size n Large IP Header (At least 20 bytes) n Poor performance (in early 2000’s 105 packets/s VS 108 today) n Usually designed to obtain shortest path, o Do not take into account additional metrics.
    [Show full text]