List of Figures
Figure 1-1: A NAT example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Figure 1-2: NATs and peer-to-peer applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Figure 1-3: Elements of an IPv6 network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Figure 1-4: An IPv6-capable organization network and the IPv4 and IPv6 Internets. . . . 11
Figure 2-1: The architecture of the TCP/IP protocols for Windows Server 2008
and Windows Vista . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Figure 2-2: The Internet Protocol Version 6 (TCP/IPv6) Properties dialog box . . . . . . . . . 31
Figure 2-3: The IP Settings tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Figure 2-4: The DNS tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Figure 3-1: The structure of global unicast addresses defined in RFC 3587 . . . . . . . . . . . 54
Figure 3-2: The topological structure of the global address . . . . . . . . . . . . . . . . . . . . . . . . 55
Figure 3-3: The structure of the link-local address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Figure 3-4: The structure of the site-local address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Figure 3-5: The structure of the unique local address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Figure 3-6: The structure of the IPv6 multicast address . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Figure 3-7: The mapping of a unicast address to its solicited-node multicast address . . 63
Figure 3-8: The mapping of IPv6 multicast addresses to Ethernet multicast addresses. . 64
Figure 3-9: The structure of the Subnet-Router anycast address. . . . . . . . . . . . . . . . . . . . . 65
Figure 3-10: The subnetting of a subnet ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Figure 3-11: The structure of the 48-bit IEEE 802 address for Ethernet . . . . . . . . . . . . . . . 74
Figure 3-12: The structure of the EUI-64 address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Figure 3-13: The mapping of IEEE 802 addresses to EUI-64 addresses . . . . . . . . . . . . . . . 75
Figure 3-14: The conversion of an EUI-64 address to an IPv6 interface identifier . . . . . . 76
Figure 3-15: The conversion of an IEEE 802 address to an IPv6 interface identifier. . . . . 77
Figure 4-1: The structure of an IPv6 packet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Figure 4-2: The structure of the IPv4 header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Figure 4-3: The structure of the IPv6 header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Figure 4-4: The chain of pointers formed by the Next Header field. . . . . . . . . . . . . . . . . . 92
Figure 4-5: The structure of the Hop-by-Hop Options header . . . . . . . . . . . . . . . . . . . . . . 93
Figure 4-6: The structure of an option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Figure 4-7: The structure of the Pad1 option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Figure 4-8: The structure of the PadN option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
xxi
xxii List of Figures
Figure 4-9: The structure of the Jumbo Payload option. . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Figure 4-10: The structure of the Router Alert option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Figure 4-11: The structure of the Destination Options header . . . . . . . . . . . . . . . . . . . . . . 97
Figure 4-12: The structure of the Home Address option . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Figure 4-13: The structure of the Routing header. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Figure 4-14: The structure of the Routing Type 0 header . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Figure 4-15: The structure of the Fragment header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Figure 4-16: The IPv6 fragmentation process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Figure 4-17: The IPv6 reassembly process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Figure 4-18: The structure of the Authentication header. . . . . . . . . . . . . . . . . . . . . . . . . . 105
Figure 4-19: The structure of the Encapsulating Security Payload header and trailer. . 105
Figure 4-20: The structure of the new IPv6 pseudo-header . . . . . . . . . . . . . . . . . . . . . . . 107
Figure 5-1: The structure of ICMPv6 messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Figure 5-2: The structure of the Destination Unreachable message. . . . . . . . . . . . . . . . . 111
Figure 5-3: The structure of the Packet Too Big message . . . . . . . . . . . . . . . . . . . . . . . . . 113
Figure 5-4: The structure of the Time Exceeded message . . . . . . . . . . . . . . . . . . . . . . . . . 114
Figure 5-5: The structure of the Parameter Problem message . . . . . . . . . . . . . . . . . . . . . 115
Figure 5-6: The structure of the Echo Request message . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Figure 5-7: The structure of the Echo Reply message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Figure 5-8: The PMTU discovery process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Figure 6-1: The format of an ND message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Figure 6-2: The TLV format for ND options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Figure 6-3: The structure of the Source Link-Layer Address option . . . . . . . . . . . . . . . . . 126
Figure 6-4: The structure of the Target Link-Layer Address option. . . . . . . . . . . . . . . . . . 127
Figure 6-5: The Target Link-Layer Address option for Ethernet. . . . . . . . . . . . . . . . . . . . . 127
Figure 6-6: The structure of the Prefix Information option . . . . . . . . . . . . . . . . . . . . . . . . 128
Figure 6-7: The structure of the Redirected Header option. . . . . . . . . . . . . . . . . . . . . . . . 130
Figure 6-8: A mixed-media configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Figure 6-9: The structure of the MTU option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Figure 6-10: The structure of the Route Information option. . . . . . . . . . . . . . . . . . . . . . . 133
Figure 6-11: An example configuration in which the Route Information option is used . 135
Figure 6-12: The structure of the Router Solicitation message . . . . . . . . . . . . . . . . . . . . . 136
Figure 6-13: The structure of the Router Advertisement message. . . . . . . . . . . . . . . . . . 138
Figure 6-14: The structure of the Neighbor Solicitation message . . . . . . . . . . . . . . . . . . 141
Figure 6-15: The structure of the Neighbor Advertisement message . . . . . . . . . . . . . . . 143
List of Figures |
xxiii |
Figure 6-16: The structure of the Redirect message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .145
Figure 6-17: The conceptual host data structures defined in RFC 4861. . . . . . . . . . . . . .148
Figure 6-18: The multicast Neighbor Solicitation message . . . . . . . . . . . . . . . . . . . . . . . .150
Figure 6-19: The unicast Neighbor Advertisement message . . . . . . . . . . . . . . . . . . . . . . .151
Figure 6-20: The states of a neighbor cache entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153
Figure 6-21: A multicast Neighbor Solicitation message for duplicate
address detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157
Figure 6-22: The multicast Neighbor Advertisement message . . . . . . . . . . . . . . . . . . . . .158
Figure 6-23: The multicast Router Solicitation message . . . . . . . . . . . . . . . . . . . . . . . . . . .161
Figure 6-24: The unicast Router Advertisement message. . . . . . . . . . . . . . . . . . . . . . . . . .162
Figure 6-25: The unicast packet sent to the router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165
Figure 6-26: The Redirect message sent by the router . . . . . . . . . . . . . . . . . . . . . . . . . . . .166
Figure 6-27: The unicast packet forwarded by the router . . . . . . . . . . . . . . . . . . . . . . . . .166
Figure 6-28: The host sending algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168
Figure 7-1: The structure of an MLD message packet. . . . . . . . . . . . . . . . . . . . . . . . . . . . .176
Figure 7-2: The structure of the Multicast Listener Query message . . . . . . . . . . . . . . . . .178
Figure 7-3: The structure of the Multicast Listener Report message. . . . . . . . . . . . . . . . .179
Figure 7-4: The structure of the Multicast Listener Done message. . . . . . . . . . . . . . . . . .181
Figure 7-5: The structure of the modified Multicast Listener Query message. . . . . . . . .183
Figure 7-6: The structure of the MLDv2 Multicast Listener Report message. . . . . . . . . .185
Figure 7-7: The structure of the multicast address record . . . . . . . . . . . . . . . . . . . . . . . . .186
Figure 8-1: The states of an autoconfigured address . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193
Figure 8-2: The address autoconfiguration process for a host (Part 1). . . . . . . . . . . . . . .195
Figure 8-3: The address autoconfiguration process for a host (Part 2). . . . . . . . . . . . . . .196
Figure 8-4: DHCPv6 messages between client and server . . . . . . . . . . . . . . . . . . . . . . . . .198
Figure 8-5: DHCPv6 options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199
Figure 8-6: DHCPv6 messages between relay agent and server . . . . . . . . . . . . . . . . . . . .200
Figure 8-7: The DHCPv6 Relay Agent Properties dialog box . . . . . . . . . . . . . . . . . . . . . . .203
Figure 8-8: The Scope Prefix page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .204
Figure 9-1: The LLMNR message format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .211
Figure 9-2: The LLMNR header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .212
Figure 9-3: The flags and indicators in the LLMNR header . . . . . . . . . . . . . . . . . . . . . . . .212
Figure 9-4: The New Host dialog box for AAAA records . . . . . . . . . . . . . . . . . . . . . . . . . .223
Figure 10-1: The sending host process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .240
Figure 10-2: Router forwarding process (part 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242
xxiv List of Figures
Figure 10-3: Router forwarding process (part 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Figure 10-4: Receiving host process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
Figure 10-5: Example configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Figure 11-1: A dual IP layer architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
Figure 11-2: Types of packets with a dual IP layer architecture . . . . . . . . . . . . . . . . . . . . 263
Figure 11-3: The dual-stack architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Figure 11-4: Types of packets with a dual-stack architecture . . . . . . . . . . . . . . . . . . . . . . 264
Figure 11-5: IPv6-over-IPv4 tunneling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Figure 11-6: Router-to-router tunneling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Figure 11-7: Host-to-router and router-to-host tunneling . . . . . . . . . . . . . . . . . . . . . . . . 269
Figure 11-8: Host-to-host tunneling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Figure 11-9: Manually configured tunneling example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Figure 12-1: An example ISATAP configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Figure 12-2: Components of ISATAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Figure 12-3: Performing router discovery with an ISATAP router. . . . . . . . . . . . . . . . . . . 282
Figure 12-4: ISATAP addressing example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
Figure 12-5: ISATAP routing example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
Figure 12-6: Example of ISATAP host to ISATAP host communication. . . . . . . . . . . . . . . 288
Figure 12-7: ISATAP host to IPv6 host communication–Part 1 . . . . . . . . . . . . . . . . . . . . . 289
Figure 12-8: ISATAP host to IPv6 host communication–Part 2 . . . . . . . . . . . . . . . . . . . . . 290
Figure 13-1: The structure of a 6to4 address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
Figure 13-2: An example 6to4 configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Figure 13-3: 6to4 components on the IPv4 and IPv6 Internets. . . . . . . . . . . . . . . . . . . . . 299
Figure 13-4: An example of a 6to4 configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
Figure 13-5: A 6to4 routing example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
Figure 13-6: An example configuration for a manually configured 6to4 router . . . . . . 306
Figure 13-7: 6to4 host to 6to4 host/router communication—Part 1. . . . . . . . . . . . . . . . 307
Figure 13-8: 6to4 host to 6to4 host/router communication—Part 2. . . . . . . . . . . . . . . . 308
Figure 13-9: 6to4 host to IPv6 host communication—Part 1 . . . . . . . . . . . . . . . . . . . . . . 309
Figure 13-10: 6to4 host to IPv6 host communication—Part 2 . . . . . . . . . . . . . . . . . . . . . 310
Figure 13-11: 6to4 host to IPv6 host communication—Part 3 . . . . . . . . . . . . . . . . . . . . . 310
Figure 13-12: Communication between ISATAP hosts in different 6to4 sites. . . . . . . . . 313
Figure 14-1: Components of the Teredo infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
Figure 14-2: Teredo address format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Figure 14-3: Teredo addressing example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
List of Figures |
xxv |
Figure 14-4: Teredo data packet format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .329
Figure 14-5: Teredo bubble packet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .329
Figure 14-6: Structure of the Authentication indicator. . . . . . . . . . . . . . . . . . . . . . . . . . . .330
Figure 14-7: Structure of the Authentication indicator when there is no
client identifier or authentication value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .331
Figure 14-8: Structure of the Origin indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .331
Figure 14-9: Types of packets containing the Authentication or Origin indicators . . . .332
Figure 14-10: Teredo routes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .333
Figure 14-11: Initial configuration for Teredo clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . .335
Figure 14-12: Maintaining the NAT mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .339
Figure 14-13: Initial communication between Teredo clients on the same link . . . . . . .340
Figure 14-14: Initial communication between Teredo clients in different sites
with cone NATs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .341
Figure 14-15: Initial communication between Teredo clients in different sites
with restricted NATs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .342
Figure 14-16: Initial communication from a Teredo client to a Teredo
host-specific relay with a cone NAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .343
Figure 14-17: Initial communication from a Teredo client to a Teredo
host-specific relay with a restricted NAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .344
Figure 14-18: Initial communication from a Teredo host-specific relay to
a Teredo client with a cone NAT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .346
Figure 14-19: Initial communication from a Teredo host-specific relay to
a Teredo client with a restricted NAT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .346
Figure 14-20: Initial communication from a Teredo client to an IPv6-only host with
a cone NAT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .348
Figure 14-21: Initial communication from a Teredo client to an IPv6-only host
with a restricted NAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .349
Figure 14-22: Initial communication from an IPv6-only host to a Teredo
client with a cone NAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .351
Figure 14-23: Initial communication from an IPv6-only host to a Teredo client with a restricted NAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .352
Figure A-1: Basic structure of IPv6 packets sent on LAN and WAN media . . . . . . . . . . .381
Figure A-2: Ethernet II encapsulation of IPv6 packets. . . . . . . . . . . . . . . . . . . . . . . . . . . . .382
Figure A-3: Ethernet IEEE 802.3 SNAP encapsulation of IPv6 packets . . . . . . . . . . . . . . .383
Figure A-4: IEEE 802.5 SNAP encapsulation of IPv6 packets . . . . . . . . . . . . . . . . . . . . . . .385
Figure A-5: FDDI encapsulation of IPv6 packets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .387
Figure A-6: IEEE 802.11 encapsulation of IPv6 packets. . . . . . . . . . . . . . . . . . . . . . . . . . . .389
xxvi |
List of Figures |
|
|
Figure A-7: The Frame Control field in the IEEE 802.11 header . . . . . . . . . . . . . . . |
. . . . . 390 |
|
Figure A-8: PPP with HDLC framing encapsulation of IPv6 packets . . . . . . . . . . . |
. . . . . 392 |
|
Figure A-9: X.25 encapsulation of IPv6 packets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . |
. . . . . 394 |
|
Figure A-10: Frame Relay encapsulation of IPv6 packets. . . . . . . . . . . . . . . . . . . . . |
. . . . . 395 |
|
Figure A-11: ATM null encapsulation of IPv6 packets . . . . . . . . . . . . . . . . . . . . . . . |
. . . . . 397 |
|
Figure A-12: ATM SNAP encapsulation of IPv6 packets . . . . . . . . . . . . . . . . . . . . . . |
. . . . . 398 |
|
Figure A-13: IPv4 encapsulation of IPv6 packets. . . . . . . . . . . . . . . . . . . . . . . . . . . . |
. . . . . 399 |
|
Figure E-1: The configuration of the IPv6 test lab. . . . . . . . . . . . . . . . . . . . . . . . . . . |
. . . . . 442 |
|
Figure F-1: Components of Mobile IPv6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . |
. . . . . 454 |
|
Figure F-2: Structure of the Mobility extension header . . . . . . . . . . . . . . . . . . . . . . |
. . . . . 456 |
|
Figure F-3: The structure of the new Type 2 Routing header . . . . . . . . . . . . . . . . . |
. . . . . 458 |
|
Figure F-4: The structure of Home Address destination option . . . . . . . . . . . . . . . |
. . . . . 459 |
|
Figure F-5: The structure of ICMPv6 Home Agent Address Discovery |
|
|
Request message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . |
. . . . . 460 |
|
Figure F-6: The structure of the ICMPv6 Home Agent Address Discovery |
|
|
Reply message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . |
. . . . . 461 |
|
Figure F-7: The structure of the ICMPv6 Mobile Prefix Solicitation message . . . |
. . . . . 462 |
|
Figure F-8: The structure of the ICMPv6 Mobile Prefix Advertisement message |
. . . . . 462 |
|
Figure F-9: The structure of the modified Router Advertisement message . . . . . |
. . . . . 463 |
|
Figure F-10: The structure of the modified Prefix Information option . . . . . . . . . |
. . . . . 464 |
|
Figure F-11: The structure of the Advertisement Interval option . . . . . . . . . . . . . |
. . . . . 464 |
|
Figure F-12: The structure of the Home Agent Information option . . . . . . . . . . . |
. . . . . 465 |
|
Figure F-13: The Return Routability procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . |
. . . . . 469 |
|
Figure F-14: Data packets sent by a correspondent node to the mobile |
|
|
node’s home address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . |
. . . . . 472 |
|
Figure F-15: Intercepted packet tunneled to a mobile node by its home agent |
. . . . . 473 |
|
Figure F-16: Tunneled packets to a home agent . . . . . . . . . . . . . . . . . . . . . . . . . . . |
. . . . . 474 |
|
Figure F-17: Forwarded packet from a home agent to a correspondent node . . |
. . . . . 475 |
|
Figure F-18: Data sent from the mobile node to the correspondent node . . . . . |
. . . . . 476 |
|
Figure F-19: Data sent from the correspondent node when a binding cache |
|
|
entry for the mobile node is present . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . |
. . . . . 477 |
|
Figure F-20: Binding updates sent from the mobile node to the home agent . . . |
. . . . 479 |
|
Figure F-21: Binding maintenance packets sent from the home agent to |
|
|
the mobile node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . |
. . . . 480 |
|
Figure F-22: Binding updates sent from the mobile node to the correspondent node 481 |
|
List of Figures |
xxvii |
Figure F-23: Binding maintenance packets sent from the correspondent
node to the mobile node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .482
Figure F-24: ICMPv6 Home Agent Address Discovery Request message sent
from the mobile node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .483
Figure F-25: ICMPv6 Home Agent Address Discovery Reply message sent from
the home agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .484
Figure F-26: ICMPv6 Mobile Prefix Solicitation message sent from the mobile node .485
Figure F-27: ICMPv6 Mobile Prefix Advertisement message sent from the mobile node 486
Figure F-28: Mobile node attaching to the first foreign link . . . . . . . . . . . . . . . . . . . . . . .490
Figure F-29: A mobile node initiating a new TCP connection with
a new correspondent node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .492
Figure F-30: A new correspondent node communicating with a mobile node . . . . . . .494
Figure F-31: A node on the home link communicating with the mobile node . . . . . . .495
Figure F-32: A mobile node changing its home address . . . . . . . . . . . . . . . . . . . . . . . . . .497
Figure F-33: A mobile node attaching to a new foreign link . . . . . . . . . . . . . . . . . . . . . .498
Figure F-34: A mobile node returning home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .501
Figure F-35: The Mobile IPv6 host sending algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . .504
Figure F-36: The Mobile IPv6 host receiving algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . .507