DHCPv6 and MAC Address inclusion

[José Queiroz]

2012/1/25 Simon Hobson <dhcp1 at thehobsons.co.uk>

> José Queiroz wrote:
>
>  Hi, sorry if this is a naive view. But, doesn't auto-assignment with
>> EUID-64 suffixes attends your needs? This way you'll have a fixed IPv6
>> address, which haves a strong association with the MAC Address, and better,
>> is predictable if you know the MAC address of the interfaces.
>>
>
> it will work for some, but it's not a good idea for public services.
> Simple example, what if you want to move a service to a different machine ?
> Using EUID-64 addresses means you either have to change the MAC on the new
> host to match, or change the DNS and wait while it propagates - with a day
> or 2 of parallel running while caches expire.
>

Well, you can work out DNS to reduce this time. And if you have the
intention of moving the services, maybe using anycast addresses can solve
the problem.


> In practice, I suspect we'll start to see a return to using multiple
> addresses per machine/interface - which at one time was the only way to run
> multiple web sites on one host. So there may be some scope for using an
> EUID-64 address for the machine, and additional addresses for the
> service(s) run on it - but that's a whole new level of management system to
> sort out.


I think that IPv6 made a move on this direction --- using multiple
addresses per machine/interface --- when it explicitly adopted this concept.


> I'm not looking forward to applying IPv6 at work - I suffer badly enough
> with people that won't apply any logic to IPv4, I hate to think what
> they'll do when let loose with (say) 256 networks of 64k addresses !
>

Well, you shall never doubt people's ability to create new ways of doing
silly things.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20120125/d8b15d3a/attachment.html>