X-PHP-Originating-Script: 20001:class-phpmailer.php From: "Oliver Freyermuth" Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx.pao1.isc.org", Issuer "COMODO RSA Organization Validation Secure Server CA" (not verified)) by bugs.isc.org (Postfix) with ESMTPS id A300CD78A16 for ; Wed, 6 Jun 2018 20:07:16 +0000 (UTC) Received: from iscwebprod.isc.org (iscwebprod.isc.org [IPv6:2001:4f8:1:d::16]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 109A43AB002 for ; Wed, 6 Jun 2018 20:07:14 +0000 (UTC) Received: from www (uid 80) (envelope-from www@iscwebprod.isc.org) id 7b7d14 by iscwebprod.isc.org (DragonFly Mail Agent v0.11); Wed, 06 Jun 2018 20:07:10 +0000 X-Mailer: PHPMailer 5.2.22 (https://github.com/PHPMailer/PHPMailer) To: dhcp-suggest@isc.org X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mx.pao1.isc.org Message-ID: <33f739f60ad60d48084d976f4b5db317@www.isc.org> Date: Wed, 6 Jun 2018 20:07:10 +0000 content-type: text/plain; charset="utf-8" Subject: ISC DHCP 4.4.1 - Missing support for RFC 6355 Return-Path: X-Spam-Status: No, score=0.5 required=5.0 tests=FREEMAIL_FORGED_FROMDOMAIN, FREEMAIL_FROM,HEADER_FROM_DIFFERENT_DOMAINS,T_RP_MATCHES_RCVD, UNPARSEABLE_RELAY autolearn=disabled version=3.4.1 X-Original-To: dhcp-public@bugs.isc.org X-RT-Incoming-Encryption: Not encrypted From www@isc.org Wed Jun 6 20:07:16 2018 Delivered-To: dhcp-public@bugs.isc.org MIME-Version: 1.0 X-RT-Original-Encoding: utf-8 X-RT-Interface: Email Content-Length: 1417 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