LLMpediaThe first transparent, open encyclopedia generated by LLMs

Organizationally Unique Identifier

Generated by GPT-5-mini
Note: This article was automatically generated by a large language model (LLM) from purely parametric knowledge (no retrieval). It may contain inaccuracies or hallucinations. This encyclopedia is part of a research project currently under review.
Article Genealogy
Parent: HTML 2.0 Hop 4
Expansion Funnel Raw 74 → Dedup 4 → NER 1 → Enqueued 1
1. Extracted74
2. After dedup4 (None)
3. After NER1 (None)
Rejected: 3 (not NE: 3)
4. Enqueued1 (None)
Organizationally Unique Identifier
NameOrganizationally Unique Identifier
AbbreviationOUI
Introduced1980s
Governing bodyInstitute of Electrical and Electronics Engineers
RegistryIEEE Registration Authority
Format24-bit hexadecimal (three octets)
Scopedevice and vendor identification

Organizationally Unique Identifier

An Organizationally Unique Identifier is a 24-bit identifier used to uniquely identify vendors, manufacturers, and other organizations that produce hardware or register protocol elements. It appears in media access control assignments, protocol registries, and device descriptors, and is maintained by the IEEE Registration Authority, a body that also manages other numbering spaces. The identifier is widely referenced in standards, procurement, and interoperability work across technology firms and networking consortia.

Overview

The identifier traces to standardization efforts led by the Institute of Electrical and Electronics Engineers and was formalized as part of practices for Ethernet addressing, Bluetooth device manufacturing, and other protocol assignments. Major technology vendors such as Intel Corporation, Cisco Systems, IBM, Apple Inc., and Samsung Electronics frequently appear in public registries through their assigned prefixes. The registry supports transparency for procurement teams at institutions like National Aeronautics and Space Administration, British Telecom, and Deutsche Telekom, and for auditing by firms such as Deloitte and PricewaterhouseCoopers. Standards bodies including International Organization for Standardization, International Electrotechnical Commission, and regional consortia reference the allocation model in interoperability specifications.

Structure and Format

The identifier consists of three octets (24 bits) typically represented in hexadecimal notation and encoded in big-endian order when embedded into larger fields. In IEEE 802 contexts it occupies the upper 24 bits of a 48-bit address, paired with a 24-bit vendor-assigned extension to form a full hardware address used by devices from Hewlett-Packard, Dell Technologies, Lenovo, and Sony Corporation. The three-octet allocation can be shown as contiguous hexadecimal bytes or dotted in documentation adopted by National Institute of Standards and Technology publications and by manufacturers such as Motorola Solutions and Texas Instruments.

Encoding conventions determine whether the identifier signals local administration or global uniqueness, a distinction referenced in normative documents from Internet Engineering Task Force working groups and in registry guidance from the IEEE Standards Association. Representations appear across firmware, driver stacks from Microsoft Corporation and Red Hat, and device management systems used by VMware and Citrix Systems.

Assignment and Administration

Assignment processes are administered by the IEEE Registration Authority with application, fee, and documentation requirements that vary by entity size and purpose. Applicants include multinational corporations like Samsung Electronics and LG Electronics, research institutions such as Massachusetts Institute of Technology and Stanford University, and government laboratories including Lawrence Berkeley National Laboratory and Los Alamos National Laboratory. The registry provides public lookup services used by network operators at AT&T and by cloud providers like Amazon Web Services and Google LLC to attribute device origins.

Reserved blocks and historical transfers follow policies similar to asset registries maintained by institutions such as United States Department of Defense acquisition programs and commercial registries overseen by IANA for different identifier spaces. Dispute resolution processes reference precedents from cases involving trademarks at forums like the World Intellectual Property Organization and contractual arbitration bodies such as the International Chamber of Commerce.

Uses and Applications

Common uses include assignment into Media Access Control addresses for Ethernet and Wi‑Fi devices produced by Qualcomm and Broadcom, registration of vendor-specific protocol elements in stacks used by Apple Inc. for accessory identification, and embedding in system descriptors for USB devices from manufacturers like Logitech and Kingston Technology. The identifier supports asset management workflows in enterprises such as Siemens and General Electric, forensic attribution in investigations handled by agencies like Federal Bureau of Investigation and Europol, and component tracking in supply chains coordinated by firms like Maersk and IBM Supply Chain initiatives.

Standards that incorporate the identifier include working documents from IEEE 802.3 and IEEE 802.11, interface specifications from USB Implementers Forum, and protocol registries referenced in IETF RFCs. Device vendor lists published by manufacturers and distributors such as Arrow Electronics and Avnet frequently cite assigned prefixes for inventory and compatibility checks.

Conflicts, Collisions, and Exhaustion

Because the identifier space is finite, high-demand sectors have prompted strategies for collision avoidance, reclamation, and extended allocation models. Notable vendors with long histories—Nokia, Ericsson, Motorola Solutions—have managed multiple allocations through corporate mergers and divestitures, requiring reassignment or transfer entries in registry records. Collision issues arise when virtualized environments managed by platforms like VMware or Hyper-V generate duplicate address assignments, necessitating administrative controls and tooling from vendors such as Cisco Systems and Juniper Networks.

Exhaustion of contiguous blocks led to allocation of alternative formats and the introduction of techniques such as locally administered addresses and vendor-extended registries used by consortiums including Zigbee Alliance and Thread Group. Mitigation practices draw on lessons from numbering plans administered by International Telecommunication Union and plateaus observed in other identifier domains overseen by IANA.

Related identifier schemes include the 48-bit Media Access Control address, Organizationally Unique Identifier assignments used as prefixes in OUIs-derived registries, and enterprise identifier systems maintained by GS1 for supply-chain item identification. Standards that interact with the identifier span IEEE 802 family documents, USB Implementers Forum specifications, and registry practices analogous to IANA allocations for Internet protocol parameters. Cross-references exist in certification programs run by Wi-Fi Alliance, Bluetooth SIG, and testing facilities at Underwriters Laboratories.

Category:Identifiers