1

Grading Policy
Mid Term Exam weightage 25 %

Quizzes 15%

Assignments 10 %

Terminal Exam 50 %

Total 100

2
 Course Material Access
All the lecture slides and helping material, and course
information would be available in following yahoo or
gmail group. (email your name and class section to
mustafashakir79@gmail.com)
• Group home page:
• https://groups.google.com/forum/#!forum/
sp24_advanced-comm-systems&networks-
msphd@googlegroups.com

3
 Rules
 What is cheating & plagiarism?
 Acting dishonestly,
 Stealing or using (without my permission) other people’s writings or ideas
 E.g.from other students, other sources such as web sites, solutions from
previous offerings of this course etc.
 Note that it doesn’t have to be literal copying – stealing ideas but
presenting in a different style is still cheating and plagiarism.
 You are also guilty if you aid in cheating & plagiarism
 zero tolerance
 HWs, paper presentation: zero score + one level reduction in course grade

 Registration and Attendance

 Registration issues should be coordinated within time in coordination with
Front Office as students registering the course in beginning week would be
also evaluated for required attendance.
 Attendance can be taken anytime during the Class.
 Results
Internals Quiz Assignments Sessional Results would be available in one week
and can be discussed in class. Terminal results would be announced after one
4 week and can email for relevant detail.
 Advanced Communication Systems
and Networks

5
 Chapter :

Telecommunications and Networks

6
 Software Defined Networking

7
Chapter 5
Network Layer:
The Control Plane

A note on the use of these Powerpoint slides:

We’re making these slides freely available to all (faculty, students, readers).
They’re in PowerPoint form so you see the animations; and can add, modify,
and delete slides (including this one) and slide content to suit your needs.
They obviously represent a lot of work on our part. In return for use, we only
ask the following: Computer
 If you use these slides (e.g., in a class) that you mention their source
(after all, we’d like people to use our book!)
Networking: A Top
 If you post any slides on a www site, that you note that they are adapted
from (or perhaps identical to) our slides, and note our copyright of this
Down Approach
material.
7th edition
Thanks and enjoy! JFK/KWR
Jim Kurose, Keith Ross
All material copyright 1996-2016 Pearson/Addison Wesley
J.F Kurose and K.W. Ross, All Rights Reserved April 2016
5-8
Chapter 5: outline
5.5 The
5.1 introduction
SDN control plane
5.2 ICMP:
5.6 routing The
protocols
Internet Control Message Protocol

5.7link
Network
state management and SNMP
 distance vector
5.3 intra-AS routing in the Internet: OSPF
5.4 routing among the ISPs: BGP

5-9
 Software Defined Networking using
Openflow standard
Dr. Mustafa Shakir

10
 OpenFlow data plane abstraction
flow: defined by header fields
generalized forwarding: simple packet-handling rules
Pattern: match values in packet header fields
Actions: for matched packet: drop, forward, modify, matched
packet or send matched packet to controller
Priority: disambiguate overlapping patterns
Counters: #bytes and #packets

* : wildcard
1. src=1.2.*.*, dest=3.4.5.*  drop
2. src = *.*.*.*, dest=3.4.*.*  forward(2)
11 3. src=10.1.2.3, dest=*.*.*.*  send to controller
 OpenFlow: Flow Table Entries

Rule Action Stats

Packet + byte counters

1. Forward packet to port(s)
2. Encapsulate and forward to controller
3. Drop packet
4. Send to normal processing pipeline
5. Modify Fields

Switch VLAN MAC MAC Eth IP IP IP TCP TCP

Port ID src dst type Src Dst Prot sport dport

12 Link layer Network layer Transport layer

 Examples: Forwarding
Functionality
Destination-based layer 3 (router) forwarding:
Switch MAC MAC Eth VLAN IP IP IP TCP TCP
Action
Port src dst type ID Src Dst Prot sport dport
* * * * * * 51.6.0.8 * * * port6
IP datagrams destined to IP address 51.6.0.8
should be forwarded to router output port 6

Destination-based layer 2 (switch) forwarding:

Switch MAC MAC Eth VLAN IP IP IP TCP TCP
Action
Port src dst type ID Src Dst Prot sport dport
22:A7:23:
* 11:E1:02 * * * * * * * * port3
layer 2 frames from MAC address
22:A7:23:11:E1:02 should be forwarded to switch
output port 3
13
 Examples: Firewall Functionality

Firewall:
Switch MAC MAC Eth VLAN IP IP IP TCP TCP
Forward
Port src dst type ID Src Dst Prot sport dport
* * * * * * * * * 22 drop
do not forward (block) all datagrams destined to TCP port 22

Switch MAC MAC Eth VLAN IP IP IP TCP TCP

Forward
Port src dst type ID Src Dst Prot sport dport
* * * * drop
do not forward* (block)
* * * *
128.119.1.1
all datagrams sent by host
128.119.1.1

14
OpenFlow abstraction
 match+action: unifies different kinds of devices
 Router  Firewall
• match: longest • match: IP addresses
destination IP prefix and TCP/UDP port
• action: forward out numbers
a link • action: permit or
 Switch deny
• match: destination  NAT
MAC address • match: IP address
• action: forward or and port
flood • action: rewrite
address and port
4-15
 Example: datagrams from
OpenFlow example hosts h5 and h6 should
be sent to h3 or h4, via s1
match action and from there to s2
IP Src = 10.3.*.* Host h6
forward(3)
IP Dst = 10.2.*.* 10.3.0.6
1 s3 controller
2

3 4
Host h5
10.3.0.5

1 s1 1 s2
2 Host h4
4 2 4
Host h1 10.2.0.4
3 3
10.1.0.1
Host h2
10.1.0.2 match action
match action Host h3
ingress port = 2
10.2.0.3 forward(3)
ingress port = 1 IP Dst = 10.2.0.3
IP Src = 10.3.*.* forward(4) ingress port = 2
forward(4)
16 IP Dst = 10.2.*.* IP Dst = 10.2.0.4
SDN: selected challenges
the control plane: dependable, reliable, performance-
scalable, secure distributed system
robustness to failures: leverage strong theory of reliable
distributed system for control plane
dependability, security: networks, protocols meeting
mission-specific requirements
e.g., real-time, ultra-reliable, ultra-secure
Internet-scaling

5-17
 M2M
Differences and similarities between M2M and IoT
SDN and NFV for IoT

Book website: http://www.internet-of-things-book.com Bahga & Madisetti, © 2015

18
 Machine-to-Machine (M2M)
Machine-to-Machine (M2M) refers to networking of
machines (or devices) for the purpose of remote
monitoring and control and data exchange.

Book website: http://www.internet-of-things-book.com Bahga & Madisetti, © 2015

19
 Machine-to-Machine (M2M)
 An M2M area network comprises machines (or M2M nodes) which have
embedded hardware modules for sensing, actuation and communication.
 Various communication protocols can be used for M2M local area networks,
such as ZigBee, Bluetooth, ModBus, M-Bus, Wireless M-Bus, Power Line
Communication (PLC), 6LoWPAN, IEEE 802.15.4, etc.
 The communication network provides connectivity to remote M2M area
networks.
 The communication network can use either wired or wireless networks (IP-
based).
 While the M2M area networks use either proprietary or non-IP based
communication protocols, the communication network uses IP-based
networks.
Book website: http://www.internet-of-things-book.com

20
 M2M Gateway
Since non–IP-based protocols are used within M2M area
networks, the M2M nodes within one network cannot
communicate with nodes in an external network.
To enable communication between remote M2M area
networks, M2M gateways are used.

Book website: http://www.internet-of-things-book.com Bahga & Madisetti, © 2015

21
 Difference between IoT and M2M
 Communication Protocols
M2M and IoT can differ in how the communication between the machines or
devices happens.
M2M uses either proprietary or non–IP-based communication protocols for
communication within the M2M area networks.
 Machines in M2M vs Things in IoT
The "Things" in IoT refers to physical objects that have unique identifiers and
can sense and communicate with their external environment (and user
applications) or their internal physical states.
M2M systems, in contrast to IoT, typically have homogeneous machine types
within an M2M area network.
Book website: http://www.internet-of-things-book.com

22
 Difference between IoT and M2M
 Hardware vs Software Emphasis
 While the emphasis of M2M is more on hardware with embedded modules, the
emphasis of IoT is more on software.
 Data Collection & examining
 M2M data is collected in point solutions and often in on-premises storage infrastructure.
 In contrast to M2M, the data in IoT is collected in the cloud (can be public, private or
hybrid cloud).
 Applications
 M2M data is collected in point solutions and can be accessed by on-premises
applications such as diagnosis applications, service management applications and on-
premises enterprise applications.
 IoT data is collected in the cloud and can be accessed by cloud applications such as
analytics applications, enterprise applications, remote diagnosis and management
applications, etc.

23
 Communication in IoT vs M2M

Book website: http://www.internet-of-things-book.com

24
 SDN layers
 Software-Defined Networking
(SDN) is a networking architecture
that separates the control plane from
the data plane and centralizes the
network controller.
 Software-based SDN controllers
maintain a unified view of the
network and make configuration,
management and provisioning
simpler.
 The underlying infrastructure in
SDN uses simple packet forwarding
hardware as opposed to specialized
hardware
Book website:in conventional networks.
http://www.internet-of-things-book.com

25
 Key Elements of SDN
 Centralized Network Controller
 With decoupled control and data planes and a centralized network
controller, the network administrators can rapidly configure the network.
 Programmable Open APIs
 SDN architecture supports programmable open APIs for interface between
the SDN application and control layers (Northbound interface).
 Standard Communication Interface (OpenFlow)
 SDN architecture uses a standard communication interface between the
control and infrastructure layers (Southbound interface).
 OpenFlow, which is defined by the Open Networking Foundation (ONF), is
the broadly accepted SDN protocol for the Southbound interface.
Book website: http://www.internet-of-things-book.com

26
 NFV
 Network Function
Virtualization (NFV) is a
technology that leverages
virtualization to consolidate
the heterogeneous network
devices onto industry-
standard high-volume
servers, switches and storage.
 NFV is complementary to
SDN as NFV can provide the
infrastructure on which SDN
can run.http://www.internet-of-things-book.com
Book website:

27