>> New: >> >> <t> DHCPv6 <xref target='RFC3315' /> can be used to obtain and >> configure addresses. In general, a network may provide for the >> configuration of addresses through Router Advertisements, >> DHCPv6 or both. Some operators have indicated that they do >> not intend to support stateless address autoconfiguration on >> their networks and will require all address assignments be >> made through DHCPv6. On such networks, devices that support >> only stateless address autoconfiguration will be unable to >> automatically configure addresses. Consequently all hosts >> SHOULD implement address configuration via DHCP.</t> >> >> >> Is this acceptable? >> >> Please respond yes or no. Given the WG's previous hesitation to having >> DHCPv6 be a SHOULD, it is important that we get a clear indication of >> whether or not the WG supports this change. >>
> Yes. I support the new text. +1 Note that this is a MUST for equipment in Cable networks, although I do understand that there will be significant networks that won¹t rely on DHCPv6 in other deployment scenarios. - Wes
-------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
