EEC 189Q: Computer Networks

Layered Architecture
Reference: Chapter 2.1-2.2, 2.3.1

Recap from last lecture

Circuit vs. Packet switching Multiplexing strategies

- Deterministic vs. statistical multiplexing

Fundamental issues in networking

Communication network is a complex, distributed system

- How do we implement it? How do we control it?

Chuah, Fall 2004

Page 1

What is The Internet?

The Internet :
- Collection of networks and routers that span the world and use the TCP/IP protocols to form a single, cooperative virtual network

intranet: connection of different LANs within an organization

- private - may use leased lines - usually small, but possibly hundreds of routers - may be connected to the Internet (or not), often by firewall

Chuah, Fall 2004

Elements of a Network
Hosts, end-systems
pcs, workstations, servers PDAs, phones, toasters router server local ISP workstation mobile

running network apps Communication links

Point-to-point, multi-access fiber, copper, radio, satellite

regional ISP

Routers: forward packets

(chunks) of data thru network

Internet: network of networks

Internet is a specific internet
Chuah, Fall 2004

company network
4

Page 2

Internet Architecture
International lines

NAP

national network ISP company LANs

regional network

on-line services ISP

university company

access via modem

Chuah, Fall 2004

Internet Structure: Network of Networks

ISP Backbone ISP

Roughly hierarchical Internet backbone (core)

Regional ISPs (Tier-2, Tier-3) Access networks at the edge

- Tier-1 ISPs (e.g., AT&T, Sprint, UUNet, BBN/Genuity) providing national/international coverage

- Residential, enterprise, campus network, small local ISPs

Chuah, Fall 2004

Page 3

NAPs, NSPs, ISPs

NSP: National Service Provider (Tier 1 Backbones) NAP: National Access Point
Example: Internet MCI, Sprint Link, UUNET

National Provider
POP

NAP NAP NAP

NAP
National Provider

Regional Provider

customers

Chuah, Fall 2004

Internet Network
Private Peering
Pacific Bell Exchange Point

Leveraging Sprints SONET-based, gigabit switch Internet backbone

Ameritech Exchange Point

Private Peering Private Peering

Sprint Exchange Point

MAE-West Exchange Point

Private Peering Private Peering Private Peering Private Peering Private Peering 8

MAE-East Exchange Point

Chuah, Fall 2004

Page 4

Sprint Network
Seattle Tacoma

Legend

DS3 OC3 OC12 OC48

Click here for a closer look at the Sprint network on the East Coast

Click here for a closer look at the Sprint network in Washington state

Stockton San Jose

Cheyenne

Chicago Roachdale

New York Pennsauken Relay Wash. DC

Kansas City

Click here for a closer look at the Sprint network in Northern California

Anaheim Atlanta Pearl City in Hawaii is a future network location Fort Worth Orlando

Chuah, Fall 2004

Chuah, Fall 2004

10

Page 5

Chuah, Fall 2004

11

Links for Long Haul Transmission

Types of links

- DS1/T1: 1.544 Mbps (24x 64Kbps) - DS3/T3: 44.736 Mbps - STS-1/OC-1: 51.84 Mbps

Possibilities
- IP over SONET - IP over ATM - IP over Frame Relay - IP over WDM

STS-3/OC-3: 155.2 Mbps STS-12/OC-12: 622.080 Mbps STS-48/OC-48: 2.488 Gbps STS-192/OC-192: 9.953 Gbps

Higher levels of services offered commercially

- Frame Relay - ATM

Chuah, Fall 2004

12

Page 6

How do we study this cloud of network?

How was it designed? Why is the Internet the way it is today? Can we reduce its complexity to something tractable?

Chuah, Fall 2004

13

Layered Architecture

Layering simplifies the architecture of complex system Layer N relies on services from layer N-1 to provide a service to layer N+1 Interfaces define the services offered Service required from a lower layer is independent of its implementation
- Information/complexity hiding - Layer N change doesnt affect other layers - Similar to object oriented methodology

Chuah, Fall 2004

14

Page 7

Protocols

Protocol: rules by which network elements communicate Protocols define the agreement between peering entities
- The format and the meaning of messages exchanged

Protocols in everyday life

- Examples: traffic control, open round-table discussion etc

Chuah, Fall 2004

15

Protocols and Services

Protocols are used to implement services

- Peering entities in layer N provide service by communicating with each other using the service provided by layer N-1

Logical vs physical communication

Chuah, Fall 2004

16

Page 8

ISO OSI Reference Model

ISO International Standard Organization OSI Open System Interconnection Started to 1978; first standard 1979
- ARPANET started in 1969; TCP/IP protocols ready by 1974

Goal: a general open standard

- Allow vendors to enter the market by using their own implementation and protocols

Chuah, Fall 2004

17

OSI Reference Model

Application Presentation Session Transport Network Datalink Physical

OSI: conceptually define service, interface, & protocol Service says what a layer does Interface says how to access the service Protocol says how is the service implemented
- A set of rules and formats that govern the communication between two peers

OSI Protocol Stack

Chuah, Fall 2004

18

Page 9

ISO OSI Reference Model

Seven layers
- Lower three layers are peer-to-peer - Next four layers are end-to-end
Layer-to -layer communication

Application Presentation Session Transport Network Datalink Physical

Peer-layer communication

Application Presentation Session Transport Network Datalink Physical

Network Datalink Physical Physical medium

Chuah, Fall 2004

19

Data Transmission

A layer can use only the service provided by the layer immediate below it Each layer may change and add a header to data packet
data data data data data data data data data data data data data data

Chuah, Fall 2004

20

Page 10

Protocol Packets

Protocol data units (PDUs): packets exchanged between peer entities Service data units (SDUs): packets handed to a layer by an upper layer Data at one layer is encapsulated in packet at a lower layer
- Envelope within envelope: PDU = SDU + (optional) header or trailer

Chuah, Fall 2004

21

Implementation of Layers

Chuah, Fall 2004

22

Page 11

Physical Layer (1)

Service: transmitting raw bits (0/1) over wire/physical link between two systems Interface: specifies how to send a bit Protocol: coding scheme used to represent a bit, voltage levels, duration of a bit Examples: coaxial cable, optical fiber links; transmitters, receivers
0 0 1 0 1 1 1 1 0 1 0 0 0 0 0 1

Bits

+V
NRZ
Chuah, Fall 2004

-V
23

Datalink Layer (2)

Service:

- Framing, i.e., attach frames separator - Send data frames between peers attached to the same physical media - Others (optional): Arbitrate the access to common physical media Ensure reliable transmission Provide flow control

Interface: send a data unit (packet) to a machine connected to the same physical media Protocol: layer addresses, implement Medium Access Control (MAC) (e.g., CSMA/CD) Example: Ethernet, PPP
24

Chuah, Fall 2004

Page 12

Network Layer (3)

Service:
- Deliver a packet to specified destination Naming and addressing Routing of packets within a network Avoidance of failed links - Perform segmentation/reassemble (fragmentation/defragmentation) - Others: Packet scheduling Buffer management

Interface: send a packet to a specified destination Protocol: define global unique addresses; construct routing tables Example: IP
25

Chuah, Fall 2004

Transport Layer (4)

Service:
- Provide an error -free and flow-controlled end-host to end-host connection - Multiplex multiple transport connections to one network connection - Split one transport connection in multiple network connections

Interface: send a packet to specify destination Protocol: implement reliability and flow control Examples: TCP and UDP

Chuah, Fall 2004

26

Page 13

Session Layer (5)

Service:
- Session setup (authentication) - Recovery from failure (broken session) - Full-duplex - Access management, e.g., token control - Synchronization, e.g., provide check points for long transfers

Interface: depends on service Protocols: token management; insert checkpoints

Chuah, Fall 2004

27

Presentation Layer (6)

Service: convert data between various representations to common format Interface: depends on service Protocol: define data formats, and rules to convert from one format to another Example: Little endian vs big endian byte orders
http://www.cs.umass.edu/~verts/cs32/endian.html

Chuah, Fall 2004

28

Page 14

Application Layer (7)

Service: Process-to-process communication

- any service provided to the end user - all layers exist to support this layer

Interface: depends on the application Protocol: depends on the application Examples: FTP, Telnet, HTTP

Chuah, Fall 2004

29

Why layering?
Key technique to implement complex systems & communication protocols

Abstraction
- Explicit structure allows identification, relationship of different pieces

- Layered reference model for discussion

Modularity -> eases maintenance, updating of system - Change of implementation of layers service transparent to rest of system - e.g., change in gate procedure doesnt affect rest of system Resuse
- Software/code, system component, protocol

Chuah, Fall 2004

30

Page 15

Design Challenges

How do you divide functionality across each layer?

- Which layer should implement what functionality?

Hop-by-hop basis or end-to-end basis Duplication of functionality between layers

- Error recovery at link layer and transport layer

Chuah, Fall 2004

31

Data and Control Planes

Another way of looking at things..

Data plane: concerned with

- Packet forwarding - Buffer management - Packet scheduling

Control Plane: concerned with installing and maintaining state for data plane

Chuah, Fall 2004

32

Page 16

Example: Routing

Data plane: use Forwarding Table to forward packets Control plane: construct and maintain Forwarding Tables (e.g., Distance Vector, Link State protocols)
Fwd table H2 R4 R1 R3 R2 R5
33

Fwd table H2 R6 H2 R4 R6

H1

Chuah, Fall 2004

OSI vs. TCP/IP

OSI: conceptually define: service, interface, protocol Internet: provide a successful implementation

Application Presentation Session Transport Network Datalink Physical

Application
host-host data transfer

Telnet FTP HTTP

TCP IP LAN

UDP

Transport Network Link Physical

bits on wire

routing datagrams src->dest

Packet radio

data transfer btw neighboring network elements (Ethernet, PPP)

34

Chuah, Fall 2004

Page 17

Internet Protocol Zoo

RealAudio RealVideo NFS/Sun RPC DNS

applicatio n

SMTP

HTTP

Telnet FTP

Chuah, Fall 2004

35

Internet Architecture

Packet-switched datagram network IP Hour-glass Architecture

- All hosts and routers run IP - IP is the glue - Common intermediate representation

TCP

UDP

IP Satellite Ethernet ATM IP Hour-glass

Chuah, Fall 2004

36

Page 18

The Internet Network layer

Transport layer: TCP, UDP

Routing protocols Path selection RIP, OSPF, BGP IP protocol Addressing conventions Packet handling conventions

Network layer

routing table

ICMP protocol Error reporting Router signaling

Link layer physical layer

Chuah, Fall 2004

37

Internet Protocol (IP)

Universal service in a heterogeneous world

- IP over everything

Virtual overlay network Globally unique logical address for a host Address resolution
- logical to physical address mapping

Chuah, Fall 2004

38

Page 19

Internet Protocol

Connectionless unreliable datagram service Packets carry a source and a destination address Each packet routed independently No guarantee that network will not lose packets
Error recovery is up to end-to-end protocols

Chuah, Fall 2004

39

Transport between Neighbors

Using underlying link layer transmission mechanism

- Example: Ethernet, Token Ring, PPP

Mapping from logical IP address to physical MAC address

- Address Resolution Protocol (ARP)

Chuah, Fall 2004

40

Page 20

End to End Transport Protocols TCP service:

UDP service:

Connection-oriented: setup required between client, server Reliable transport between sender and receiver Flow control: sender wont overwhelm receiver Congestion control: throttle sender when network overloaded

Unreliable data transfer between sender and receiver Does not provide: connection setup, reliability, flow control, congestion control

Q:Why UDP?

Chuah, Fall 2004

41

World-Wide Web
Hypertext transfer protocol

Webs application layer protocol Client/server model - client: browser that requests, receives, displays Web objects - server: Web server sends objects in response to requests

PC running Explorer

htt p re que st htt p re spo nse

t ues req e p t ons ht esp r p htt

Server running NCSA Web server

Mac running Navigator

Chuah, Fall 2004

42

Page 21

HTTP Protocol
Uses TCP transport service:

Client initiates TCP connection (creates socket) to server, port 80 Server accepts TCP connection from client Http messages (application-layer protocol messages) exchanged between browser (http client) and Web server (http server) TCP connection closed

Chuah, Fall 2004

43

Summary

Computer networks use packet switching Fundamental issues in networking

- Addressing/Naming and routing/forwarding - Error/Flow/Congestion control

Layered architecture for maintainability Internet is based on TCP/IP protocol suite

Chuah, Fall 2004

44

Page 22

Proof-of-Concept

With layered architecture, it doesnt matter how you implement the layer, as long as it provides the service follows the protocol as specified! The Bongo Project: http://eagle.auc.ca/~dreid/

Chuah, Fall 2004

45

Links for Long Haul Transmission

Types of links

- DS1/T1: 1.544 Mbps (24x 64Kbps) - DS3/T3: 44.736 Mbps - STS-1/OC-1: 51.84 Mbps

Possibilities
- IP over SONET - IP over ATM - IP over Frame Relay - IP over WDM

STS-3/OC-3: 155.2 Mbps STS-12/OC-12: 622.080 Mbps STS-48/OC-48: 2.488 Gbps STS-192/OC-192: 9.953 Gbps

Higher levels of services offered commercially

- Frame Relay - ATM

Chuah, Fall 2004

46

Page 23