1. CS 1652 Jack Lange University of Pittsburgh
The slides are adapted from the publisher’s material
All material copyright
J.F Kurose and K.W. Ross, All Rights Reserved

2. The Internet network layer
host, router network layer functions:
transport layer: TCP, UDP
IP protocol
addressing conventions
datagram format
packet handling conventions
routing protocols
path selection
RIP, OSPF, BGP
network
layer
forwarding
table
ICMP protocol
error reporting
router “signaling”
link layer
physical layer
Network Layer: Data Plane

3. 32 bit destination IP address
IP datagram format
IP protocol version
number
ver
length
32 bits
data
(variable length,
typically a TCP
or UDP segment)
16-bit identifier
header
checksum
time to
live
32 bit source IP address
head.
len
type of
service
flgs
fragment
offset
upper
layer
32 bit destination IP address
options (if any)
total datagram
length (bytes)
header length
(bytes)
“type” of data
for
fragmentation/
reassembly
max number
remaining hops
(decremented at
each router)
upper layer protocol
to deliver payload to
e.g. timestamp,
record route
taken, specify
list of routers
to visit.
how much overhead?
20 bytes of TCP
20 bytes of IP
= 40 bytes + app layer overhead
Network Layer: Data Plane

4. IP fragmentation, reassembly
network links have MTU (max.transfer size) - largest possible link-level frame
different link types, different MTUs
large IP datagram divided (“fragmented”) within net
one datagram becomes several datagrams
“reassembled” only at final destination
IP header bits used to identify, order related fragments …
fragmentation:
in: one large datagram
out: 3 smaller datagrams
reassembly …
Network Layer: Data Plane

5. IP fragmentation, reassemblyID =x
offset =0
fragflag
length
=4000
example:
4000 byte datagram
MTU = 1500 bytes ID =x
offset =0
fragflag =1
length
=1500
=185
=370
=1040
one large datagram becomes
several smaller datagrams
1480 bytes in data field
offset =
1480/8
Network Layer: Data Plane

6. IPv4 Addressing

7. IP addressing: introduction
IP address: 32-bit identifier for host, router interface
interface: connection between host/router and physical link
router’s typically have multiple interfaces
host typically has one or two interfaces (e.g., wired Ethernet, wireless )
IP addresses associated with each interface =
223 1 1 1
Network Layer: Data Plane

8. Subnets IP address: what’s a subnet ? subnet part - high order bits
host part - low order bits
what’s a subnet ?
device interfaces with same subnet part of IP address
can physically reach each other without intervening router
subnet
network consisting of 3 subnets
Network Layer: Data Plane

9. Subnets
how many?
Network Layer: Data Plane

10. IP addressing: CIDR CIDR: Classless InterDomain Routing
subnet portion of address of arbitrary length
address format: a.b.c.d/x, where x is # bits in subnet portion of address
subnet
part
host
part
/23
Network Layer: Data Plane

11. IP addresses: how to get one?
Q: how does network get subnet part of IP addr? A: gets allocated portion of its provider ISP’s address space
ISP's block /20
Organization /23
Organization /23
Organization /23
… … ….
Organization /23
Network Layer: Data Plane

12. Hierarchical addressing: route aggregation
hierarchical addressing allows efficient advertisement of routing
information:
Organization 0
/23
Organization 1
“Send me anything
with addresses
beginning
/20”
/23
Organization 2
/23 .
Fly-By-Night-ISP .
Internet
Organization 7
/23
“Send me anything
with addresses
beginning
/16”
ISPs-R-Us
Network Layer: Data Plane

13. Hierarchical addressing: more specific routes
ISPs-R-Us has a more specific route to Organization 1
Organization 0
/23
“Send me anything
with addresses
beginning
/20”
Organization 2
/23 .
Fly-By-Night-ISP .
Internet
Organization 7
/23
“Send me anything
with addresses
beginning /16
or /23”
ISPs-R-Us
Organization 1
/23
Network Layer: Data Plane

14. IP addressing: the last word...
Q: how does an ISP get block of addresses?
A: ICANN: Internet Corporation for Assigned
Names and Numbers
allocates addresses
manages DNS
assigns domain names, resolves disputes
Network Layer: Data Plane

15. IP addresses: how to get one?
Q: How does a host get IP address?
hard-coded by system admin
Provided by network admin
DHCP: Dynamic Host Configuration Protocol: dynamically get address from as server
“plug-and-play”
Network Layer

16. DHCP: Dynamic Host Configuration Protocol
goal: allow host to dynamically obtain its IP address from network server when it joins network
can renew its lease on address in use
allows reuse of addresses (only hold address while connected/“on”)
support for mobile users who want to join network (more shortly)
DHCP overview:
host broadcasts “DHCP discover” msg [optional]
DHCP server responds with “DHCP offer” msg [optional]
host requests IP address: “DHCP request” msg
DHCP server sends address: “DHCP ack” msg
Network Layer: Data Plane

17. DHCP client-server scenario
/24
arriving DHCP
client needs
address in this
network
/24
/24
Network Layer: Data Plane

18. DHCP client-server scenario
DHCP server:
DHCP discover
src : , 68
dest.: ,67
yiaddr:
transaction ID: 654
arriving
client
Broadcast: is there a DHCP server out there?
DHCP offer
src: , 67
dest: , 68
yiaddrr:
transaction ID: 654
lifetime: 3600 secs
Broadcast: I’m a DHCP server! Here’s an IP address you can use
DHCP request
src: , 68
dest:: , 67
yiaddrr:
transaction ID: 655
lifetime: 3600 secs
Broadcast: OK. I’ll take that IP address!
DHCP ACK
src: , 67
dest: , 68
yiaddrr:
transaction ID: 655
lifetime: 3600 secs
Broadcast: OK. You’ve got that IP address!
Network Layer: Data Plane

19. DHCP client-server scenario
DHCP server:
arriving
client
DHCP discover
src : , 68
dest.: ,67
yiaddr:
transaction ID: 654
DHCP offer
src: , 67
dest: , 68
yiaddrr:
transaction ID: 654
Lifetime: 3600 secs
DHCP request
src: , 68
dest:: , 67
yiaddrr:
transaction ID: 655
Lifetime: 3600 secs
time
DHCP ACK
src: , 67
dest: , 68
yiaddrr:
transaction ID: 655
Lifetime: 3600 secs
Network Layer

20. NAT: network address translation
rest of
Internet
local network
(e.g., home network)
10.0.0/24
all datagrams leaving local
network have same single source NAT IP address: ,different source port numbers
datagrams with source or
destination in this network
have /24 address for
source, destination (as usual)
Network Layer: Data Plane

21. NAT: Network Address Translation
Motivation: local network uses just one IP address as far as outside world is concerned:
range of addresses not needed from ISP: just one IP address for all devices
can change addresses of devices in local network without notifying outside world
can change ISP without changing addresses of devices in local network
devices inside local net not explicitly addressable, visible by outside world (a security plus).
Network Layer

22. NAT: Network Address Translation
Implementation: NAT router must:
outgoing datagrams: replace (source IP address, port #) of every outgoing datagram to (NAT IP address, new port #)
. . . remote clients/servers will respond using (NAT IP address, new port #) as destination addr.
remember (in NAT translation table) every (source IP address, port #) to (NAT IP address, new port #) translation pair
incoming datagrams: replace (NAT IP address, new port #) in dest fields of every incoming datagram with corresponding (source IP address, port #) stored in NAT table
Network Layer

23. NAT: network address translation
NAT translation table
WAN side addr LAN side addr
1: host
sends datagram to
, 80
2: NAT router
changes datagram
source addr from
, 3345 to
, 5001,
updates table
, , 3345
…… ……
S: , 3345
D: , 80 1
S: , 80
D: , 3345 4
S: , 5001
D: , 80 2
S: , 80
D: , 5001 3
4: NAT router
changes datagram
dest addr from
, 5001 to , 3345
3: reply arrives
dest. address:
, 5001
* Check out the online interactive exercises for more examples:
Network Layer: Data Plane

24. NAT: Network Address Translation
16-bit port-number field:
60,000 simultaneous connections with a single LAN-side address!
NAT is controversial:
routers should only process up to layer 3
violates end-to-end argument
NAT possibility must be taken into account by app designers, eg, P2P applications
address shortage should instead be solved by IPv6
Incoming connection not possible
NAT traversal (static binding, UPnP, relaying - Skype)
Network Layer

25. ICMP

26. ICMP: Internet Control Message Protocol
Used by hosts & routers to communicate network-level information
error reporting: unreachable host, network, port, protocol
echo request/reply (used by ping)
Network-layer “above” IP:
ICMP msgs carried in IP datagrams
ICMP message: type, code plus first 8 bytes of IP datagram causing error
Type Code description
echo reply (ping)
dest network unreachable
dest host unreachable
dest protocol unreachable
dest port unreachable
dest network unknown
dest host unknown
source quench (congestion
control - not used)
echo request (ping)
route advertisement
router discovery
TTL expired
bad IP header
Network Layer

27. Traceroute and ICMP Source sends series of UDP segments to dest
First has TTL =1
Second has TTL=2, etc.
Unlikely port number
When nth datagram arrives to nth router:
Router discards datagram
And sends to source an ICMP message (type 11, code 0)
Message includes name of router& IP address
When ICMP message arrives, source calculates RTT
Traceroute does this 3 times
Stopping criterion
UDP segment eventually arrives at destination host
Destination returns ICMP “host unreachable” packet (type 3, code 3)
When source gets this ICMP, stops.
Network Layer

28. IPv6

29. IPv6: motivation
initial motivation: 32-bit address space soon to be completely allocated.
additional motivation:
header format helps speed processing/forwarding
header changes to facilitate QoS
IPv6 datagram format:
fixed-length 40 byte header
no fragmentation allowed
Network Layer: Data Plane

30. IPv6 datagram format
priority: identify priority among datagrams in flow
flow Label: identify datagrams in same “flow.”
(concept of“flow” not well defined).
next header: identify upper layer protocol for data
ver
pri
flow label
payload len
next hdr
hop limit
source address
(128 bits)
destination address
(128 bits)
data
32 bits
Network Layer: Data Plane

31. Other changes from IPv4
checksum: removed entirely to reduce processing time at each hop
options: allowed, but outside of header, indicated by “Next Header” field
ICMPv6: new version of ICMP
additional message types, e.g. “Packet Too Big”
multicast group management functions
Network Layer: Data Plane

32. Transition from IPv4 to IPv6
not all routers can be upgraded simultaneously
no “flag days”
how will network operate with mixed IPv4 and IPv6 routers?
tunneling: IPv6 datagram carried as payload in IPv4 datagram among IPv4 routers
IPv4 header fields
UDP/TCP payload
IPv6 source dest addr
IPv6 header fields
IPv4 payload
IPv4 source, dest addr
IPv6 datagram
IPv4 datagram
Network Layer: Data Plane

33. connecting IPv6 routers
Tunneling
logical view:
IPv4 tunnel
connecting IPv6 routers E
IPv6 F A B A B
IPv6 C D E
IPv6 F
physical view:
IPv4
IPv4
Network Layer: Data Plane

34. connecting IPv6 routers
Tunneling
logical view:
IPv4 tunnel
connecting IPv6 routers E
IPv6 F A B A B
IPv6 C D E
IPv6 F
physical view:
IPv4
IPv4
flow: X
src: A
dest: F
data
A-to-B:
IPv6
Flow: X
Src: A
Dest: F
data
src:B
dest: E
B-to-C:
IPv6 inside
IPv4
B-to-C:
IPv6 inside
IPv4
Flow: X
Src: A
Dest: F
data
src:B
dest: E
E-to-F:
IPv6
flow: X
src: A
dest: F
data
Network Layer: Data Plane

35. IPv6: adoption Google: 8% of clients access services via IPv6
NIST: 1/3 of all US government domains are IPv6 capable
Long (long!) time for deployment, use
20 years and counting!
think of application-level changes in last 20 years: WWW, Facebook, streaming media, Skype, …
Why?
Network Layer: Data Plane