0% found this document useful (0 votes)
17 views25 pages

Chapter 1 Part3

Uploaded by

awansumaira499
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
17 views25 pages

Chapter 1 Part3

Uploaded by

awansumaira499
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 25

Chapter 1: roadmap

1.1 what is the Internet?


1.2 network edge
 end systems, access networks, links
1.3 network core
 packet switching, circuit switching, network
structure
1.4 delay, loss, throughput in networks
1.5 protocol layers, service models
1.6 networks under attack: security
1.7 history

Introduction 1-1
Protocol “layers”
Networks are
complex,
with many “piece
s”: Question:
 hosts is there any hope of
organizing structure of
 routers network?
 links of various
media …. or at least our
 applications discussion of networks?
 protocols
 hardware,
software
Introduction 1-2
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

 a series of steps

Introduction 1-3
Layering of airline
functionality
ticket (purchase) ticket (complain) ticket

baggage (check) baggage (claim baggage

gates (load) gates (unload) gate

runway (takeoff) runway (land) takeoff/landing

airplane routing airplane routing airplane routing airplane routing airplane routing

departure intermediate air-traffic arrival


airport control centers airport

layers: each layer implements a service


 via its own internal-layer actions
 relying on services provided by layer
below
Introduction 1-4
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 of implementation of layer’s service
transparent to rest of system
 e.g., change in gate procedure doesn’t
affect rest of system
 layering considered harmful?

Introduction 1-5
Open Systems Interconnection (OSI) model is a conceptual model created
by the International Organization for Standardization which enables diverse
communication systems to communicate using standard protocols.

Introduction 1-6
Internet protocol stack
 application: supporting
network applications
 FTP, SMTP, HTTP application
 transport: process-process
data transfer transport
 TCP, UDP
 network: routing of datagrams network
from source to destination
 IP, routing protocols
link
 link: data transfer between
neighboring network elements physical
 Ethernet, 802.111 (WiFi), PPP
 physical: bits “on the wire”

Introduction 1-7
ISO/OSI reference
model
 presentation: allow
applications to interpret application
meaning of data, e.g.,
encryption, compression, presentation
machine-specific
conventions session
 session: synchronization, transport
checkpointing, recovery of
network
data exchange
 Internet stack “missing” link
these layers! physical
 these services, if needed, must
be implemented in application
 needed?

Introduction 1-8
source Encapsulatio
message
segment Ht
M
M
application
transport
n
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-9
Chapter 1: roadmap
1.1 what is the Internet?
1.2 network edge
 end systems, access networks, links
1.3 network core
 packet switching, circuit switching, network
structure
1.4 delay, loss, throughput in networks
1.5 protocol layers, service models
1.6 networks under attack: security
1.7 history

Introduction 1-10
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-11
Bad guys: put malware into hosts via
Internet
 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 email distribution or
(Distributed Denial-of-Service) DDoS
attacks
Introduction 1-12
Bad guys: attack server, network infrastructure

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)

3. send packets to target


from compromised
target
hosts

Introduction 1-13
Bad guys: attack server, network infrastructure

Introduction 1-14
Bad guys: attack server, network infrastructure
Vulnerability attack
•sending a few well-crafted messages to a vulnerable application or operating
system running on a targeted host
• If the right sequence of packets can stop or can crash the host

Bandwidth flooding
•attacker sends a lot of packets to the targeted host—so many packets that the
target’s access link becomes clogged, preventing legitimate packets from
reaching the server

Introduction 1-15
Bad guys: attack server, network infrastructure

Connection flooding
 The attacker establishes a large number of half-open or fully open
TCP connections (TCP connections are discussed in Chapter 3) at the
target host
The host can become so bogged down with these bogus
connections that it stops accepting legitimate connections

Introduction 1-16
Bad guys can sniff packets
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

Introduction 1-17
Bad guys can use fake
addresses
IP spoofing: send packet with false source
address
A C

src:B dest:A payload

Introduction 1-18
Chapter 1: roadmap
1.1 what is the Internet?
1.2 network edge
 end systems, access networks, links
1.3 network core
 packet switching, circuit switching, network
structure
1.4 delay, loss, throughput in networks
1.5 protocol layers, service models
1.6 networks under attack: security
1.7 history

Introduction 1-19
Internet history
1961-1972: Early packet-switching principles
 1961: Kleinrock -  1972:
queueing theory  ARPAnet public demo
shows effectiveness  NCP (Network Control
of packet-switching Protocol) first host-host
 1964: Baran - protocol
packet-switching in  first e-mail program
military nets
 ARPAnet has 15 nodes
 1967: ARPAnet
conceived by
Advanced Research
Projects Agency
 1969: first ARPAnet
node operational

Introduction 1-20
Internet history
1972-1980: Internetworking, new and proprietary nets

 1970: ALOHAnet satellite


network in Hawaii Cerf and Kahn’s
 1974: Cerf and Kahn - internetworking
architecture for principles:
interconnecting networks  minimalism, autonomy -
 1976: Ethernet at Xerox no internal changes
PARC required to interconnect
networks
 late70’s: proprietary  best effort service model
architectures: DECnet, SNA,
 stateless routers
XNA
 decentralized control
 late 70’s: switching fixed
length packets (ATM define today’s Internet
precursor) architecture
 1979: ARPAnet has 200
nodes
Introduction 1-21
Internet history
1980-1990: new protocols, a proliferation of networks

 1983: deployment of  new national


TCP/IP networks: Csnet,
 1982: smtp e-mail BITnet, NSFnet,
protocol defined Minitel
 1983: DNS defined  100,000 hosts
for name-to-IP- connected to
address translation confederation of
 1985: ftp protocol networks
defined
 1988: TCP
congestion control

Introduction 1-22
Internet history
1990, 2000’s: commercialization, the Web, new apps
 early 1990’s: ARPAnet late 1990’s – 2000’s:
decommissioned  more killer apps:
 1991: NSF lifts restrictions
instant messaging,
on commercial use of NSFnet P2P file sharing
(decommissioned, 1995)
 network security to
 early 1990s: Web
 hypertext [Bush 1945, forefront
 est. 50 million host,
Nelson 1960’s]
 HTML, HTTP: Berners-Lee 100 million+ users
 1994: Mosaic, later  backbone links
Netscape running at Gbps
 late 1990’s:
commercialization of the
Web

Introduction 1-23
Internet history
2005-present
 ~750 million hosts
 Smartphones and tablets
 Aggressive deployment of broadband access
 Increasing ubiquity of high-speed wireless access
 Emergence of online social networks:
 Facebook: soon one billion users
 Service providers (Google, Microsoft) create their
own networks
 Bypass Internet, providing “instantaneous”
access to search, emai, etc.
 E-commerce, universities, enterprises running
their services in “cloud” (eg, Amazon EC2)

Introduction 1-24
Introduction: summary
covered a “ton” of you now have:
material!  context, overview,
 Internet overview “feel” of networking
 what’s a protocol?  more depth, detail
 network edge, core, to follow!
access network
 packet-switching
versus circuit-
switching
 Internet structure
 performance: loss,
delay, throughput
 layering, service models
 security
 history Introduction 1-25

You might also like