Important Information

Slide content, tables and diagrams are drawn from the

3rd (2006) and 4th (2010) editions of TCP/IP Protocol
Suite by Behrouz A. Forouzan /& publisher’s (McGraw
Hill) supporting materials.
Use and Reproduction of these slides is not permitted
without the permission of the CQUniversity
COIT20261 course coordinator.
 Week 9
IPv6 Addressing (Chapter 26)
IPv6 Protocol (Chapter 27)
Routing in IPv6 (online material)
ICMPv6 (Chapter 28)

Jan-19 2
 Chapter 26

Jan-19 3
Objectives
 Understand the shortcomings of IPv4
 Know the IPv6 address format, address types, and
abbreviations

Jan-19 4
IPv6
 IPv6 has these advantages over IPv4:
 larger address space
 better header format
 new options
 allowance for extension
 support for resource allocation
 support for more security

Jan-19 5
 IPv6 Addresses
 IPv6 addresses are 4 times as large as IPv4
 16 bytes compared to 4 bytes
 Default representation is now hexadecimal colon notation –
32 hexadecimal numbers
 16 bit (2 byte/octet) colon sections instead of 8 bit dotted
decimal notation
 Sections within the address are of variable length but all
will be divisible by 4 bits (one hex number)

Jan-19 6
 Abbreviated Address
 Leading zeros in each colon segment are important but can
be left out for a shorter address and assumed if the number
is not 4 hex long

Jan-19 7
 Abbreviated Address with
Consecutive Zeros
 A further abbreviation is to leave out a run of zeros and
signify this by a double colon.
 Only one run of zeros can be abbreviated this way so that
the address can be reconstructed without additional
information

Jan-19 8
 CIDR Address
 IPv6 allows classless addressing in the same
notation as IPv4

Jan-19 9
 Address Structure
 There are 3 categories of addresses
 Unicast – defines a single node
 Anycast – a group of computers with the same prefix
(similar to broadcasting)
 Multicast – a number of nodes that are members of a
certain group

Jan-19 10
 Address Space Allocation

Jan-19 11
Type Prefixes for IPv6 Addresses

Jan-19 12
 Unspecified Address
 Used when a node does not know its address –
fills address space with all zeros

Jan-19 13
 Loopback Address
 A more efficient loopback address – only taking
up one address space – replaces 127.0.0.0

Jan-19 14
 Embedded IPv4:
Compatible Addresses
 Used when a node using IPv6 wants to send to a IPv6 node
but the packet will pass through a IPv4 network.
 It must embed the IPv4 address in an IPv6 space so that the
router on the IPv4 network can extract the address for the
best route

Jan-19 15
 Embedded IPv4:
Mapped Address
 Used when a node using IPv6 wants to send to an IPv4 node
mostly over IPv6 networks.
 The sender is using IPv6, to signify this, it sends a mapped
address so the receiver knows how it has to send back

Jan-19 16
 Unique Local Unicast Address
 Like IPv4 Private address space
 IPv6 uses two large blocks – one at site and one at
link level
 Block defined by random number
 Not routed externally

Jan-19 17
 Link Local Block
 Self configuring self assigned
 Note discussion on page 781 re:
autoconfiguration

Jan-19 18
 Multicast Block
 Large blocks of addresses are assigned for
multicast
 Assigned as permanent or transient

Jan-19 19
Global Unicast Addresses
 Used for one-to-one communication between
two hosts.
 CIDR notation for the block is 2000::/3, which
means that the three leftmost bits are the same
for all addresses in this block (001).
 The size of this block is 125 bits, which is more
than enough for the Internet expansion in the
many years to come.

Jan-19 20
 Global Unicast Address
Structure
Three levels of hierarchy
 Global Routing Prefix
 Subnet Identifier
 Interface Identifier

Jan-19 21
 Chapter 27

Jan-19 22
Objectives
 Be familiar with the IPv6 header format.
 Know the extension header types.
 Describe the methods of transition from IPv4 to IPv6.

Jan-19 23
IPv6 Datagram

Jan-19 24
Format of an IPv6 Datagram

Jan-19 25
Comparison between IPv4 and IPv6 Packet
Header

Jan-19 26
Extension Header Format

Jan-19 27
Extension Header Types

Jan-19 28
 Hop-by-hop Option Header
Format
 Added so a source can pass information to routers
its packet visits

Jan-19 29
 Source Routing
 Allows either strict or loose source routing (defined by the
mask field)

Jan-19 30
 Fragmentation
 IPv6 fragmentation is only done by the original source
 To determine the best fragment size the source can perform
Path MTU Discovery

Jan-19 31
 Authentication
 This section can validate the sender and ensure
integrity of the data

Jan-19 32
Comparison between IPv4 options and
IPv6 Extension Headers

Jan-19 33
Transition from IPv4 to IPv6
 Three strategies have been devised by the IETF to
provide for transition from IPv4 to IPv6
 Dual Stack
 Tunnelling
 Header Translation

Jan-19 34
 Dual Stack
 Version field is
the first in both
protocols so it
can be directed

Jan-19 35
 Tunnelling
 The destination is only IPv6
 So when an IPv4 network is encountered the router adds a header
to route the message through that IPv4 network only
 This new header is removed at the end boundary of that network
and is not replaced with another IPv4 header
 The packet continues its route with the original IPv6 address

IPv4 header
IPv6 header
Payload

Jan-19 36
 Header Translation
 The sender wants to use IPv6 but the destination only uses
IPv4
 So the IPv6 header is converted to an IPv4 header so that
the destination can accept the packet
 Intermediate networks are running a dual stack if they are
IPv6 already

IPv6 header IPv4 header

Payload Payload

Jan-19 37
 Online material

Jan-19 38
Objectives
 Understand the IPv6 routing table.
 Understand the route matching procedure in IPv6.
 Compare and contrast OSPFv2 and OSPFv3.

Jan-19 39
Routing table
Routing table contains the following entries:
 Destination prefix: IPv6 address prefix and the
prefix length. The prefix length can be between 0-128.
Usually, the non relevant bits are set to zero in the
routing table. The prefix length is used to determine
whether an incoming datagram matches this route.
 Next Hop address: The IPv6 address (usually, link-
local) of the first router along the path to the
destination. If the destination is directly connected,
there is no need for a Next Hop address.

Jan-19 40
Routing table (contd.)
 Interface: The local interface of the router that is used
to reach the Next Hop address.
 Metric: A number indicating the total distance to the
destination so that the best route among multiple
routes to the same destination can be selected.
Different routing protocols calculate different values
for the metric.

Jan-19 41
Routing table (contd.)
 Timer: Time elapsed since the information about the
route was last updated.
 Route Source or the protocol: This may be a static
entry, a directly connected route, or a route from a
routing protocol, such as RIPng, OSPF for IPv6, BGP,
etc.

Jan-19 42
Routing Table Entry Types
 Directly-attached Network Routes: Network
prefixes for subnets that are directly attached. Typical
prefix length 64.
 Remote Network Routes: Network prefixes for
subnets that are only available through other routers.
Remote network routes have subnet prefixes typically
with a prefix length of 64 or a prefix for an address
space typically with a prefix length less than 64.

Jan-19 43
Routing Table Entry Types
(contd.)
 Host Routes: A host route is a route to a specific IPv6
address with a prefix length of 128 (directly attached
and remote network routes have IPv6 addresses with
prefix lengths less than 128.
 Default Route: The default route is used when a more
specific network or host route is not found(similar to
IPv4). The default route prefix is ::/0.

Jan-19 44
Route matching procedure
 When a packet arrives, the destination address is extracted
and checked in the cache.
 If the destination is not in the cache, the routing table is
checked:
 1. A host route that matches the entire destination address
 2. A network route with the longest prefix length that
matches the destination
 3. The default route (the network prefix ::/0)
 The interface to be used for the forwarding and the next-
hop address are found and the packet is forwarded.

Jan-19 45
Routing Protocols in IPv6
 RIPng, OSPF for IPv6, and BGP-4
 IS-IS for IPv6 and EIGRP for IPv6
 Multicast routing protocols

Jan-19 46
RIPng (RFC 2080)
 Uses Bellman-Ford (a distance vector) algorithm.
 Similar to RIPv2.

Jan-19 47
OSPF for IPv6 (RFC 5340)
 The fundamentals are same as that of OSPF for IPv4.
 Some changes required because of the increased
address size of IPv6 and the changes in protocol
semantics.
 OSPF for IPv6 is defined in RFC 5340.
 RFC 1584 describes IPv4 multicast extensions to OSPF.
 RFC 3101 adds Not-So-Stubby Areas (NSSAs) to OSPF.
 RFC 5340 modifies OSPF to support the exchange of
routing information for IPv6.
 New version number is version 3.
Differences between OSPFv2
and OSPFv3:
 Protocol processing per-link, not per-subnet. The
terms network and subnet are replaced by the term
link.
 Removal of addressing semantics.
 Flooding scope.
 Explicit support for multiple instances per link.

Jan-19 49
Differences between OSPFv2 and
OSPFv3: (contd.)
 Use of link-local addresses.
 Authentication.
 OSPF packet format changes.
 LSA format changes.
 Handling unknown LSA types.
 Stub area support.
OSPF for IPv6 (contd.)
 Multicast addresses
 FF02::5 - Represents all shortest path first routers
on the link-local scope. This is equivalent to
224.0.0.5 in OSPFv2.
 FF02::6 - Represents all designated routers on the
link-local scope. This is equivalent to 224.0.0.6 in
OSPFv2.

Jan-19 51
BGP-4 (RFC 4271)
 No specific BGP for IPv6 has been developed.
 Uses capability of BGP-4 to have protocols other than
IPv4.
 RFC 4760 defines Multi-protocol Extensions for BGP-4
 Enables BGP to carry routing information of protocols
other than IPv4 e.g. MPLS, IPv6, Multicast etc.
 To carry IPv6, the multiprotocol NLRI (Network Layer
Reachability Information) and its next-hop
information must be added (RFC2545).

Jan-19 52
 Chapter 28

Jan-19 53
Objectives
 Compare and contrast ICMPv4 and ICMPv6.

Jan-19 54
ICMPv6
 ICMPv6, while similar in strategy to ICMPv4, has
changes that make it more suitable for IPv6.
 ICMPv6 has absorbed some protocols that were
independent in version 4.

Jan-19 55
Comparison of Network Layers in Version 4
and Version 6

Jan-19 56
Categories of ICMPv6 Messages

Jan-19 57
Error Reporting Messages

Jan-19 58
 Comparison of Error Reporting
Messages in ICMPv4 and ICMPv6
 Source quench: not needed because of priority and flow label
fields
 Note Redirection is classified as a Neighbour discovery message

Jan-19 59
 Packet-too-big Message
Format
 Needed because now the sender fragments the packets to
their optimum size to traverse the path
 At no point along the path does the packet get fragmented
again
 So if a packet is too big for a network (perhaps different
path to original) then an error message is needed to report
this back to the sender

Jan-19 60
Other Messages
 Informational
 Neighbour-Discovery
 Group Membership

Jan-19 61
Comparison of Query Messages in ICMPv4
and ICMPv6

Jan-19 62
After the lecture…
 Review the lecture material at least once.
 Read all relevant sections in the textbook.
 Attempt all tutorial problems.
 Check if you are competent with the objectives
mentioned at the beginning of each topic.

Jan-19 63