Why doesn't Windows support RFC 6106 and when will it support it?
That’s a good question. RFC 6106 is intended for configuring DNS server addresses in environments that don’t have DHCP servers. We don’t see any demand for it, however, for several reasons.
First, much of the perceived complexity associated with stateful DHCP has been mitigated with stateless DHCP implementations (RFC 3736).
Second, the requirements for customer premise equipment (RFC 6204) specify DHCPv6 support as a MUST have, and DHCP is important for lots of other reasons – such as assigning DNS servers. In other words, most people are going to need to deploy a DHCPv6 server anyway even if they don’t want it for assigning IP addresses. If Windows supported RFC 6106, it wouldn’t really simplify things for most customers – since they would still have DHCPv6 deployed anyway for configuring other aspects of the hosts. In fact, RFC 6106 support would further instigate fragmentation of the network configuration space and make it harder for software and hardware partners to engineer IPv6 support. RFC 5505 discuses some of the principles of host configurations, including the value of minimizing diversity (section 2.3). -- Christopher Palmer - Microsoft