Organizationally unique identifier
An organizationally unique identifier (OUI) is a 24-bit number that uniquely identifies a vendor, manufacturer, or other organization.
OUIs are purchased from the Institute of Electrical and Electronics Engineers (IEEE) Registration Authority by the "assignee" (IEEE term for the vendor, manufacturer, or other organization). They are used to uniquely identify a particular piece of equipment through derived identifiers such as MAC addresses,[1][2] Subnetwork Access Protocol protocol identifiers, World Wide Names for Fibre Channel devices.[3]
In MAC addresses, the OUI is combined with a 24-bit number (assigned by the owner or 'assignee' of the OUI) to form the address. The first three octets of the address are the OUI.
Representational and Formatting Conventions / Standards (IEEE 802-2001)
The following terms are defined (either implicitly or explicitly) in IEEE Standard 802-2001 for use in referring to the various representations and formats of OUIs and the identifiers that may be created using them.[4]
Hexadecimal Representation
“The representation of a sequence of octet values in which the values of the individual octets are displayed in order from left to right, with each octet value represented as a two-digit hexadecimal numeral, and with the resulting pairs of hexadecimal digits separated by hyphens. The order of the hexadecimal digits in each pair, and the mapping between the hexadecimal digits and the bits of the octet value, are derived by interpreting the bits of the octet value as a binary numeral using the normal mathematical rules for digit significance.”[4] (See hexadecimal).
Canonical Format
“The format of a MAC data frame in which the octets of any MAC addresses conveyed in the MAC user data field have the same bit ordering as in the Hexadecimal Representation.”[4] (See MAC data frame, MAC addresses)
Significance Order
This appears from the context of the IEEE Standard 802-2001 to be another term for the 'Hexadecimal Representation' – i.e., “by interpreting the bits of the octet value as a binary numeral using the normal mathematical rules for digit significance.”[4]
Bit-Reversed Representation
“The representation of a sequence of octet values in which the values of the individual octets are displayed in order from left to right, with each octet value represented as a two-digit hexadecimal numeral, and with the resulting pairs of hexadecimal digits separated by colons. The order of the hexadecimal digits in each pair, and the mapping between the hexadecimal digits and the bits of the octet value, are derived by reversing the order of the bits in the octet value and interpreting the resulting bit sequence as a binary numeral using the normal mathematical rules for digit significance.”[4]
The bit-reversed representation corresponds to the convention of transmitting the least-significant-bit of each byte first in serial data communications.
Noncanonical Representation
“The format of a MAC data frame in which the octets of MAC addresses conveyed in the MAC user data field have the same bit ordering as in the Bit-reversed representation.”[4]
Transmission Order
The order in which an octet or a sequence of octets is transmitted over the transmission medium – this order normally corresponds to the bit-reversed representation.
Example:
An OUI consisting of the hexadecimal digits ACDE4816 would be represented as follows:
Hexadecimal / Canonical format: AC-DE-48 | OUI | | Octet 0 | Octet 1 | Octet 2 | | A C | D E | 4 8 | |1010 1100|1101 1110|0100 1000| Bit-reversed / Noncanonical format: 35:7B:12 | OUI | | Octet 0 | Octet 1 | Octet 2 | | 3 5 | 7 B | 1 2 | |0011 0101|0111 1011|0001 0010|
Potential for Confusion in Token Ring Settings
Ethernet users are used to seeing canonical form, such as in the output of the ifconfig command. Canonical form is the intended standard.
However, since IEEE 802.3 (Ethernet) and IEEE 802.4 (Token Bus) send the bytes (octets) over the wire, left-to-right, with least significant bit in each byte first, while IEEE 802.5 (Token Ring) and IEEE 802.6 (FDDI) send the bytes over the wire with the most significant bit first, confusion may arise when an OUI in the latter scenario is represented with bits reversed from the canonical representation. So for instance, an OUI whose canonical form is ACDE48 could be seen written as 357B12 if translation is done improperly or inconsistently. The latter form (Bit-Reversed or Noncanonical representation), may also be referred to in the literature as "MSB format", "IBM format", or "Token Ring format" for this reason. RFC2469 explains the problem in more detail.
Format
The OUI is normally discussed and represented as a set of octets in hexadecimal notation separated by dashes (i.e., FF-FF-FF) or as a set of octets separated by colons in bit-reversed notation (i.e., FF:FF:FF).[1]
The two least-significant-bits of the second nibble of the first octet of the hexadecimal representation (i.e., the two least significant bits of the first octet) of the OUI are reserved as flag bits for some protocols (e.g., 'M' bit and 'X' bit), flags to indicate whether the address is part of an individual (unicast) or group (multicast) address block (e.g., Individual/Group [I/G] bit or Unicast/Multicast [U/M] bit), flags to indicate whether an address is universally or locally administered (e.g., Universal/Local [U/L] bit), etc., and should not contain the values 1, 2, 3, 5, 6, 7, 9, a, b, d, e, or f, unless these values reflect the true meaning of these flag bits – if the organization that owns the OUI does set one of these bits when creating an identifier, then the value of the second nibble of the first octet changes accordingly in representations of the OUI (e.g., if the hexadecimal value of the second nibble of the first octet is 'C' and the least-significant-bit is set, then the value becomes 'D').
Note: “Three-octet values occupying the same fields as OUIs can occupy, but with the next-to-LSB of the first octet set to 1, are locally assigned and have no relationship to the IEEE-assigned values...”.[1]
Example:
The following figure shows the position of these bits in significance order:
| OUI |
| Octet 0 | Octet 1 | Octet 2 |
| nibble | nibble | nibble |
| __||__ | __||__ | __||__ |
| | | | | | | | | |
| 0 || 1 | 2 || 3 | 4 || 5 |
|bits||bits|bits||bits|bits||bits|
|7654||3210|7654||3210|7654||3210|
||||| ||||||||| ||||||||| |||||
| A C | D E | 4 8 |
|1010 1100|1101 1110|0100 1000|
| | || | |
| | || | least-significant-bit of OUI
| | || least-significant-byte of OUI
| | |least-significant-bit of first octet of OUI = I/G or M bit
| | next-to-least-significant-bit of first octet of OUI = U/L or X bit
| most-significant-byte of OUI
most-significant-bit of OUI
Note: The OUI of AC-DE-48 could be in use and is not a reserved value.
Notes:
- The IEEE also has Company ID (CID) where the four least significant bits of Octet 0 are designated the M bit, X bit, Y bit, and Z bit, respectively, beginning with the least significant bit. In the CID, the M, X, Y, and Z bits have the values 0, 1, 0, and 1, respectively.[5]
- In the following, 'F' and 'h' represent any hexadecimal number.
- In the following, 'c' represents the digits of the OUI, and 'e' represents the digits of the extension identifier supplied by the organization to whom the OUI is registered.
Types of Identifiers
32-bit Context Dependent Identifier (CDI-32)
The CDI-32 was historically recommended as context dependent identifier that was formed by concatenating the 24-bit OUI with an 8-bit extension identifier that is assigned by the organization that purchased the OUI – the resulting identifier was generally represented as a set of octets separated by dashes (hexadecimal notation) or colons (bit-reversed notation) as in FF-FF-FF-FF or FF:FF:FF:FF, as a string of 4 bytes as in {FF,FF,FF,FF}, or as a base 16 number as in FFFFFFFF16.[5]
40-bit Context Dependent Identifier (CDI-40)
The CDI-40 was historically recommended as context dependent identifier that was formed by concatenating the 24-bit OUI with a 16-bit extension or by concatenating a 36-bit OUI-36 with a 4-bit extension.[5] In either case, the extension was assigned by the organization that purchased the OUI. The resulting identifier was generally represented as a set of octets separated by dashes (hexadecimal notation) or colons (bit-reversed notation) as in FF-FF-FF-FF-FF or FF:FF:FF:FF:FF, as a string of 5 bytes as in {FF,FF,FF,FF,FF}, or as a base 16 number as in FFFFFFFFFF16.
Note: There ware also IAB based CDI-40 sequences that were formed by combining the 36-bit IEEE assigned IAB base value with the 4-bit extension identifier assigned by the organization – e.g., if the IEEE assigned IAB base value is 0x0050C257A and the 4-bit extension identifier is 0xF, then the CDI-40 values generated by combining these two numbers are from 0x0050C257AF00 to 0x0050C257AFFF
48-bit Media Access Control Identifier (MAC-48)
The IEEE now considers the label MAC-48 to be an obsolete term which was previously used to refer to a specific type of EUI-48 identifier used to address hardware interfaces (e.g., Network Interface Controllers and other network hardware) within existing IEEE 802 based networking applications and should not be used in the future.[5] Instead, the term EUI-48 should be used by manufacturers and others in the field for this purpose – i.e., MAC-48 identifier is identical to the EUI-48 identifier and is an obsolete label for it, although some distinction is still made when encapsulating MAC-48 and EUI-48 identifiers within EUI-64 identifiers (but now encapsulating mechanism is also deprecated).[5]
48-bit Extended Unique Identifier (EUI-48)
The EUI-48 is an identifier that is formed by concatenating the 24-bit OUI with a 24-bit extension identifier that is assigned by the organization that purchased the OUI – the resulting identifier is generally represented as a set of octets separated by dashes (hexadecimal notation) or colons (bit-reversed notation) as in FF-FF-FF-FF-FF-FF or FF:FF:FF:FF:FF:FF, as a string of 6 bytes as in {FF,FF,FF,FF,FF,FF}, or as a base 16 number as in FFFFFFFFFFFF16.[5]
60-bit Extended Unique Identifier (EUI-60)
The EUI-60 is an identifier that is formed by concatenating the 24-bit OUI with a 36-bit extension identifier that is assigned by the organization that purchased the OUI – the resulting identifier is generally represented by a string of 15 nibbles, as a base 16 number as in FFFFFFFFFFFFFFF16, or as FF-FF-FF:F.F.F.F.F.F.F.F.F as an EUI-64 value.[5]
Note: This identifier was previously used as the worldwide name (WWN) identifier within some storage systems. Its use is now considered deprecated by the IEEE and the EUI-64 identifier should be used in the future for this and all other purposes for which the EUI-60 was previously used. Some of the storage systems in which an OUI based variant was used are Fibre Channel, and Serial Attached SCSI (SAS).[5]
64-bit Extended Unique Identifier (EUI-64)
The EUI-64 is an identifier that is formed by concatenating the 24-bit OUI with a 40-bit extension identifier that is assigned by the organization that purchased the OUI – the resulting identifier is generally represented as a set of octets separated by dashes (hexadecimal notation) or colons (bit-reversed notation) as in FF-FF-FF-FF-FF-FF-FF-FF or FF:FF:FF:FF:FF:FF:FF:FF, as a string of 8 bytes as in {FF,FF,FF,FF,FF,FF,FF,FF}, or as a base 16 number as in FFFFFFFFFFFFFFFF16.[5]
Note: According to the IEEE guidelines, the first four digits of the organizationally assigned identifier (i.e., the first four digits of the extension identifier) portion of an EUI-64 “shall not be FFFE16 or FFFF16” (i.e., EUI-64 identifiers of the form ccccccFFFEeeeeee and ccccccFFFFeeeeee are not allowed) – this is to support the encapsulation of EUI-48 (FFFE16) and MAC-48 (FFFF16) values into EUI-64 values (though now the encapsulation is deprecated).
Other Identifiers
IPv6 uses a 64-bit Modified Extended Unique Identifier (Modified EUI-64) in the lower half of some IPv6 addresses. A Modified EUI-64 is an EUI-64 with the U/L bit inverted.[6]
There are other identifiers that may be formed using the OUI but those listed above are the most commonly used.
Encapsulating
Mapping an EUI-48 to an EUI-64 is deprecated. The mapping is described here for historical reasons.
Other identifiers, such as MAC-48 and EUI-48 values, can be contained within a larger identifier or 'container', such as EUI-64, by creating the larger identifier through a process of combining the smaller identifier with specified values placed in specified bit-positions within the larger identifier – this process is known as 'encapsulation' and is provided for the purpose of easing the transition from MAC-48 and EUI-48 to EUI-64 and to provide a mechanism for the conversion of MAC-48 and EUI-48 identifiers to EUI-64 in such a way that duplicate or conflicting values are avoided.[5]
Encapsulation Examples
Encapsulation of MAC-48 within EUI-64 Example:
Assuming that an organization has registered the OUI of AC-DE-48 and that the organization has created the MAC-48 value of AC-DE-48-23-45-67 by concatenating the extension identifier 23-45-67, this MAC-48 identifier has the following binary transmission order:
| OUI | extension identifier | field
| 1st | 2nd | 3rd | 4th | 5th | 6th | octet
| C A | E D | 8 4 | 3 2 | 5 4 | 7 6 | hex
0011 0101 0111 1011 0001 0010 1100 0100 1010 0010 1110 0110 bits
| | | | | | | | | | | |
lsb msb lsb msb lsb msb lsb msb lsb msb lsb msb
The same MAC-48 identifier after encapsulation within an EUI-64 has the following transmission order:
| OUI | MAC label | extension identifier | field
| 1st | 2nd | 3rd | 4th | 5th | 6th | 7th | 8th | order
| C A | E D | 8 4 | F F | F F | 3 2 | 5 4 | 7 6 | hex
00110101 01111011 00010010 11111111 11111111 11000100 10100100 11100110 bits
| | | | | | | | | | | | | | | |
lsb msb lsb msb lsb msb lsb msb lsb msb lsb msb lsb msb lsb msb
The same MAC-48 identifier after encapsulation within an EUI-64 has the following significance order:
| OUI | MAC label | extension identifier | field
| AC | DE | 48 | FF | FF | 23 | 45 | 67 | hex
10101100 11011110 01001000 11111111 11111111 00100011 01000101 01100111 bits
| | | |
| most-significant-byte least-significant-byte |
most-significant-bit least-significant-bit
Encapsulation of EUI-48 within EUI-64 Example:
Assuming that an organization has registered the OUI of AC-DE-48 and that the organization has created the EUI-48 value of AC-DE-48-23-45-67 by concatenating the extension identifier 23-45-67, this EUI-48 identifier has the following format in significance order:
| company_id | extension identifier | field
| AC | DE | 48 | 23 | 45 | 67 | hex
10101100 11011110 01001000 00100011 01000101 01100111 bits
| | | |
| most-significant-byte least-significant-byte |
most-significant-bit least-significant-bit
The same EUI-48 identifier after encapsulation within an EUI-64 has the following format in significance order:
| company_id | EUI label | extension identifier | field
| AC | DE | 48 | FF | FE | 23 | 45 | 67 | hex
10101100 11011110 01001000 11111111 11111110 00100011 01000101 01100111 bits
| | | |
| most-significant-byte least-significant-byte |
most-significant-bit least-significant-bit
Encapsulation of MAC-48 or EUI-48 within Modified EUI-64 Example:
In the encapsulation within a Modified EUI-64 a MAC-48 is treated as an EUI-48 and the U/L bit is inverted.[6] Assuming that an organization has registered the OUI of AC-DE-48 and that the organization has created the MAC-48 or EUI-48 value of AC-DE-48-23-45-67 by concatenating the extension identifier 23-45-67, this MAC-48 or EUI-48 identifier has the following format in significance order:
| company_id | extension identifier | field
| AC | DE | 48 | 23 | 45 | 67 | hex
10101100 11011110 01001000 00100011 01000101 01100111 bits
| | | |
| most-significant-byte least-significant-byte |
most-significant-bit least-significant-bit
The same MAC-48 or EUI-48 identifier after encapsulation within a Modified EUI-64 has the following format in significance order:
| company_id | EUI label | extension identifier | field
| AE | DE | 48 | FF | FE | 23 | 45 | 67 | hex
10101110 11011110 01001000 11111111 11111110 00100011 01000101 01100111 bits
| | | |
| most-significant-byte least-significant-byte |
most-significant-bit least-significant-bit
NAA Name_Identifier
Network Address Authority (NAA) Name_Identifier formats define the first nibble (4 bits) to define the format of the identifier:
| Value | NAA Type | Length |
|---|---|---|
| 1h | NAA IEEE 48-bit | 8 bytes |
| 2h | NAA IEEE Extended | 8 bytes |
| 5h | NAA IEEE Registered | 8 bytes |
| 6h | NAA IEEE Registered Extended | 16 bytes |
| Ch, Dh, Eh, Fh | NAA EUI-64 Mapped | 8 bytes |
This encapsulation is used in Fibre Channel[7] and SAS, and is also supported in iSCSI in RFC 3980. This addition requires either a shortened vendor-specific identifier field, or some OUI bits are assumed to be 0, such as when using EUI-64 Mapped format.
Individual Address Block
An Individual Address Block is an inactive registry activity which has been replaced by the MA-S registry product as of January 1, 2014. The IAB uses a MA-L (and OUI) belonging to the IEEE Registration Authority, concatenated with 12 additional IEEE-provided bits (for a total of 36 bits), leaving only 12 bits for the IAB owner to assign to their (up to 4096) individual devices. An IAB is ideal for organizations requiring not more than 4096 unique 48-bit numbers (EUI-48). Unlike an OUI, which allows the assignee to assign values in various different number spaces (for example, EUI-48, EUI-64, and the various context-dependent identifier number spaces), the Individual Address Block could only be used to assign EUI-48 identifiers. All other potential uses based on the OUI from which the IABs are allocated are reserved, and remain the property of the IEEE Registration Authority. It should also be noted that, between 2007 and September 2012, the OUI value 00:50:C2 was used for IAB assignments. After September 2012, the value 40:D8:55 was used. The owners of an already assigned IAB may continue to use the assignment.[8][5]
The OUI-36 is a deprecated registry activity name, which has been replaced by the MA-S registry product name as of January 1, 2014. This registry activity includes both a 36-bit unique number used in some standards and the assignment of a block of EUI-48 and EUI-64 identifiers (while owner of IAB cannot assign EUI-64) by the IEEE Registration Authority. The owner of an already assigned OUI-36 registry product may continue to use the assignment.
Example of EUI-48 created within an IAB: An EUI-48 identifier is formed by combining the 36-bit IEEE assigned IAB base value with a 12-bit extension identifier assigned by the organization – e.g., if the IEEE assigned IAB base-16 value is 0x0050C257A and the 12-bit extension identifier is 0xFFF, then the EUI-48 value generated by combining these two numbers is 0x0050C257AFFF.
Compare to
- Universally unique identifier (UUID)
- Object identifier (OID)
- Private Enterprise numbers (PEN)
See also
References
- ^ a b c The Institute of Electrical and Electronics Engineers, Incorporated (IEEE) (1963-01-01). Registration authority.
- ^ Groth, David; Toby Skandier (2005). 'Network+ Study Guide, Fourth Edition'. Sybex, Inc. ISBN 0-7821-4406-3.
- ^ IEEE. "Guidelines for Fibre Channel Use of the Organizationally Unique Identifier (OUI)" (PDF).
- ^ a b c d e f IEEE Std 802-2001 (PDF). The Institute of Electrical and Electronics Engineers, Inc. (IEEE). 2002-02-07. ISBN 0-7381-2941-0. Retrieved 2011-09-08.
- ^ a b c d e f g h i j k "Guidelines for Use of Extended Unique Identifier (EUI), Organizationally Unique Identifier (OUI), and Company ID (CID)" (PDF). IEEE Standards Association. IEEE. Retrieved 12 October 2018.
{{cite web}}: Cite has empty unknown parameter:|dead-url=(help) - ^ a b "IANA Considerations and IETF Protocol Usage for IEEE 802 Parameters". IETF. RFC 5342.
{{cite web}}:|access-date=requires|url=(help); Missing or empty|url=(help) - ^ "Guidelines for Fibre Channel Use of the Organizationally Unique Identifier (OUI)" (PDF). IEEE-SA. Retrieved 2013-01-25.
- ^ "IEEE-SA - IEEE Registration Authority". standards.ieee.org. Retrieved 2018-09-20.
{{cite web}}: Cite has empty unknown parameter:|dead-url=(help)
External links
- IEEE Registration Authority Tutorials
- IEEE Registration Authority - Frequently Asked Questions
- IEEE Public OUI and Company ID, etc. Assignment lookup
- IEEE Public OUI list
- IEEE Public IAB list
- IEEE IAB and OUI MAC Address Lookup Database and API
- [rfc:5342 IANA Considerations and IETF Protocol Usage for IEEE 802 Parameters]
- IANA list of Ethernet Numbers
- Wireshark's OUI Lookup Tool and MAC address list