DUY TÂN UNIVERSITY

INFORMATION TECHNOLOGY FACILITY

***

COMPUTER NETWORK COURSE

GROUP PROJECT REPORT

PROJECT NAME: INTRODUCTION TO SDN (SOFTWARE DEFINE

NETWORK)

GROUP NUMBER: 6

GROUP MEMBER:
1. ĐẬU HOÀNG TÀI

2. HUỲNH ĐỨC TIN

3. LÊ HỮU THANH THUẬN

4. PHẠM MINH QUY

Submit date: 17/06/2020

TABLE OF CONTEN
T
1.PROJECT NAME: INTRODUCTION TO SDN (SOFTWARE DEFINE NETWORK).........................1
2.GROUP NUMBER: 6..............................................................................................................................1
3.GROUP MEMBER:.................................................................................................................................1
5.TABLE OF CONTENT............................................................................................................................2
5.1.Introduce................................................................................................................................................3
5.2. Brief History.........................................................................................................................................3
5.3. Technical overview...............................................................................................................................4
5.3.1. SDN Application...........................................................................................................................4
5.3.2. SDN Controller..............................................................................................................................5
5.3.3. SDN Datapath................................................................................................................................5
5.3.4. SDN Control to Data-Plane Interface (CDPI)................................................................................5
5.3.5. SDN Northbound Interface (NBI)..................................................................................................5
5.4. Standards information...........................................................................................................................6
5.4.1. Introduction standards related to SDN...........................................................................................6
5.4.2. SDN and NFV Open Standards Activities....................................................................................6
Table 5.1..............................................................................................................................................6
5.5. Application Of SDN Today..................................................................................................................7
5.5.1. Benefits of SDN.............................................................................................................................7
5.5.2. Issues with SDN............................................................................................................................8
5.5.3. The technological revolution is called SDN...................................................................................9
5.5.4. Challenges with SDN...................................................................................................................10
5.5.5. SDN application..........................................................................................................................10
6. SDN development trend........................................................................................................................12
7. Conclusion.............................................................................................................................................12
8. References.............................................................................................................................................12

5.1.Introduce
Software-defined networking (SDN) technology is an approach to network management that enables
dynamic, programmatically efficient network configuration in order to improve network performance and
monitoring, making it more like cloud computing than traditional network management.SDN is meant to
address the fact that the static architecture of traditional networks is decentralized and complex while
current networks require more flexibility and easy troubleshooting. SDN attempts to centralize network
intelligence in one network component by disassociating the forwarding process of network packets (data
plane) from the routing process (control plane). The control plane consists of one or more controllers,
which are considered the brain of the SDN network where the whole intelligence is incorporated.
However, the intelligent centralization has its own drawbacks when it comes to security,scalability and
elasticity and this is the main issue of SDN.

5.2. Brief History

The history of SDN principles can be traced back to the separation of the control and data plane first used
in the public switched telephone network as a way to simplify provisioning and management well before
this architecture began to be used in data networks.
The Internet Engineering Task Force (IETF) began considering various ways to decouple the control and
forwarding functions in a proposed interface standard published in 2004 appropriately named
"Forwarding and Control Element Separation" (ForCES).The ForCES Working Group also proposed a
companion SoftRouter Architecture.Additional early standards from the IETF that pursued separating
control from data include the Linux Netlink as an IP Services Protocol and A Path Computation Element
(PCE)-Based Architecture.
These early attempts failed to gain traction for two reasons. One is that many in the Internet community
viewed separating control from data to be risky, especially owing to the potential for a failure in the
control plane. The second is that vendors were concerned that creating standard application programming
interfaces (APIs) between the control and data planes would result in increased competition.
The use of open-source software in split control/data plane architectures traces its roots to the Ethane
project at Stanford's computer sciences department. Ethane's simple switch design led to the creation of
OpenFlow.An API for OpenFlow was first created in 2008.That same year witnessed the creation of NOX
—an operating system for networks.
Work on OpenFlow continued at Stanford, including with the creation of testbeds to evaluate the use of
the protocol in a single campus network, as well as across the WAN as a backbone for connecting
multiple campuses.In academic settings there were a few research and production networks based
on OpenFlow switches from NEC and Hewlett-Packard; as well as based on Quanta Computer
whiteboxes, starting from about 2009.
Beyond academia, the first deployments were by Nicira in 2010 to control OVS from Onix, co-developed
with NTT and Google. A notable deployment was Google's B4 deployment in 2012.Later Google
acknowledged their first OpenFlow with Onix deployments in their Datacenters at the same time. Another
known large deployment is at China Mobile.
The Open Networking Foundation was founded in 2011 to promote SDN and OpenFlow.
At the 2014 Interop and Tech Field Day, software-defined networking was demonstrated by Avaya using
shortest path bridging and OpenStack as an automated campus, extending automation from the data center
to the end device, removing manual provisioning from service delivery.

5.3. Technical overview

5.3.1. SDN Application
SDN Applications are programs that explicitly, directly, and programmatically communicate their
network requirements and desired network behavior to the SDN Controller via a northbound interface
(NBI). In addition, they may consume an abstracted view of the network for their internal decision-
making purposes. An SDN Application consists of one SDN Application Logic and one or more NBI
Drivers. SDN Applications may themselves expose another layer of abstracted network control, thus
offering one or more higher-level NBIs through respective NBI agents.
 5.3.2. SDN Controller
The SDN Controller is a logically centralized entity in charge of (i) translating the requirements
from the SDN Application layer down to the SDN Datapaths and (ii) providing the SDN Applications
with an abstract view of the network (which may include statistics and events). An SDN Controller
consists of one or more NBI Agents, the SDN Control Logic, and the Control to Data-Plane Interface
(CDPI) driver. Definition as a logically centralized entity neither prescribes nor precludes implementation
details such as the federation of multiple controllers, the hierarchical connection of controllers,
communication interfaces between controllers, nor virtualization or slicing of network resources.

5.3.3. SDN Datapath

The SDN Datapath is a logical network device that exposes visibility and uncontested control
over its advertised forwarding and data processing capabilities. The logical representation may encompass
all or a subset of the physical substrate resources. An SDN Datapath comprises a CDPI agent and a set of
one or more traffic forwarding engines and zero or more traffic processing functions. These engines and
functions may include simple forwarding between the datapath's external interfaces or internal traffic
processing or termination functions. One or more SDN Datapaths may be contained in a single (physical)
network element—an integrated physical combination of communications resources, managed as a unit.
An SDN Datapath may also be defined across multiple physical network elements. This logical definition
neither prescribes nor precludes implementation details such as the logical to physical mapping,
management of shared physical resources, virtualization or slicing of the SDN Datapath, interoperability
with non-SDN networking, nor the data processing functionality, which can include OSI layer 4-7
functions.

5.3.4. SDN Control to Data-Plane Interface (CDPI)

The SDN CDPI is the interface defined between an SDN Controller and an SDN Datapath, which
provides at least (i) programmatic control of all forwarding operations, (ii) capabilities advertisement, (iii)
statistics reporting, and (iv) event notification. One value of SDN lies in the expectation that the CDPI is
implemented in an open, vendor-neutral and interoperable way.The SDN CDPI is the interface defined
between an SDN Controller and an SDN Datapath, which provides at least (i) programmatic control of all
forwarding operations, (ii) capabilities advertisement, (iii) statistics reporting, and (iv) event notification.
One value of SDN lies in the expectation that the CDPI is implemented in an open, vendor-neutral and
interoperable way.

5.3.5. SDN Northbound Interface (NBI)

SDN NBIs are interfaces between SDN Applications and SDN Controllers and typically provide
abstract network views and enable direct expression of network behavior and requirements. This may
occur at any level of abstraction (latitude) and across different sets of functionality (longitude). One value
of SDN lies in the expectation that these interfaces are implemented in an open, vendor-neutral and
interoperable way.SDN NBIs are interfaces between SDN Applications and SDN Controllers and
typically provide abstract network views and enable direct expression of network behavior and
requirements. This may occur at any level of abstraction (latitude) and across different sets of
functionality (longitude). One value of SDN lies in the expectation that these interfaces are implemented
in an open, vendor-neutral and interoperable way.
5.4. Standards information
5.4.1. Introduction standards related to SDN
Unlike some technology areas, such as Wi-Fi, there is no single standards body responsible for
developing open standards for SDN and NFV. Rather, there is a large and evolving collection of
standards-developing organizations (SDOs), industrial consortia, and open development initiatives
involved in creating standards and guidelines for SDN and NFV. Table 3.1 lists the main SDOs and other
organizations involved in the effort and the main outcomes so far produced. This section covers some of
the most prominent efforts.Unlike some technology areas, such as Wi-Fi, there is no single standards
body responsible for developing open standards for SDN and NFV. Rather, there is a large and evolving
collection of standards-developing organizations (SDOs), industrial consortia, and open development
initiatives involved in creating standards and guidelines for SDN and NFV. Table 3.1 lists the main SDOs
and other organizations involved in the effort and the main outcomes so far produced. This section covers
some of the most prominent efforts.

5.4.2. SDN and NFV Open Standards Activities

Table 5.1
Organization Mission SDN and NFV related
effort
Open networking foundation An industry consortium OpenFlow
(ONF) dedicated to the promotion and
adoption of SDN through open
standard development.
Internet Engineering Task Force The Internet’s technical standards Interface to routing systems
(IETF) body. Produces RFCs and (I2RS)
Internet standards. Service function chaining
European Telecommunications An EU-sponsored standards NFV architecture
Standards Institute (ETSI) organization that produces
globally applicable standards for
information and communications
technologies.
OpenDaylight A collaborative project under the OpenDaylight
auspices of the Linux
Foundation.
International Telecommunication United Nations agency that SDN functional requirements and
Union — Telecommunication produces Recommendations with architecture
Standardization Sector (ITU-T) a view to standardizing
telecommunications on a
worldwide basis.
Internet Research Task Force Research group within IRTF. SDN architecture
(IRTF) Software Defined Produces SDN-related RFCs.
Networking Research Group
(SDNRG)
Broadband Forum (BBF) Industry consortium developing Requirements and framework for
broadband packet networking SDN in telecommunications
specifications. broadband networks
Metro Ethernet Forum (MEF) Industry consortium that Defining APIs for service
promotes the use of Ethernet for orchestration over SDN and NFV
metropolitan and wide-area
applications.
IEEE 802 An IEEE committee responsible Standardize SDN capabilities on
for developing standards for access networks.
LANs.
Optical Internetworking Forum Industry consortium promoting Requirements on transport
(OIF) development and deployment of networks in SDN architectures
interoperable networking
solutions and services for optical
networking products.
Open Data Center Alliance Consortium of leading IT SDN usage model
(ODCA) organizations developing
interoperable solutions and
services for cloud computing.
Alliance for Telecommunications A standards organization that Operational opportunities and
Industry Solutions (ATIS) develops standards for the challenges of SDN/NFV
unified communications (UC) programmable infrastructure
industry.
Open Platform for NFV An open source project focused NFV infrastructure
(OPNFV) on accelerating the evolution of
NFV.

5.5. Application Of SDN Today

5.5.1. Benefits of SDN
Software-defined networks (SDNs) are a network architecture approach that allows the network to be
controlled intelligently and centrally, or programmed, using software applications. This helps operators
manage the entire network consistently and comprehensively, regardless of the underlying network
technology.

With SDN, network administrators can change any network switching rules as needed.
Administrators can prioritize, remove priority, or even request to block specific types of packets with
specific levels of control and security. This is particularly useful in the cloud architecture, because it
allows administrators to manage traffic more flexibly and efficiently when there are multiple service
tenants. Basically, this allows administrators to use switches more effectively and have more control over
network traffic than ever before.

Other benefits of SDN are to provide clear management and display of network components and
configurations. Administrators only need to interact with a single centralized controller to distribute
policies to switches connected in the network, instead of having to configure multiple devices
individually. This capability is also a major advantage in security because the controller can monitor
traffic and deploy security policies in a centralized, synchronized and easy manner. For example, if the
controller sees suspicious traffic, it can reroute or discard the packet immediately without forwarding it to
another processing component.

SDN also provides the ability to virtualize hardware and services without the need for specialized
hardware as before, leading to a reduction in hardware identifiers thus reducing the ability of hackers to
trace signals. to attack the system while reducing network deployment operating costs.SDN also provides
the ability to virtualize hardware and services without the need for specialized hardware as before,
leading to a reduction in hardware identifiers thus reducing the ability of hackers to trace signals. to attack
the system while reducing network deployment operating costs.

In addition, SDN has contributed to the emergence of software-defined wide area network (SD-
WAN) technology. SD-WAN uses the virtual overlay aspect of SDN technology, to abstract the
connection links of an organization throughout the LAN and create a virtual network that can use any
link. which connector the controller sees fit to send and receive traffic.In addition, SDN has contributed to
the emergence of software-defined wide area network (SD-WAN) technology. SD-WAN uses the virtual
overlay aspect of SDN technology, to abstract the connection links of an organization throughout the
LAN and create a virtual network that can use any link. which connector the controller sees fit to send
and receive traffic.

SDN is an open source product. Because SDN adheres to open standards, it can theoretically work
with any vendor's network hardware. From an IT perspective, this allows organizations the ability to
avoid rigid supplier in a wide range of network products. This allows IT to become extremely agile
because an open standard solution like SDN simplifies the task of connecting to different clouds,
applications, and devices. And it allows network administrators to use the software for many tasks they
usually do manually.

5.5.2. Issues with SDN

Security is not only an advantage but also a challenge for SDN technology. SDN is managed and
controlled through a single centralized controller, so it is a lucrative target for hackers. Once this attack is
successful, the attacker can take over the entire network.

Another challenge that sounds quite funny to SDN is that although it has the name of "definable", it
actually doesn't have any unified definition and common standards. Different vendors offer different
approaches for SDN, from hardware- and virtual-platform-focused models to hyper-converged network
designs and controller less methods. . There are many different designs and orientations. Therefore it is
often confused with many other concepts such as white box networking, network partitioning, network
automation and programmable networks. Although SDN can work with these technologies and processes,
they are essentially a separate technology.

SDN technology emerged very early and received much attention around 2011, when it was
introduced with the OpenFlow protocol. However, since then, its implementation has been relatively
slow, especially among businesses with smaller network architectures and few resources. In addition,
many businesses present a very high cost of SDN deployment which is a factor causing concern for the
deployment of this technology. SDN technology emerged very early and received much attention around
2011, when it was introduced with the OpenFlow protocol. However, since then, its implementation has
been relatively slow, especially among businesses with smaller network architectures and few resources.
In addition, many businesses present a very high cost of SDN deployment which is a factor causing
concern for the deployment of this technology.

SDN has been used in the network of service providers, network operators, telecommunications,
carriers, along with large companies, such as Facebook and Google, all have resources to deal with. and
contribute to an emerging technology. However, the popularity of SDN is not wide due to many
accompanying problems. Especially, the initial deployment costs and existing network architecture of
most enterprises are still not large enough to show the real benefits of SDN.

5.5.3. The technological revolution is called SDN

SDN has not been used much in practice due to many obstacles. However, with the rapid growth in
multimedia content, the explosion of cloud computing, the impact of mobile phone use is increasing and
the pressure of business operations is constantly on the rise. Costs will make SDN more explosive in the
future. In order to keep up and grow, many businesses and organizations are gradually transitioning to
SDN technology to revolutionize network design and operation within their organizations.

SDN allows programming of network behavior in a centrally controlled manner through software
applications that use an open API. Creating open interfaces for traditional closed network platforms and
implementing a common SDN control layer, operators can manage their entire network and devices
consistently without regard for concern. complexity of network technology.

There are four important areas in which SDN technology can make a difference to an organization.

Network programming capabilities: SDN allows controlling network behavior with software
outside devices that provide physical connectivity of the network. Therefore, network operators can adjust
the behavior of networks to support new services and even individual customers easily. By separating
hardware from software, operators can introduce new, different, fast, unbounded, proprietary services.

Focus on intelligent control: SDN is built on logical centralized network topologies, enabling
intelligent control and management of network resources. Traditional network control is a distributed
method in which devices operate independently with limited awareness of the overall state of the
network. Therefore, each device will not be able to optimize performance based on general status, but
only can operate separately leading to the ability to reduce overall performance of the entire network.
SDN provides centralized control, bandwidth management, recovery, security and thus can build
intelligent, optimal and organized policies based on the comprehensive state of the network.

Network abstraction: Services and applications that run on SDN technology are abstracted from the
underlying hardware and technologies that provide physical connectivity from the network controller.
Applications will interact with the network through APIs, instead of management interfaces that are
tightly coupled with the hardware.

Openness: SDN architecture opens up a new era of openness, enabling the interoperability of many
vendors as well as promoting a vendor-neutral ecosystem. Openness comes from the SDN approach itself.
Open APIs support a wide range of applications, including cloud service coordination, OSS / BSS, SaaS,
and important connected applications. In addition, intelligent software can control hardware from
multiple vendors with an open programming interface such as OpenFlow. Finally, from within SDN,
intelligent network applications and services can run in a common software environment.
 5.5.4. Challenges with SDN
Security is both a right and a concern with SDN technology. The central controller used by SDN has
a single weakness, if targeted by an attacker, that can paralyze the entire network.

5.5.5. SDN application

Apply SDN technology to breakthrough in Internet exchange station architecture.

Within the framework of Asia-Pacific Internet Technology Forum (APRICOT 2017) at the ongoing
APIX conference in Ho Chi Minh City. Ho Chi Minh City, one of the discussions that attracted much
attention from technology circles was the application of SDN (Software-Defined Networking) technology
in the model of Internet transfer station architecture (Internet eXchange Point - IXP called off point is
IX).

Internet exchange station is a connection point that allows independent networks of different
organizations and service providers to connect and exchange traffic. Points IX are essential for Internet
development, through which networks easily upgrade bandwidth to increase traffic, reduce latency, and
save costs in peering deployments.

In Vietnam, the Vietnam Internet Network Information Center (VNNIC), the Ministry of
Information and Communications is the unit managing and operating national Internet transshipment
centers, called VNIX for short-term VN.vn http://www.vnnic.vn/vnix/

Different from transit connections completely dependent on policies and configuration techniques
from upstream service providers, the IX system is characterized by connection policies and techniques
that are consistent across all connections. peering, this is a favorable condition to deploy SDN
application.

SDN technology is a technology that allows the separation between network control function and
data switching function. The application of SDN technology to IX systems will bring about many
practical effects. Accordingly, the entire connection operation and routing control of IX will be controlled
centrally at the Controller device, via the open standard Openflow protocol. This makes it easy for
administrators to quickly develop and implement policies to control traffic going through IX.
 Currently, the popular model of Internet transfer stations in the world operates at Layer 2 in OSI
model (Open Systems Interconnection). Independent stand-alone router controller, individual connections
to central switches and relaying traffic back and forth between these switches, control management will
have to be done individually on each device. were. This overloads the devices in IXs and makes it
difficult to control, monitor and analyze the flow of traffic through IX.

Image 5.1 - Model of traditional Internet traffic transfer station of layer 2

The application of SDN technology makes it easy for the IX system to control centralized,
synchronized and especially easy in expanding connection points, quickly recovering from incidents,
easily monitoring and analyzing traffic. In addition, the use of the Openflow open standard helps to
prevent IX systems from being dependent on proprietary device switching systems.

At this seminar, experts from TouIX (one point IX in France) introduced as the first unit in the world
to have successfully converted the traditional IX class 2 architecture model to SDN application and great
benefits. The great bring of technology in the management and operation of the IX system. With the
above advantages, the application of SDN technology is forecasted to be one of the future development
trends of the IX systems.

6. SDN development trend

Currently, SDN is really a direction of particular interest in both research and application. We can
easily recognize that SDN is suitable for the centralized network environment and has extremely large
traffic volume including:

 Enterprise network systems: Campus network and data center network (Data Center)
 Network system for cloud computing – Cloud
 SDN has received interest from the "giants" in the technology industry when both Google and
Facebook have participated in research and building their own data centers using SDN. It is predicted that
in the near future, SDN will eliminate the commercial monopoly in the network equipment field which
has long been held by CISCO and will open a revolution like Apple has created for iPhone.

7. Conclusion
Officially launched around 2008 at Stanford University, USA, but SDN has created a revolution in
the IT industry. With both Google and Facebook currently investing heavily in SDN, it has shown its
heat. It is predicted that in the next 5 years, SDN will replace the entire traditional network system.

8. References
- https://en.wikipedia.org/wiki/Software-defined_networking

- https://www.networkworld.com/article/3209131/what-sdn-is-and-where-its-going.html

- https://tools.ietf.org/html/rfc7426

- https://tek4.vn/sdn-la-gi-tai-sao-sdn-lai-la-xu-cho-cong-nghe-mang-tuong-lai/

- https://www.thegioimaychu.vn/blog/tong-hop/software-defined-networks-sdn-la-gi-p1848/