Chapter 1

Introduction:
Computer Networks
& Internet
Part-III

Computer Networking: A
Top-Down Approach
8th edition
Jim Kurose, Keith Ross
Pearson, 2020
Introduction: 1-1
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-2
Network security
 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!
 We now need to think about:
• how bad guys can attack computer networks
• how we can defend networks against attacks
• how to design architectures that are immune to attacks
Introduction: 1-3
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-4
Bad guys: fake identity
IP spoofing: injection of packet with false source address

A C

src:B dest:A payload

Introduction: 1-5
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-6
Lines of defense:
 authentication: proving you are who you say you are
• cellular networks provides hardware identity via SIM card; no such
hardware assist in traditional Internet
 confidentiality: via encryption
 integrity checks: digital signatures prevent/detect tampering
 access restrictions: password-protected VPNs
 firewalls: specialized “middleboxes” in access and core
networks:
 off-by-default: filter incoming packets to restrict senders, receivers,
applications
 detecting/reacting to DOS attacks
… lots more on security (throughout, Chapter 8) Introduction: 1-7
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-8
Protocol “layers” and reference models

Networks are complex, Question: is there any

with many “pieces”: hope of organizing
 hosts structure of network?
 routers  and/or our discussion
 links of various media of networks?
 applications
 protocols
 hardware, software

Introduction: 1-9
Example: organization of air travel

end-to-end transfer of person plus baggage

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

How would you define/discuss the system of airline travel?

 a series of steps, involving many services
Introduction: 1-10
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

 via its own internal-layer actions
 relying on services provided by layer below
Introduction: 1-11
Why layering?
Approach to designing/discussing complex systems:
 explicit structure allows identification,
relationship of 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

Introduction: 1-12
Layered Internet protocol stack
 application: supporting network applications
• HTTP, IMAP, SMTP, DNS
application
application
 transport: process-process data transfer
• TCP, UDP transport
transport
 network: routing of datagrams from source to
destination network
• IP, routing protocols
link
 link: data transfer between neighboring
network elements physical
• Ethernet, 802.11 (WiFi), PPP
 physical: bits “on the wire”
Introduction: 1-13
 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., reliably) from transport
one process to another, using services of network layer

network  transport-layer protocol encapsulates network

application-layer message, M, with
transport layer-layer header Ht to create a link
link
transport-layer segment
• Ht used by transport layer protocol to
physical implement its service physical

source destination

Introduction: 1-14
 Services, Layering and Encapsulation
M

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

application application
Ht M
transport transport
Hn Ht M
network Network-layer protocol transfers transport-layer segment
network
[Ht | M] from one host to another, using link layer services
Hl Hn Ht
link M
link
Link-layer protocol transfers datagram [Hn| [Ht |M] from
host to neighboring host, using network-layer services
physical  link-layer protocol encapsulates network physical
datagram [Hn| [Ht |M], with link-layer header
source Hl to create a link-layer frame destination

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

message segment datagram frame

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

 Services, Layering and Encapsulation

message M
application M application

segment Ht M
transport Ht M
transport
datagram Hn Ht M Hn Ht M
network network

frame Hl Hn Ht M Hl Hn Ht M
link link

physical physical

source destination

Introduction: 1-18
 source Encapsulation:
message
segment Htt
M
M
application
transport
an end-end
datagram Hn Ht M network view
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-19
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-20
Internet history
1961-1972: Early packet-switching principles
 1961: Kleinrock - queueing  1972:
theory shows effectiveness of • ARPAnet public demo
packet-switching • NCP (Network Control Protocol)
 1964: Baran - packet-switching first host-host protocol
in military nets • first e-mail program
 1967: ARPAnet conceived by • ARPAnet has 15 nodes
Advanced Research Projects
Agency
 1969: first ARPAnet node
operational
Internet history
1972-1980: Internetworking, new and proprietary networks
 1970: ALOHAnet satellite
Cerf and Kahn’s internetworking
network in Hawaii principles:
 1974: Cerf and Kahn -  minimalism, autonomy - no
architecture for interconnecting internal changes required to
networks interconnect networks
 best-effort service model
 1976: Ethernet at Xerox PARC
 stateless routing
 late70’s: proprietary  decentralized control
architectures: DECnet, SNA, XNA define today’s Internet architecture
 1979: ARPAnet has 200 nodes

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

Introduction: 1-23
Internet history
1990, 2000s: commercialization, the Web, new applications
 early 1990s: ARPAnet late 1990s – 2000s:
decommissioned  more killer apps: instant
 1991: NSF lifts restrictions on messaging, P2P file sharing
commercial use of NSFnet  network security to forefront
(decommissioned, 1995)
 est. 50 million host, 100 million+
 early 1990s: Web
users
• hypertext [Bush 1945, Nelson 1960’s]
 backbone links running at Gbps
• HTML, HTTP: Berners-Lee
• 1994: Mosaic, later Netscape
• late 1990s: commercialization of the
Web
Introduction: 1-24
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-25
Chapter 1: summary
We’ve covered a “ton” of material!
 Internet overview
 what’s a protocol? You now have:
 network edge, access network, core  context, overview,
• packet-switching versus circuit-
switching vocabulary, “feel”
• Internet structure of networking
 performance: loss, delay, throughput  more depth,
 layering, service models detail, and fun to
 security follow!
 history
Introduction: 1-26
Additional Chapter 1 slides

Introduction: 1-27
 ISO/OSI reference model
Two layers not found in Internet
application
protocol stack!
presentation
 presentation: allow applications to
interpret meaning of data, e.g., encryption, session
compression, machine-specific conventions transport
 session: synchronization, checkpointing, network
recovery of data exchange link
 Internet stack “missing” these layers!
physical
• these services, if needed, must be
implemented in application The seven layer OSI/ISO
reference model
• needed?
Introduction: 1-28
 Services, Layering and Encapsulation
M

application M application
message
Ht M
transport Ht M
transport
segment
Hn Ht M Hn Ht M
network network
datagram

Hl Hn Ht Hl Hn Ht M
link M
link
frame

physical physical

source destination

Introduction: 1-29
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-30