| From: | "Oliver Freyermuth" <o.freyermuth@googlemail.com> |
| To: | dhcp-suggest@isc.org |
| Date: | Wed, 6 Jun 2018 20:07:10 +0000 |
| Subject: | ISC DHCP 4.4.1 - Missing support for RFC 6355 |
Bug Report from www.isc.org:
Name: Oliver Freyermuth
Email: o.freyermuth@googlemail.com
Software Version: ISC DHCP 4.4.1
OS: Gentoo Linux
Subject:Missing support for RFC 6355
Bug Detail
===========
RFC 6355 is about creating UUID-Based DHCPv6 Unique Identifiers (DUID-UUID).
This is a crucial functionality for dhclient, since in DHCPv6 enterprise environments, bare metal machines are usually deployed automatically, and the chain of running environments (bare metal discovery system, installer environment, finally installed OS), even when all use dhclient, are currently all creating different DUIDs.
DHCP leases in enterprise environments are usually distributed on unique client features, in the v4 world this was the MAC address.
In the v6 world, the only consistent possibility in the RFCs is DUID-UUID. Assigning by MAC address (which is a stretch of the RFCs...) fails if client DUIDs are generated randomly in each of the aforementioned environments, since leases will stay valid after the first client DUID has requested a lease.
dhcpcd already has working, very portable support for RFC-6355 (see https://roy.marples.name/git/dhcpcd.git/patch/?id=71981cab0e41ea2833489bc51307611727276aff ), so an implementation in dhclient would be greatly appreciated to overcome the existing design issue of DHCPv6 for automated deployments.
---
This email was received through isc.org Bug Submission Form