This document discusses software defined mobility management for mobile internet. It begins with an overview of existing mobility management solutions and their shortcomings. It then discusses how software defined networking (SDN) could help address issues with existing solutions by providing programmable devices and centralized control. The document proposes a SDN-based architecture for internet mobility management using OpenFlow. It describes an algorithm for optimally placing binding cache entries to minimize routing path stretch and handoff latency. Experimental results on test networks demonstrate advantages of the SDN approach through flexible, adaptive mobility management.
The document discusses the transport SDN framework and APIs. It provides an overview of the transport SDN toolkit, including the SDN framework, APIs, and a global transport SDN prototype demonstration. The framework uses a three-layer model with an infrastructure layer containing network elements, a control layer with multiple controllers, and an application layer. Transport SDN APIs are being developed to standardize the southbound and northbound interfaces. The demonstration showed a multi-domain, multi-vendor transport SDN deployment across five carrier labs and nine system vendors.
The hague rina-workshop-congestioncontrol-peymanICT PRISTINE
Programmable Congestion Control allows for custom congestion controllers to be configured per Distributed Inter-networking (DIF) layer in RINA, taking advantage of RINA's flow aggregation and breaking the long end-to-end control loop into shorter loops. This programmability occurs through different DIF configurations and congestion control policies without any changes to the underlying mechanisms. A new congestion control policy called LGC is being developed based on logistic growth functions that takes advantage of RINA's flow aggregation capabilities.
This document summarizes network concepts based on a Cisco book. It discusses how PCs communicate, network devices like hubs and switches, IP and MAC addressing, the OSI model and its seven layers, network segmentation using bridges routers and gateways, Ethernet operations, and concepts like cut-through forwarding, interframe gap, carrier signals, and CSMA/CD. The document is presented as a review of key topics in networking and internetworking.
This document discusses how the RINA framework supports network slicing through connectivity and performance isolation. It allows sharing of network resources while managing risks like security, costs, and ensuring high resource utilization. RINA isolates connectivity and performance at all layers through management of associations and quality of service. It also supports the flow of information needed to construct and manage network slices. RINA offers simplification through separation of concerns and code reuse, lowering total cost of ownership. It can be incrementally deployed and provides a coherent architecture for software-defined networking and network functions virtualization.
This document provides an overview of networking concepts including network types, medium access control protocols, TCP/IP protocol suite, addressing, Ethernet frames, ARP, and standards organizations. It begins with an agenda that lists these topics and includes diagrams to illustrate CSMA/CD, the OSI model, TCP/IP encapsulation, and Ethernet encapsulation. Examples are provided for different network devices, addressing formats and protocols.
In this session you will learn:
OSI reference model
OSI layers
Modbus communication protocol
Profibus communication protocol
Fieldbus communication protocol
This document summarizes a presentation on software defined networking (SDN). It discusses how SDN virtualizes networks in the same way server and desktops have been virtualized. SDN decouples the control plane from the data plane, allowing centralized control of network behavior and dynamic infrastructure provisioning. OpenFlow is presented as one approach to enable SDN by allowing communication between the network control and network devices. Potential benefits of SDN include flexibility, provisioning speed, improved security, efficiency and cost savings.
The document discusses the transport SDN framework and APIs. It provides an overview of the transport SDN toolkit, including the SDN framework, APIs, and a global transport SDN prototype demonstration. The framework uses a three-layer model with an infrastructure layer containing network elements, a control layer with multiple controllers, and an application layer. Transport SDN APIs are being developed to standardize the southbound and northbound interfaces. The demonstration showed a multi-domain, multi-vendor transport SDN deployment across five carrier labs and nine system vendors.
The hague rina-workshop-congestioncontrol-peymanICT PRISTINE
Programmable Congestion Control allows for custom congestion controllers to be configured per Distributed Inter-networking (DIF) layer in RINA, taking advantage of RINA's flow aggregation and breaking the long end-to-end control loop into shorter loops. This programmability occurs through different DIF configurations and congestion control policies without any changes to the underlying mechanisms. A new congestion control policy called LGC is being developed based on logistic growth functions that takes advantage of RINA's flow aggregation capabilities.
This document summarizes network concepts based on a Cisco book. It discusses how PCs communicate, network devices like hubs and switches, IP and MAC addressing, the OSI model and its seven layers, network segmentation using bridges routers and gateways, Ethernet operations, and concepts like cut-through forwarding, interframe gap, carrier signals, and CSMA/CD. The document is presented as a review of key topics in networking and internetworking.
This document discusses how the RINA framework supports network slicing through connectivity and performance isolation. It allows sharing of network resources while managing risks like security, costs, and ensuring high resource utilization. RINA isolates connectivity and performance at all layers through management of associations and quality of service. It also supports the flow of information needed to construct and manage network slices. RINA offers simplification through separation of concerns and code reuse, lowering total cost of ownership. It can be incrementally deployed and provides a coherent architecture for software-defined networking and network functions virtualization.
This document provides an overview of networking concepts including network types, medium access control protocols, TCP/IP protocol suite, addressing, Ethernet frames, ARP, and standards organizations. It begins with an agenda that lists these topics and includes diagrams to illustrate CSMA/CD, the OSI model, TCP/IP encapsulation, and Ethernet encapsulation. Examples are provided for different network devices, addressing formats and protocols.
In this session you will learn:
OSI reference model
OSI layers
Modbus communication protocol
Profibus communication protocol
Fieldbus communication protocol
This document summarizes a presentation on software defined networking (SDN). It discusses how SDN virtualizes networks in the same way server and desktops have been virtualized. SDN decouples the control plane from the data plane, allowing centralized control of network behavior and dynamic infrastructure provisioning. OpenFlow is presented as one approach to enable SDN by allowing communication between the network control and network devices. Potential benefits of SDN include flexibility, provisioning speed, improved security, efficiency and cost savings.
RINA research results - NGP forum - SDN World Congress 2017ARCFIRE ICT
RINA is a radically simple network architecture that takes an inter-process communication (IPC) approach. The key aspects of RINA are:
1) It uses a single type of layer called a Distributed IPC Facility (DIF) that can repeat as many times as needed. Each layer provides the same service of communication flows between application instances.
2) Layers isolate different scopes and allocate resources (e.g. bandwidth) to competing flows in a programmable way.
3) Experimental results show RINA can solve problems like congestion control and seamless renumbering more easily than IP networks. It also simplifies network management.
The document introduces RINA (Recursive Internet Architecture), a new networking architecture that aims to address structural problems with the OSI reference model. RINA defines a single type of layer that repeats as needed, providing the same inter-process communication (IPC) service between applications. It separates mechanisms from policies to simplify management. RINA allows for incremental deployment alongside existing technologies and is being researched through open source projects and standardization efforts.
The hageu rina-workshop-security-peterICT PRISTINE
RINA provides a framework to securely manage connectivity and network association. It protects layers instead of individual protocols, and addresses are contained within securable Distributed Interface Functions (DIFs). DIFs can replace firewalls and enable centralized policy-based authentication, authorization, and access control. RINA separates security mechanisms from policies, uses a common layer structure across layers, and minimizes complexity to improve security. It also provides a new access control architecture and key management system to securely manage network functions even if systems are compromised.
Introduction for internet connectivity (IoT)FabMinds
The document discusses key concepts related to internet connectivity including protocols, headers, packets and network interfaces. It defines common terms like IP header, TCP header, packet, IP address, port, socket and host. Packet refers to a set of bytes that travels through routers until reaching its destination. Headers include parameters encoded according to the IP and TCP protocols and travel with a packet. Network interfaces link layers and addresses and are identified by ports.
The document describes an SDK to exploit the programmability of RINA. RINA is a networking architecture based on the theory that networking is inter-process communication. The SDK aims to provide programmable functions at each layer through consistent APIs. It discusses design decisions around using Linux, a user/kernel split, programming languages, and threading models. The goal is to separate mechanism from policy to simplify network structure and support new requirements through re-usable policies across layers.
Samrat Ganguly
NEC
ONS2015: http://bit.ly/ons2015sd
ONS Inspire! Webinars: http://bit.ly/oiw-sd
Watch the talk (video) on ONS Content Archives: http://bit.ly/ons-archives-sd
This document provides an overview of SDN and Openflow. It describes the current state of networking with tightly coupled control and data planes. SDN is defined as having decoupled control and data planes, flow-based forwarding instead of destination-based, control logic in a controller, and a programmable network. The SDN architecture has layers including the infrastructure, Openflow southbound interface, network operating system controller, northbound APIs, programming languages, and applications.
1. MPLS simplifies forwarding by introducing label switching which uses a forwarding table and label carried in each packet rather than conventional IP routing based on IP addresses.
2. MPLS establishes label switched paths between routers where each router along the path transmits the packet to the next router by means of a label. Edge routers analyze packets and assign an initial label.
3. The main benefits of MPLS include improved performance, scalability, and traffic engineering capabilities compared to conventional IP routing.
The document discusses the flaws in the current network architecture. It describes how the architecture lacks structure, with protocols designed independently without commonality. This has led to protocol proliferation. The architecture also has issues with naming, addressing, multi-homing, and mobility due to using IP addresses as the sole identifier. The application programming interface further limits adoption of new protocols and provides no way to request quality of service parameters. Overall, the current architecture has problems in its structure, protocols, naming/addressing, service model, and lacks considerations for security and management.
Protocols and Interfaces - IPv4, IPv6, X.25, X.75Pradnya Saval
Introduction to TCP/IP: Issues in IPV4, IPV6 protocol, Mature Packet Switching Protocols: ITU Recommendation X.25, User Connectivity, Theory of Operations, Network Layer Functions, X.75 Internetworking Protocol, Advantages and Drawbacks
Passive Optical Networks: The MAC protocolsGiovanni Murru
This document discusses passive optical networks and their MAC protocols. It begins by describing the components and topology of a PON. It then explains that TDMA is commonly used to manage upstream transmission from ONUs to avoid collisions. The key MAC protocols, including MPCP and DBA, are explained in detail. Finally, it covers efficient polling mechanisms, QoS support, and bandwidth allocation strategies in PONs.
First Contact: Can Switching to RINA save the Internet?ARCFIRE ICT
RINA aims to provide advantages over the current Internet by optimizing all phases of communication. The study evaluates RINA's performance compared to TCP in a one-ISP scenario. It finds that RINA reduces preparation time compared to DHCP and DNS in the Internet, and improves efficiency for subsequent connections by reusing existing flows. RINA shows potential to combine benefits of TCP extensions like Fast Open. Future work includes optimizing RINA proxies and investigating a full transition from the Internet to RINA.
Energy-efficient Path Allocation Heuristic for Service Function ChainingStefano Salsano
1) The document proposes an energy-efficient heuristic algorithm for service function chaining path allocation in SDN networks. The goal is to minimize energy consumption by switching off unused servers while meeting quality of service constraints.
2) It formulates the problem as a mixed integer linear program to find optimal resource allocations and then develops a low-complexity heuristic to solve larger problem instances in reasonable time.
3) Results show the heuristic finds near-optimal solutions with much less computation time compared to the optimal approach as problem size increases in terms of network size and number of flows.
This document discusses a bandwidth-driven flow allocation policy for RINA that aims to guarantee bandwidth for flows during their lifetime and prevent network congestion. It proposes utilizing existing flow request and routing information to extend the routing graph with capacity details. A logically centralized but fault-tolerant approach is described that uses Raft consensus to intercept flow allocations and reserve bandwidth along viable paths. Congestion prevention is achieved by assuming each flow will use its requested bandwidth and rejecting requests that cannot be satisfied.
Area: Internet Area
Working Group: Distributed Mobility Management (DMM)
Draft: MN Identifier Types for RFC 4283 Mobile Node Identifier Option (draft-ietf-dmm-4283mnids-01 )
RFC: Requirements for Distributed Mobility Management (rfc7333)
This document summarizes various handover schemes for wireless communication. It discusses WiMAX and WLAN technologies and their architectures. For WiMAX, it describes the types of WiMAX and the mobile WiMAX architecture. It then explains horizontal handover schemes for WiMAX including hard handover, soft handover, fast BS switching, and enhanced ARP handover. For vertical handovers between WiMAX and WLAN, it outlines solutions like mobile IP, IP multicast, MIH, FMIPv6, HMIPv6, and SIP. It concludes that enhanced ARP handover has the best performance for horizontal handovers while the best vertical handover uses a combination of solutions.
RouteFlow & IXPs
This talk will discuss the architecture of RouteFlow which is a leading OpenFlow based virtual router. It will focus on the new projects based upon RouteFlow which are finding traction in Internet eXchange Points (IXPs) - Cardigan being one of the most popular one. Some common aspects of IXPS will be shown. The talk will conclude with a list of future projects and vision of SDN routing.
About Raphael Vincent Rosa
Raphael is a Communications Network Engineer. He finished his MS in Computer Science working with intra datacenter routing, contributing to open source SDN projects such as Ryu network controller and RouteFlow platform. Currently he is pursuing PhD research under the guidance of Dr. Christian Esteve Rothenburg with main interests in SDN and Distributed-NFV topics.
Mobile Ad Hoc Network of Simulation Framework Based on OPNETateeq ateeq
This document discusses mobile ad hoc networks (MANETs) and their simulation in OPNET. It defines MANETs as wireless networks without centralized administration composed of nodes that can freely and dynamically self-organize. The key characteristics of MANETs are that nodes are equal, there is no central control, and topology is dynamic. Common routing protocols for MANETs include DSDV, AODV, DSR. The document outlines modeling MANETs in OPNET including the network model with nodes, node model with routing/wireless modules, and analyzing performance metrics like delay from simulation results.
This presentation is divided into two parts. The first part describes the mobility management on different layers of TCP/IP stack. In the second, a set of IoT standards is presented including a small description for each.
5G in Brownfield how SDN makes 5G Deployments WorkLumina Networks
This document summarizes an open source networking group meetup about 5G and brownfield networks. It discusses how 5G will utilize distributed micro data centers and container networking to deploy services. It also explains how an open source central controller using projects like OpenStack and OpenDaylight can provide orchestration, service paths, and abstraction of network elements. Finally, it provides examples of how container networking and an open source SDN controller can help establish service paths and enable the deployment of 5G in hybrid brownfield environments.
RINA research results - NGP forum - SDN World Congress 2017ARCFIRE ICT
RINA is a radically simple network architecture that takes an inter-process communication (IPC) approach. The key aspects of RINA are:
1) It uses a single type of layer called a Distributed IPC Facility (DIF) that can repeat as many times as needed. Each layer provides the same service of communication flows between application instances.
2) Layers isolate different scopes and allocate resources (e.g. bandwidth) to competing flows in a programmable way.
3) Experimental results show RINA can solve problems like congestion control and seamless renumbering more easily than IP networks. It also simplifies network management.
The document introduces RINA (Recursive Internet Architecture), a new networking architecture that aims to address structural problems with the OSI reference model. RINA defines a single type of layer that repeats as needed, providing the same inter-process communication (IPC) service between applications. It separates mechanisms from policies to simplify management. RINA allows for incremental deployment alongside existing technologies and is being researched through open source projects and standardization efforts.
The hageu rina-workshop-security-peterICT PRISTINE
RINA provides a framework to securely manage connectivity and network association. It protects layers instead of individual protocols, and addresses are contained within securable Distributed Interface Functions (DIFs). DIFs can replace firewalls and enable centralized policy-based authentication, authorization, and access control. RINA separates security mechanisms from policies, uses a common layer structure across layers, and minimizes complexity to improve security. It also provides a new access control architecture and key management system to securely manage network functions even if systems are compromised.
Introduction for internet connectivity (IoT)FabMinds
The document discusses key concepts related to internet connectivity including protocols, headers, packets and network interfaces. It defines common terms like IP header, TCP header, packet, IP address, port, socket and host. Packet refers to a set of bytes that travels through routers until reaching its destination. Headers include parameters encoded according to the IP and TCP protocols and travel with a packet. Network interfaces link layers and addresses and are identified by ports.
The document describes an SDK to exploit the programmability of RINA. RINA is a networking architecture based on the theory that networking is inter-process communication. The SDK aims to provide programmable functions at each layer through consistent APIs. It discusses design decisions around using Linux, a user/kernel split, programming languages, and threading models. The goal is to separate mechanism from policy to simplify network structure and support new requirements through re-usable policies across layers.
Samrat Ganguly
NEC
ONS2015: http://bit.ly/ons2015sd
ONS Inspire! Webinars: http://bit.ly/oiw-sd
Watch the talk (video) on ONS Content Archives: http://bit.ly/ons-archives-sd
This document provides an overview of SDN and Openflow. It describes the current state of networking with tightly coupled control and data planes. SDN is defined as having decoupled control and data planes, flow-based forwarding instead of destination-based, control logic in a controller, and a programmable network. The SDN architecture has layers including the infrastructure, Openflow southbound interface, network operating system controller, northbound APIs, programming languages, and applications.
1. MPLS simplifies forwarding by introducing label switching which uses a forwarding table and label carried in each packet rather than conventional IP routing based on IP addresses.
2. MPLS establishes label switched paths between routers where each router along the path transmits the packet to the next router by means of a label. Edge routers analyze packets and assign an initial label.
3. The main benefits of MPLS include improved performance, scalability, and traffic engineering capabilities compared to conventional IP routing.
The document discusses the flaws in the current network architecture. It describes how the architecture lacks structure, with protocols designed independently without commonality. This has led to protocol proliferation. The architecture also has issues with naming, addressing, multi-homing, and mobility due to using IP addresses as the sole identifier. The application programming interface further limits adoption of new protocols and provides no way to request quality of service parameters. Overall, the current architecture has problems in its structure, protocols, naming/addressing, service model, and lacks considerations for security and management.
Protocols and Interfaces - IPv4, IPv6, X.25, X.75Pradnya Saval
Introduction to TCP/IP: Issues in IPV4, IPV6 protocol, Mature Packet Switching Protocols: ITU Recommendation X.25, User Connectivity, Theory of Operations, Network Layer Functions, X.75 Internetworking Protocol, Advantages and Drawbacks
Passive Optical Networks: The MAC protocolsGiovanni Murru
This document discusses passive optical networks and their MAC protocols. It begins by describing the components and topology of a PON. It then explains that TDMA is commonly used to manage upstream transmission from ONUs to avoid collisions. The key MAC protocols, including MPCP and DBA, are explained in detail. Finally, it covers efficient polling mechanisms, QoS support, and bandwidth allocation strategies in PONs.
First Contact: Can Switching to RINA save the Internet?ARCFIRE ICT
RINA aims to provide advantages over the current Internet by optimizing all phases of communication. The study evaluates RINA's performance compared to TCP in a one-ISP scenario. It finds that RINA reduces preparation time compared to DHCP and DNS in the Internet, and improves efficiency for subsequent connections by reusing existing flows. RINA shows potential to combine benefits of TCP extensions like Fast Open. Future work includes optimizing RINA proxies and investigating a full transition from the Internet to RINA.
Energy-efficient Path Allocation Heuristic for Service Function ChainingStefano Salsano
1) The document proposes an energy-efficient heuristic algorithm for service function chaining path allocation in SDN networks. The goal is to minimize energy consumption by switching off unused servers while meeting quality of service constraints.
2) It formulates the problem as a mixed integer linear program to find optimal resource allocations and then develops a low-complexity heuristic to solve larger problem instances in reasonable time.
3) Results show the heuristic finds near-optimal solutions with much less computation time compared to the optimal approach as problem size increases in terms of network size and number of flows.
This document discusses a bandwidth-driven flow allocation policy for RINA that aims to guarantee bandwidth for flows during their lifetime and prevent network congestion. It proposes utilizing existing flow request and routing information to extend the routing graph with capacity details. A logically centralized but fault-tolerant approach is described that uses Raft consensus to intercept flow allocations and reserve bandwidth along viable paths. Congestion prevention is achieved by assuming each flow will use its requested bandwidth and rejecting requests that cannot be satisfied.
Area: Internet Area
Working Group: Distributed Mobility Management (DMM)
Draft: MN Identifier Types for RFC 4283 Mobile Node Identifier Option (draft-ietf-dmm-4283mnids-01 )
RFC: Requirements for Distributed Mobility Management (rfc7333)
This document summarizes various handover schemes for wireless communication. It discusses WiMAX and WLAN technologies and their architectures. For WiMAX, it describes the types of WiMAX and the mobile WiMAX architecture. It then explains horizontal handover schemes for WiMAX including hard handover, soft handover, fast BS switching, and enhanced ARP handover. For vertical handovers between WiMAX and WLAN, it outlines solutions like mobile IP, IP multicast, MIH, FMIPv6, HMIPv6, and SIP. It concludes that enhanced ARP handover has the best performance for horizontal handovers while the best vertical handover uses a combination of solutions.
RouteFlow & IXPs
This talk will discuss the architecture of RouteFlow which is a leading OpenFlow based virtual router. It will focus on the new projects based upon RouteFlow which are finding traction in Internet eXchange Points (IXPs) - Cardigan being one of the most popular one. Some common aspects of IXPS will be shown. The talk will conclude with a list of future projects and vision of SDN routing.
About Raphael Vincent Rosa
Raphael is a Communications Network Engineer. He finished his MS in Computer Science working with intra datacenter routing, contributing to open source SDN projects such as Ryu network controller and RouteFlow platform. Currently he is pursuing PhD research under the guidance of Dr. Christian Esteve Rothenburg with main interests in SDN and Distributed-NFV topics.
Mobile Ad Hoc Network of Simulation Framework Based on OPNETateeq ateeq
This document discusses mobile ad hoc networks (MANETs) and their simulation in OPNET. It defines MANETs as wireless networks without centralized administration composed of nodes that can freely and dynamically self-organize. The key characteristics of MANETs are that nodes are equal, there is no central control, and topology is dynamic. Common routing protocols for MANETs include DSDV, AODV, DSR. The document outlines modeling MANETs in OPNET including the network model with nodes, node model with routing/wireless modules, and analyzing performance metrics like delay from simulation results.
This presentation is divided into two parts. The first part describes the mobility management on different layers of TCP/IP stack. In the second, a set of IoT standards is presented including a small description for each.
5G in Brownfield how SDN makes 5G Deployments WorkLumina Networks
This document summarizes an open source networking group meetup about 5G and brownfield networks. It discusses how 5G will utilize distributed micro data centers and container networking to deploy services. It also explains how an open source central controller using projects like OpenStack and OpenDaylight can provide orchestration, service paths, and abstraction of network elements. Finally, it provides examples of how container networking and an open source SDN controller can help establish service paths and enable the deployment of 5G in hybrid brownfield environments.
Demystifying Orchestration and Assurance Across SDN NFV CE2.0WebNMS
Service providers worldwide are moving toward the dream goal of service automation from the front end of customer ordering and service monitoring to the back end of service provisioning, network monitoring, and active service-level agreement (SLA) enforcement.These are explored in depth with expert opinions. Also explored are a customer self-service portal for on-demand ordering and monitoring of Ethernet services, intelligent customer premises equipment for provisioning and monitoring, and testing and monitoring software for ensuring workability across physical and virtual networks.
The document discusses the promise of SDN for transport networks. It notes changing business and usage models are driving the need for more elastic, on-demand networks. SDN can help by providing programmable control of optical networks through standardized interfaces. The OIF and ONF conducted a global demo of transport SDN using an application for cloud bursting over optical networks. This identified gaps around multi-domain control and relationships between controllers and network management. Wider SDN deployment faces challenges around operational simplicity, scalability, security and continuous availability. Multiple SDOs are working on related standards but alignment is still needed.
Transport SDN Overview and Standards Update: Industry PerspectivesInfinera
This document provides an overview and update on transport SDN standards. It discusses:
1) The evolving core network landscape including 100Gb coherent technology and bandwidth needs for cloud services.
2) Transport SDN can provide dynamic network programmability and unified control over multi-layer, multi-vendor networks.
3) Key applications for transport SDN include networking as a service, virtual transport networks, and multi-layer orchestration.
Using ICN to simplify data delivery, mobility management and secure transmissionITU
ICN provides a unified network and transport layer addressing content by name rather than by location. By disrupting traditional connection-oriented communication model, ICN simplifies data delivery, mobility management and secure transmission over an heterogeneous network access. In the demo, we select DASH video delivery as use case and show the benefits of ICN mobility management, in-network control (rate/loss) and network-assisted bitrate adaptation for a multi-homed user device.
We also illustrate how ICN can effectively reduce transport cost via native edge caching and multi-point/multi-source communications over the backhaul. To that aim, we orchestrate an ICN-enhanced virtualized network backhaul and shows its utilization over time.
Author : Giovanna Carofiglio, Cisco Systems
Presented at ITU-T Focus Group IMT-2020 Workshop and Demo Day, 7 December 2016.
More details on the event : http://www.itu.int/en/ITU-T/Workshops-and-Seminars/201612/Pages/Programme.aspx
This document provides an overview of the syllabus for a Computer Networks course. It includes:
- An outline of the course units which cover data communication components, the OSI model, TCP/IP model, and each layer of the OSI model from layers 2 through 7.
- Evaluation criteria which includes continuous internal evaluation, semester end examination, and mandatory minimum marks.
- Suggested reading materials including textbooks and publications.
- An overview of the Computer Networks lab covering various experiments involving networking tools, protocols, programming, and simulation.
Cardigan is an SDN-based distributed routing fabric that is being deployed at an Internet exchange (IXP) to provide routing as a service. It aims to build experience with SDN, provide a practical migration path from non-SDN networks, and rethink IXP architecture. The pilot deployment has been running for 9 months, routing traffic for 90 organizations through 1134 flows on each switch.
The document discusses handoff schemes for high-speed mobile internet services. It covers horizontal handoffs, which involve changing access points within the same network, and vertical handoffs, which involve changing network technologies. It proposes two schemes: 1) Performing authentication for neighboring access points in advance to reduce handoff latency. 2) Creating a Handoff Management System Multi-Network (HMSMN) architecture to manage handoffs across different network types. Both schemes aim to make handoffs faster and more seamless for users moving between access points and network technologies at high speeds.
Realizing a Multi-Layer Transport SDN: Practical Considerations and Implement...Infinera
The document discusses implementing software-defined networking (SDN) across multiple network layers. It describes challenges with current isolated network layers and vendor-specific solutions. SDN could help by enabling programmable networking, network abstractions, and open standardized interfaces. This would allow centralized control across multi-layer, multi-vendor networks. The document also outlines an architecture using an Open Transport Switch (OTS) and SDN controller to provide multi-layer provisioning and traffic optimization across packet and optical networks in a demonstration network.
This document discusses when a service mesh may be needed and provides an overview of the current service mesh landscape. It begins with why microservices are adopted and the challenges of operating distributed applications. It then describes a maturity journey where a service mesh is not initially needed but may become useful for applications that become more complex, distributed, and interdependent. The document outlines some current major service mesh implementations and notes that the technology is still new and changing rapidly. It recommends investigating service meshes through proof of concepts but cautions that production usage requires significant resources. It profiles F5 Aspen Mesh and NGINX solutions for service meshes and microservices.
RINA as a Clean-Slate Approach to Software Networks ICT PRISTINE
RINA is a clean-slate networking architecture that models the network as a hierarchy of applications interconnected across distributed application frameworks (DAFs). It uses a single layer approach with two protocols for data transfer and application management. RINA addresses many of the goals for 5G networks, such as facilitating dense device deployments, reducing service creation times, and providing secure, reliable connectivity. The document proposes using RINA to provide the infrastructure for network function virtualization, such as through service chains, VNF connectivity and resiliency, and software-based management. This could optimize fabric usage within network points of presence while being compatible with current IP-based network deployments.
Considerations for Deploying Virtual Network Functions and ServicesOpen Networking Summit
The document discusses considerations for deploying virtual network functions and services using network function virtualization (NFV). It describes the key concepts of NFV including separating network functions from dedicated hardware, increasing network elasticity, and addressing heterogeneity. It outlines the main business drivers for NFV including reducing costs, simplifying network management, and shortening time to market for new services. Finally, it discusses carrier Ethernet use cases, virtual network function deployment models, and options for deploying functions at customer premises.
APNIC Training Delivery Manager Terry Sweetser presents an overview of Internet Exchange Points at PacNOG 31, held in Port Vila, Vanuatu from 26 to 30 June 2023.
PITA 27th AGM & Business Forum Expo 23: Internet Exchange PointsAPNIC
APNIC Training Delivery Manager Terry Sweetser presented on smarter networking and Internet traffic efficiency with Internet Exchange Points at the PITA 27th AGM & Business Forum Expo 23, held from 29 May to 1 June 2023, in Port Moresby, Papua New Guinea.
This document discusses Software Defined Networking (SDN), Segment Routing (SR), Network Functions Virtualization (NFV), and Mobile Edge Computing (MEC) as essential technologies for 5G networks. It explains that SDN and SR are needed to dynamically set up network slices to guarantee quality of service, while NFV and MEC are needed to instantiate virtual network functions. It then provides more detailed explanations of why SDN and NFV are important technologies, focusing on the trends of blurred lines between computation and communications, and declining profitability of traditional network providers.
Similar to Aalto University Mobile Management in SDN (20)
2. Agenda
1. Mobility Management in the Internet
2. Internet mobility overview
3. Problem in detail
4. Mobility management based on SDN
1. Existing research
2. Benefits of SDN based mobility
5. Software Defined Internet Mobility Management
1. Architecture overview
2. An open flow instantiation
3. Binding cache Placement Algorithm
1. Evaluation, experiment and results
6. Summary
24.3.2016
2
3. Mobility
Management in the
Internet
24.3.2016
3
• Along with the growing of mobile data services
efforts on Internet mobility have been paid
• So far there is no consensus
– Remains as an open issue
4. MMI and cellular networks
• Cellular networking has been providing mobility
• Why it may not suit Internet Mobility?
ISP handover
Inter device switching
• Trend to provide flexible & dynamic mobility management
• IP is considered as the core part of upcoming cellular networks
• LTE deployment has started in many markets: does not have circuit switched services
anymore
• Cellular networking is evolving toward IP- based designs (e.g. femtocells )
24.3.2016
4
5. Existing Internet Mobility solution
• Internet mobility = Uninterrupted internet connectivity
• Candidates: many IP mobility solutions
• IETF released standards that may be adopted into 3GPP: Proxy
Mobile IPv6 (EPC 3GPP)
• Challenge:
• Mobility contradicts current Internet architecture: Tight coupling
of higher layer protocols with IP address:
• TCP sessions are identified by Source-IP-add, Source-port, dest-IP add and dest
port
• Approach categories:
1. Routing based -> Keep IP address
2. Mapping based -> Use identifier to resolve locator (IP address):
Mobile IP protocols
24.3.2016
5
6. Integrating Internet mobility
management and SDN
• Despite of the various realizations of mobility management
they drawback different aspects: still an unsolved issue
• SDN emerging network architectural has a new approach:
• Network structures, functions and performance are defined simpler
thanks to programmable devices and centralized control logic
• Network features required to support IP mobility can also be
realized in software defined ways.
• Open Flow the most well known instantiation of SDN
24.3.2016
6
7. SDN helps to solve IP mobility
protocols problems ?
• Programmable devices provide flexibility
• Centralized control enables awareness of all mobility details
• IP mobility may require less host involvement under SDN
24.3.2016
7
9. Internet mobility overview
1. Mobile IP
• IETF standards
- Many derivatives (PMIP v6 )
- Standardization began two decades ago
2. Identifier/Locator Split ( ILS ) designs
• Relies on hosts to realize mobility management
• An IP address has embedded both identifier and locator
- A concept also discussed widely in past decades
3. Other proposals on future Internet Architecture
• Substantial changes to the current Internet
24.3.2016
9
10. MobileIP&derivatives
• Minimal Handover Latency
• No client software requirement ( in the case
of PMIPv6)
• Extremely Light Weight Protocol, MAG
function can be implemented on a low-cost
access point
• MIP centralizes mobility signalling and
forwarding -> single Home Agent (HA)
• Increase signalling cost when out Home
network
• All packets from CN to MN have to go
through HA -> Triangle routing problem
• Thus heavy load for HAs
• Distributed Mobility Management (DMM)
• Multiple mobility anchors
• HoA not a fixed location any more
*Under standardization
24.3.2016
10
11. 1. ILS designs
24.3.2016
11
• Two categories:
– Separate edge and core add name spaces. Focused in
global routing *
– Entire IP space as locators: A namespace for identifiers
• Host based solutions (mobility
implemented at host side)
• Either introduce a new layer or modify
existing layer
• Host Identity Protocol (HIP)= DNS +
Rendezvous -> new layer above network
layer
• Identifier/Locator Network Protocol (ILNP) =
Split IP ->Modifies transport layer
• Name Based Sockets (NBS) = Domain
names ID-> new layer above transport layer
• LISP Mobile Node= Endpoint ID and Routing
locators (RLOC)->Lightweight tunnel routing
on each mobile host (avoids use of DNS)
*These are not in the scope of this slides
The same idea with different
formatting, implementation
and mapping functions
13. Mobility management analysis
Considering handoff management:
• Three categories:
• Local scope handoff : MIPs
• Global scope handoff : ILS designs
• Hybrid: DMM solutions *(under standardization at IETF)
• Local scope handoff :propagate mapping to close HA
• Global scope handoff: propagate globally if HA has changed
• Packets are forwarded to an intermediary node close to MN
Similarities: All of them require MN to announce its up to date mapping to network
so that CN can reach it , directly(ILS) or indirectly (MIP)
24.3.2016
13
14. Routing path stretch and handoff
efficiency
Trade off between routing path stretch and hand off latency
• Limited scope of mapping announcement reduce signalling
overhead and latency but CN loses exact location and has to
reach MN via indirection which may lead to routing path stretch.
• Mobile IP leads to routing path stretch (e.g. triangle routing)
• ILS heavy overhead and large latency
• DMM a balanced option? (Last draft: 2015-04-22 )
• Future mobile users connect simultaneously to multiple ISP and switch between
them.
24.3.2016
14
15. Mobility management based on SDN
Existing research
• Open Roads
• Improve robustness of handoff with multicast Open Flow
• Improving basic IP mobility functions adopted by existing
protocols
• SDN/Open Flow in Virtualized LTE to support distributed
mobility management
24.3.2016
15
16. Benefits of SDN based mobility
1. Existing solutions with different trade-offs, and not really
flexible
2. A promising way to seek balance for the performance of the
trade off
3. Programmable devices are enabled as potential rendezvous
for MNs
1. No performing mapping announcement in arbitrary scope
2. Centralized control can define the scope
24.3.2016
16
17. Software Defined Internet Mobility
Management
The important for SDIMM:
Seek an algorithm that optimizes the
scope of mapping announcements
24.3.2016
17
18. • Architecture overview
24.3.2016
18
– Identifiers as in ILS
» Any format but a field in
packet devices can
recognize
– Locators of MNs
» IP address, normally
– Two control plane sub
functions:
» SDN controllers collect
current location of MN
» SDN controllers download
mapping in relevant SDN
devices (on request or
update)
20. Protocol basis
1. Locator ( CoA )
• IP address
2. Identifier ( HoA )
• IP address
3. OpenFlow controller
maintains binding cache
4. OpenFlow switches
1. Maintain replica of binding
cache
2. Redirect packets to MN
according flow table
• Inter domain handoff: long
distance, tringle and the
optimize
• Short distance: single logic
24.3.2016
20
21. Binding Cache Placement Algorithm
But in which switch (TS) place cache binding
• MN’s first hop = Triangle routing (like MIP)
• CN’s first hop = Large number of flow table download and
high latency (like HIP)
=>Binding Cache Placement Problem
24.3.2016
21
23. 1. Evaluation
1. Algorithm proposed, assuming:
1. Intra domain scenario
2. MN to CN only relies in destination address
2. Algorithm random for each path pair of previous and current
path chose randomly any switch
3. Algorithm CN, For each pair of paths choose CN’s first hop
24.3.2016
23
27. Conclusion
Experiment show advantage of SDN architecture due to:
• Centralized control
• Programmable devices
• In general SDN enables flexibility
• => Adaptive to various scenarios in future
mobile Internet
24.3.2016
27