Can Openwrt org apply for a (DUID-EN) org/enterprise number...?

[Bjørn Mork]

Hauke Mehrtens <hauke at hauke-m.de> writes:
> On 10/8/25 20:53, Paul D wrote:
>> https://www.iana.org/assignments/enterprise-numbers/assignment/apply/
>> Motivation:
>> https://github.com/openwrt/odhcp6c/pull/73#issuecomment-3382596182
>> 
>
> Hi,
>
> OpenWrt has a Organizationally unique identifier (OUI) from the IEEE.
>
> --------
> 20-05-B6   (hex)		OpenWrt
> 2005B6     (base 16)		OpenWrt
> 				 137 MONTAGUE ST STE 380
> 				Brooklyn  NY  11201
> 				US
> --------
>
> I haven't fully understood why you need a DUID-EN from IANA. Could you
> please explain it again.

Looks like a misunderstanding of how DUID-LLT is supposed to work:
https://github.com/openwrt/odhcp6c/pull/73#issuecomment-3382270139

If a DUID-EN can be generated once and stored forever, then so can a
DUID-LLT.  It does not matter if the device donating a mac address is
moved to another host.  The time makes the DUID unique.

> Does this cost money?

No, it doesn't.  It's free.  See
https://www.rfc-editor.org/rfc/rfc9371.html

But I guess the real cost is that OpenWrt would have to create a policy
and internal registry of it's usage.  Otherwise it would pretty soon be
unusable because of collisions.

An enterprise number can also be useful e.g for your own SNMP OIDs,
RADIUS VSAs, and structured syslog.

But personally I don't think DUID-EN is a very good usecase for OpenWrt.
That's more something for a hardware vendor which already issue unique
serial numbers for example.  Then they can create a DUID with their
enterprise number and the device serial number.  OpenWrt would have to
create an maintain a serial number registry or similar to be able to use
DUID-EN.  And there is absolutely no upside compared to the DUID-LLT.

Just my .02 €


Bjørn