> > 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 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 manageer.
There are at least two other changes in the environment in the last 10 years. First, we have many networks that require authentication (802.1x or variants). Second, we have many networks (wireless) that do not support broadcast very well. If we took these two requirements into account, we would probably end up with something somewhat different from RA, DHCP and SEND. -- Christian Huitema -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
