Assignees are encouraged to assign

鼓励受让人仅分配一种形式的EUI-48或EUI-64标识符，而不考虑其应用。换句话说，鼓励组织不要将相同的标识符分配给多个组织以用于不同的最终应用程序。该建议的目的是减少由管理每个组织内多个上下文相关的地址空间的复杂性引起的可能的错误。<br>例如，用于指定I / O驱动程序软件接口，语言代码和硬件型号的EUI-48值不应重叠。同样，用于指定I / O驱动程序软件接口，语言代码，硬件型号和硬件实例的EUI-64值绝不能重叠。通过消除主观的应用程序类判断，这种无重叠策略有望减少标识符值的意外重复，尽管可能会消耗更多的标识符值。

Assignees are encouraged to assign only one form of EUI-48 or EUI-64 identifier, regardless of application. In other words, the organization is encouraged to not assign the same identifier to multiple organizations for different end-application uses. The intent of this recommendation is to reduce possible errors introduced by the complexities of managing multiple context dependent address spaces within each organization. <br>For example, EUI-48 values that specify I/O driver software interfaces, language codes, and hardware model numbers should never overlap. Similarly, EUI-64 values that specify I/O driver software interfaces, language codes, hardware model numbers, and hardware instances should never overlap. This no-overlap strategy is expected to reduce unintentional duplication of identifier values, by elimination of subjective application-class judgments, although a few more identifier values may be consumed.

鼓励被指派人只分配一种形式的EUI-48或EUI-64标识符，而不考虑应用。换言之，鼓励组织不要为不同的最终应用程序用途将同一标识符分配给多个组织。本建议的目的是减少在每个组织中管理多个上下文相关地址空间的复杂性所带来的可能错误。<br>例如，指定I/O驱动程序软件接口、语言代码和硬件型号的EUI-48值决不能重叠。类似地，指定I/O驱动程序软件接口、语言代码、硬件型号和硬件实例的EUI-64值决不能重叠。这种无重叠策略期望通过消除主观的应用程序类判断来减少标识符值的无意重复，尽管可能会消耗更多的标识符值。