Network layer
❒
❒
❒
Network Layer Overview and IP
Network Layer
❒
on rcving side, delivers
segments to transport layer
network
data link
physical
network
data link
physical
network
data link
physical
network layer protocols in every
host, router
❒ Router examines header fields
in all IP datagrams passing
through it
network
data link
physical
network
data link
physical
network
data link
physical
network
data link
physical
network
data link
physical
4-1
application
transport
network
data link
physical
Network Layer
4-2
Interplay between routing and forwarding
routing algorithm
forwarding: move packets from router’s
input to appropriate router output
local forwarding table
header value output link
0100
0101
0111
1001
routing: determine route taken by packets
from source to dest.
❍
application
transport
network
data link
physical
on sending side encapsulates
segments into datagrams
❒
Key Network-Layer Functions
❒
transport segment from sending
to receiving host
3
2
2
1
value in arriving
packet’s header
Routing algorithms
0111
1
3 2
Network Layer
4-3
Network service model
Network Layer
4-4
Virtual circuits
“source-to-dest path behaves much like telephone circuit”
Example services for individual datagrams:
❒ guaranteed delivery
❍
performance-wise
❍
network actions along source-to-dest path
❒ Guaranteed delivery with less than 40
msec delay
❒ call setup, teardown for each call before data can flow
Example services for a flow of datagrams:
❒ each packet carries VC identifier (not destination host
❒ In-order datagram delivery
❒ every router on source-dest path maintains “state” for
address)
each passing connection
❒ Guaranteed minimum bandwidth to flow
❒ link, router resources (bandwidth, buffers) may be
❒ Restrictions on changes in inter-packet
spacing
Network Layer
allocated to VC
4-5
Network Layer
4-6
1
Datagram networks
Forwarding table
❒
no call setup at network layer
❒
routers: no state about end-to-end connections
❒
packets forwarded using destination host address
❒
Why is this OK for the Internet?
❍
❍
no network-level concept of “connection”
Destination Address Range
packets between same source-dest pair may take different paths
application
transport
network
data link
physical
4 billion
possible entries
application
transport
2. Receive data network
data link
physical
1. Send data
Link Interface
11001000 00010111 00010000 00000000
through
11001000 00010111 00010111 11111111
0
11001000 00010111 00011000 00000000
through
11001000 00010111 00011000 11111111
1
11001000 00010111 00011001 00000000
through
11001000 00010111 00011111 11111111
2
otherwise
Network Layer
3
4-7
Network Layer
Longest prefix matching
Datagram or VC network: why?
Internet
Prefix Match
11001000 00010111 00010
11001000 00010111 00011000
11001000 00010111 00011
otherwise
Link Interface
0
1
2
3
❒
❒
Which interface?
❍
❒
Which interface?
Network Layer
❒
evolved from telephony
❒
human conversation:
❍
can adapt, perform control,
error recovery
simple inside network,
complexity at “edge”
❍
❒
many link types
❍
different characteristics
❍
uniform service difficult
strict timing, reliability
requirements
need for guaranteed
service
“dumb” end systems
❍
telephones
❍
complexity inside network
Network Layer 4-10
IP datagram format
IP protocol version
number
header length
(bytes)
“type” of data
Host, router network layer functions:
Transport layer: TCP, UDP
max number
remaining hops
(decremented at
each router)
upper layer protocol
to deliver payload to
IP protocol
•addressing conventions
•datagram format
•packet handling conventions
forwarding
table
ATM
4-9
The Internet Network layer
Routing protocols
•path selection
•RIP, OSPF, BGP
“elastic” service, no strict
timing req.
“smart” end systems
(computers)
❍
DA: 11001000 00010111 00011000 10101010
Network
layer
data exchange among computers
❍
Examples
DA: 11001000 00010111 00010110 10100001
4-8
ICMP protocol
•error reporting
•router “signaling”
how much overhead
with TCP?
Link layer
physical layer
❒
20 bytes of TCP
❒
20 bytes of IP
❒
Network Layer
4-11
= 40 bytes + app
layer overhead
32 bits
ver head. type of
length
len service
fragment
16-bit identifier flgs
offset
time to upper
Internet
layer
live
checksum
32 bit source IP address
total datagram
length (bytes)
for
fragmentation/
reassembly
32 bit destination IP address
Options (if any)
data
(variable length,
typically a TCP
or UDP segment)
E.g. timestamp,
record route
taken, specify
list of routers
to visit.
Network Layer 4-12
2
IP Fragmentation & Reassembly
❒
network links have MTU
(max.transfer size) - largest
possible link-level frame.
❍
❒
fragmentation:
in: one large datagram
out: 3 smaller datagrams
different link types,
different MTUs
❍
❍
one datagram becomes
several datagrams
length ID fragflag offset
=4000 =x
=0
=0
Example
large IP datagram divided
(“fragmented”) within net
❍
IP Fragmentation and Reassembly
❒ 4000 byte
One large datagram becomes
several smaller datagrams
datagram
❒ MTU = 1500 bytes
length ID fragflag offset
=1500 =x
=1
=0
1480 bytes in
data field
reassembly
“reassembled” only at
final destination
length ID fragflag offset
=1500 =x
=1
=185
offset =
1480/8
IP header bits used to
identify, order related
fragments
length ID fragflag offset
=1040 =x
=0
=370
Network Layer 4-13
Subnets
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
223.1.1.1
❒
223.1.1.2
223.1.1.4
223.1.1.3
223.1.2.1
To determine the
subnets, detach each
interface from its
host or router,
creating islands of
isolated networks.
Each isolated network
is called a subnet.
❍
❒
223.1.3.2
223.1.3.1
223.1.1.0/24
223.1.2.0/24
subnet part (high
order bits)
223.1.1.2
223.1.1.4
host part (low order
bits)
223.1.1.3
223.1.2.1
223.1.2.9
223.1.3.27
What’s a subnet ?
❍
❍
223.1.2.2
LAN
device interfaces with
same subnet part of
IP address
223.1.3.2
223.1.3.1
can physically reach
each other without
intervening router
network consisting of 3 subnets
Network Layer 4-16
Subnets
223.1.1.2
How many?
Recipe
❒
❍
223.1.2.2
223.1.3.27
223.1.1.1
IP address:
223.1.2.9
host may have multiple
interfaces
223.1.1.1 = 11011111 00000001 00000001 00000001
IP addresses
223
1
1
1
associated with each
interface
Network Layer 4-15
Subnets
Network Layer 4-14
223.1.1.1
223.1.1.4
223.1.1.3
223.1.9.2
223.1.7.0
223.1.9.1
223.1.7.1
223.1.8.1
223.1.3.0/24
Subnet mask: /24
Network Layer 4-17
223.1.8.0
223.1.2.6
223.1.2.1
223.1.3.27
223.1.2.2
223.1.3.1
223.1.3.2
Network Layer 4-18
3
Classful Addressing
IP addressing: CIDR
CIDR: Classless InterDomain Routing
class
❍
A
0 network
B
10
C
110
D
1110
1.0.0.0 to
127.255.255.255
host
network
host
network
host
128.0.0.0 to
191.255.255.255
192.0.0.0 to
223.255.255.255
❍
subnet portion of address of arbitrary length
address format: a.b.c.d/x, where x is # bits in
subnet portion of address
224.0.0.0 to
239.255.255.255
multicast address
32 bits
host
part
subnet
part
11001000 00010111 00010000 00000000
200.23.16.0/23
Network Layer 4-19
Network Layer 4-20
IP addresses: how to get one?
IP addresses: how to get one?
Q: How does host get IP address?
Q: How does network get subnet part of IP
addr?
❒
❍
❒
A: gets allocated portion of its provider ISP’s
address space
hard-coded by system admin in a file
/etc/hosts
DHCP: Dynamic Host Configuration Protocol:
dynamically get address from as server
❍
“plug-and-play”
(more in next chapter)
ISP's block
11001000 00010111 00010000 00000000
200.23.16.0/20
Organization 0
Organization 1
Organization 2
...
Organization 7
11001000 00010111 00010000 00000000
11001000 00010111 00010010 00000000
11001000 00010111 00010100 00000000
…..
….
11001000 00010111 00011110 00000000
200.23.16.0/23
200.23.18.0/23
200.23.20.0/23
….
200.23.30.0/23
Network Layer 4-21
Hierarchical addressing: route aggregation
Hierarchical addressing allows efficient advertisement of routing
information:
Network Layer 4-22
Hierarchical addressing: more specific
routes
ISPs-R-Us has a more specific route to Organization 1
Organization 0
Organization 0
200.23.16.0/23
200.23.16.0/23
Organization 1
200.23.18.0/23
Organization 2
200.23.20.0/23
Organization 7
.
.
.
.
..
Fly-By-Night-ISP
“Send me anything
with addresses
beginning
200.23.16.0/20”
Organization 2
200.23.20.0/23
Internet
200.23.30.0/23
ISPs-R-Us
“Send me anything
with addresses
beginning
199.31.0.0/16”
Network Layer 4-23
Organization 7
.
..
.
.
.
Fly-By-Night-ISP
“Send me anything
with addresses
beginning
200.23.16.0/20”
Internet
200.23.30.0/23
ISPs-R-Us
Organization 1
200.23.18.0/23
“Send me anything
with addresses
beginning 199.31.0.0/16
or 200.23.18.0/23”
Longest prefix match!
Network Layer 4-24
4
NAT: Network Address Translation
IP addressing: the last word...
Q: How does an ISP get block of addresses?
rest of
Internet
A: ICANN: Internet Corporation for Assigned
local network
(e.g., home network)
10.0.0/24
10.0.0.1
10.0.0.4
Names and Numbers
❍
allocates addresses
❍
manages DNS
❍
assigns domain names, resolves disputes
10.0.0.2
138.76.29.7
10.0.0.3
All datagrams leaving local
network have same single source
NAT IP address: 138.76.29.7,
different source port numbers
Datagrams with source or
destination in this network
have 10.0.0/24 address for
source, destination (as usual)
Network Layer 4-25
NAT: Network Address Translation
Network Layer 4-26
NAT: Network Address Translation
Implementation: NAT router must:
❒
Motivation: local network uses just one IP address as
far as outside word is concerned:
❍
❍
❍
❍
❍
no need to be allocated range of addresses from
ISP: - just one IP address is used 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
❍
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
devices inside local net not explicitly addressable,
visible by outside world (a security plus).
Network Layer 4-27
NAT: Network Address Translation
2: NAT router
changes datagram
source addr from
10.0.0.1, 3345 to
138.76.29.7, 5001,
updates table
2
NAT translation table
WAN side addr
LAN side addr
138.76.29.7, 5001 10.0.0.1, 3345
……
……
S: 138.76.29.7, 5001
D: 128.119.40.186, 80
138.76.29.7
S: 128.119.40.186, 80
D: 138.76.29.7, 5001
3: Reply arrives
dest. address:
138.76.29.7, 5001
3
1
10.0.0.4
S: 128.119.40.186, 80
D: 10.0.0.1, 3345
NAT: Network Address Translation
1: host 10.0.0.1
sends datagram to
128.119.40, 80
S: 10.0.0.1, 3345
D: 128.119.40.186, 80
Network Layer 4-28
10.0.0.1
10.0.0.2
4
10.0.0.3
4: NAT router
changes datagram
dest addr from
138.76.29.7, 5001 to 10.0.0.1, 3345
Network Layer 4-29
❒ 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
Network Layer 4-30
5
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
0
3
3
3
3
3
3
4
Code
0
0
1
2
3
6
7
0
8
9
10
11
12
0
0
0
0
0
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
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
Network Layer 4-31
❒ 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 4-32
IPv6 Header (Cont)
IPv6
❒ Initial motivation: 32-bit address space soon
to be completely allocated.
❒ Additional motivation:
❍
header format helps speed processing/forwarding
❍
header changes to facilitate QoS
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
IPv6 datagram format:
❍
fixed-length 40 byte header
❍
no fragmentation allowed
Network Layer 4-33
Other Changes from IPv4
❒
❒
❒
Network Layer 4-34
Transition From IPv4 To IPv6
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 4-35
❒ Not all routers can be upgraded simultaneous
❍
❍
no “flag days”
How will the network operate with mixed IPv4 and
IPv6 routers?
❒ Dual-stack
❒
Tunneling: IPv6 carried as payload in IPv4
datagram among IPv4 routers
Network Layer 4-36
6
Tunneling
Logical view:
Physical view:
A
B
IPv6
IPv6
A
B
IPv6
Flow: X
Src: A
Dest: F
data
IPv6
C
D
IPv4
IPv4
Src:B
Dest: E
Flow: X
Src: A
Dest: F
data
A-to-B:
IPv6
E
F
IPv6
IPv6
E
F
tunnel
B-to-C:
IPv6 inside
IPv4
IPv6
Src:B
Dest: E
Flow: X
Src: A
Dest: F
IPv6
Flow: X
Src: A
Dest: F
data
data
B-to-C:
IPv6 inside
IPv4
E-to-F:
IPv6
Network Layer 4-37
7