Many thanks to Nick McKeown (Stanford), Jennifer Rexford (Princeton), Scott Shenker (Berkeley), Nick Feamster (Princeton), Li Erran Li (Columbia), Yashar Ganjali (Toronto)
Software defined networking (SDN) aims to decouple the network control and data planes by providing an open standard application programming interface (API). This allows for a logically centralized controller that maintains a global view of the network. The controller can programmatically configure forwarding rules on SDN switches using the API. This new architecture enables more flexible, programmable networks and has consequences for both industry and research. For industry, it promises to accelerate innovation, lower costs, and create new services. For research, it provides opportunities to develop new network programming languages and abstractions that simplify network specification and management.
This document provides an overview of network programmability and Software Defined Networking (SDN). It discusses the evolution from traditional networks to SDN, including early concepts like active networking and separating the control and data planes. OpenFlow is introduced as an SDN protocol that enables an external controller to program the forwarding behavior of network switches. Key benefits of SDN like network programmability, innovation, and direct control over the data plane are covered. The roles of the SDN controller and OpenFlow switches are described. Examples of SDN applications and components like controllers are also mentioned.
Software defined networking (SDN) separates the network control plane from the forwarding plane, allowing a single, centralized control plane to control multiple forwarding devices. SDN gives network administrators the ability to abstract the underlying network infrastructure and program how network traffic is handled. This allows SDN to simplify network management and make the network more flexible, programmable, and adaptable to changing needs. However, implementing SDN also presents challenges related to changing traditional network architectures, security, and specialized technical knowledge requirements.
The Challenges of SDN/OpenFlow in an Operational and Large-scale NetworkOpen Networking Summits
Jun Bi
Professor & Director
Tsinghua University
Outline
• Intra-AS (campus level) IPv6 source address validation using OpenFlow (with extension)
– Good for introducing new IP services to network
• Planning next step if we run SDN as a common infrastructure for new services and architectures
– Some personal viewpoints and thoughts on design challenges
– Forwarding abstraction for Post-IP architectures
– Control abstraction for scalable NOS and programmable/manageable virtualization platform
– Inter-AS policies negotiation abstraction
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
The realization of network softwarization, an overarching buzzword to encompass all software-centric developments from the Software-Defined Networking (SDN) and Network Function Virtualization (NFV) trends, is being enabled through a set of innovations in high-speed data plane design and implementation. Recent efforts include te-architecting the hardware-software interfaces and exposing programmatic interfaces (e.g., OpenFlow), programmable hardware-based pipelines (e.g. Protocol Independent Switch Architecture – PISA) along suitabe programming languages (e.g., P4), and multiple advances on low overhead virtualization and fast packet processing libraries (e.g. DPDK, FD.io) for Linux based general purpose processor platforms. This talk provides an overview of relevant ongoing work and discusses the trade-offs of each design and implementation choice of software-defined dataplanes regarding Programmability, Performance, and Portability.
Analytical Modeling of End-to-End Delay in OpenFlow Based NetworksAzeem Iqbal
OpenFlow enabled networks split and separate the data and control planes of traditional networks. This design commodifies network switches and enables centralized control of the network. Control decisions are made by an OpenFlow controller, and locally cached by switches, as directed by controllers. Since controllers are not necessarily co-located with switches that can significantly impact the forwarding delay incurred by packets in switches. Only very few studies have been conducted to evaluate the performance of OpenFlow in terms of end-to-end delay. In this work we develop a stochastic model for the end to end delay in OpenFlow switches based on measurements made in Internetscale experiments performed on three different platforms, i.e. Mininet, the GENI testbed and the OF@TEIN testbed.
Senior Network Analyst Tashi Phuntsho gives an overview of network automation at the fifth Bhutan Network Operators Group (btNOG 5) meeting on 4 June 2018.
Software defined networking (SDN) decouples the network control and forwarding functions, allowing the control to be centralized and the underlying network to be abstracted from applications. This provides benefits like centralized management, rapid innovation, and increased network programmability. SDN uses protocols like OpenFlow that define messages between a controller and switches to build flow tables for packet forwarding using matches and actions. SDN is well suited for data center networks where it allows for network virtualization and easier configuration changes.
Software defined networking (SDN) aims to decouple the network control and data planes by providing an open standard application programming interface (API). This allows for a logically centralized controller that maintains a global view of the network. The controller can programmatically configure forwarding rules on SDN switches using the API. This new architecture enables more flexible, programmable networks and has consequences for both industry and research. For industry, it promises to accelerate innovation, lower costs, and create new services. For research, it provides opportunities to develop new network programming languages and abstractions that simplify network specification and management.
This document provides an overview of network programmability and Software Defined Networking (SDN). It discusses the evolution from traditional networks to SDN, including early concepts like active networking and separating the control and data planes. OpenFlow is introduced as an SDN protocol that enables an external controller to program the forwarding behavior of network switches. Key benefits of SDN like network programmability, innovation, and direct control over the data plane are covered. The roles of the SDN controller and OpenFlow switches are described. Examples of SDN applications and components like controllers are also mentioned.
Software defined networking (SDN) separates the network control plane from the forwarding plane, allowing a single, centralized control plane to control multiple forwarding devices. SDN gives network administrators the ability to abstract the underlying network infrastructure and program how network traffic is handled. This allows SDN to simplify network management and make the network more flexible, programmable, and adaptable to changing needs. However, implementing SDN also presents challenges related to changing traditional network architectures, security, and specialized technical knowledge requirements.
The Challenges of SDN/OpenFlow in an Operational and Large-scale NetworkOpen Networking Summits
Jun Bi
Professor & Director
Tsinghua University
Outline
• Intra-AS (campus level) IPv6 source address validation using OpenFlow (with extension)
– Good for introducing new IP services to network
• Planning next step if we run SDN as a common infrastructure for new services and architectures
– Some personal viewpoints and thoughts on design challenges
– Forwarding abstraction for Post-IP architectures
– Control abstraction for scalable NOS and programmable/manageable virtualization platform
– Inter-AS policies negotiation abstraction
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
The realization of network softwarization, an overarching buzzword to encompass all software-centric developments from the Software-Defined Networking (SDN) and Network Function Virtualization (NFV) trends, is being enabled through a set of innovations in high-speed data plane design and implementation. Recent efforts include te-architecting the hardware-software interfaces and exposing programmatic interfaces (e.g., OpenFlow), programmable hardware-based pipelines (e.g. Protocol Independent Switch Architecture – PISA) along suitabe programming languages (e.g., P4), and multiple advances on low overhead virtualization and fast packet processing libraries (e.g. DPDK, FD.io) for Linux based general purpose processor platforms. This talk provides an overview of relevant ongoing work and discusses the trade-offs of each design and implementation choice of software-defined dataplanes regarding Programmability, Performance, and Portability.
Analytical Modeling of End-to-End Delay in OpenFlow Based NetworksAzeem Iqbal
OpenFlow enabled networks split and separate the data and control planes of traditional networks. This design commodifies network switches and enables centralized control of the network. Control decisions are made by an OpenFlow controller, and locally cached by switches, as directed by controllers. Since controllers are not necessarily co-located with switches that can significantly impact the forwarding delay incurred by packets in switches. Only very few studies have been conducted to evaluate the performance of OpenFlow in terms of end-to-end delay. In this work we develop a stochastic model for the end to end delay in OpenFlow switches based on measurements made in Internetscale experiments performed on three different platforms, i.e. Mininet, the GENI testbed and the OF@TEIN testbed.
Senior Network Analyst Tashi Phuntsho gives an overview of network automation at the fifth Bhutan Network Operators Group (btNOG 5) meeting on 4 June 2018.
Software defined networking (SDN) decouples the network control and forwarding functions, allowing the control to be centralized and the underlying network to be abstracted from applications. This provides benefits like centralized management, rapid innovation, and increased network programmability. SDN uses protocols like OpenFlow that define messages between a controller and switches to build flow tables for packet forwarding using matches and actions. SDN is well suited for data center networks where it allows for network virtualization and easier configuration changes.
Radisys/Wind River: The Telcom Cloud - Deployment Strategies: SDN/NFV and Vir...Radisys Corporation
Radisys and Wind River present on the evolution to the Telecom Cloud and how cloud technology and network virtualization will provide both big opportunities and challenges for operators. Important details and insights are shared on Network Function Virtualization (NFV), Software Defined Network (SDN) and Virtualization.
The document discusses security issues in software-defined networking (SDN). It outlines how SDN architectures separate the control plane from the data plane and use centralized controllers. However, this introduces new security threats, such as attacks on controllers, control plane communication, and applications. The document analyzes threats across the different SDN layers and proposes some mitigation approaches, concluding that while SDN was not initially designed with security in mind, it could potentially improve network security when properly implemented.
ONOS: Open Network Operating System. An Open-Source Distributed SDN Operating...ON.LAB
ONOS
Open Network Operating System
An Open-Source Distributed SDN OS
Pankaj Berde, Jonathan Hart, Masayoshi Kobayashi, Pavlin Radoslavov, Pingping Lin, Rachel Sverdlov, Suibin Zhang, William Snow, Guru Parulkar
This document provides an overview of software defined networking (SDN), including its evolution from traditional router architectures, the seminal Clean Slate project and OpenFlow protocol, and the current SDN architecture. It discusses key SDN concepts like the separation of the control and data planes, standardization bodies, example applications like VOLTHA and ONOS, and related technologies like NFV and P4.
The main scope of up-gradation to the advanced computer networks is to make the technical advancement in the network management and so managing the traffic control (that is the control plane and data or forwarding plane) while abridging it in the Multi-Controller Domain. SDN refers to the isolation of the network control plane from the forwarding plane, with a control plane overseeing many networking systems. This paper investigates how new improvements in SDN and the programmability of networks can be helpful to abridge tasks, improve dexterity, and encounter new task necessities within the U.S. Department of Defense (DoD) and open networks. These improvised network services across the digital network entail a multi-controller domain. This paper represents the research in SDN and multi-controller domain, aiming at OpenFlow Protocol and its upcoming challenging tasks.
OpenFlow/Software-defined Networking aims to open up the network infrastructure through a "software-defined networking" approach. It proposes using simple packet forwarding hardware with an open interface and a network operating system that provides a well-defined open API. This allows multiple network operating systems or versions to run over the same underlying hardware, similar to how virtualization allows multiple operating systems to run on the same computer hardware. OpenFlow specifies the open interface and protocol to enable this new paradigm of network virtualization and programmability.
btNOG 9 presentation Introduction to Software Defined NetworkingAPNIC
SDN evolved from the Clean Slate project which sought to redesign the internet using a clean slate approach. This led to the development of OpenFlow, which separated the control plane and data plane of network devices. SDN is defined as the separation of the network control plane from the forwarding plane, with a control plane controlling several devices. It provides network agility and flexibility through enhanced programmability, disaggregation of the control plane from hardware, and centralized network control with visibility. Key SDOs developing SDN standards include ONF, IETF, and IEEE.
Networking revolution in last 6-7 years. This document shows the very brief of high level concept in changing Networking technology from legacy networking to future ideas.
Software defined networking (SDN) uses OpenFlow to separate the control plane of network switches from the data plane. This allows for network programmability and innovation through open protocols and APIs. SDN has the potential to reduce network costs, increase flexibility, and lead to new use cases. However, challenges remain around OpenFlow limitations, scalability, and vendor dependence.
The document discusses software defined networking (SDN) and OpenFlow, including their history, key concepts, potential uses and challenges. SDN aims to separate the network control and forwarding functions through open standards like OpenFlow. This could make networks more programmable and innovative while reducing costs. However, challenges include limitations of the current standards and ensuring scalability and interoperability across vendors.
This document discusses network virtualization and its history. It provides the following key points:
1) Network virtualization aims to decouple virtual networks from physical infrastructure through techniques like tunneling and encapsulation, allowing independent address spaces and topologies.
2) Early work included overlay networks for deployment and experimentation. Virtualization is now used in data centers to isolate tenant traffic and connect virtual machines across sites.
3) The OpenVirteX project aims to advance network virtualization by exposing the entire physical topology to virtual network controllers and allowing independent address spaces and topologies through header rewriting. This would provide more flexibility than existing solutions.
Software-Defined Networking(SDN):A New Approach to NetworkingAnju Ann
This document provides an overview of Software-Defined Networking (SDN). It discusses how SDN decouples the network control plane from the forwarding plane, allowing for centralized control and programmability. The key components of the SDN architecture include OpenFlow switches, an SDN controller, and northbound and southbound APIs. OpenFlow is described as the primary southbound protocol, allowing the controller to program how packets are handled by switches. Example applications of SDN mentioned are network slicing and multi-tenancy in cloud computing. Challenges for SDN adoption are also noted.
SDN 101: Software Defined Networking Course - Sameh Zaghloul/IBM - 2014SAMeh Zaghloul
This document provides an overview of software defined networking (SDN). It discusses how SDN enables data center teams to use software to efficiently control network resources, compared to traditional network switches. The document outlines several SDN topics and related technologies, including SDN standards, network function virtualization, use cases, sample projects, surveys, case studies, online courses, and software tools. It also includes sections on SDN architecture and how SDN is important for virtual environments and VM mobility.
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.
Understanding network and service virtualizationSDN Hub
This document discusses network and service virtualization technologies. It begins with an overview of challenges with current network architectures and how virtualization addresses them. It then covers three key trends: 1) network virtualization using SDN to program networks dynamically, 2) service virtualization using NFV to virtualize network functions, and 3) new infrastructure tools like Open vSwitch, OpenDaylight, and Docker networking. Finally, it discusses approaches to deploying network and service virtualization and provides a vendor landscape.
This document provides an introduction to OpenFlow, SDN, and NFV. It describes the need for new networking paradigms and outlines some of the key problems with traditional networking approaches. OpenFlow is presented as providing open interfaces and programmability to network nodes. SDN is defined as separating the control logic from the forwarding plane and enabling programmable automation through open APIs. NFV aims to virtualize network functions to improve flexibility, reduce costs, and accelerate service deployment using standard IT virtualization technologies.
Radisys/Wind River: The Telcom Cloud - Deployment Strategies: SDN/NFV and Vir...Radisys Corporation
Radisys and Wind River present on the evolution to the Telecom Cloud and how cloud technology and network virtualization will provide both big opportunities and challenges for operators. Important details and insights are shared on Network Function Virtualization (NFV), Software Defined Network (SDN) and Virtualization.
The document discusses security issues in software-defined networking (SDN). It outlines how SDN architectures separate the control plane from the data plane and use centralized controllers. However, this introduces new security threats, such as attacks on controllers, control plane communication, and applications. The document analyzes threats across the different SDN layers and proposes some mitigation approaches, concluding that while SDN was not initially designed with security in mind, it could potentially improve network security when properly implemented.
ONOS: Open Network Operating System. An Open-Source Distributed SDN Operating...ON.LAB
ONOS
Open Network Operating System
An Open-Source Distributed SDN OS
Pankaj Berde, Jonathan Hart, Masayoshi Kobayashi, Pavlin Radoslavov, Pingping Lin, Rachel Sverdlov, Suibin Zhang, William Snow, Guru Parulkar
This document provides an overview of software defined networking (SDN), including its evolution from traditional router architectures, the seminal Clean Slate project and OpenFlow protocol, and the current SDN architecture. It discusses key SDN concepts like the separation of the control and data planes, standardization bodies, example applications like VOLTHA and ONOS, and related technologies like NFV and P4.
The main scope of up-gradation to the advanced computer networks is to make the technical advancement in the network management and so managing the traffic control (that is the control plane and data or forwarding plane) while abridging it in the Multi-Controller Domain. SDN refers to the isolation of the network control plane from the forwarding plane, with a control plane overseeing many networking systems. This paper investigates how new improvements in SDN and the programmability of networks can be helpful to abridge tasks, improve dexterity, and encounter new task necessities within the U.S. Department of Defense (DoD) and open networks. These improvised network services across the digital network entail a multi-controller domain. This paper represents the research in SDN and multi-controller domain, aiming at OpenFlow Protocol and its upcoming challenging tasks.
OpenFlow/Software-defined Networking aims to open up the network infrastructure through a "software-defined networking" approach. It proposes using simple packet forwarding hardware with an open interface and a network operating system that provides a well-defined open API. This allows multiple network operating systems or versions to run over the same underlying hardware, similar to how virtualization allows multiple operating systems to run on the same computer hardware. OpenFlow specifies the open interface and protocol to enable this new paradigm of network virtualization and programmability.
btNOG 9 presentation Introduction to Software Defined NetworkingAPNIC
SDN evolved from the Clean Slate project which sought to redesign the internet using a clean slate approach. This led to the development of OpenFlow, which separated the control plane and data plane of network devices. SDN is defined as the separation of the network control plane from the forwarding plane, with a control plane controlling several devices. It provides network agility and flexibility through enhanced programmability, disaggregation of the control plane from hardware, and centralized network control with visibility. Key SDOs developing SDN standards include ONF, IETF, and IEEE.
Networking revolution in last 6-7 years. This document shows the very brief of high level concept in changing Networking technology from legacy networking to future ideas.
Software defined networking (SDN) uses OpenFlow to separate the control plane of network switches from the data plane. This allows for network programmability and innovation through open protocols and APIs. SDN has the potential to reduce network costs, increase flexibility, and lead to new use cases. However, challenges remain around OpenFlow limitations, scalability, and vendor dependence.
The document discusses software defined networking (SDN) and OpenFlow, including their history, key concepts, potential uses and challenges. SDN aims to separate the network control and forwarding functions through open standards like OpenFlow. This could make networks more programmable and innovative while reducing costs. However, challenges include limitations of the current standards and ensuring scalability and interoperability across vendors.
This document discusses network virtualization and its history. It provides the following key points:
1) Network virtualization aims to decouple virtual networks from physical infrastructure through techniques like tunneling and encapsulation, allowing independent address spaces and topologies.
2) Early work included overlay networks for deployment and experimentation. Virtualization is now used in data centers to isolate tenant traffic and connect virtual machines across sites.
3) The OpenVirteX project aims to advance network virtualization by exposing the entire physical topology to virtual network controllers and allowing independent address spaces and topologies through header rewriting. This would provide more flexibility than existing solutions.
Software-Defined Networking(SDN):A New Approach to NetworkingAnju Ann
This document provides an overview of Software-Defined Networking (SDN). It discusses how SDN decouples the network control plane from the forwarding plane, allowing for centralized control and programmability. The key components of the SDN architecture include OpenFlow switches, an SDN controller, and northbound and southbound APIs. OpenFlow is described as the primary southbound protocol, allowing the controller to program how packets are handled by switches. Example applications of SDN mentioned are network slicing and multi-tenancy in cloud computing. Challenges for SDN adoption are also noted.
SDN 101: Software Defined Networking Course - Sameh Zaghloul/IBM - 2014SAMeh Zaghloul
This document provides an overview of software defined networking (SDN). It discusses how SDN enables data center teams to use software to efficiently control network resources, compared to traditional network switches. The document outlines several SDN topics and related technologies, including SDN standards, network function virtualization, use cases, sample projects, surveys, case studies, online courses, and software tools. It also includes sections on SDN architecture and how SDN is important for virtual environments and VM mobility.
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.
Understanding network and service virtualizationSDN Hub
This document discusses network and service virtualization technologies. It begins with an overview of challenges with current network architectures and how virtualization addresses them. It then covers three key trends: 1) network virtualization using SDN to program networks dynamically, 2) service virtualization using NFV to virtualize network functions, and 3) new infrastructure tools like Open vSwitch, OpenDaylight, and Docker networking. Finally, it discusses approaches to deploying network and service virtualization and provides a vendor landscape.
This document provides an introduction to OpenFlow, SDN, and NFV. It describes the need for new networking paradigms and outlines some of the key problems with traditional networking approaches. OpenFlow is presented as providing open interfaces and programmability to network nodes. SDN is defined as separating the control logic from the forwarding plane and enabling programmable automation through open APIs. NFV aims to virtualize network functions to improve flexibility, reduce costs, and accelerate service deployment using standard IT virtualization technologies.
Presentation of IEEE Slovenia CIS (Computational Intelligence Society) Chapte...University of Maribor
Slides from talk presenting:
Aleš Zamuda: Presentation of IEEE Slovenia CIS (Computational Intelligence Society) Chapter and Networking.
Presentation at IcETRAN 2024 session:
"Inter-Society Networking Panel GRSS/MTT-S/CIS
Panel Session: Promoting Connection and Cooperation"
IEEE Slovenia GRSS
IEEE Serbia and Montenegro MTT-S
IEEE Slovenia CIS
11TH INTERNATIONAL CONFERENCE ON ELECTRICAL, ELECTRONIC AND COMPUTING ENGINEERING
3-6 June 2024, Niš, Serbia
Redefining brain tumor segmentation: a cutting-edge convolutional neural netw...IJECEIAES
Medical image analysis has witnessed significant advancements with deep learning techniques. In the domain of brain tumor segmentation, the ability to
precisely delineate tumor boundaries from magnetic resonance imaging (MRI)
scans holds profound implications for diagnosis. This study presents an ensemble convolutional neural network (CNN) with transfer learning, integrating
the state-of-the-art Deeplabv3+ architecture with the ResNet18 backbone. The
model is rigorously trained and evaluated, exhibiting remarkable performance
metrics, including an impressive global accuracy of 99.286%, a high-class accuracy of 82.191%, a mean intersection over union (IoU) of 79.900%, a weighted
IoU of 98.620%, and a Boundary F1 (BF) score of 83.303%. Notably, a detailed comparative analysis with existing methods showcases the superiority of
our proposed model. These findings underscore the model’s competence in precise brain tumor localization, underscoring its potential to revolutionize medical
image analysis and enhance healthcare outcomes. This research paves the way
for future exploration and optimization of advanced CNN models in medical
imaging, emphasizing addressing false positives and resource efficiency.
Using recycled concrete aggregates (RCA) for pavements is crucial to achieving sustainability. Implementing RCA for new pavement can minimize carbon footprint, conserve natural resources, reduce harmful emissions, and lower life cycle costs. Compared to natural aggregate (NA), RCA pavement has fewer comprehensive studies and sustainability assessments.
A SYSTEMATIC RISK ASSESSMENT APPROACH FOR SECURING THE SMART IRRIGATION SYSTEMSIJNSA Journal
The smart irrigation system represents an innovative approach to optimize water usage in agricultural and landscaping practices. The integration of cutting-edge technologies, including sensors, actuators, and data analysis, empowers this system to provide accurate monitoring and control of irrigation processes by leveraging real-time environmental conditions. The main objective of a smart irrigation system is to optimize water efficiency, minimize expenses, and foster the adoption of sustainable water management methods. This paper conducts a systematic risk assessment by exploring the key components/assets and their functionalities in the smart irrigation system. The crucial role of sensors in gathering data on soil moisture, weather patterns, and plant well-being is emphasized in this system. These sensors enable intelligent decision-making in irrigation scheduling and water distribution, leading to enhanced water efficiency and sustainable water management practices. Actuators enable automated control of irrigation devices, ensuring precise and targeted water delivery to plants. Additionally, the paper addresses the potential threat and vulnerabilities associated with smart irrigation systems. It discusses limitations of the system, such as power constraints and computational capabilities, and calculates the potential security risks. The paper suggests possible risk treatment methods for effective secure system operation. In conclusion, the paper emphasizes the significant benefits of implementing smart irrigation systems, including improved water conservation, increased crop yield, and reduced environmental impact. Additionally, based on the security analysis conducted, the paper recommends the implementation of countermeasures and security approaches to address vulnerabilities and ensure the integrity and reliability of the system. By incorporating these measures, smart irrigation technology can revolutionize water management practices in agriculture, promoting sustainability, resource efficiency, and safeguarding against potential security threats.
CHINA’S GEO-ECONOMIC OUTREACH IN CENTRAL ASIAN COUNTRIES AND FUTURE PROSPECTjpsjournal1
The rivalry between prominent international actors for dominance over Central Asia's hydrocarbon
reserves and the ancient silk trade route, along with China's diplomatic endeavours in the area, has been
referred to as the "New Great Game." This research centres on the power struggle, considering
geopolitical, geostrategic, and geoeconomic variables. Topics including trade, political hegemony, oil
politics, and conventional and nontraditional security are all explored and explained by the researcher.
Using Mackinder's Heartland, Spykman Rimland, and Hegemonic Stability theories, examines China's role
in Central Asia. This study adheres to the empirical epistemological method and has taken care of
objectivity. This study analyze primary and secondary research documents critically to elaborate role of
china’s geo economic outreach in central Asian countries and its future prospect. China is thriving in trade,
pipeline politics, and winning states, according to this study, thanks to important instruments like the
Shanghai Cooperation Organisation and the Belt and Road Economic Initiative. According to this study,
China is seeing significant success in commerce, pipeline politics, and gaining influence on other
governments. This success may be attributed to the effective utilisation of key tools such as the Shanghai
Cooperation Organisation and the Belt and Road Economic Initiative.
ACEP Magazine edition 4th launched on 05.06.2024Rahul
This document provides information about the third edition of the magazine "Sthapatya" published by the Association of Civil Engineers (Practicing) Aurangabad. It includes messages from current and past presidents of ACEP, memories and photos from past ACEP events, information on life time achievement awards given by ACEP, and a technical article on concrete maintenance, repairs and strengthening. The document highlights activities of ACEP and provides a technical educational article for members.
Literature Review Basics and Understanding Reference Management.pptxDr Ramhari Poudyal
Three-day training on academic research focuses on analytical tools at United Technical College, supported by the University Grant Commission, Nepal. 24-26 May 2024
DEEP LEARNING FOR SMART GRID INTRUSION DETECTION: A HYBRID CNN-LSTM-BASED MODELgerogepatton
As digital technology becomes more deeply embedded in power systems, protecting the communication
networks of Smart Grids (SG) has emerged as a critical concern. Distributed Network Protocol 3 (DNP3)
represents a multi-tiered application layer protocol extensively utilized in Supervisory Control and Data
Acquisition (SCADA)-based smart grids to facilitate real-time data gathering and control functionalities.
Robust Intrusion Detection Systems (IDS) are necessary for early threat detection and mitigation because
of the interconnection of these networks, which makes them vulnerable to a variety of cyberattacks. To
solve this issue, this paper develops a hybrid Deep Learning (DL) model specifically designed for intrusion
detection in smart grids. The proposed approach is a combination of the Convolutional Neural Network
(CNN) and the Long-Short-Term Memory algorithms (LSTM). We employed a recent intrusion detection
dataset (DNP3), which focuses on unauthorized commands and Denial of Service (DoS) cyberattacks, to
train and test our model. The results of our experiments show that our CNN-LSTM method is much better
at finding smart grid intrusions than other deep learning algorithms used for classification. In addition,
our proposed approach improves accuracy, precision, recall, and F1 score, achieving a high detection
accuracy rate of 99.50%.
Using recycled concrete aggregates (RCA) for pavements is crucial to achieving sustainability. Implementing RCA for new pavement can minimize carbon footprint, conserve natural resources, reduce harmful emissions, and lower life cycle costs. Compared to natural aggregate (NA), RCA pavement has fewer comprehensive studies and sustainability assessments.
Iron and Steel Technology Roadmap - Towards more sustainable steelmaking.pdf
SDN approach.pptx
1. 6.888
Lecture 14:
Software Defined Networking
Mohammad Alizadeh
Spring 2016
Many thanks to Nick McKeown (Stanford), Jennifer Rexford (Princeton), Scott
Shenker (Berkeley), Nick Feamster (Princeton), Li Erran Li (Columbia), Yashar
Ganjali (Toronto)
1
4. Software Defined Network
A network in which the control plane is
physically separate from the data plane.
and
A single (logically centralized) control plane
controls several forwarding devices.
4
5. Software Defined Network (SDN)
Packet
Forwarding
Packet
Forwarding
Packet
Forwarding
Packet
Forwarding
Packet
Forwarding
Control
Control
Control
Control
Control
Global Network Map
Control Plane
Control
Program
Control
Program
Control
Program
5
6. What You Said
“Overall, the idea of SDN feels a little bit unsettling
to me because it is proposing to change one of the
main reasons for the success of computer
networks: fully decentralized control. Once we
introduce a centralized entity to control the network
we have to make sure that it doesn’t fail, which I
think is very difficult.”
6
7. Entire backbone
runs on SDN
A Major Trend in Networking
Bought for $1.2 billion
(mostly cash) 7
8. The Networking “Planes”
Data plane: processing and delivery of packets with local
forwarding state
– Forwarding state + packet header forwarding decision
– Filtering, buffering, scheduling
Control plane: computing the forwarding state in routers
– Determines how and where packets are forwarded
– Routing, traffic engineering, failure detection/recovery, …
Management plane: configuring and tuning the network
– Traffic engineering, ACL config, device provisioning, …
8
10. Data and Control Planes
Switching
Fabric
Processor
Line card
Line card
Line card
Line card
Line card
Line card
data plane
control plane
10
11. Data Plane
Streaming algorithms on packets
– Matching on some header bits
– Perform some actions
Example: IP Forwarding
host host host
LAN 1
... host host host
LAN 2
...
router router router
WAN WAN
1.2.3.4 1.2.3.7 1.2.3.156 5.6.7.8 5.6.7.9
1.2.3.0/24
5.6.7.0/24
forwarding table 11
12. Control Plane
Compute paths the packets will follow
– Populate forwarding tables
– Traditionally, a distributed protocol
Example: Link-state routing (OSPF, IS-IS)
– Flood the entire topology to all nodes
– Each node computes shortest paths
– Dijkstra’s algorithm
12
14. 1
2
3
“If , send to 3”
Data
“If a packet is going to B,
then send it to output 3”
1. Figure out which routers and links are present.
2. Run Dijkstra’s algorithm to find shortest paths.
14
15. Management Plane
Traffic Engineering: setting the weights
– Inversely proportional to link capacity?
– Proportional to propagation delay?
– Network-wide optimization based on traffic?
3
2
2
1
1
3
1
4
5
3
3
15
16. Challenges
(Too) many task-specific control mechanisms
– No modularity, limited functionality
Indirect control
– Must invert protocol behavior, “coax” it to do what you want
– Ex. Changing weights instead of paths for TE
Uncoordinated control
– Cannot control which router updates first
Interacting protocols and mechanisms
– Routing, addressing, access control, QoS
The network is
• Hard to reason about
• Hard to evolve
• Expensive
16
17. Example 1: Inter-domain Routing
Today’s inter-domain routing protocol, BGP, artificially
constrains routes
- Routing only on destination IP address blocks
- Can only influence immediate neighbors
- Very difficult to incorporate other information
Application-specific peering
– Route video traffic one way, and non-video another
Blocking denial-of-service traffic
– Dropping unwanted traffic further upstream
Inbound traffic engineering
– Splitting incoming traffic over multiple peering links
17
18. Two locations, each with data center &
front office
All routers exchange routes over all links
R1 R2
R5
R4
R3
Chicago (chi)
New York (nyc)
Data Center Front Office
Example 2: Access Control
18
21. A new short-cut link added between data centers
Intended for backup traffic between centers
R1 R2
R5
R4
R3
Data Center
Packet filter:
Drop nyc-FO -> *
Permit *
Packet filter:
Drop chi-FO -> *
Permit *
Front Office
chi
nyc
Example 2: Access Control
21
22. Oops – new link lets packets violate access control policy!
Routing changed, but
Packet filters don’t update automatically
R1 R2
R5
R4
R3
Data Center
Packet filter:
Drop nyc-FO -> *
Permit *
Packet filter:
Drop chi-FO -> *
Permit *
Front Office
chi
nyc
Example 2: Access Control
22
23. Custom Hardware
Custom Hardware
Custom Hardware
Custom Hardware
Custom Hardware
OS
OS
OS
OS
OS
Network OS
Feature Feature
How SDN Changes the Network
Feature Feature
Feature Feature
Feature Feature
Feature Feature
Feature Feature
23
23
24. Control Program 1
Network OS
1. Open interface to packet forwarding
3. Consistent, up-to-date global network view 2. At least one Network OS
probably many.
Open- and closed-source
Software Defined Network (SDN)
Packet
Forwarding
Packet
Forwarding
Packet
Forwarding
Packet
Forwarding
Packet
Forwarding
Control Program 2
24
24
25. Network OS
Network OS: distributed system that creates a
consistent, up-to-date network view
– Runs on servers (controllers) in the network
– NOX, ONIX, Floodlight, Trema, OpenDaylight, HyperFlow,
Kandoo, Beehive, Beacon, Maestro, … + more
Uses forwarding abstraction to:
– Get state information from forwarding elements
– Give control directives to forwarding elements
25
26. Control Program A Control Program B
Network OS
Software Defined Network (SDN)
Packet
Forwarding
Packet
Forwarding
Packet
Forwarding
Packet
Forwarding
Packet
Forwarding
26
27. Control Program
Control program operates on view of network
– Input: global network view (graph/database)
– Output: configuration of each network device
Control program is not a distributed system
– Abstraction hides details of distributed state
27
28. Forwarding Abstraction
Purpose: Standard way of defining forwarding state
– Flexible
• Behavior specified by control plane
• Built from basic set of forwarding primitives
– Minimal
• Streamlined for speed and low-power
• Control program not vendor-specific
OpenFlow is an example of such an abstraction
28
29. Network OS
Software Defined Network
29
Global Network View
Control Program
Virtual Topology
Network Hypervisor
30. Virtualization Simplifies Control Program
A
B
A
B
Abstract Network View
Global Network View
AB drop
Hypervisor then inserts flow entries as needed
AB drop
AB drop
30
32. What You Said
“However, I remain skeptical that such an
approach will actually simplify much in the long
run. That is, the basic paradigm in networks
(layers) is in fact a simple model. However, the
ever-changing performance and functionality goals
have forced more complexity into network design.
I'm not sure if SDN will be able to maintain its
simplified model as goals continue to evolve.”
32
33. Does SDN Simplify the Network?
Abstraction doesn’t eliminate complexity
- NOS, Hypervisor are still complicated pieces of code
SDN main achievements
- Simplifies interface for control program (user-specific)
- Pushes complexity into reusable code (SDN platform)
Just like compilers….
33
35. OpenFlow Protocol
Data Path (Hardware)
Control Path OpenFlow
Ethernet Switch
Network OS
Control Program A Control Program B
OpenFlow Basics
35
36. Control Program A Control Program B
Network OS
OpenFlow Basics
Packet
Forwarding
Packet
Forwarding
Packet
Forwarding
Flow
Table(s)
“If header = p, send to port 4”
“If header = ?, send to me”
“If header = q, overwrite header with r,
add header s, and send to ports 5,6”
36
37. Primitives <Match, Action>
Match arbitrary bits in headers:
– Match on any header, or new header
– Allows any flow granularity
Action
– Forward to port(s), drop, send to controller
– Overwrite header with mask, push or pop
– Forward at specific bit-rate
Header Data
Match: 1000x01xx0101001x
40. The Road to SDN
Active Networking: 1990s
- First attempt make networks programmable
- Demultiplexing packets to software programs, network
virtualization, …
Control/Dataplane Separation: 2003-2007
- ForCes [IETF],
RCP, 4D [Princeton, CMU],
SANE/Ethane [Stanford/Berkeley]
- Open interfaces between data and control plane, logically
centralized control
OpenFlow API & Network Oses: 2008
- OpenFlow switch interface [Stanford]
- NOX Network OS [Nicira]
40
N. Feamster et al., “The Road to SDN: An Intellectual History of Programmable Networks”, ACM
SIGCOMM CCR 2014.
41. SDN Drivers
Rise of merchant switching silicon
- Democratized switching
- Vendors eager to unseat incumbents
Cloud / Data centers
- Operators face real network management problems
- Extremely cost conscious; desire a lot of control
The right balance between vision & pragmatism
- OpenFlow compatible with existing hardware
A “killer app”: Network virtualization
41
42. Virtualization is Killer App for SDN
Consider a multi-tenant datacenter
- Want to allow each tenant to specify virtual topology
- This defines their individual policies and requirements
Datacenter’s network hypervisor compiles these
virtual topologies into set of switch configurations
- Takes 1000s of individual tenant virtual topologies
- Computes configurations to implement all simultaneously
This is what people are paying money for….
- Enabled by SDN’s ability to virtualize the network
44. 4D
Decision: all management and control logic
Dissemination: communicating with routers
Discovery: topology and traffic monitoring
Data: packet handling
routers
Decision
Dissemination
Discovery
Data
Network-level
objectives
Direct
control
Network-
wide views
45. What You Said
“The paper reads more like a thought-exercise or
meta discussion of the future SDN field than a
presentation of research. I am surprised sigcomm
published it.”
“some good things about the way the paper was
structured was that it mentioned that it had a lot of
future work to do and didn't think it was a final
solution. By at least addressing that it needs to
continue to expand, the authors acknowledge they
don't know the merits behind their solution…”
45
46. What You Said
“The most compelling aspect of SDN and of the 4D
Approach proposed, in my opinion, is the ability to
enable innovation. However, SDN taken to the
extreme proposed in the 4D approach seems to
me to significantly limit scalability and increase
complexity.”
46
47. What You Said
“My concern is that, previous designs that is aware
of the delay of updating network view, take the
consideration right on their control (they have
control rules and protocol that touch this directly).
But SDN tries to hide this nature from the
programmers. I am not sure if the design of the
software, in the absence of these concerns, will
end up with expected results.”
47
48. Practical Challenges
Scalability
– Decision elements responsible for many routers
Reliability
– Surviving failures of decision elements and routers
Response time
– Delays between decision elements and routers
Consistency
– Ensuring multiple decision elements behave consistently
Security
– Network vulnerable to attacks on decision elements
Interoperability
– Legacy routers and neighboring domains
48