and in starting from scratch with IPv6, the IETF has made the mistake of throwing out the meaningful results of this dialogue.
As a matter of historical accuracy, the IPv6 auto-config design was done at a time when DHCP was so new that reliable implementations were not available. The best model for host auto-configuration then was probably Appletalk.
The IPv6 auto-configuration was modeled after IPX (based on XNS) auto- configuration. IPX was very successful at the time and it's auto- configuration mechanisms were considered an improvement over IPv4. At the time considered better for enterprises than IPv4. The IPv6 auto- configuration was based on a protocol that was very widely deployed.
The initial design goal was very explicitly to support zero-config router-free stand-alone LANs as well as routed networks. I don't think there's any reason to abandon that goal today, even though it's fairly clear that something with DHCP's level of capability is needed for larger routed networks that may or may not have a proactive IT manager.
I agree. Bob -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
