{ "status": 0, "status_bits": [], "ra_email": "", "comment": "MAC (OUI/EUI or CID/ELI) address based AID", "confidential": false, "title": "MAC (OUI/EUI or CID/ELI) address based AID", "description": "

MAC (or OUI/EUI or CID/ELI) address based AID (up to 52 application-specific bits)

\n

You can generate AIDs using a company identification (OUI or CID) or using an NUI (an NUI-48 is a 48-bit NUI that is an EUI-48, ELI-48, SAI-48, or AAI-48).

\n

New definition as of 3 December 2023

\n

Syntax:

\n
D2 76 00 01 86 F2 + Size (1 nibble) + ELI/EUI/OUI/CID/... (1-16 nibbles BigEndian binary) + \"F\" padding if nibble count is odd + [ application-defined bits ]
\n

The \"size\" nibble defines the length of the identifier (ELI/EUI/...): 

\n\n

Next comes the identifier. It can be any MAC-based identifier between 1 nibble (4-bit) and 16 nibbles (64-bit), but they must be defined by IEEE and must be unique and unambiguous, because a non-unique MAC-based identifier cannot be encoded into an unique AID.

\n

Examples of IEEE identifiers are:

\n\n

* IEEE recommends not to use the 28-bit identifier MA-M to identify a company, but we don't see any reason why not to do it, since the MA-M prefix is unique and unambiguous.

\n

** You can generate an AID using the MAC of your network card, but then you must make sure that nobody else can use that network card, otherwise they could use it to generate an AID that you have previously defined. In other words: If you have created an AID using your MAC address, then you will lose the permission to use the AID namespace once you give/sell the network card to someone else.

\n

*** IEEE defines \"Administrator CIDs\" (e.g. 3AA3F8, CA30BF, 4A07D6, FA94F1) which are not assigned exclusively, to allow local administrators to create ELIs. These CIDs and their constructed ELIs must not be used to create an AID, because the resulting AID will be ambiguous!

\n

In the end, you can append an optional PIX to the AID.

\n

Examples

\n
    \n
  1. If you want to use a 6-byte MAC address (MAC-48, used for network devices), a EUI-48 address (used for other devices and software), or an ELI-48 as an identifier:
    \n
    D2 76 00 01 86 F2 B1 12 23 34 45 56 6F           = EUI-48/ELI-48 11:22:33:44:55:66, without application-specific part
    D2 76 00 01 86 F2 B1 12 23 34 45 56 6F __ __ __  = EUI-48/ELI-48 address 11:22:33:44:55:66, with 0-24 bits application-specific part
    \n
    2. \n
  2. If you have a EUI-64 (based on OUI) or ELI-64 (based on CID):
    \n
    D2 76 00 01 86 F2 F1 12 23 34 45 56 67 78 8F     = EUI-64/ELI-64 address 11:22:33:44:55:66:77:88, without application-specific part
    D2 76 00 01 86 F2 F1 12 23 34 45 56 67 78 8F __  = EUI-64/ELI-64 address 11:22:33:44:55:66:77:88, with 0-8 bits application-specific part
    \n
    3. \n
  3. You can also merely use an OUI/MA-L, MA-M, OUI-36/MA-S, IAB, or CID as an identifier:
    \n
    D2 76 00 01 86 F2 51 23 45 6F                    = OUI (MA-L) 123456, without application-specific part
    D2 76 00 01 86 F2 51 23 45 6F __ __ __ __ __ __  = OUI (MA-L) 123456, with 0-48 bits application-specific part
    \n
    D2 76 00 01 86 F2 61 23 45 67                    = MA-M 1234567, without application-specific part
    D2 76 00 01 86 F2 61 23 45 67 __ __ __ __ __ __  = MA-M 1234567, with 0-48 bits application-specific part
    \n
    D2 76 00 01 86 F2 81 23 45 67 89                 = OUI-36 (MA-S) 123456789, without application-specific part
    D2 76 00 01 86 F2 81 23 45 67 89 __ __ __ __ __  = OUI-36 (MA-S) 123456789, with 0-40 bits application-specific part
    \n
    D2 76 00 01 86 F2 B0 05 0C 21 23 45 6F           = IAB before September 2012 (00-50-C2) 123456, without application-specific part
    D2 76 00 01 86 F2 B0 05 0C 21 23 45 6F __ __ __  = IAB before September 2012 (00-50-C2) 123456, with 0-24 bits application-specific part
    \n
    D2 76 00 01 86 F2 B4 0D 85 51 23 45 6F           = IAB after September 2012 (40-D8-55) 123456, without application-specific part
    D2 76 00 01 86 F2 B4 0D 85 51 23 45 6F __ __ __  = IAB after September 2012 (40-D8-55) 123456, with 0-24 bits application-specific part
    \n
    4. \n
  4. Although CID cannot be used to generate a UAA MAC address, the CID is still unique and cannot overlap with OUI, so CID (an ELI) can be still used to create a unique AID.
    \n
    D2 76 00 01 86 F2 51 A2 34 5F                    = CID 1A2345, without application specific part
    D2 76 00 01 86 F2 51 A2 34 5F __ __ __ __ __ __  = CID 1A2345, with 0-48 bits application specific part
    \n
    5. \n
", "created": "2022-09-23 22:18:44", "updated": "2025-07-24 21:35:40", "children": [] }