Software-Defined Networks and Applications PDF

Software-Defined Networks and Its Applications  Introduction  the core principles and functionalities of Software-Defined Networking (SDN) quite thoroughly! SDN indeed revolutionizes network management by decoupling the control plane from the data pla...

Software-Defined Networks and Its Applications  Introduction  the core principles and functionalities of Software-Defined Networking (SDN) quite thoroughly! SDN indeed revolutionizes network management by decoupling the control plane from the data plane, enabling centralized control and programmability through software.  Decoupling Control and Data Planes: SDN separates the control logic from hardware switches, allowing centralized management of the network through a software-based controller.  Centralized Control: By centralizing control, SDN enables more efficient management of the entire network, including individual switches, routers, and other devices.  Virtualization and Programmability: SDN utilizes programming-based controllers or APIs to manage and direct network traffic. It enables the creation of virtual networks and control over traditional networks using software-controlled applications.  Automation and Efficiency: SDN facilitates automation and strategy-based management, optimizing resource utilization, and enabling quicker responses to changes in network demand or traffic.  Differentiation from Network Functions Virtualization (NFV): While NFV also involves virtualizing network functions, it's distinct from SDN. NFV focuses on virtualizing network services, while SDN concentrates on separating control and data planes for centralized management.  The research aims to explore SDN's layered architecture, emphasizing its ability to enhance network flexibility, agility, and control, enabling swift adaptation to evolving business requirements.  SDN vs Traditional Networks  the fundamental difference lies in their underlying infrastructure: SDN relies on software- based control, whereas traditional networking relies predominantly on hardware.  SDN's software-centric approach provides several advantages:  Flexibility: SDN's reliance on software for control allows for greater adaptability and agility in managing networks. It enables quicker adjustments to configurations, resource allocation, and scalability compared to traditional networking methods, which heavily depend on hardware configurations.  Enhanced Management: With a centralized controller managing the network, SDN offers more efficient network supervision and easier configuration changes across the infrastructure.  Security: SDN can offer enhanced security due to increased visibility and the ability to define secure paths for data. However, the reliance on a centralized controller becomes a potential vulnerability.  Compromising the controller could potentially jeopardize the entire network's security, Traditional networking, on the other hand, relies on dedicated hardware for control and forwarding functions. While it might have been the norm for years, it can be less adaptable and might not easily accommodate rapid changes or modifications.  SDN's security advantages in providing visibility and the ability to define secure paths are significant, but the vulnerability of the centralized controller poses a critical challenge. Protecting this control point becomes pivotal in ensuring the overall security of an SDN-based network. SDN Working: A Functional Overview  A software-defined networking architecture is a network structure that involves data forwarding tasks, centralizing cleverness, conceptualizing style from applications and services.  There are two different stages of abstraction inside a router. One is the control plane, which is carried out as a piece of the software that carries out the routing tasks and the development of the routing table and administration, and others are data functionalities  In the data functionalities, tasks are to forward a packet into the destination IP field in the IP header and match with the routing table the local copy inside the interface that is the forwarding database, and lastly forwarding the packet to the outgoing interface S. SDN network Traditional network no. 1. It is an old conventional networking approach. An SDN is a virtual networking approach. 2. It has centralized control. It has distributed control. 3. It is programmable. It is non-programmable. 4. It is an open interface It is a closed interface network. network. 5. The decoupling of the Both data plane and control data plane and control plane are set up in the same plane by programming plane in a traditional software in SDN. network. 6. It is hard to program again and to substitute existing It is not difficult to systems according to program according to utilization. necessity. 7. Its cost is low. Its cost is high. 8. It carries automatic It carries manual/static configuration so it takes configuration so it takes a smaller amount of additional time. time. 9. Extensibility is excessive Extensibility is small in this in these networks. network. 10. Because it is a centralized It is hard to remove and report  SDN Working: A Functional Overview  Router Abstraction: Control vs. Data Functionalities  Control Plane: Handles routing tasks, builds routing tables, and manages network administration.  Data Plane: Forwards packets based on routing table information, using a forwarding database to determine the outgoing interface.  Complexity of Control Functionalities in Traditional Routers  Control functionalities are executed within individual routers, leading to complexity when synchronizing multiple routers' control planes to manage a global routing table.  Challenges with Distributed Control Architecture  Requirement for synchronization among various routers' control planes increases complexity.  Traditional routing protocols like distance vector and link-state have scalability limitations.  Difficulty for network managers to implement updates across routers based on policy changes.  Transition to Software-Defined Networking (SDN)  Centralization of control in SDN: Separates control and data functionalities, leading to easier management and adaptability.  Overcoming scalability issues: SDN provides a more flexible and programmable approach to network management, improving adaptability and scalability.  Components and Implementation Architecture  SDN applications programs explicitly, straightforwardly, automatically prerequisite want their network to conduct SDN Controller by the northward interface (NBI). Figure 3.2 shows the details of SDN components and functions.  Components of an SDN  SDN components include Controller, Data path, Data Plane Interface, Northbound Interface, Controller Placement, OpenFlow and Open Source.  SDN Application 1. SDN Application Layer Overview  Enhanced Network Control: Provides an additional layer of control through specialized applications.  Network-Based Interfaces (NBIs): Offered through dedicated specialists for advanced control. 2. Functionality of SDN Applications  Monitoring: Real-time tracking and analysis of network performance to identify and address issues promptly.  Troubleshooting: Efficient resolution of network problems by utilizing network data for pinpointing issues.  Policies: Enforcement of network policies for compliance, security, and optimal resource utilization.  Security Automation: Automated response mechanisms to counter threats or vulnerabilities.  Configuration: Streamlining network configuration processes for adaptability.  Management: Comprehensive capabilities for efficient network oversight and control. 3. Utilizing Network Data for Innovation  Data Leveraging: Applications leverage network data (topology, statistics, etc.) for innovative solutions.  Tailored Functionality: Customized applications for diverse network requirements.  SDN Controller 1. SDN Controller Overview  Role: Bridges the gap between SDN application layer and network data path.  Function: Interprets application requirements and provides a conceptual network view. 2. Components of an SDN Controller  NBI Agent: Acts as an intermediary for communication between the controller and applications.  SDN Control Logic: Executes control algorithms and policies based on application and network state information.  Control to Data-Plane Interface (CDPI) Driver: Facilitates communication between the controller and network devices, translating instructions for execution in the data plane. 3. Orchestrating Network Operations  Input Processing: Receives directives from SDN applications.  Control Logic Execution: Processes inputs to make decisions and formulate network configurations.  Data Plane Interaction: Communicates with network devices to implement desired changes. SDN Datapath 1. Overview of SDN Datapath Components  Control to Data-Plane Interface (CDPI): Enables communication between controller and datapath, translating commands for execution.  Traffic Sending Engines: Responsible for efficient packet forwarding based on controller instructions.  Traffic Handling Functions: Manages traffic operations like packet inspection, QoS, routing decisions, etc., optimizing traffic flow.  External and Internal Interfaces: Connects with external network elements and manages internal traffic flow within the SDN environment.  Compatibility: Designed for seamless integration with diverse network devices and elements. SDN Datapath 1. Functionality of SDN Datapath Data Transmission: Efficiently transmits packets based on controller directives. Traffic Optimization: Manages traffic operations for enhanced network performance. Interface Management: Facilitates communication both within the SDN environment and with external network elements. 2. Interoperability and Adaptability Seamless Integration: Works with various network devices for compatibility. Flexibility: Enables optimized traffic flow within heterogeneous network environments.  SDN Control to Data-Plane Interface (CDPI) 1. SDN Controller-Datapath Interface Overview  Control over Essential Operations: Enables control over packet forwarding, information dissemination, performance insights, and event notifications.  Key Functions: Forwarding Operations, Advertisement Capabilities, Statistics Reporting, Event Notification. 2. Importance of Openness and Interoperability  Standardized Communication: Facilitates standardized and consistent interaction between controller and datapath.  Compatibility Assurance: Ensures compatibility across diverse network elements, irrespective of vendor specifics.  Interoperability Benefits: Enables seamless communication and collaboration within the SDN ecosystem. 3. Enhanced Network Management  Efficient Network Control: Empowers the central controller for agile and programmable network management.  Agility and Scalability: Contributes to a more responsive and scalable network infrastructure.  SDN Northbound Interfaces (NBI) 1. Function of SDN NBIs  Network Views: Provide perspectives of the network to controllers and applications.  Expressing Network Behavior: Enable direct specification of network behaviors and requirements. 2. Spatial Analogy: Abstraction and Functionality  Latitude of Abstraction: Represents the varying levels of abstraction in expressing network behavior and requirements.  Longitude of Functionality: Encompasses diverse sets of functionalities that SDN NBIs offer. 3. Flexibility and Adaptability  Variable Abstraction Levels: Allows expression of network needs at different abstraction levels.  Diverse Functional Sets: Offers various functionalities across the SDN ecosystem. SDN Control Plane: Incorporated-Hierarchical-Distributed 1. Centralized and Hierarchical Design  Initial Structure: Single control component with an overarching view of the network.  Advantages: Enhanced control logic performance. 2. Limits of Centralization  Flexibility Constraints: Size and complexity of networks pose limitations.  Scalability Challenges: Inadequate for larger or evolving network structures. 3. Strategies for Improvement  Hierarchical Approaches: Proposed solutions incorporating hierarchical control structures.  Fully Distributed Models: Suggestions for completely distributed control plane designs. 4. Benefits and Adaptability  Enhanced Scalability: Addressing limitations of centralized control for larger networks.  Improved Flexibility: Allowing for adaptability in diverse network environment Controller Placement  key components and challenges in SDN control plane planning and architecture. Here's a summarization for a PowerPoint slide: 1. Significance of Control Elements  Number and Dynamics: Crucial aspects in planning an SDN control plane.  Adaptability and Change: Understanding the need for flexible control elements. 2. Challenges: Controller-Device Delay  Concern in Large Networks: Delay between controllers and network devices is a significant challenge, particularly in expansive networks.  Impact on Efficiency: Highlighting the potential issues with delays in communication. 3. Fundamental Components of SDN Infrastructure  SDN Controller: Single controller, possibly deployed in a highly available cluster.  SDN-Empowered Switches: Multiple switches forming the network fabric. 4. Defining SDN Architecture  Composition: Combination of hardware and software-based networking technologies.  SDN Design: Defines network administration through this combination, ensuring flexibility and adaptability.  OpenFlow and Open Source in SDN Architecture  significance of OpenFlow and the relationship between SDN, open networking, and open Slide Title: OpenFlow in SDN and Relationship with Openness 1. OpenFlow in SDN  Primary SDN Protocol: Defines communication between SDN controllers and forwarding plane devices.  Advantages: Programmability, centralized intelligence, and network abstraction. 2. Openness in SDN Models  Utilization of Software: Most SDN models use proprietary or open-source software on commodity hardware.  Open Networking Concept: SDN aligns with open networking principles but is not inherently open source. 3. Clarifying Openness in SDN  Open Networking vs. Open Source: SDN doesn't mandate open networking principles, and it's not inherently open source.  Functionalities of SDN: Valued for functional partitioning, network virtualization, and automation through programmability. 4. Significance of SDN's Capabilities  Functional Partitioning: Dividing network functionality for enhanced management.  Network Virtualization: Creating virtualized network instances for flexible configurations.  Automation through Programmability: Enhancing network operations through programmable interfaces.  SDN Design 1. Unified Control in SDN  Isolation of Control and Data Planes: Essential feature in SDN architecture, segregating control and data functions in network devices. 2. API Integration in SDN  APIs as Connective Elements: APIs serve as connectors between various layers of the SDN architecture, facilitating communication and interaction. 3. API Types 1. Northbound APIs  Purpose: Facilitate communication with higher layers, such as applications and business tools.  Function: Enable automation and rule-based control for user-centric communication needs. 2. Southbound APIs  Objective: Communicate with lower layers, i.e., networking devices.  Function: Exchange data and instructions with devices like switches, routers, and firewalls.  Role of Northbound APIs  Interaction with Applications and Business Tools: Facilitate communication with external applications and business-oriented tools.  User Communication Assistance: Enable automatic transmission of network rules and traffic shaping for clients.  Bridge Between Application and Control Layers: Facilitate interaction between the Application and Control Layers in the SDN architecture.  Function of Southbound APIs  Data Transmission to Networking Devices: Transfer data to various networking devices like switches, routers, firewalls, and VMs (compute Nodes).  Common Protocols: OpenFlow/OpenStack - widely used protocols for Southbound communication.  Bridge Between Control and Infrastructure Layers: Facilitate communication between the SDN control layer and the SDN infrastructure layer. Orchestrator 1. Role of Orchestrator  Position in SDN Architecture: Resides at the SDN application layer.  Functionality: Programs automated behaviors within the network.  Facilitation of Networking Components: Assists in provisioning necessary networking hardware and software components for applications and services. 2. Orchestrator Operations  API Utilization: Understands client demands through APIs.  Translation and Communication: Converts demands into a language understandable by the SDN control layer.  Triggering Network Actions: Notifies the control layer to initiate actions like VM creation (e.g., virtual Firewalls).  Controller 1. Role of SDN Controller  Position in SDN Architecture: Located at the control layer within the SDN stack.  Centralized Network View: Provides a comprehensive overview of the entire network organization.  Facilitation of Information Flow: Enables organizational decision-makers to transmit directives and strategies to the underlying infrastructure layer (VMs, virtual routers, switches). 2. Controller Functions  Information Transmission: Allows for the passage of coordinating principles and strategies.  Data Plane Influence: Shapes the data plane based on instructions received, determining how traffic will be routed by VMs. Compute 1.Compute in SDN Architecture 1.Position in Infrastructure Layer: Integral part of the infrastructure layer within SDN engineering. 2.Purpose: Forms the foundation for creating virtual machines (VMs) used for various functionalities. 2.Functionalities Supported by Compute 1.Virtualized Services: Enables the creation and operation of diverse virtual machines. 2.Examples of Virtual Machines: Includes virtual firewalls, load balancers, switches, routers, etc., utilized for running client services.  Implementation Architecture 1. Control and Data Separation in SDN  Function Segregation in Routers: SDN segregates control and data functionalities within routers.  Transition to Centralized Control: Shifting from a distributed control plane to a centralized control plane architecture.  Role of Control Plane: Acts as the intelligence center, making decisions centralized at a route controller. 2. Control Plane Operations  Decision-Making Hub: Controls and implements routing algorithms, functioning as the brains of the routers.  Centralization of Decision-Making: All routing decisions centralized within the route controller. 3. Data Plane Operations  Execution of Control Decisions: Carries out tasks directed by the control plane.  Packet Forwarding: Responsible for  Pros and Cons of SDN The benefits of Software-Defined Networking (SDN) encompass several aspects crucial for enterprise network management. 1. Key Advantages of SDN  Programmability of Traffic: Allows flexible control and management of network traffic, adapting to changing requirements.  Policy-Driven Network Management: Enables rule-based management, enhancing network governance and compliance.  Virtualization: Facilitates the creation of virtualized network instances, improving scalability and resource utilization.  Network Automation: Streamlines network operations, automating tasks for increased efficiency. 2. Impact on Enterprise Networks  Adaptability to Change: Enables networks to align with evolving demands and technological advancements.  Support for Data-Intensive Applications: Enables design support for data-intensive applications, including virtual machines and large data networks like big data and virtualization. SDN Misconceptions 1. SDN as a Structural Change  Contrast with Traditional Infrastructure: Represents a significant departure from conventional networking infrastructure.  No Need for Complete Overhaul: Implementation doesn’t require a full replacement of existing hardware and software with SDN components. 2. Gradual Adoption of SDN Use Cases  Enhancement Through Specific Use Cases: Organizations can initiate SDN adoption with targeted use cases.  Examples of Use Cases:  Network Optimization through Monitoring  Identification of Account and Access Control Boundaries 3. Reshaping Network Architecture  Integration with Existing Devices: SDN does not replace traditional network devices but enables integrated control and various levels of automation.  Evolution of Network Control: Redefines architecture for centralized control with automation capabilities across the network. Pros of SDN Centralized Network Provisioning 1. Definition of Network Provisioning  Purpose: Methodology for configuring a network to enable authorized access for users, devices, and servers.  Focus Areas: Primarily centered around ensuring connectivity and security. 2. Key Aspects of Network Provisioning  Connectivity Emphasis: Involves ensuring seamless connectivity within the network infrastructure.  Security Priority: Focuses significantly on device and identity management for robust network security. Holistic Enterprise Management 3. Unified Network Management with SDN  Consolidation of Responsibilities: SDN combines various network functions like firewalls and servers into a single entity.  Streamlined Operations: Simplifies management by centralizing responsibilities. 4. Automated Support and Maintenance  Dynamic Response to Network Issues: SDN autonomously reroutes traffic in case of network failures, optimizing connectivity.  Efficiency in Troubleshooting: Offers quick and automated solutions, reducing manual intervention and time required for maintenance. Pros of SDN More Granular Security 1. Granular Security Definition  Explicit Activity Limitation: Ability to restrict specific actions while permitting others.  IT Management Priority: Addressing security concerns by providing organized and detailed access control. 2. Challenges in Modern Networks  Dynamic Virtual Environments: Difficulty in consistently applying firewall and content filtering measures due to the transient nature of virtual machines within real networks. 3. Role of SDN Controller in Security  Centralized Control Point: The SDN Controller serves as a pivotal control hub.  Uniform Dissemination of Security Policies: Enables consistent and reliable distribution of security and operational data across the enterprise network. Pros of SDN Lower Operating Costs 1. Affordability of SDN Implementation  Accessibility of Free SDN Products: Not all SDN solutions require significant upfront investment; some are available for free.  Considerations for Licensed SDN Products: While certain SDN plans like VMware’s NSX require licensing fees, some come integrated with the operating system, such as Microsoft’s Hyper-V Network Virtualization. 2. Projected Cost Savings and Benefits  Managerial Productivity: Enhanced management and control of virtualization.  Improved Server Utilization: Optimization leading to better server usage.  Centralization and Automation: Reduction in operational costs by centralizing and automating standard organizational processes. 3. Anticipated Savings  Pending Concrete Evidence: Although concrete evidence of savings is yet to be fully demonstrated, SDN is expected to significantly reduce costs and streamline operations by centralizing and automating many standard organizational tasks. Pros of SDN Hardware-Savings and Reduced Capital Expenditures Revitalizing Existing Network Devices 1. Centralization of Logic: SDN centralizes intelligence, extending the lifespan of current network devices by removing the need for extensive logic within switches. 2. Cost Reduction Impact: Reduces costs associated with switches and overall network equipment. 1. Cost-Effective Switching Solutions 1. Shift from Proprietary to Silicon Switches: SDN allows the acquisition of more cost-effective silicon switches instead of proprietary, expensive alternatives like Cisco or Juniper. 2. Financial Benefits: Cost savings in building the network infrastructure by opting for more economical switching options. 2. Operational Cost Reduction 1. Reduced Dependency on Specialized Staff: Unlike non-SDN networks requiring specialists for proprietary equipment, SDN’s centralized management plane can be handled by a single controller, reducing operational costs. Pros of SDN Hardware-Savings and Reduced Capital Expenditures Revitalizing Existing Network Devices 1. Centralization of Logic: SDN centralizes intelligence, extending the lifespan of current network devices by removing the need for extensive logic within switches. 2. Cost Reduction Impact: Reduces costs associated with switches and overall network equipment. 1. Cost-Effective Switching Solutions 1. Shift from Proprietary to Silicon Switches: SDN allows the acquisition of more cost-effective silicon switches instead of proprietary, expensive alternatives like Cisco or Juniper. 2. Financial Benefits: Cost savings in building the network infrastructure by opting for more economical switching options. 2. Operational Cost Reduction 1. Reduced Dependency on Specialized Staff: Unlike non-SDN networks requiring specialists for proprietary equipment, SDN’s centralized management plane can be handled by a single controller, reducing operational costs. Pros of SDN Cloud Abstraction 1.Cloud Computing's Role in SDN 1.Abstracting Cloud Resources: Utilizing software to abstract cloud assets facilitates seamless integration with SDN. 2.Simplified Integration: Eases the process of consolidating various cloud suites within the network infrastructure. 2.Network Management in Data Centers 1.Comprehensive Control via SDN: SDN controllers can effectively manage all networking components within large- scale data center platforms. 2.Centralized Management: Provides centralized control Cons of SDN 1. Latency in SDN:  Crucial for real-time applications like Voice over IP (VoIP).  Device utilization impacts network space and communication speed.  Communication speed correlates with the quantity of virtualized assets.  Increasing speed may necessitate additional virtualized assets, potentially introducing significant latency. 2. Maintenance  Criticality: Essential for network administration tasks.  Challenge in Scaling: Scaling up the network can pose challenges in device management and maintenance. 3. Complexity  Security Concerns: Lack of standardized security protocols for SDN, posing potential security risks.  Expertise Requirement: Proficiency in SDN supervision necessary to mitigate major security threats.  Cons of SDN 4. Configuration  Costly Reconfiguration: Reconfiguring SDN protocols and controllers incurs significant costs.  Organizational Impact: Network-wide reconfiguration necessary for making changes. 5. Device Security  Absence of Traditional Security Components: Lack of inherent security features like those found in traditional routers and switches.  Vulnerability: Potential increase in vulnerability to external threats due to missing security elements. 6. Device Security  Absence of Traditional Routers and Switches: SDN does not rely on conventional routers and switches.  Lack of Inherent Security Features: Security components like firewall protection present in traditional devices may be absent in SDN.  Increased Vulnerability: This absence of traditional security elements in SDN might make the organization more susceptible to external threats. SDN Applications and Architectures: 1. Definition:  SDN applications execute tasks within a software-defined networking environment, capable of functioning as firmware-embedded functions in traditional network hardware. 1. Architectural Tiers:  First Tier: Comprises physical infrastructure and hardware supporting the network.  Second Tier: SDN controllers manage and direct traffic flow.  Third Tier: SDN applications dictate specific functions through the controller. 2. Examples of SDN Applications:  Network virtualization programs.  Network monitoring tools.  Intrusion detection systems.  Flow balancing for load distribution. SDN Environnent for Applications  There are broadly two types of SDN applications: internal and external applications Types of SDN Applications: Internal SDN Applications:  Characteristics: Programs written in languages like Java for platforms such as OpenDaylight (ODL).  Deployment: Hosted within and run alongside the OpenDaylight controller software in the OSGi container.  Requirement: Adherence to controller design specifications and execution within the same environment. External SDN Applications:  Characteristics: Applications facilitated by the OpenDaylight controller but deployed externally.  Language Use: Utilizes scripting languages like Bash.  Deployment: Runs remotely, separate from the controller, on a different host.  Access Method: Uses applications providing access to services and APIs offered by the controller. SDN Environnent for Applications Security Services in SDN:  Real-time Threat Response: Immediate response to network violations is crucial; continuous monitoring ensures network component safety.  Adapting to Digitization: With increased digitization, network layers become more susceptible to advanced threats, necessitating proactive measures. Network Monitoring and Intelligence:  Complex Architectures: SDN aids in managing complex architectures and large data volumes, which can otherwise be challenging to comprehend.  Eliminating Issues: Monitoring helps address issues like port congestion, heterogeneous networks, or abnormal traffic patterns.  Technology Integration: Integration of monitoring and intelligence technologies within SDN architectures facilitates agile and efficient network monitoring, especially in cloud ecosystems and data centers. SDN Environnent for Applications Data Transmission Management:  Enhancing User Experience: Managers utilize data transmission management to ensure quality online video experiences for end-users, enhancing user satisfaction and addressing uncertainties in network performance.  Benefits for Operators: SDN applications offer significant improvements beyond network management, positively impacting operator businesses and organizations. Content Availability:  Content Delivery Optimization: SDN applications manage content servers, optimizing content distribution across various servers and geographies based on availability and types of content.  Intelligent Routing: Applications check content availability before routing requests to servers, ensuring requests are directed to appropriate servers based on content type and availability.  Dynamic Content Handling: For dynamic content, SDN applications direct requests to servers providing dynamic content rather than caching servers, optimizing network performance.  SDN Environnent for Applications Guideline and Compliance-Bound Applications:  Cloud Transition for Regulated Jobs: SDN allows regulated and guideline-bound tasks to extend into the cloud securely. It enables monitoring and control of network traffic, switches, and hypervisors within the SDN architecture to maintain compliance. High-Performance Applications:  Enhancing Application Delivery: SDN, when integrated with virtualization, facilitates the delivery of resource-intensive applications like graphic design, CAD, etc., providing powerful desktop experiences and application streaming. SDN's capabilities, such as traffic segmentation, security measures, and QoS solutions, support these high-performance applications. Distributed Application Control and Cloud Integration:  Data Center Agility: SDN's flexibility allows seamless integration across distributed clouds and locations within a data center. It enables the smooth flow of network traffic between diverse locations and cloud environments, abstracting network controls and simplifying data exchange.  Telecom Industry Perspective: SDN and NFV (Network Functions Virtualization) have been key focal points in the telecom industry, driving visions, architectures, and trials to revolutionize network management. Common Application of SDN in Enterprise Networks