Chapter27

IPv6
Protocol

TCP/IP Protocol Suite 1

Copyright The McGraw-Hill Companies, Inc. Permission required for reproduction or display.
OBJECTIVES:
To give the format of an IPv6 datagram composed of a base
header and a payload.
To discuss different fields used in an IPv6 datagram based
header and compare them with the fields in IPv4 datagram.
To show how the options in IPv4 header are implemented using
the extension header in IPv6.
To show how security is implemented in IPv6.
To discuss three strategies used to handle the transition from
IPv4 to IPv6: dual stack, tunneling, and header translation.

TCP/IP Protocol Suite 2

Chapter 27.1 Introduction
Outline
27.2 Packet Format

27.3 Transition to IPv6

TCP/IP Protocol Suite 3

 271INTRODUCTION

In this introductory section, we discuss

two topics: rationale for a new protocol
and the reasons for delayed adoption.

TCP/IP Protocol Suite 4

 TopicsDiscussedintheSection
Rationale for Change
Reason for Delay in Adoption

TCP/IP Protocol Suite 5

 272PACKETFORMAT

The IPv6 packet is shown in Figure 27.1.

Each packet is composed of a mandatory
base header followed by the payload.
The payload consists of two parts:
optional extension headers and data
from an upper layer. The base header
occupies 40 bytes, whereas the
extension headers and data from the
upper layer contain up to 65,535 bytes of
information.

TCP/IP Protocol Suite 6

 TopicsDiscussedintheSection
Base Header
Flow Label
Comparison between IPv4 and IPv6 Headers
Extension Headers
Comparison between IPv4 and IPv6 Options

TCP/IP Protocol Suite 7

 Figure 27.1 IPv6 datagram

TCP/IP Protocol Suite 8

 Figure 27.2 Format of the base header

TCP/IP Protocol Suite 9

TCP/IP Protocol Suite 10
 Figure 27.3 Extension header format

TCP/IP Protocol Suite 11

 Figure 27.4 Extension header types

TCP/IP Protocol Suite 12

 Figure 27.5 Hop-by-hop option header format

TCP/IP Protocol Suite 13

 Figure 27.6 The format of the option in a hop-by-hop option header

00000 Pad1
Action C Type
00001 PadN Type
2 bits 1 bit 5 bits
00010 Jumbo payload

Action: if the option not recognized

00 Skip this option
01 Discard datagram, no more action C: Change in option value
10 Discard datagram and send ICMP message 0 Does not change in transit
11 Discard datagram send ICMP message if not multicast 1 May be changed in transit

TCP/IP Protocol Suite 14

 Figure 27.7 Pad1

TCP/IP Protocol Suite 15

 Figure 27.8 PadN

TCP/IP Protocol Suite 16

 Figure 27.9 Jumbo payload

TCP/IP Protocol Suite 17

 Figure 27.10 Source routing

TCP/IP Protocol Suite 18

 Figure 27.11 Source routing example

Source: A Source: A Source: A Source: A

Destination: R1 Destination: R2 Destination: R3 Destination: B
Left: 3 Left: 2 Left: 1 Left: 0
R2 R1 R1 R1
R3 R3 R2 R2
B B B R3

TCP/IP Protocol Suite 19

 Figure 27.12 Fragmentation

TCP/IP Protocol Suite 20

 Figure 27.13 Authentication

TCP/IP Protocol Suite 21

 Figure 27.14 Calculation of authentication data

TCP/IP Protocol Suite 22

 Figure 27.15 Encrypted security payload

TCP/IP Protocol Suite 23

 273TRANSITIONFROMIPv4TOIPv6

Because of the huge number of systems

on the Internet, the transition from IPv4
to IPv6 cannot happen suddenly. It will
take a considerable amount of time
before every system in the Internet can
move from IPv4 to IPv6. The transition
must be smooth to prevent any problems
between IPv4 and IPv6 systems. Three
strategies have been devised by the IETF
to help the transition (see Figure 27.16).

TCP/IP Protocol Suite 24

 TopicsDiscussedintheSection
Dual Stack
Tunneling
Header Translation

TCP/IP Protocol Suite 25

 Figure 27.16 Three transition strategies

TCP/IP Protocol Suite 26

 Figure 27.17 Dual stack

TCP/IP Protocol Suite 27

 Figure 27.18 Tunneling strategy

IPv4 header
IPv6 header
Payload

TCP/IP Protocol Suite 28

 Figure 27.19 Header translation strategy

IPv6 header IPv4 header

Payload Payload

TCP/IP Protocol Suite 29