how would you do SLAAC with 64 bits?

hinkley 3 hours ago | parent | next [-]

Was DHCP so bad? It carries information important to using such a device anyway.

	▲	DaSHacka 3 hours ago \| parent \| next [-]
		+1, the majority of corporate networks I have seen used DHCPv6 or similar anyway
	▲	convolvatron 2 hours ago \| parent \| prev [-]
		well, its not without issues. the actual motivation was not that dhcp is the suxxors, but to promote a model where the assigned prefix was free and highly dynamic. the goal being to support a model where one could support multiple prefixes to handle the common case of multiple internet connections. more importantly to allow providers to shuffle the address space around without having to coordinate with the end organization. this was perceived to be necessary to prevent the v6 address space from accruing segmentation.

api 3 hours ago | parent | prev | next [-]

You don't, and that's fine.

cyberax an hour ago | parent | prev [-]

The same way you do it now. The router announces a prefix, and devices negotiate unique addresses.

Keep in mind that SLAAC isn't. Modern IPv6 stacks use privacy addresses, so they still need to run the address collision detection.

There's also a proposal to have SLAAC with longer prefixes, because otherwise you need to use DHCP-PD if you want to have subnetting in IPv6.