From philipp@redfish-solutions.com Sat Aug 19 17:56:22 2017 X-Original-To: dhcp-public@bugs.isc.org MIME-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) X-RT-Incoming-Encryption: Not encrypted References: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD autolearn=ham autolearn_force=no version=3.4.0 In-Reply-To: Content-Transfer-Encoding: quoted-printable From: "Philip Prindeville" To: dhcp-public@isc.org content-type: text/plain; charset="utf-8" X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on mx.pao1.isc.org Return-Path: X-RT-Interface: Email Date: Sat, 19 Aug 2017 11:53:54 -0600 X-RT-Original-Encoding: utf-8 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 8D775D78AEB for ; Sat, 19 Aug 2017 17:56:22 +0000 (UTC) Received: from mail.redfish-solutions.com (mail.redfish-solutions.com [66.232.79.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 31E2834AC14 for ; Sat, 19 Aug 2017 17:53:57 +0000 (UTC) Received: from macmini.redfish-solutions.com (macmini.redfish-solutions.com [192.168.1.38]) (authenticated bits=0) by mail.redfish-solutions.com (8.15.2/8.15.2) with ESMTPSA id v7JHruLV013487 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Sat, 19 Aug 2017 11:53:57 -0600 Subject: Re: [ISC-Bugs #45812] Implementing RFC-6355 X-Scanned-BY: MIMEDefang 2.79 on 192.168.1.3 Message-ID: X-Mailer: Apple Mail (2.3273) Delivered-To: dhcp-public@bugs.isc.org RT-Message-ID: Content-Length: 1145 > On Aug 19, 2017, at 2:48 AM, Francis Dupont via RT wrote: > > On Fri Aug 18 23:56:30 2017, philipp@redfish-solutions.com wrote: >> Hi. >> >> I was going through the sources of 4.3.5, in particular, how the >> DUID_LL is generated, and it seems wrong. >> >> Quoting the RFC, we have: >> >> 4. DUID-UUID Format > > => DUID LL and DUID UUID are different formats. DUID LLT and LL > are supported, UUID is not but you can use the raw value. > Salut Francis! Seigneur, ca fait quoi? Vignt ans ou plus? Tu vas bien? So, as I understand it then, there’s currently no support for RFC 6355? Because I see the “diid-uuid” string in common/tables.c mapping to DUID_UUID… I just don’t see DUID_UUID being used anywhere in the sources. Would you accept a fix for DUID-UUID based on an MD5 (or SHA1) hash of the MAC address? We have an application where we need to provision IPv6 leases for assigned addresses (of course) in real-time as boxes get rolled out in the field, and the operations teams are told by installers in the field radioing in MAC addresses as they pull boxes out of their van. -Philip