
- •For Web Developers
- •Contents at a Glance
- •Table of Contents
- •List of Figures
- •List of Tables
- •Foreword
- •Why Does Microsoft Care About IPv6?
- •Preface
- •Acknowledgments
- •Introduction
- •Who Should Read This Book
- •What You Should Know Before Reading This Book
- •Organization of This Book
- •Appendices of This Book
- •About the Companion CD-ROM
- •System Requirements
- •IPv6 Protocol and Windows Product Versions
- •A Special Note to Teachers and Instructors
- •Disclaimers and Support
- •Technical Support
- •Limitations of IPv4
- •Consequences of the Limited IPv4 Address Space
- •Features of IPv6
- •New Header Format
- •Large Address Space
- •Stateless and Stateful Address Configuration
- •IPsec Header Support Required
- •Better Support for Prioritized Delivery
- •New Protocol for Neighboring Node Interaction
- •Extensibility
- •Comparison of IPv4 and IPv6
- •IPv6 Terminology
- •The Case for IPv6 Deployment
- •IPv6 Solves the Address Depletion Problem
- •IPv6 Solves the Disjoint Address Space Problem
- •IPv6 Solves the International Address Allocation Problem
- •IPv6 Restores End-to-End Communication
- •IPv6 Uses Scoped Addresses and Address Selection
- •IPv6 Has More Efficient Forwarding
- •IPv6 Has Support for Security and Mobility
- •Testing for Understanding
- •Architecture of the IPv6 Protocol for Windows Server 2008 and Windows Vista
- •Features of the IPv6 Protocol for Windows Server 2008 and Windows Vista
- •Installed, Enabled, and Preferred by Default
- •Basic IPv6 Stack Support
- •IPv6 Stack Enhancements
- •GUI and Command-Line Configuration
- •Integrated IPsec Support
- •Windows Firewall Support
- •Temporary Addresses
- •Random Interface IDs
- •DNS Support
- •Source and Destination Address Selection
- •Support for ipv6-literal.net Names
- •LLMNR
- •PNRP
- •Literal IPv6 Addresses in URLs
- •Static Routing
- •IPv6 over PPP
- •DHCPv6
- •ISATAP
- •Teredo
- •PortProxy
- •Application Support
- •Application Programming Interfaces
- •Windows Sockets
- •Winsock Kernel
- •Remote Procedure Call
- •IP Helper
- •Win32 Internet Extensions
- •Windows Filtering Platform
- •Manually Configuring the IPv6 Protocol
- •Configuring IPv6 Through the Properties of Internet Protocol Version 6 (TCP/IPv6)
- •Configuring IPv6 with the Netsh.exe Tool
- •Disabling IPv6
- •IPv6-Enabled Tools
- •Ipconfig
- •Route
- •Ping
- •Tracert
- •Pathping
- •Netstat
- •Displaying IPv6 Configuration with Netsh
- •Netsh interface ipv6 show interface
- •Netsh interface ipv6 show address
- •Netsh interface ipv6 show route
- •Netsh interface ipv6 show neighbors
- •Netsh interface ipv6 show destinationcache
- •References
- •Testing for Understanding
- •The IPv6 Address Space
- •IPv6 Address Syntax
- •Compressing Zeros
- •IPv6 Prefixes
- •Types of IPv6 Addresses
- •Unicast IPv6 Addresses
- •Global Unicast Addresses
- •Topologies Within Global Addresses
- •Local-Use Unicast Addresses
- •Unique Local Addresses
- •Special IPv6 Addresses
- •Transition Addresses
- •Multicast IPv6 Addresses
- •Solicited-Node Address
- •Mapping IPv6 Multicast Addresses to Ethernet Addresses
- •Anycast IPv6 Addresses
- •Subnet-Router Anycast Address
- •IPv6 Addresses for a Host
- •IPv6 Addresses for a Router
- •Subnetting the IPv6 Address Space
- •Step 1: Determining the Number of Subnetting Bits
- •Step 2: Enumerating Subnetted Address Prefixes
- •IPv6 Interface Identifiers
- •EUI-64 Address-Based Interface Identifiers
- •Temporary Address Interface Identifiers
- •IPv4 Addresses and IPv6 Equivalents
- •References
- •Testing for Understanding
- •Structure of an IPv6 Packet
- •IPv4 Header
- •IPv6 Header
- •Values of the Next Header Field
- •Comparing the IPv4 and IPv6 Headers
- •IPv6 Extension Headers
- •Extension Headers Order
- •Hop-by-Hop Options Header
- •Destination Options Header
- •Routing Header
- •Fragment Header
- •Authentication Header
- •Encapsulating Security Payload Header and Trailer
- •Upper-Layer Checksums
- •References
- •Testing for Understanding
- •ICMPv6 Overview
- •Types of ICMPv6 Messages
- •ICMPv6 Header
- •ICMPv6 Error Messages
- •Destination Unreachable
- •Packet Too Big
- •Time Exceeded
- •Parameter Problem
- •ICMPv6 Informational Messages
- •Echo Request
- •Echo Reply
- •Comparing ICMPv4 and ICMPv6 Messages
- •Path MTU Discovery
- •Changes in PMTU
- •References
- •Testing for Understanding
- •Neighbor Discovery Overview
- •Neighbor Discovery Message Format
- •Neighbor Discovery Options
- •Source and Target Link-Layer Address Options
- •Prefix Information Option
- •Redirected Header Option
- •MTU Option
- •Route Information Option
- •Neighbor Discovery Messages
- •Router Solicitation
- •Router Advertisement
- •Neighbor Solicitation
- •Neighbor Advertisement
- •Redirect
- •Summary of Neighbor Discovery Messages and Options
- •Neighbor Discovery Processes
- •Conceptual Host Data Structures
- •Address Resolution
- •Neighbor Unreachability Detection
- •Duplicate Address Detection
- •Router Discovery
- •Redirect Function
- •Host Sending Algorithm
- •References
- •Testing for Understanding
- •MLD and MLDv2 Overview
- •IPv6 Multicast Overview
- •Host Support for Multicast
- •Router Support for Multicast
- •MLD Packet Structure
- •MLD Messages
- •Multicast Listener Query
- •Multicast Listener Report
- •Multicast Listener Done
- •Summary of MLD
- •MLDv2 Packet Structure
- •MLDv2 Messages
- •The Modified Multicast Listener Query
- •MLDv2 Multicast Listener Report
- •Summary of MLDv2
- •MLD and MLDv2 Support in Windows Server 2008 and Windows Vista
- •References
- •Testing for Understanding
- •Address Autoconfiguration Overview
- •Types of Autoconfiguration
- •Autoconfigured Address States
- •Autoconfiguration Process
- •DHCPv6
- •DHCPv6 Messages
- •DHCPv6 Stateful Message Exchange
- •DHCPv6 Stateless Message Exchange
- •DHCPv6 Support in Windows
- •IPv6 Protocol for Windows Server 2008 and Windows Vista Autoconfiguration Specifics
- •Autoconfigured Addresses for the IPv6 Protocol for Windows Server 2008 and Windows Vista
- •References
- •Testing for Understanding
- •Name Resolution for IPv6
- •DNS Enhancements for IPv6
- •LLMNR
- •Source and Destination Address Selection
- •Source Address Selection Algorithm
- •Destination Address Selection Algorithm
- •Example of Using Address Selection
- •Hosts File
- •DNS Resolver
- •DNS Server Service
- •DNS Dynamic Update
- •Source and Destination Address Selection
- •LLMNR Support
- •Support for ipv6-literal.net Names
- •Peer Name Resolution Protocol
- •References
- •Testing for Understanding
- •Routing in IPv6
- •IPv6 Routing Table Entry Types
- •Route Determination Process
- •Strong and Weak Host Behaviors
- •Example IPv6 Routing Table for Windows Server 2008 and Windows Vista
- •End-to-End IPv6 Delivery Process
- •IPv6 on the Sending Host
- •IPv6 on the Router
- •IPv6 on the Destination Host
- •IPv6 Routing Protocols
- •Overview of Dynamic Routing
- •Routing Protocol Technologies
- •Routing Protocols for IPv6
- •Static Routing with the IPv6 Protocol for Windows Server 2008 and Windows Vista
- •Configuring Static Routing with Netsh
- •Configuring Static Routing with Routing and Remote Access
- •Dead Gateway Detection
- •References
- •Testing for Understanding
- •Overview
- •Node Types
- •IPv6 Transition Addresses
- •Transition Mechanisms
- •Using Both IPv4 and IPv6
- •IPv6-over-IPv4 Tunneling
- •DNS Infrastructure
- •Tunneling Configurations
- •Router-to-Router
- •Host-to-Router and Router-to-Host
- •Host-to-Host
- •Types of Tunnels
- •PortProxy
- •References
- •Testing for Understanding
- •ISATAP Overview
- •ISATAP Tunneling
- •ISATAP Tunneling Example
- •ISATAP Components
- •Router Discovery for ISATAP Hosts
- •Resolving the Name “ISATAP”
- •Using the netsh interface isatap set router Command
- •ISATAP Addressing Example
- •ISATAP Routing
- •ISATAP Communication Examples
- •ISATAP Host to ISATAP Host
- •ISATAP Host to IPv6 Host
- •Configuring an ISATAP Router
- •References
- •Testing for Understanding
- •6to4 Overview
- •6to4 Tunneling
- •6to4 Tunneling Example
- •6to4 Components
- •6to4 Addressing Example
- •6to4 Routing
- •6to4 Support in Windows Server 2008 and Windows Vista
- •6to4 Host/Router Support
- •6to4 Router Support
- •6to4 Communication Examples
- •6to4 Host to 6to4 Host/Router
- •6to4 Host to IPv6 Host
- •Example of Using ISATAP and 6to4 Together
- •Part 1: From ISATAP Host A to 6to4 Router A
- •Part 2: From 6to4 Router A to 6to4 Router B
- •Part 3: From 6to4 Router B to ISATAP Host B
- •References
- •Testing for Understanding
- •Introduction to Teredo
- •Benefits of Using Teredo
- •Teredo Support in Microsoft Windows
- •Teredo and Protection from Unsolicited Incoming IPv6 Traffic
- •Network Address Translators (NATs)
- •Teredo Components
- •Teredo Client
- •Teredo Server
- •Teredo Relay
- •Teredo Host-Specific Relay
- •The Teredo Client and Host-Specific Relay in Windows
- •Teredo Addresses
- •Teredo Packet Formats
- •Teredo Data Packet Format
- •Teredo Bubble Packets
- •Teredo Indicators
- •Teredo Routing
- •Routing for the Teredo Client in Windows
- •Teredo Processes
- •Initial Configuration for Teredo Clients
- •Maintaining the NAT Mapping
- •Initial Communication Between Teredo Clients on the Same Link
- •Initial Communication Between Teredo Clients in Different Sites
- •Initial Communication from a Teredo Client to a Teredo Host-Specific Relay
- •Initial Communication from a Teredo Host-Specific Relay to a Teredo Client
- •Initial Communication from a Teredo Client to an IPv6-Only Host
- •Initial Communication from an IPv6-Only Host to a Teredo Client
- •References
- •Testing for Understanding
- •IPv6 Security Considerations
- •Authorization for Automatically Assigned Addresses and Configurations
- •Recommendations
- •Protection of IPv6 Packets
- •Recommendations
- •Host Protection from Scanning and Attacks
- •Address Scanning
- •Port Scanning
- •Recommendations
- •Control of What Traffic Is Exchanged with the Internet
- •Recommendations
- •Summary
- •References
- •Testing for Understanding
- •Introduction
- •Planning for IPv6 Deployment
- •Platform Support for IPv6
- •Application Support for IPv6
- •Unicast IPv6 Addressing
- •Tunnel-Based IPv6 Connectivity
- •Native IPv6 Connectivity
- •Name Resolution with DNS
- •DHCPv6
- •Host-Based Security and IPv6 Traffic
- •Prioritized Delivery for IPv6 Traffic
- •Deploying IPv6
- •Set Up an IPv6 Test Network
- •Begin Application Migration
- •Configure DNS Infrastructure to Support AAAA Records and Dynamic Updates
- •Deploy a Tunneled IPv6 Infrastructure with ISATAP
- •Upgrade IPv4-Only Hosts to IPv6/IPv4 Hosts
- •Begin Deploying a Native IPv6 Infrastructure
- •Connect Portions of Your Intranet over the IPv4 Internet
- •Connect Portions of Your Intranet over the IPv6 Internet
- •Summary
- •References
- •Testing for Understanding
- •Basic Structure of IPv6 Packets
- •LAN Media
- •Ethernet: Ethernet II
- •Ethernet: IEEE 802.3 SNAP
- •Token Ring: IEEE 802.5 SNAP
- •FDDI
- •IEEE 802.11
- •WAN Media
- •Frame Relay
- •ATM: Null Encapsulation
- •ATM: SNAP Encapsulation
- •IPv6 over IPv4
- •References
- •Added Constants
- •Address Data Structures
- •in6_addr
- •sockaddr_in6
- •sockaddr_storage
- •Wildcard Addresses
- •in6addr_loopback and IN6ADDR_LOOPBACK_INIT
- •Core Sockets Functions
- •Name-to-Address Translation
- •Address-to-Name Translation
- •Using getaddrinfo
- •Address Conversion Functions
- •Socket Options
- •New Macros
- •References
- •General
- •Addressing
- •Applications
- •Sockets API
- •Transport Layer
- •Internet Layer
- •Network Layer Security
- •Link Layer
- •Routing
- •IPv6 Transition Technologies
- •Chapter 1: Introduction to IPv6
- •Chapter 2: IPv6 Protocol for Windows Server 2008 and Windows Vista
- •Chapter 3: IPv6 Addressing
- •Chapter 4: The IPv6 Header
- •Chapter 5: ICMPv6
- •Chapter 6: Neighbor Discovery
- •Chapter 8: Address Autoconfiguration
- •Chapter 9: IPv6 and Name Resolution
- •Chapter 10: IPv6 Routing
- •Chapter 11: IPv6 Transition Technologies
- •Chapter 12: ISATAP
- •Chapter 13: 6to4
- •Chapter 14: Teredo
- •Chapter 15: IPv6 Security Considerations
- •Chapter 16: Deploying IPv6
- •IPv6 Test Lab Setup
- •CLIENT1
- •ROUTER1
- •ROUTER2
- •CLIENT2
- •IPv6 Test Lab Tasks
- •Performing Link-Local Pings
- •Enabling Native IPv6 Connectivity on Subnet 1
- •Configuring ISATAP
- •Configuring Native IPv6 Connectivity for All Subnets
- •Using Name Resolution
- •Configuring an IPv6-Only Routing Infrastructure
- •Overview
- •Mobile IPv6 Components
- •Mobile IPv6 Transport Layer Transparency
- •Mobile IPv6 Messages and Options
- •Mobility Header and Messages
- •Type 2 Routing Header
- •Home Address Option for the Destination Options Header
- •ICMPv6 Messages for Mobile IPv6
- •Modifications to Neighbor Discovery Messages and Options
- •Mobile IPv6 Data Structures
- •Binding Cache
- •Binding Update List
- •Home Agents List
- •Correspondent Registration
- •Return Routability Procedure
- •Detecting Correspondent Nodes That Are Not Mobile IPv6–Capable
- •Mobile IPv6 Message Exchanges
- •Data Between a Mobile Node and a Correspondent Node
- •Binding Maintenance
- •Home Agent Discovery
- •Mobile Prefix Discovery
- •Mobile IPv6 Processes
- •Attaching to the Home Link
- •Moving from the Home Link to a Foreign Link
- •Moving to a New Foreign Link
- •Returning Home
- •Mobile IPv6 Host Sending Algorithm
- •Mobile IPv6 Host Receiving Algorithm
- •References
- •Glossary
- •Index
- •About the Author
- •System Requirements

130 Understanding IPv6, Second Edition
+ RouterAdvertisement:
- SourceLinkLayerAddress:
Type: Source Link-Layer Address, 1(0x1) Length: 1, in unit of 8 octets
Address: 00-B0-D0-23-47-33
+MTU:
+PrefixInformation: - PrefixInformation:
Type: Prefix Information, 3(0x3) Length: 4, in unit of 8 octets PrefixLength: 64 (0x40)
-Flags: 192 (0xC0)
L:(1.......) On-Link determination allowed
A:(.1......) Autonomous address-configuration
R:(..0.....) Not router Address
S:(...0....) Not a site prefix
P: (....0...) Not a router prefix
Rsv: (.....000)
ValidLifetime: 4294967295 (0xFFFFFFFF)
PreferredLifetime: 4294967295 (0xFFFFFFFF)
Reserved: 0 (0x0)
Prefix: FD43:2DA1:3FE9:2:0:0:0:0
Redirected Header Option
The Redirected Header option is sent in Redirect messages to specify the IPv6 packet that caused the router to send a Redirect message. It can contain all or part of the redirected IPv6 packet, depending on the size of the IPv6 packet that was initially sent.
Figure 6-7 shows the structure of the Redirected Header option.
Type = 4
Length
Reserved
Portion of Redirected Packet
• • •
Figure 6-7 The structure of the Redirected Header option
The following list describes the fields in the Redirected Header option:
■Type The value of this field is 4.
■Length The value of this field is the number of 8-byte blocks in the entire option.
■Reserved The Reserved field is a 48-bit field reserved for future use and set to 0.
■Portion of redirected packet This field contains either the IPv6 packet or a portion of the IPv6 packet that caused the Redirect message to be sent. The amount of the original packet that is included is the leading portion of the packet so that the entire Redirect message is no more than 1280 bytes in length.
Chapter 6 Neighbor Discovery |
131 |
Network Monitor Capture
Here is an example of a Redirected Header option used in a Redirect message as displayed by Network Monitor 3.1 (capture 06_03 in the \NetworkMonitorCaptures folder on the companion CD-ROM):
Frame:
+Ethernet: Etype = IPv6
+Ipv6: Next Protocol = ICMPv6, Payload Length = 128
- Icmpv6: Redirect, Target = FE80:0:0:0:2B0:D0FF:FE23:4735
MessageType: Redirect, 137(0x89)
-Redirect: Code: 0 (0x0)
Checksum: 31003 (0x791B) Reserved: 0 (0x0)
TargetAddress: FE80:0:0:0:2B0:D0FF:FE23:4735 DestAddress: 2001:DB8:0:0:0:0:0:1
-RedirectedHeader:
Type: Redirected Header, 4(0x4)
Length: 11, in unit of 8 octets
Reserved: 0 |
(0x0) |
|
|
- InvokingPacket: Next Protocol = ICMPv6, Payload Length = 40 |
|||
- Versions: IPv6, Internet Protocol, DSCP 0 |
|||
Version: |
(0110 |
............................ |
) IPv6, Internet Protocol, |
6(0x6) |
|
|
|
DSCP: |
(.... |
000000...................... |
) Differentiated services |
codepoint 0 |
|
|
|
ECT: |
(.......... |
0..................... |
) ECN-Capable Transport not |
set |
|
|
|
CE: |
(........... |
0.................... |
) ECN-CE not set |
FlowLabe: |
(............ |
|
00000000000000000000) 0 |
PayloadLength: 40 (0x28)
NextProtocol: ICMPv6, 58(0x3a)
HopLimit: 128 (0x80)
SourceAddress: FE80:0:0:0:260:8FF:FE52:F9D8
DestinationAddress: 3000:0:0:0:0:0:0:1
OriginalIPPayload: Binary Large Object (40 Bytes)
MTU Option
The MTU option is sent in Router Advertisement messages to indicate the IPv6 MTU of the link. This option is typically used when the IPv6 MTU for a link is not well known or needs to be set because of a translational or mixed-media bridging configuration. The MTU option overrides the IPv6 MTU reported by the interface hardware.
In bridged or Layer-2 switched environments, it is possible to have different link-layer technologies with different link-layer MTUs on the same link. In this case, differences in IPv6 MTUs between nodes on the same link are not detected through Path MTU Discovery. The MTU option is used to indicate the highest IPv6 MTU supported by all link-layer technologies on the link.

132 Understanding IPv6, Second Edition
Figure 6-8 shows a switched configuration where the MTU option is used to solve a mixedmedia problem.
Host A
Ethernet Switch |
IPv6 Router |
FDDI
Ethernet
Backbone
FDDI |
Rest of IPv6 Network |
Ethernet Switch
Host B
Figure 6-8 A mixed-media configuration
Two IPv6 hosts, Host A and Host B, are connected to two different Ethernet (Layer 2) switches using Fiber Distributed Data Interface (FDDI) ports. The two switches are connected by an Ethernet backbone. When Host A and Host B negotiate a TCP connection, each reports a TCP maximum segment size of 4312 (the FDDI IPv6 MTU of 4352, minus 40 bytes of the IPv6 header). However, when TCP data on the connection begins to flow, the switches silently discard IPv6 packets larger than 1500 bytes that are sent between Host A and Host B.
With the MTU option, the IPv6 router for the subnet reports an IPv6 MTU of 1500 in the Router Advertisement message for all hosts on the link. When both Host A and Host B adjust their IPv6 MTU from 4352 to 1500, maximum-sized TCP segments sent between them are not discarded by the intermediate switches.
Note FDDI is an older technology whose use has been made obsolete by 100-Mbps Ethernet. This configuration is unlikely to be used on modern networks and serves only as an example of a mixed-media subnet.
Figure 6-9 shows the structure of the MTU option.
Type = 5
Length = 1
Reserved
MTU
Figure 6-9 The structure of the MTU option
The following list describes the fields in the MTU option:
■Type The value of this field is 5.
■Length The value of this field is 1. (There are 8 bytes in the entire option.)

Chapter 6 Neighbor Discovery |
133 |
■Reserved The Reserved field is a 16-bit field reserved for future use and set to 0.
■MTU The MTU field indicates the IPv6 MTU that should be used by the host for the link on which the Router Advertisement was received. The size of this field is 32 bits. The value in the MTU field is ignored if it is larger than the link MTU.
Network Monitor Capture
Here is an example of an MTU option used in a Router Advertisement message as displayed by Network Monitor 3.1 (capture 06_02 in the \NetworkMonitorCaptures folder on the companion CD-ROM):
Frame:
+Ethernet: Etype = IPv6
+Ipv6: Next Protocol = ICMPv6, Payload Length = 96 - Icmpv6: Router Advertisement
MessageType: Router Advertisement, 134(0x86)
+ RouterAdvertisement:
- SourceLinkLayerAddress:
Type: Source Link-Layer Address, 1(0x1) Length: 1, in unit of 8 octets
Address: 00-B0-D0-23-47-33 - MTU:
Type: MTU, 5(0x5)
Length: 1, in unit of 8 octets Reserved: 0 (0x0)
MTU: 1500 (0x5DC)
+PrefixInformation:
+PrefixInformation:
Route Information Option
The Route Information option is sent in Router Advertisement messages to specify individual routes for receiving hosts to add to their local routing table. The Route Information option is described in RFC 4191.
Figure 6-10 shows the structure of the Route Information option.
Type |
= 24 |
Length |
|
Prefix Length |
|
Reserved1 |
|
Preference |
|
Reserved2 |
|
Route Lifetime
Prefix
Figure 6-10 The structure of the Route Information option
134 Understanding IPv6, Second Edition
The fields in the Route Information option are as follows:
■Type The value of this field is 24.
■Length The value of the Length field depends on the prefix length of the route and the corresponding size of the Prefix field. If the prefix length is 0 (and there is no Prefix field), the value of the Length field is 1. If the prefix length is greater than 0 and less than 65, the length of the Prefix field is 64 bits and the value of the Length field is 2. If the prefix length is greater than 64, the length of the Prefix field is 128 bits and the value of the Length field is 3.
■Prefix Length The Prefix Length field indicates the number of leading bits in the Prefix field that are significant for the route. Valid values range from 0 through 128. The size of this field is 8 bits.
■Reserved1 The Reserved1 field is a 3-bit field reserved for future use and set to 0.
■Preference The Preference field indicates the level of preference for this route as sent from the advertising router. If multiple routers advertise the same prefix using a Route Information option, you can configure the routers so that they advertise the route with different preference levels. Valid values in binary are 01 (High), 00 (Medium), and 11 (Low). The size of this field is 2 bits.
■Reserved2 The Reserved2 field is a 3-bit field reserved for future use and set to 0.
■Route Lifetime The Route Lifetime field indicates the amount of time in seconds that the prefix is valid for route determination. The size of this field is 32 bits. For an infinite route lifetime, the Route Lifetime field is set to 0xFFFFFFFF.
■Prefix The Prefix field indicates the route prefix. The size of the Prefix field can be 0, 64, or 128 bits, depending on the value of the Prefix Length field. If the prefix length is 0, the size of the Prefix field is 0. If the prefix length is greater than 0 and less than 65, the size of the Prefix field is 64 bits. If the prefix length is greater than 64, the size of the Prefix field is 128 bits. The prefix length indicates the number of high-order bits in the prefix that are relevant for route determination. All bits in the Prefix field past the prefix length must be set to 0.
A typical use of the Route Information option is to enable hosts to make better forwarding decisions when sending data. Figure 6-11 shows a simple network configuration where the Route Information option can be useful.
Without the Route Information option, you would typically configure the routers so that only Router 1 advertises itself as a default router on Subnet 1. Hosts on Subnet 1 sending traffic to hosts on Subnet 2 would have to rely on Redirect messages from Router 1 to inform them that the best next-hop address to reach hosts on Subnet 2 is actually Router 2. For more information, see the “Redirect Function” section in this chapter.