9.On the Scope Lease page, specify the non-temporary and temporary address preferred and valid lifetimes as needed. Click Next.

10.On the Completing The New Scope Wizard page, click Finish.

When the scope is created, you can configure scope-specific DHCPv6 options by right-clicking Scope Options within the scope, and then clicking Configure Options.

IPv6 Protocol for Windows Server 2008 and Windows Vista Autoconfiguration Specifics

The following are the specific autoconfiguration behaviors of IPv6 in Windows Server 2008 and Windows Vista:

■Computers running Windows Server 2008 or Windows Vista by default generate random interface IDs for non-temporary autoconfigured IPv6 addresses, including public and link-local addresses, rather than using EUI-64–based interface IDs. A public IPv6 address is a global address that is registered in DNS and is typically used by server applications for incoming connections, such as a Web server. You can disable this default behavior with the netsh interface ipv6 set global randomizeidentifiers=disabled command. You can enable the default behavior with the netsh interface ipv6 set global randomizeidentifiers=enabled command.

■With a randomly derived interface ID, the chance of duplicating the link-local address is very small. Therefore, computers running Windows Server 2008 or Windows Vista do not wait for duplicate address detection (DAD) to complete before sending router solicitations or multicast listener discovery reports using their derived link-local addresses. This is known as optimistic DAD.

■Computers running Windows Server 2008 or Windows Vista do not attempt stateful address autoconfiguration with DHCPv6 if no router advertisements are received.

■RFC 4862 does not require a specific order for sending the initial router solicitation and performing duplicate address detection for the derived link-local address. The IPv6 protocol for Windows Server 2008 and Windows Vista sends the Router Solicitation message before performing duplicate address detection on the link-local address. In this way, duplicate address detection and router discovery are done in parallel to save time during the interface initialization process.

■If the derived link-local address is a duplicate, stateless address autoconfiguration for the IPv6 protocol for Windows Server 2008 and Windows Vista can continue with the receipt of a multicast Router Advertisement message containing site-local, unique local, or global prefixes. The attempted link-local address is shown with a “Duplicate” state in the display of the netsh interface ipv6 show address command and a site-local, unique local, or global address—rather than the duplicate link-local address—is used for neighbor discovery processes.

206 Understanding IPv6, Second Edition

Autoconfigured Addresses for the IPv6 Protocol for Windows Server 2008 and Windows Vista

By default, the following IPv6 addresses are automatically configured for the IPv6 protocol for Windows Server 2008 and Windows Vista:

■Link-local addresses using randomly derived interface identifiers are assigned to all local area network (LAN) interfaces.

■If included as a site-local prefix in a Prefix Information option of a router advertisement with the Autonomous flag set to 1, a site-local address using a randomly derived interface identifier is assigned to the LAN interface that received the router advertisement.

■If included as a global or unique local prefix in a Prefix Information option of a router advertisement with the Autonomous flag set to 1, a global or unique local address using a randomly derived permanent interface identifier is assigned to the LAN interface that received the router advertisement.

■If included as a global or unique local prefix in a Prefix Information option of a router advertisement with the Autonomous flag set to 1, a temporary global or unique local address using a randomly derived temporary interface identifier is assigned to the LAN interface that received the router advertisement. This is the default behavior for Windows Vista. Window Server 2008 does not create temporary addresses by default. You can enable temporary addresses with the netsh interface ipv6 set privacy enabled command.

■If the M flag is set to 1 in a received Router Advertisement message, a stateful IPv6 address based on DHCPv6 scope for the subnet is assigned to the LAN interface that received the DHCPv6 Reply message.

■If public IPv4 addresses are assigned to interfaces of the computer and there are no global or unique local autoconfiguration prefixes received in Router Advertisement messages, corresponding 6to4 addresses using 6to4-derived interface identifiers are assigned to the 6to4 tunneling interface. 6to4 is described in RFC 3056.

■For computers running Windows Vista, for all IPv4 addresses that are assigned to interfaces of the computer, corresponding link-local addresses using Intra-Site Automatic Tunnel Addressing Protocol (ISATAP)–derived interface identifiers (::0:5EFE:w.x.y.z or ::200:5EFE:w.x.y.z) are assigned to the ISATAP tunneling interface. ISATAP is described in RFC 4214.

■If included as a global, unique local, or site-local prefix in a Prefix Information option of a router advertisement received on the ISATAP interface, a global, unique local, or sitelocal address using the ISATAP-derived interface identifier corresponding to the IPv4 address that is the best source to use to reach the ISATAP router is assigned to the ISATAP interface.

■The loopback address (::1) is assigned to the Loopback Pseudo-Interface 1.

Note To receive a Router Advertisement message from an ISATAP router, by default the host must be able to resolve the name “isatap” to an IPv4 address. This is done through normal name resolution mechanisms, including DNS and NetBIOS over TCP/IP name queries. Once resolved, the host sends a Router Solicitation message encapsulated in an IPv4 header to the ISATAP router. The ISATAP router then sends a Router Advertisement message encapsulated in an IPv4 header to the host. Computers running Windows Server 2008 or Windows Vista with Service Pack 1 will not automatically create an ISATAP tunneling interface or assign it link-local ISATAP addresses unless the name “isatap” is resolved to an IPv4 address.

For more information about ISATAP, see Chapter 12, “ISATAP.” For more information about 6to4, see Chapter 13, “6to4.”

The following is an example of the display of the netsh interface ipv6 show address command for a host running Windows Vista that received a Router Advertisement message containing the prefixes fd4a:3a9:27a1:f282::/64 and 2001:db8:d005:f282::/64 with both the M and O flags set to 0 on its LAN interface (interface index 8):

Interface 1: Loopback Pseudo-Interface 1

Note In this example display, the ISATAP interface is named “Local Area Connection* 9.”

In addition to autoconfigured addresses, the IPv6 protocol for Windows Server 2008 and Windows Vista also supports manual configuration of IPv6 addresses through the properties of the Internet Protocol Version 6 (TCP/IPv6) component in the Network Connections folder and with the netsh interface ipv6 add address command. For more information, see Chapter 2, “IPv6 Protocol for Windows Server 2008 and Windows Vista .”