Networking Basics: A Review
Carey Williamson
Department of Computer Science
University of Calgary
Communications Networks
Historically, there have been two different
philosophies guiding the design, operation, and
evolution of communication networks
— the “telco” view (i.e., telecommunications networks to
support voice telephony and other emerging services,
such as fax, data, location, etc.)
— the “data networking” view (i.e., the Internet)
While the two approaches share some similar
goals and challenges (e.g., scale, geography,
heterogeneity), they often have quite different
underlying assumptions
2
Telco Networks (1 of 2)
Over 100 years old
Circuit-switched network
Designed for transmission of human voice
Twisted pair copper wire for residential access
— “cheap”, adequate bandwidth, easy to handle...
Aggregation of multiple calls at toll office for
multiplexing/demultiplexing using TDM
Low bandwidth required per call (e.g., 64 Kbps)
Fixed bandwidth required per call
3
Telco Networks (2 of 2)
Call routing and circuit allocation decided once per call
at time of call arrival
End to end path allocation, with dedicated circuit
(reserved bandwidth) per active call
All bits travel same path; stay in same order
Call state information crucial in network switches
Busy signal if no path possible (blocking <= 2%)
Billing model based on time used (in minutes)
Single class of service; high reliability (99.99%)
New services: faxes, modems, mobility, ...
4
The Internet (1 of 2)
About 50 years old
Packet-switched network
Variable size packets permitted
Designed for transmission of data
Wide range of access technologies
Wide range of user and application behaviour
Bursty, variable bandwidth required per call
Aggregation of traffic at routers/switches
Transmission links shared on stat mux basis
5
The Internet (2 of 2)
Connection-less network layer protocol (IP)
“Best effort” datagram delivery model
Packet routing decided on a per packet basis
No end to end path allocation; no reserved bandwidth
per active call
Packets can travel any path; packets can be delayed,
lost, duplicated, re-ordered
Minimal state info in network switches
Single class of service
Billing model? (hours? pkts? bytes? bandwidth?)
6
Internet Protocol Stack
Application: supporting network
applications and end-user services Application
— FTP, SMTP, HTTP, DNS, NTP
Transport: end to end data transfer Transport
— TCP, UDP
Network: routing of datagrams from Network
source to destination
— IPv4, IPv6, BGP, RIP, routing protocols Data Link
Data Link: hop by hop frames, channel
access, flow/error control Physical
— PPP, Ethernet, IEEE 802.11b
001101011...
Physical: raw transmission of bits
7
Internet Protocol Stack
Application Application
Transport Transport
Network Network
Data Link Data Link
Physical Core Physical
Network
8
Internet Protocol Stack
Application Application Application
Router
Transport Transport Transport
Network Network Network
Data Link Data Link Data Link
Physical Physical Physical
9
Internet Protocol Stack
Application Application Application
Transport Switch
Transport Transport
Network Network Network
Data Link Data Link Data Link
Physical Physical Physical
10