DHCPv6 Stateless Clients obtain configuration data from DHCP Server, by sending Information-request messages. The configuration data typically has no associated lifetime, hence there is no information telling a host when to refresh its configuration information. DHCPv6 Information-Refresh time option...

RFC3315 specifies User Class Option for IPv6 hosts. DHCP administrators may define specific user class identifiers to convey information about a client's software configuration or about its user's preferences. User classes are created to support the implementation of various scenarios like: To...

Understanding of address configuration in automatic mode Windows Server 2008 and Windows Vista include a DHCPv6-capable DHCP client that will perform stateful address autoconfiguration with a DHCPv6 server. Windows Server 2008 includes a DHCPv6-capable DHCP server. A host (DHCP Client...

In a previous post, I had discussed the DHCPv6 client behaviour in Windows Vista . A few customers who're evaluating IPv6 in Windows Vista responded asking about the support for DHCPv6 Prefix Delegation and/or asked why the Vista DHCPv6 client doesn't request an IPv6 subnet prefix by default. In most...

In Windows Server 2008 (WS08), Microsoft has introduced DHCPv6 functionality to the DHCP server. In Windows Server 2008 (previously known as "Longhorn" Server) Beta 2, we released the DHCPv6 Stateless Server functionality. In Beta 3, we are introducing the DHCPv6 Stateful Server functionality....

Windows Vista introduces support for DHCPv6. The DHCPv6 client implementation in Windows Vista is compliant with RFC 3315. It supports 2 modes of operation: a stateless mode and a stateful mode of operation. DHCPv6 Stateless mode is where the host uses a non-DHCPv6 method to obtain an IPv6 address...