@synackray Pitchforks are not necessary, just enough noise so that
marketing/sales realize this is an issue.
It's just gone to L2 at JTAC.
Yes, the RFCs suggest client-id should be opaque,
but the real world usage in the non-enterprise is nearly alway
01 then MAC.
If we add into the mix an ISP/Telco DHCP server matching
options 82 and 61 (circuit-id/client-id) as a means of mapping
fixed/static address, we have slightly fragile process.
The introduction of JDHCP esp. dhcpv6-client PD was such a mess
that some of us are rather grumpy with Juniper.
There were/are the same sort of snafus with dhcp-local-server esp.
on EXs when dealing with wireless APs, most of which have not been fixed.
This actively lost Juniper business (to Fortinet) so I'm unhappy to see the SRX
CPE devices go the same way.
Too much complaining from a grumpy old SysEng,
Peter Cherny, luddite@luddite.com.au