On 15 Dec, Mark Andrews wrote: | [...] | | Step one fix the root. ==> To continue with the template above in the same spirit: Step two: determine how laptops in the pleanary meeting room will be fed with the IPv6-only address of the appropriate recursive name server (eg. /etc/resolv.conf for Unixes) in the absence of that information in a DHCPv4 environment. One would have to choose between: - DHCPv6 option (RFC 3646 by way of RFC 3315-stateful or RFC 3736-stateless). That would mean that a DHCPv6 server would be UP&RUNNING during the meeting and laptops equipped with a DHCPv6 client - Modified RA (RFC 5006 - Experimental!) - Manual setting: everybody would have to emacs/vi their /etc/resolv.conf or use any GUI available on their OS, while reading the recursive server's IPv6 address on the projection board I think this issue which is not an obvious one (it is still a daily hurdle for many people among "IPv6 volunteers") deserves being looked during the experiment preparation if it hasn't been taken into account yet. Mohsen. _______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf