if the company address or contact information changes after I have received the
OUI, IAB and/or Ethertype Field?
My organization is writing a standard or specification that will include use of the OUI. How do I make sure this is okay with the IEEE RA?
An OUI / "company_id" is a 24-bit globally unique assigned number referenced by various standards. For example, the OUI is used in the family of 802 LAN standards: Ethernet, Token Ring, etc. The OUI is usually concatenated with another 24 bits that are assigned by that Organization in order to make a 48-bit number that is unique to a particular piece of network hardware, to make it possible to uniquely address that hardware. For example, the Ethernet MAC Address is such a 48-bit number, unique to one particular Ethernet interface. The OUI is usually concatenated with 24 or 40 bits to form an EUI-48 or an EUI-64. There are other uses of the OUI however, such as its use as a company identifier in the SNAP protocol.
An Individual Address Block is
for people who need
less than 4097 no more than unique 48-bit numbers (EUI-48) and thus
find it hard to justify buying their own OUI. The IAB is a particular OUI
belonging to the IEEE Registration Authority, concatenated with 12 additional
IEEE-provided bits, leaving only 12 bits for the owner to assign to his (up to 4096) individual devices.
The Length/Type field in an Ethernet/802.3 data frame is simply called a Type field, when used to identify the protocol (as opposed to specifying the frame’s length). The Type field provides a context for interpretation of the data field of an Ethernet/802.3 data frame (protocol identification). Refer to IEEE Std 802.3, clause 3 and especially sub-clauses 3.1.1 and 3.2.6. See also IEEE Std 802 sub-clause 10.4.
values, that can be formed by appending the OUI/IAB values with other fields, include
the following: MAC Address, Vendor Address, Vendor ID, NIC Address,
You must first have an OUI or an
IAB, to which you then append 24 or 12 bits respectively, in a way that makes
the resulting 48-bit number unique.
24 or 12 bits must be unique within your organization, which will require coordination
among all the users of your organization's OUI or IAB.
If the company already has an assignment, send an e-mail to the IEEE Registration Authority requesting the contact information for the company, and then make arrangements within your company to use your existing OUI or IAB.
Once the application is completed successfully, the Requestor will receive an e-mail with a tracking number and payment information. The application will be processed within seven days after receipt of payment as long as there are no problems with the information on the application or the payment. The Requestor will receive an e-mail with the assignment information once the application is processed.
The OUI is $1,650.00 (US); the
IAB is $550.00 (US) and the EtherType Field is $2,500.00 (US). The only other
fees that would be involved is a $15.00 bank fee that is only applicable with
the wire transfer payment method and a fee for private status on the public
listing. There are no annual fees.
The OUI is $1,650.00 (US); the IAB is $550.00 (US) and the EtherType Field is $2,500.00 (US). The only other fee that would be involved is a $15.00 bank fee that is only applicable with the wire transfer payment method and a fee for private status of the public listing. There are no annual fees.
The IEEE accepts checks (payable to IEEE Standards Dept.), purchase orders, wire transfers, as well as American Express, VISA, Master Card, Diners Club and Discover Card.
What standards are involved with OUI and IAB?
This single assignment covers both OUI (802) and "company_id". Its applications are
The OUI defined in IEEE Std 802-2001 can be used to generate 48 bit Universal LAN MAC addresses to identify LAN and MAN stations uniquely, and Protocol Identifiers to identify public and private protocols. These are used in Local and Metropolitan Area Network applications. The relevant standards include CSMA/CD (IEEE Std 802.3, ISO 8802-3), Token Bus (IEEE Std 802.4, ISO 8802-4), Token Ring (IEEE Std 802.5, ISO/IEC 8802-5), IEEE Std 802.6 (ISO/IEC DIS 8802-6), FDDI (ISO 9314-2) and WLAN (IEEE 802.11, ISO/IEC 8802-11) .
The "company_id" defined in
IEEE Std 1212-1991, IEEE Standard Control and Status Register (CSR)
Architecture, is referenced by IEEE Std 896.2-1991, IEEE Standard for
Futurebus+(TM) Physical Layer Specification and Profiles, and IEEE Std
1596-1992, IEEE Standard for Scalable Coherent Interface, as well as IEEE Std
1394-1995, IEEE Standard for a High Performance Serial Bus. In this context,
the 24-bit company_id value is a portion of a 48-bit
Module_Vendor_Id ROM location (and related locations) and identifier that uniquely identifies hardware vendors
and I/O software interface architectures. Also included is ANSIX3.230-1994
Fibre Channel Standard.
No. A parent company and a subsidiary company can share an OUI and if a company is sold, the OUI may be transferred to the new company. However, the OUI cannot be sold or distributed by anyone other than IEEE.
However, a company may resell individual EUI-64 identifiers, based on unique extensions to their purchased OUI values.
The Registration Authority requires that you use 95% of the existing assignment's 48-bit numbers before a second number can be issued to you. You may use a separate subset of the original assignment's 48-bit numbers for your new project.
If this requirement cannot be met, the IEEE can issue an additional assignment to your company providing you send a letter on company letterhead stating that you will not ship product on the new assigned number until 95% of the existing number is used. Your company must use care to ensure that large numbers of the 48-bit numbers are not left unused. Exceptions to this policy are rarely granted.
For registration information, please click here.
>>>>>>_Please_ work with Mick or network folks to get the write spelling for this word, whether Ethernet Type, EtherType, Ethertype, Ether Type. Then, use this name consistently throughout the tutorials and FAQs.
Please fax or mail a letter on company letterhead noting the changes (new company name, contact name, contact job title, address, phone, fax, e-mail address) with a press release or some details of the company name change to the IEEE Registration Authority at +1 732-562-1571.
The IEEE Registration Authority requests that any organization that intends to utilize the Organizationally Unique Identifier in the standardization of a technical area that has not previously been reviewed and approved by the IEEE, please contact the IEEE Registration Authority.
For further information, contact IEEE Registration Authority.
The following was extracted from the UseOfEUI.htm web page, and is better placed here.
My company has consumed ˝ of the MAC-48 address space to distinctively identify networking cards in desktop computers. Another division is planning to produce laptop computers. Should that division apply for a different OUI/company_id identifier?
No. The organization is responsible for consuming a preponderance of its MAC-48 address space before requesting an additional OUI/company_id identifier. To avoid duplicate address assignments, a central authority should assign blocks of MAC-48 address space to each division, on a demand basis, until all blocks have been consumed.
In my company, division A has consumed ˝ of the MAC-48 address space to distinctively identify networking cards. Now division B plans to produce IEEE Std 1394-1995 nodes, which have distinctive EUI-64 identifiers. Can we use the existing OUI/company_id identifier to generate these EUI-64 node identifiers?
Yes. The same OUI/company_id identifier can be used to generate these EUI-64 identifiers.
Do the previously assigned MAC-48 addresses affect the assignment of future EUI-64 identifiers?
Previously consumed MAC-48 addresses have no effect on the assignment of future EUI-64 identifiers.
My group is designing an IEEE Std 1394-1995 networking node, which has MAC-48 and EUI-64 identifiers in the 1394 and network interfaces respectively. Since both identifier effectively identify the same node, could the MAC-48 identifier be extended to form the EUI-64?
Yes. A valid (known to be unique)
EUI-64 can be generated by encapsulating the MAC-48 identifier, as described
GUIDELINES FOR 64-BIT GLOBAL IDENTIFIER (EUI-64) REGISTRATION AUTHORITY
subclause Restricted and encapsulated values.
I would like to distinctively identify software objects, or files stored on a disk drive. Can I use an EUI-64 identifier for this purpose?
No. When the volume of identifiers exceeds the one-per-hardware-instance volume, a larger identifier should be used. For example, files on a disk could be identified by concatenating an EUI-64 (that uniquely identifies the disk) with a 64-bit time stamp or sequence number.