"hardware" data-expr and RFC-3315

[Paul Selkirk]

You don't need new functions, at least for this application.  The
following incantation synthesizes a DUID-LL:

send dhcp6.client-id = concat(00:03:00, hardware);

In addition, 4.1.1 added a -D option, where the client can specify
which type of DUID to send.

				paul

> Date: Tue, 02 Feb 2010 15:32:25 -0800
> From: "Philip A. Prindeville" <philipp_subx at redfish-solutions.com>
> X-Spam-Status: No, score=-3.7 required=5.0 tests=AWL,BAYES_00 autolearn=ham
> 	version=3.2.5
> 
> I'm looking at RFC 3315, section 9.4 right now, and seeing:
> 
> 9.4. DUID Based on Link-layer Address [DUID-LL]
> ... 
> 
> and wondering if the function "hardware" should be replaced by two functions, one called "hardware-type" which returns the ARP-type (as per ASSIGNED NUMBERS, "ADDRESS RESOLUTION PROTOCOL PARAMETERS"), and another called "hardware-addr", which reutrns the unadorned MAC address itself (i.e. what would be substring(hardware, 1, 1023) currently).
> 
> The hardware type would need to be packed into octet format, and one could implement RFC-3315's DUID-LL's as:
> 
> send dhcp-client-identifier concat(03, encode-int(hardware-type), hardware-addr);
> 
> instead.
> 
> Is it worth filing a bug to get these two functions implemented?
> 
> Thanks,
> 
> -Philip
> 
> 
> _______________________________________________
> dhcp-hackers mailing list
> dhcp-hackers at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-hackers
>