Introduction

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:

 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!)
 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 material.
Computer
For a revision history, see the slide note for this page.
Networking: A Top-
Thanks and enjoy! JFK/KWR
Down Approach
All material copyright 1996-2020 8th edition
J.F Kurose and K.W. Ross, All Rights Reserved
Jim Kurose, Keith Ross
Pearson, 2020
Introduction: 1-1
Network security
 field of network security:
• how bad guys can attack computer networks
• how we can defend networks against attacks
• how to design architectures that are immune to
attacks
 Internet not originally designed with (much)
security in mind
• original vision: “a group of mutually trusting users
attached to a transparent network” 
• Internet protocol designers playing “catch-up”
• security considerations in all layers!
Introduction: 1-99
Bad guys: malware
 malware can get in host from:
• virus: self-replicating infection by
receiving/executing object (e.g., e-mail attachment)
• worm: self-replicating infection by passively
receiving object that gets itself executed
 spyware malware can record keystrokes, web sites
visited, upload info to collection site
 infected host can be enrolled in botnet, used for spam
or distributed denial of service (DDoS) attacks

Introduction: 1-100
Bad guys: denial of service
Denial of Service (DoS): attackers make resources
(server, bandwidth) unavailable to legitimate
traffic by overwhelming resource with bogus traffic
1. select target
2. break into hosts
around the
network (see
botnet) target
3. send packets to
target from
compromised hosts
Introduction: 1-101
Bad guys: packet interception
packet “sniffing”:
 broadcast media (shared Ethernet, wireless)
 promiscuous network interface reads/records all
packets (e.g., including passwords!) passing by

A C

src:B dest:A payload

B

Wireshark software used for our end-of-chapter labs is a (free)

packet-sniffer
Introduction: 1-102
Bad guys: fake identity

IP spoofing: send packet with false source

address

A C

src:B dest:A payload

… lots more on security (throughout, Chapter 8)

Introduction: 1-103
Protocol “layers” and reference models

Networks are complex,

with many “pieces”: Question:
 hosts is there any hope of
 routers organizing
 links of various media structure of
 applications network?
 protocols
 hardware, software
…. or at least our
discussion of
networks?
Introduction: 1-105
Example: organization of air travel

ticket (purchase) ticket (complain)

baggage (check) baggage (claim)
gates (load) gates (unload)
runway takeoff runway landing
airplane routing airplane routing
airplane routing

airline travel: a series of steps, involving many services

Introduction: 1-106
Example: organization of air travel

ticket (purchase) ticketing service ticket (complain)

baggage (check) baggage service baggage (claim)
gates (load) gate service gates (unload)
runway takeoff runway service runway landing
airplane routing routing service
airplane routing airplane routing

layers: each layer implements a service Q: describe in

 via its own internal-layer actions words the service
 relying on services provided by layer below provided in each
layer above
Introduction: 1-107
Why layering?
dealing with complex systems:
 explicit structure allows identification, relationship of
complex system’s pieces
• layered reference model for discussion
 modularization eases maintenance, updating of
system
• change in layer's service implementation: transparent to
rest of system
• e.g., change in gate procedure doesn’t affect rest of system
 layering considered harmful?
 layering in other complex systems?
Introduction: 1-108
Internet protocol stack
 application: supporting network
applications
• IMAP, SMTP, HTTP application
 transport: process-process data transfer
transport
• TCP, UDP
 network: routing of datagrams from network
source to destination
• IP, routing protocols link
 link: data transfer between neighboring
network elements physical
• Ethernet, 802.11 (WiFi), PPP
 physical: bits “on the wire”
Introduction: 1-109
 ISO/OSI reference model
Two layers not found in Internet
protocol stack! application
 presentation: allow applications to presentation
interpret meaning of data, e.g., session
encryption, compression, machine-
specific conventions transport
 session: synchronization, network
checkpointing, recovery of data link
exchange
 Internet stack “missing” these layers! physical
• these services, if needed, must be The seven layer OSI/ISO
implemented in application reference model
• needed?
Introduction: 1-110
 Services, Layering and Encapsulation
M
Application exchanges messages to implement some
application application service using services of transport layer application
Ht M
transport Transport-layer protocol transfers M (e.g., transport
reliably) from one process to another, using
services of network layer
network § transport-layer protocol encapsulates
network
application-layer message, M, with
link transport layer-layer header Ht to link
create a transport-layer segment
• Ht used by transport layer protocol
physical to implement its service physical

source destination

Introduction: 1-111
 Services, Layering and Encapsulation
M

application application
Ht M
transport Transport-layer protocol transfers M (e.g., reliably) from
one process to another, using services of network layer
transport
Hn Ht M
network Network-layer protocol transfers transport-layer
network
segment [Ht | M] from one host to another,
using link layer services
link link
§ network-layer protocol encapsulates
transport-layer segment [Ht | M] with
physical network layer-layer header Hn to create a physical
network-layer datagram
• Hn used by network layer protocol to
source implement its service destination

Introduction: 1-112
 Services, Layering and Encapsulation
M

application application
Ht M
transport transport
Hn Ht M
network Network-layer protocol transfers transport-layer segment [H t
network
| M] from one host to another, using link layer services

Hl Hn Ht
link M
link
Link-layer protocol transfers datagram [H n| [Ht
|M] from host to neighboring host, using
network-layer services physical
physical
§ link-layer protocol encapsulates network
datagram [Hn| [Ht |M], with link-layer
source header Hl to create a link-layer frame destination

Introduction: 1-113
 Encapsulation
Matryoshka dolls (stacking dolls)

messagesegment datagram frame

Credit: https://dribbble.com/shots/7182188-Babushka-Boi Introduction: 1-114

 source
message M application Encapsulation
segment Ht M transport
datagram Hn Ht M network
frame Hl Hn Ht M link
physical
link
physical

switch

destination Hn Ht M network
M application
Hl Hn Ht M link Hn Ht M
Ht M transport physical
Hn Ht M network
Hl Hn Ht M link router
physical
Introduction: 1-115
Chapter 1: roadmap
 What is the Internet?
 What is a protocol?
 Network edge: hosts, access
network, physical media
 Network core: packet/circuit
switching, internet structure
 Performance: loss, delay,
throughput
 Security
 Protocol layers, service models
 History
Introduction: 1-116
 Internet history
1961-1972: Early packet-switching principles
 1961: Kleinrock - queueing  1972:
theory shows effectiveness • ARPAnet public demo
of packet-switching
• NCP (Network Control
 1964: Baran - packet- Protocol) first host-host
switching in military nets protocol
 1967: ARPAnet conceived • first e-mail program
by Advanced Research
Projects Agency
• ARPAnet has 15 nodes
 1969: first ARPAnet node
operational

Introduction: 1-117
Oct 29 1969:
un día histórico!
 Internet history
1972-1980: Internetworking, new and proprietary nets
 1970: ALOHAnet satellite
network in Hawaii Cerf and Kahn’s
 1974: Cerf and Kahn - internetworking principles:
 minimalism, autonomy - no
architecture for interconnecting
networks internal changes required
to interconnect networks
 1976: Ethernet at Xerox PARC
 best-effort service model
 late70’s: proprietary  stateless routing
architectures: DECnet, SNA, XNA
 decentralized control
 late 70’s: switching fixed length
packets (ATM precursor) define today’s Internet
architecture
 1979: ARPAnet has 200 nodes

Introduction: 1-119
 Internet history
1980-1990: new protocols, a proliferation of networks
 1983: deployment of  new national networks:
TCP/IP CSnet, BITnet, NSFnet,
 1982: smtp e-mail Minitel
protocol defined  100,000 hosts connected to
 1983: DNS defined for confederation of networks
name-to-IP-address
translation
 1985: ftp protocol defined
 1988: TCP congestion
control
Introduction: 1-120
 Internet history
1990, 2000s: commercialization, the Web, new applications

 early 1990s: ARPAnet late 1990s – 2000s:

decommissioned  more killer apps: instant
 1991: NSF lifts restrictions messaging, P2P file sharing
on commercial use of NSFnet  network security to
(decommissioned, 1995) forefront
 early 1990s: Web
 est. 50 million host, 100
• hypertext [Bush 1945, Nelson 1960’s]
million+ users
• HTML, HTTP: Berners-Lee
• 1994: Mosaic, later Netscape  backbone links running at
• late 1990s: commercialization of Gbps
the Web
Introduction: 1-121
Internet history
2005-present: scale, SDN, mobility, cloud
§ aggressive deployment of broadband home access (10-100’s Mbps)
§ 2008: software-defined networking (SDN)
§ increasing ubiquity of high-speed wireless access: 4G/5G, WiFi
§ service providers (Google, FB, Microsoft) create their own networks
• bypass commercial Internet to connect “close” to end user, providing
“instantaneous” access to social media, search, video content, …
§ enterprises run their services in “cloud” (e.g., Amazon Web Services,
Microsoft Azure)
§ rise of smartphones: more mobile than fixed devices on Internet
(2017)

§ ~15B devices attached to Internet (2023, statista.com)

Introduction: 1-122
Summary
We’ve covered a “ton” of
material!
 Internet overview
 what’s a protocol? You now have:
 network edge, access network, core  context,
• packet-switching versus circuit- overview,
switching vocabulary,
• Internet structure “feel” of
 performance: loss, delay, networking
throughput  more depth,
 layering, service models
detail, and fun to
 security follow!
 history
Introduction: 1-123
Wireshark
application
(www browser,
packet
email client)
analyzer
application

OS
packet Transport (TCP/UDP)
capture copy of all Network (IP)
Ethernet frames Link (Ethernet)
(pcap) sent/received
Physical

Introduction: 1-124