git: 529e9a00ddd3 - main - net/ieee_oui.h: clarify how `OUI_FREEBSD_BASE` is managed

From: Enji Cooper <ngie_at_FreeBSD.org>
Date: Tue, 03 Nov 2026 05:05:20 UTC
The branch main has been updated by ngie:

URL: https://cgit.FreeBSD.org/src/commit/?id=529e9a00ddd3a207f3841c6581c9f1a23532972e

commit 529e9a00ddd3a207f3841c6581c9f1a23532972e
Author:     Enji Cooper <ngie@FreeBSD.org>
AuthorDate: 2026-08-09 05:25:03 +0000
Commit:     Enji Cooper <ngie@FreeBSD.org>
CommitDate: 2026-11-03 05:05:14 +0000

    net/ieee_oui.h: clarify how `OUI_FREEBSD_BASE` is managed
    
    Note that the FreeBSD Foundation manages the current value
    associated with `OUI_FREEBSD_BASE`.
    
    Trim trailing whitespace in comments in the change while here.
    
    MFC after:      1 week
    Pull Request:   https://ron-dev.freebsd.org/FreeBSD/src/pulls/82
---
 sys/net/ieee_oui.h | 11 +++++++----
 1 file changed, 7 insertions(+), 4 deletions(-)

diff --git a/sys/net/ieee_oui.h b/sys/net/ieee_oui.h
index b5dd9fccefe1..553d9fcd3ba1 100644
--- a/sys/net/ieee_oui.h
+++ b/sys/net/ieee_oui.h
@@ -30,18 +30,21 @@
  *
  */
 
-/* Organizationally Unique Identifier assigned by IEEE 14 Nov 2013 */
+/*
+ * The Organizationally Unique Identifier (OUI) was assigned by IEEE on
+ * 14 Nov 2013. The OUI registration is managed by the FreeBSD Foundation.
+ */
 #define OUI_FREEBSD_BASE 0x589cfc000000
 #define OUI_FREEBSD(nic) (OUI_FREEBSD_BASE | (nic))
 
-/* 
+/*
  * OUIs are most often used to uniquely identify network interfaces
  * and occupy the first 3 bytes of both destination and source MAC
  * addresses.  The following allocations exist so that various
  * software systems associated with FreeBSD can have unique IDs in the
  * absence of hardware.  The use of OUIs for this purpose is not fully
  * fleshed out but is now in common use in virtualization technology.
- * 
+ *
  * Allocations from this range are expected to be made using COMMON
  * SENSE by developers.  Do NOT take a large range just because
  * they're currently wide open.  Take the smallest useful range for
@@ -50,7 +53,7 @@
  *
  * In the event of a conflict arbitration of allocation in this file
  * is subject to core@ approval.
- * 
+ *
  * Applications are differentiated based on the high order bit(s) of
  * the remaining three bytes.  Our first allocation has all 0s, the
  * next allocation has the highest bit set.  Allocating in this way