Professional Documents
Culture Documents
Hari Krishna Raju Kanekal Nomus Comm-Systems
Hari Krishna Raju Kanekal Nomus Comm-Systems
NOMUS COMM-SYSTEMS
IPv6 Overview
IPv6 Features
IPv6 Addressing Modes
IPv6 Address Types
IPv6 Special Address
IPv6 Headers
IPv6 Communication
IPv6 Routing
IPv6 Implementation
IPv6 Summary
Internet Protocol Version 4 HTTP, TELNET,
application
Incredibly successful SNMP, FTP, etc.
presentation
Today’s Internet runs over IPv4 session
version 2
Larger Address Space
IP Version 6 is a 128 bit address
2^128 = 3.4 x1038 [Approx 340 Trillion Trillion Trillion IP addresses]
According to an estimate, 1564 addresses can be allocated to every
square meter of this earth
Simplified Header
IPv6 header has been simplified by moving all unnecessary
information and options (which are present in IPv4 header) to the end
of the IPv6 header
End-to-end Connectivity
Every system now has unique IP address and can traverse through the
internet without using NAT or other translating components
Auto-configuration
IPv6 supports both stateful and stateless auto configuration mode of its
host devices. This way absence of a DHCP server does not put halt on inter
segment communication
Faster Forwarding/Routing
Simplified header puts all unnecessary information at the end of the
header
All information in first part of the header are adequate for a Router
to take routing decision thus making routing decision as quickly as
looking at the mandatory header
IPSec
Initially it was decided for IPv6 to must have IPSec security, making it
more secure than IPv4. This feature has now been made optional
No Broadcast
IPv6 does not have any Broadcast support anymore left with it. It uses
multicast to communicate with multiple hosts
Anycast Support
IPv6 has introduced Anycast mode of packet routing. In this mode,
multiple interfaces over the Internet are assigned same Anycast IP
address. Routers, while routing, send the packet to the nearest
destination
Mobility
This feature enables hosts (such as mobile phone) to roam around in
different geographical area and remain connected with the same IP
address. The mobility feature of IPv6 takes advantage of auto IP
configuration and Extension headers
Enhanced Priority Support
In IPv4 to provide QoS but it could only be used if the end-to-end
devices support it, that is, the source and destination device and
underlying network must support it
In IPv6, Traffic class and Flow label are used to tell the underlying
routers how to efficiently process the packet and route it
Extensibility
IPv4 provides only 40-bytes for options, whereas options in IPv6 can be
as much as the size of IPv6 Extension headers
Jumbograms
Jumbograms is an optional feature of IPv6. Jumbograms allow packets with
payloads 2^32 - 1 (4,294,967,295) bytes by making use of a 32-bit length field.
Node : Any device that runs an Implementation of IPv6. This Includes
Routers and Hosts.
Router : A node that can forward IPv6 packets not explicitly addressed
to itself. On an IPv6 network, a router also typically advertises its presence
and host configuration information.
Host : A node that cannot forward IPv6 packets not explicitly addressed
to itself (a non-router).
Neighbors : Nodes connected to the same link.
Link MTU : The maximum transmission unit (MTU)—the number of
bytes in the largest IPv6 packet—that can be sent on a link. The link MTU
is the same as the maximum payload size of the link-layer technology
Path MTU : The maximum-sized IPv6 packet that can be sent without
performing host fragmentation between a source and destination over a
path in an IPv6 network. The path MTU is typically the smallest link MTU
of all the links in the path
An IPv6 address is made of 128 bits divided into
eight 16-bits blocks
Each block is then converted into 4-digit
Hexadecimal numbers separated by colon symbols
Eg : 128 Bit IPv6 address in binary format
0010000000000001 0000000000000000 0011001000111000 1101111111100001
0000000001100011 0000000000000000 0000000000000000 1111111011111011
Each block is then converted into Hexadecimal and separated
by ‘:’ symbol:
2001:0000:3238:DFE1:0063:0000:0000:FEFB
2001:0000:3238:DFE1:0063:0000:0000:FEFB
Even after converting into Hexadecimal format,
IPv6 address remains long
IPv6 provides some rules to shorten the address.
The rules are as follows:
Rule.1: Discard leading Zero(es):
2001:0:3238:DFE1:63:0:0:FEFB
Rule.2:If two of more blocks contain consecutive zeroes,
omit them all and replace with double colon sign ::
2001:0:3238:DFE1:63::FEFB
Unicast :
An identifier for a single interface. A packet sent to a unicast address is
delivered to the interface identified by that address.
Multicast :
An identifier for a set of interfaces (typically belonging to different nodes).
A packet sent to a multicast address is delivered to all interfaces identified
by that address.
Anycast :
An identifier for a set of interfaces (typically belonging to different nodes).
A packet sent to an anycast address is delivered to one of the interfaces
identified by that address (the "nearest" one, according to the routing
protocols' measure of distance).
No more Broadcast Addresses.
Unicast IPv6 Addresses
Global unicast addresses
Link-local addresses
Site local addresses
Unique local addresses
Special addresses
Transition addresses
Multicast IPv6 Addresses
Anycast IPv6 Address.
IPv6 Address has two parts, Prefix and Interface ID
Prefix length is stated in classless inter-domain routing (CIDR)
notation. CIDR notation is a slash at the end of the address that is followed
by the prefix length in bits
n bits 128-n bits
Prefix Interface ID
To create an EUI-64 address from an IEEE 802 address, the 16 bits of 11111111
11111110 (0xFFFE) are inserted into the IEEE 802 address between the company ID
and the extension ID.
24 bits 16 bits 24 bits
Link-local addresses are used between on-link neighbors and for Neighbor
Discovery processes, which define how nodes on an IPv6 subnet interact with
hosts and routers.
The scope of a link-local address (the region of the network across which the
address is unique) is the local link.
A link-local address is always automatically configured, even in the absence
of all other unicast addresses
An IPv6 router never forwards link-local traffic beyond the link.
Address prefix for all link-local addresses is FE80::/64.
10 bits 54 bits 64 bits
IPv6 Multicast addresses have the first 8 bits set to 1111 1111.
Flags is a set of 4 bit field i.e 0RPT flags
The high-order flag is reserved, and must be initialized to 0.
Transient(T) flag indicates permanently-assigned (‘well-known”)
multicast address, assigned by the Internet Assigned Numbers Authority
(IANA) and a non permanently-assigned (“transient” or “dynamically”
assigned) multicast address.
Prefix (P) flag indicates a multicast address that is assigned based on
the network prefix.
Rendezvous Point (R) flag indicates a multicast address that embed the
address on the RP used in PIM-SM (Protocol Independent Multicast-
Sparse Mode).
Scope is a 4 bit multicast scope value used to limit the scope of the
multicast group.
Group ID is a 112 bits and identifies the multicast group and is unique
within the scope. Multicast addresses from FF01:: through FF0F:: are
reserved, well-known addresses.
Defined values for scope field is follows.
0 Reserve
1 Interface-local scope
2 Link-local scope
3 Reserve
4 Admin-local scope
5 Site-local scope
8 Organization-local scope
E Global scope
F Reserved.
Here which are not listed is a unassigned values.
To identify all nodes for the interface-local and link-local scope
FF01::1 Interface-local scope all nodes multicast address
FF02::1 Link-local scope all nodes multicast address
To identify all routers for the interface-local, link-local scope and site-
local scope.
FF01::2 Interface-local scope all routers multicast address
FF02::2 Link-local scope all routers multicast address
FF05::2 Site-local scope all routers multicast address
For more details at http://www.iana.org/assignments/ipv6-multicast-
addresses.
For each unicast and anycast address configured there is a
corresponding Solicited-Node Multicast.
Used for two purposes, for the replacement of ARP and DAD.
Used in Neighbor Solicitation messages.
Multicast address with a link-local scope.
Solicited-Node multicast consists of prefix + lower 24 bits from unicast
or anycast and appending those bits to prefix FF02:0:0:0:0:1::/104.
FF02:0:0:0:0:1:FFXX:XXXX
Here XX:XXXX is a lower 24bits from unicast or anycast
Eg: 4037::01:800:200E:8C6C => FF02::1:FF0E:8C6C
An IPv6 anycast address is an address that is assigned to more than one
interface(typically belonging to different nodes).
A packet sent to an anycast address is routed to the “nearest” interface
having that address, according to the routing protocols measure of
distance.
Anycast addresses are allocated from the unicast address space.
Anycast addresses are syntactically indistinguishable from unicast
address.
A unicast address is assigned to more than one interface, thus turning it
into an anycast address, the address is assigned must be explicitly
configured.
Anycast address has a longest prefix P of that address that identifies the
topological region.
Anycast address must be maintained as a separate entry in the routing
system (commonly referred to as a "host route").
The Subnet-Router anycast address is predefined. Its format is as follows:
Version IHL Service Type Total Length Version Class Flow Label
Identifier Flags Fragment Offset Payload Length Next Header Hop Limit
Changed Removed
IPv6 Header
40 octets, 8 fields
+ Unlimited Chained Extension (options) Header
IPv6 payloads can contain zero or more extension headers,
which can vary in length.
A Next Header field in the IPv6 header indicates the next
extension header.
Each extension header contains another Next Header field
that indicates the next extension header.
The last extension header indicates the upper layer protocol
(such as TCP, UDP, or ICMPv6), if any, that the upper layer
protocol data unit contains.
RFC 2460 defines the following IPv6 extension headers that
all IPv6 nodes must support :
Hop-by-Hop Options Header => Processed by every router
Destination Options Header => Processed by routers listed in Routing extension
Routing Header => List of routers to cross
Fragment Header => After reassembling the packet
Authentication Header => Processed by the destination
Encryption Security Payload Header => Cipher content of the remaining information
Destination Options Header => Processed only by the destination
The Option Type field assigns a particular meaning to the three highest
order bits
The two highest order bits (Action) specify the action that must be taken if the
processing IPv6 node doesn’t recognize the option type.
00 Skip over this option and continue to process eventual subsequent options.
01 Discard the packet.
10 Discard the packet, regardless of whether the packet destination address is
multicast; the source node is notified by an ICMP packet.
11 Discard the packet, and only if its destination address is not multicast, the
source node is notified by an ICMP packet.
The third bit C (Change) specifies whether the Option data can change
en route to the packet’s final destination
0 Option data cannot change en route.
1 Option data can change en route.
Pad 1 Option :
The Pad 1 option is defined in RFC 2460.
It is used to insert a single byte of padding so that the Hop-by-Hop
Options or Destination Options headers fall on 8-byte boundaries
and to accommodate the alignment requirements of options.
With Option Type set to 0, the option is skipped if not recognized,
and it is not allowed to change in transit.
Option Type = 0
Pad N Option :
The Destination Options header is used to specify delivery parameters for either
intermediate destinations or the final destination.
It is identified by the value of 60 in the previous header’s Next Header field.
Next Header field and Header Extension Length field has the same meaning as
the Hop-by-Hop Options header.
The Destination Options header is used in two ways:
If a Routing header is present, it specifies delivery or processing options at
each intermediate destination.
If no Routing header is present or if this header occurs after the Routing
header, it specifies delivery or processing options at the final destination.
Options used by Destination Options Header are Pad 1, Pad N, Home Address
Options e.t.c.
Next Header Header Extension Routing Segments
(8Bit) Length (8Bit) Type (8Bit) Left (8Bit)
Reserved (32Bit)
Address 1 (128 Bit)
. . . .
Address N (128 Bit)
The Routing header is used by an IPv6 source to list one or more
intermediate nodes to be "visited" on the way to a packet's destination.
This header supports a function very similar to the IPv4 packet Loose Source
Route and Record Route option.
It is identified by the value of 43 in the previous header’s Next Header field.
Next Header field and Header Extension Length field has the same meaning
as the Hop-by-Hop Options header.
The 8-bit Routing Type field specifies the Type of Routing header.
Type 0 Source Route (DEPRECATED) [RFC5095]
Type 1 Nimrod (DEPRECATED 2009-05-06) [DARPA]
Type 2 Type 2 Routing Header[RFC6275]
Type 3 RPL Source Route Header[RFC6554]
The 8-bit Segments Left field contains the number of explicitly listed
intermediate nodes still to be visited before reaching the final destination. The
maximum legal value for this field is 23.
A B
Network
Network
Network Network
R1
R2 R3
Type 3 is a common network configuration for Source Routes with the
Routing Protocol for Low-Power and Lossy Networks(RPL)
Next Header Header Extension Routing Segments
(8Bit) Length (8Bit) Type (8Bit) Left (8Bit)
CmprI : No. of prefix octets from each segment, except than the last segment,
(i.e., segments 1 through n-1) that are elided.
CmprE : No. of prefix octets from the last segment (i.e., segment n) that are
elided.
Pad : No. of octets that are used for padding after Address[n].
Type 2 is a Mobile IPv6.
The Fragment header is used by an IPv6 Source to send a packet larger than
would fit in the path MTU to its destination.
The Fragment header cannot be used for jumbograms.
It is identified by the value of 44 in the previous header’s Next Header field.
Next Header field has the same meaning as the Hop-by-Hop Options header.
Fragment offset, in 8-octet units, of the data following this header, relative to
the start of the Fragmentable Part of the original packet.
More Fragments Flag : 1 = more fragments; 0 = last fragment.
In order to send a packet that is too large to fit in the MTU of the path to its
destination, a source node may divide the packet into fragments and send each
fragment as a separate packet to be reassembled at the receiver.
For every packet that is to be fragmented, the source generated an
Identification value and it must be different than that of any other fragmented
packet sent recently with same source and destination addresses.
Authentication Data
Payload
Padding
Padding Length Next Header
Authentication Data
It is identified by the value of 50 in the previous header’s Next
Header field.
Security Parameters Index, Sequence Number, Next Header and
Authentication Data same as Authentication header.
Payload Data field is a encrypted data that has to be transferred.
Padding field is used by ciphers to pad the data to the full length of
block ( 0 to 255 bytes range only to pad).
Pad Length field is a size of padding in bytes.
ESP header provides no security to Extension headers (occur before
the ESP header).
The value 59 in the Next Header field of an IPv6 header or any
Extension header indicates that there is nothing following that
header.
If the Payload Length field of the IPv6 header indicates the
presence of octets past the end of a header whose Next Header field
contains 59, those must be ignored, and passed on unchanged if the
packet is forwarded.
Source Address
Destination Address
Upper –Layer Packet Length
Zero Next Header
Packet (MTU=1300)
Packet Received
Msg No. Msg Type Description
128 Echo Request RFC 4443. Used for the
129 Echo Reply ping & trace route.
130 Multicast Listener Query RFC 2710. Used for
131 Multicast Listener Report multicast group
132 Multicast Listener Done management.
133 Router Solicitation RFC 2461. Used for
134 Router Advertisement neighbor discovery and
135 Neighbor Solicitation Auto Configuration.
136 Neighbor Advertisement
137 Redirect Message
138 Router Renumbering RFC 2894.
139 ICMP Node Information Query draft-ietf-ipngwg-icmp-
140 ICMP Node Information Response name-lookups-15.txt
Msg No. Msg Type Description
141 Inverse ND Solicitation RFC 3122.
142 Inverse ND Advertisement
143 Version 2 Multicast Listener Report RFC 3810.
144 IMCP Home Agent Address RFC 3775. ICMPv6
Discovery Request Message messages for Mobile IPv6
145 ICMP Home Agent Address
Discovery Request Message
146 ICMP Mobile Prefix Solicitation
147 ICMP Mobile Prefix Advertisement
148 Certification Path Solicitation RFC 3971. SEcure
149 Certification Path Advertisement Neighbor Discovery
151 Multicast Router Advertisement RFC 4286
152 Multicast Router Solicitation
153 Multicast Router Termination
Msg No. Msg Type Description
157 Duplicate Address Request Code RFC 8505
Suffix
158 Duplicate Address Confirmation Code
Suffix
160 Extended Echo Request Message RFC 8335
161 Extended Echo Reply Message
IPv6 ND is a set of messages and processes defined in RFC 4861
that determine relationships between neighboring nodes.
ND replaces Address Resolution Protocol (ARP), ICMP Router
Discovery and Redirect used in IPv4 and provides additional
functionality.
IPv6 nodes use Neighbor Discovery for the following purposes:
• For autoconfiguration of IPv6 addresses
• To determine network prefixes, routes and other configuration
information
• For Duplicate IP address detection (DAD)
• To determine layer two addresses of nodes on the same link
• To find neighboring routers that can forward their packets
• To keep track of which neighbors are reachable and which are
not (NUD)
• To detect changed link-layer addresses
Router Solicitation(RS) Message ICMPv6 Type 133, Sent by hosts
to request that any local routers send a Router Advertisement message
so they don't have to wait for the next regular advertisement message.
Router Advertisement(RA) Message ICMPv6 Type 134, Sent by
routers to tell hosts that they exist and provide important prefix and
parameter information to them.
Neighbor Solicitation(NS) Message ICMPv6 Type 135, Sent by
nodes to verify the existence of another host and to ask it to transmit a
Neighbor Advertisement.
Neighbor Advertisement(NA) Message ICMPv6 Type 136, Sent by
hosts to indicate the existence of the host and provide information
about it.
Redirect Message ICMPv6 Type 137, Sent by router to tell a host of
a better method to route data to a particular destination.
ND solves a set of problems related to the interaction between
nodes attached to the same link. It defines 9 set of mechanisms and
can be categorized into three functions
1. Host-Router Functions
2. Host-Host Communication Functions
3. Redirect Function
Router Discovery is how a host discovers the local routers on an
attached link. This process is equivalent to ICMPv4 router discovery.
Prefix Discovery is the process by which hosts discover the network
prefixes for local link destinations. This is similar to the exchange of the
ICMPv4 Address Mask Request and Address Mask Reply messages.
Parameter Discovery is the process by which host discovers link
parameters (such as the link MTU) or Internet parameters (such as the
hop limit value) to place in outgoing packets.
Address Autoconfiguration is the mechanisms needed in order to
allow nodes to configure an address for an interface in a stateless
manner in absence of DHCPv6 Router.
Address resolution is the process by which nodes resolve a neighbor’s
IPv6 address to its link-layer address. It is equivalent to ARP in IPv4.
Next-hop determination is the algorithm for mapping an IPv6
destination address into the IPv6 address of the neighbor to which traffic
for the destination should be sent. The next- hop can be a router or the
destination itself.
Neighbor Unreachability Detection is a process that nodes determine
that a neighbor is no longer reachable. For neighbors used as routers,
alternate default routers can be tried. For both routers and hosts, address
resolution can be performed again.
Duplicate Address Detection, a node determines whether or not an
address it wishes to use is already in use by another node. This process is
equivalent to using gratuitous ARP frames in IPv4.
Redirect, a router informs a host of a better first-hop node to reach a
particular destination. It is equivalent to the use of the ICMPv4 Redirect.
Neighbor Discovery messages include zero or more options, some of
which may appear multiple times in the same message. Options should be
padded when necessary to ensure that they end on their natural 64-bit
boundaries. ND options are formatted in type-length-value (TLV) format.
Type Option Name
1 Source Link-Layer Address (Eg. IEEE 802 Address)
2 Target Link-Layer Address
3 Prefix Information
4 Redirected Header
5 MTU
Type (8Bit) Length (8Bit) Link Layer Address (Variable)
Type field is set to 1 for a Source Link-Layer Address option and is set to
2 for a Target Link-Layer Address option.
Length field is length of the option (including the type and length
fields) in units of 8 octets.
The Source Link-Layer Address option contains the link-layer address of
the sender of the packet. It is used in the Neighbor Solicitation, Router
Solicitation, and Router Advertisement packets.
The Target Link-Layer Address option contains the link-layer address of
the target. It is used in Neighbor Advertisement and Redirect packets.
These options must be silently ignored for other Neighbor Discovery
messages.
Type = 3 Length = 4 Prefix Length L|A|R|Reserve
Valid Lifetime (32 Bit)
Preferred Lifetime (32 Bit)
Reserved2 (32 Bit)
Prefix (128 Bit)
Is there a No No
default
router? Indicate an error
Ethernet Header
Dst MAC: 33:33:FF:34:56:78
IPv6 Header
Src IP: 2000::1234:5679
Dst IP: FF02::1:FF34:5678
Hop Limit : 255
Neighbor Solicitation
Target Address : 2000::1234:5678
Neighbor Discovery Option
Source Link Layer : 00:1F:D0:E9:E2:52
Host A Neighbor Advertisement Host B
Ethernet Header
Dst MAC: 00:1F:D0:E9:E2:52
IPv6 Header
Src IP: 2000::1234:5678
Dst IP: 2000::1234:5679
Hop Limit : 255
Neighbor Advertisement
Target Address : 2000::1234:5678
Neighbor Discovery Option
Target Link Layer : FC:C2:3D:03:54:9E
A neighboring node is reachable if there has been a recent confirmation
that IPv6 packets sent to the neighboring node were received and
processed by the neighboring node.
Neighbor unreachability does not necessarily verify the end-to-end
reachability of the destination. Because a neighboring node can be a host
or router, the neighboring node might not be the final destination of the
packet.
Neighbor unreachability verifies only the reachability of the first hop to
the destination.
Reachability is determined by the receipt of a Neighbor Advertisement
message in response to a unicast Neighbor Solicitation message.
Another method of determining reachability is when upper-layer
protocols indicate that the communication using the next-hop address is
making forward progress.
Host A Neighbor Solicitation Host B
Ethernet Header
Dst MAC: FC:C2:3D:03:54:9E
IPv6 Header
Src IP: FE80::21F:D0FF:FEE9:E252
Dst IP: FE80::FEC2:3DFF:FE03:549E
Hop Limit : 255
Neighbor Solicitation
Target Address : FE80::FEC2:3DFF:FE03:549E
Neighbor Discovery Option
Source Link Layer : 00:1F:D0:E9:E2:52
Host A Neighbor Advertisement Host B
Ethernet Header
Dst MAC: 00:1F:D0:E9:E2:52
IPv6 Header
Src IP: FE80::FEC2:3DFF:FE03:549E
Dst IP: FE80::21F:D0FF:FEE9:E252
Hop Limit : 255
Neighbor Advertisement
Target Address : FE80::FEC2:3DFF:FE03:549E
IPv4 nodes use ARP Request messages and a method called Gratuitous
ARP to detect a duplicate IP address on the local link.
Similarly, IPv6 nodes use the Neighbor Solicitation message to detect
duplicate address use on the local link.
Before a node can configure its IPv6 address using stateless
autoconfiguration, it must verify on the local link that the tentative
address it wants to use is unique and not already in use by another mode.
Node sending a Neighbour Solicitation (NS) on the local link using
unspecified address (::) as its source address and solicited-node
multicast of the tentative unicast address as the destination address.
If a duplicate address – no assignment of this unicast address.
For a duplicate address, the defending node replies with a multicast
Neighbor Advertisement.
An IPv6 node does not perform duplicate address detection for anycast
addresses.
Host A Host B Host C
Ethernet Header
Dst MAC: 33:33:00:00:00:02
IPv6 Header
Src IP: FE80::222:85FF:FE33:4455
Dst IP: FF02::02
Hop Limit : 255
Router Solicitation
Neighbor Discovery Option
Source Link Layer : 00:22:85:33:44:55
Host Router Advertisement Router
Ethernet Header
Dst MAC: 33:33:00:00:00:01
IPv6 Header
Src IP: FE80::21F:D0FF:FEE9:E252
Dst IP: FF02::1
Hop Limit : 255
Router Advertisement
Cur Hop Limit, Flags, Router/Reachable/Retrans
Neighbor Discovery Option
Source link-layer address, MTU, Prefix information
In addition to configuring a default router, IPv6 router discovery also
configures the following:
Default value of Hop Limit field.
Use of stateful address protocol, such as DHCPv6, for addresses and
other configuration parameters.
The timers used in reachability detection and the retransmission of
Neighbor Solicitations.
The list of network prefixes defined for the link. Each network prefix
contains both the network prefix and its valid and preferred lifetimes.
The MTU of the local link.
Specific routes to add to the routing table.
When an IPv6 address is assigned, it goes through various states either
before assigning or after assigning. These address states are applicable to
both manually and automatically configured addresses.
Tentative address :
The address is in the process of being verified as unique.
Verification occurs through duplicate address detection.
When an address is configured on a network interface (either
manually or automatically), the address is initially in the tentative
state.
An interface discards received packets addressed to a tentative
address, but accepts Neighbor Discovery packets related to
Duplicate Address Detection (DAD) for the tentative address.
Duplicate address :
• If DAD finds that an address is not unique, it is moved to the
duplicate state. Such an address cannot be used for sending and
receiving data.
Preferred address :
• An address used to send and receive data packets from and to a
network interface without any restriction on the upper layer protocols.
Deprecated address :
• A preferred address becomes deprecated when its preferred lifetime
expires. The use of this address is discouraged, but not prohibited.
Valid address :
• A uniquely verified address that you can assign to a network interface
for sending and receiving data. A valid address can be a preferred or
deprecated address.
Invalid address :
• A network interface address that can no longer send or receive data
packets. A valid address becomes invalid when its valid lifetime
expires. An invalid address is removed from the network interface.
It works (roughly) as follows:
The host configures a link-local address.
It checks that the address is unique – i.e., it performs Duplicate Address
Detection (DAD) for that address.
• Sends a NS, and waits for any answers.
The host sends a Router Solicitation message.
When a Router Advertisement is received, it configures a “tentative”
IPv6 address.
It checks that the address is unique – i.e., it performs Duplicate Address
Detection (DAD) for that address.
• Sends a NS, and waits for any answers.
If the address is unique, it typically becomes a “preferred” address.
Link-local
only
Router
Advertisement
DAD Successful
Valid
Preferred
Preferred Lifetime
Expired
Valid Lifetime Expired
Deprecated Invalid
Routers use the redirect function to inform originating hosts of a better
first-hop neighbor to which traffic should be forwarded for a specific
destination.
Nodes receiving it may modify its routing table according to the new
router address.
There are two instances where redirect is used
1. A router informs an originating host of the IP address of a router
available on the local link that is “closer” to the destination.
• “Closer” is routing metric function used to reach the destination
network segment.
• This condition can occur when there are multiple routers on a
network segment and the originating host chooses a default
router and it is not the best one to use to reach the destination.
2. A router informs an originating host that the destination is a
neighbor (it is on the same link as the originating host).
• This condition can occur when the prefix list of a host does not
include the prefix of the destination.
• Because the destination does not match a prefix in the list, the
originating host forwards the packet to its default router.
The originating host forwards a unicast packet to its default router.
The router processes the packet and notes that the address of the
originating host is a neighbor.
The router forwards the packet to the appropriate next-hop address.
The router sends the originating host a Redirect message.
Upon receipt of the Redirect message, the originating host updates
the destination address entry in the destination cache with the
address in the Target Address field.
(1) Send packets to Router 1
Host A
Dual Stack
Network IPv4
Internet
Dual Stack Dual-stack
Network
Core