Network Working Group D. Eastlake 3rd
Request for Comments: 5342 Eastlake Enterprises
BCP: 141 September 2008
Updates: 2153
Category: Best Current Practice
Network Working Group D. Eastlake 3rd
Request for Comments: 5342 Eastlake Enterprises
BCP: 141 September 2008
Updates: 2153
Category: Best Current Practice
IANA Considerations and IETF Protocol Usage for IEEE 802 Parameters
IEEE802参数的IANA考虑因素和IETF协议使用
Status of This Memo
关于下段备忘
This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Distribution of this memo is unlimited.
本文件规定了互联网社区的最佳现行做法，并要求进行讨论和提出改进建议。本备忘录的分发不受限制。
Abstract
摘要
Some IETF protocols make use of Ethernet frame formats and IEEE 802 parameters. This document discusses some use of such parameters in IETF protocols and specifies IANA considerations for allocation of code points under the IANA OUI (Organizationally Unique Identifier).
一些IETF协议使用以太网帧格式和IEEE 802参数。本文档讨论了IETF协议中此类参数的一些使用，并指定了IANA OUI（组织唯一标识符）下代码点分配的IANA注意事项。
Table of Contents
目录
1. Introduction ....................................................3
1.1. Notations Used in This Document ............................3
1.2. The IEEE Registration Authority ............................3
1.2.1. The IANA OUI ........................................4
1.3. Acknowledgements ...........................................4
2. Ethernet Identifier Parameters ..................................4
2.1. 48-Bit MAC Identifiers and OUIs ............................4
2.1.1. EUI-48 Allocations under the IANA OUI ...............5
2.1.2. EUI-48 IANA Allocation Considerations ...............5
2.2. 64-Bit MAC Identifiers .....................................6
2.2.1. IPv6 Use of Modified EUI-64 Identifiers .............6
2.2.2. EUI-64 IANA Allocation Considerations ...............8
2.3. Other MAC-48 Identifiers Used by IETF ......................9
2.3.1. Identifiers Prefixed 33-33 ..........................9
2.3.2. The 'CF Series' ....................................10
2.3.2.1. Changes to RFC 2153 .......................10
3. Ethernet Protocol Parameters ...................................10
3.1. Ethernet Protocol Allocation under the IANA OUI ...........12
4. Other OUI-Based Parameters .....................................13
5. IANA Considerations ............................................13
5.1. Expert Review and IESG Ratification .......................14
5.2. Informational IANA Web Page Material ......................15
5.3. OUI Exhaustion ............................................15
6. Security Considerations ........................................15
7. Normative References ...........................................15
8. Informative References .........................................16
Appendix A. Templates ............................................18
A.1. EUI-48/EUI-64 Identifier or Identifier Block Template .....18
A.2. 5-Octet Ethernet Protocol Identifier Template .............18
A.3. Other IANA OUI-Based Parameter Template ...................19
Appendix B. Ethertypes ............................................19
B.1. Some Ethertypes Specified by The IETF .....................19
B.2. Some IEEE 802 Ethertypes ..................................20
1. Introduction ....................................................3
1.1. Notations Used in This Document ............................3
1.2. The IEEE Registration Authority ............................3
1.2.1. The IANA OUI ........................................4
1.3. Acknowledgements ...........................................4
2. Ethernet Identifier Parameters ..................................4
2.1. 48-Bit MAC Identifiers and OUIs ............................4
2.1.1. EUI-48 Allocations under the IANA OUI ...............5
2.1.2. EUI-48 IANA Allocation Considerations ...............5
2.2. 64-Bit MAC Identifiers .....................................6
2.2.1. IPv6 Use of Modified EUI-64 Identifiers .............6
2.2.2. EUI-64 IANA Allocation Considerations ...............8
2.3. Other MAC-48 Identifiers Used by IETF ......................9
2.3.1. Identifiers Prefixed 33-33 ..........................9
2.3.2. The 'CF Series' ....................................10
2.3.2.1. Changes to RFC 2153 .......................10
3. Ethernet Protocol Parameters ...................................10
3.1. Ethernet Protocol Allocation under the IANA OUI ...........12
4. Other OUI-Based Parameters .....................................13
5. IANA Considerations ............................................13
5.1. Expert Review and IESG Ratification .......................14
5.2. Informational IANA Web Page Material ......................15
5.3. OUI Exhaustion ............................................15
6. Security Considerations ........................................15
7. Normative References ...........................................15
8. Informative References .........................................16
Appendix A. Templates ............................................18
A.1. EUI-48/EUI-64 Identifier or Identifier Block Template .....18
A.2. 5-Octet Ethernet Protocol Identifier Template .............18
A.3. Other IANA OUI-Based Parameter Template ...................19
Appendix B. Ethertypes ............................................19
B.1. Some Ethertypes Specified by The IETF .....................19
B.2. Some IEEE 802 Ethertypes ..................................20
Some IETF protocols use Ethernet or other [IEEE] 802 related communication frame formats and parameters [IEEE802]. These include MAC (Media Access Control) identifiers and protocol identifiers.
一些IETF协议使用以太网或其他[IEEE]802相关通信帧格式和参数[IEEE802]。这些包括MAC（媒体访问控制）标识符和协议标识符。
This document specifies IANA considerations for the allocation of code points under the IANA OUI. It also discusses some other IETF use of IEEE 802 code points.
本文件规定了IANA OUI下代码点分配的IANA注意事项。它还讨论了IETF对IEEE 802码点的其他一些使用。
[RFC5226] is incorporated herein except where there are contrary provisions in this document.
[RFC5226]并入本文件，除非本文件中有相反规定。
This document uses hexadecimal notation. Each octet (that is, 8-bit byte) is represented by two hexadecimal digits giving the value of the octet as an unsigned integer. Successive octets are separated by a hyphen. This document consistently uses IETF bit ordering although the physical order of bit transmission within an octet on an IEEE [802.3] link is from the lowest order bit to the highest order bit (i.e., the reverse of the IETF's ordering).
本文档使用十六进制表示法。每个八位字节（即8位字节）由两个十六进制数字表示，该八位字节的值为无符号整数。连续的八位字节用连字符分隔。尽管IEEE[802.3]链路上八位字节内的位传输的物理顺序是从最低阶位到最高阶位（即，IETF的顺序相反），但本文件始终使用IETF位顺序。
In this document:
在本文件中：
"IAB" stands for Individual Address Block, not for Internet Architecture Board;
“IAB”代表单个地址块，而不是Internet架构板；
"MAC" stands for Media Access Control, not for Message Authentication Code; and
“MAC”代表媒体访问控制，不代表消息认证码；和
"OUI" stands for Organizationally Unique Identifier.
“OUI”代表组织上唯一的标识符。
"**" indicates exponentiation. For example, 2**24 is two to the twenty-fourth power.
“**”表示幂运算。例如，2**24是2到24次方。
Originally the responsibility of Xerox Corporation, the registration authority for Ethernet parameters is now the IEEE Registration Authority, available on the web at:
最初由施乐公司负责，以太网参数的注册机构现在是IEEE注册机构，可在以下网址获得：
http://standards.ieee.org/regauth/
http://standards.ieee.org/regauth/
Anyone may apply to that Authority for parameters. They may impose fees or other requirements but commonly waive fees for applications from standards development organizations.
任何人都可以向该机构申请参数。他们可能会收取费用或其他要求，但通常会免除标准开发组织的申请费用。
A list of some allocated OUIs and IABs and their holders is downloadable from the IEEE Registration Authority site.
一些分配的OUI和IAB及其持有者的列表可从IEEE注册机构网站下载。
The OUI 00-00-5E has been allocated to IANA.
OUI 00-00-5E已分配给IANA。
The contributions and support of the following people, listed in alphabetic order, is gratefully acknowledged:
感谢以下人员的贡献和支持（按字母顺序排列）：
Bernard Aboba, Scott O. Bradner, Ian Calder, Michelle Cotton, Lars Eggert, Eric Gray, Alfred Hoenes, Russ Housley, Charlie Kaufman, Erik Nordmark, Dan Romascanu, Mark Townsley, and Geoff Thompson.
伯纳德·阿博巴、斯科特·布拉德纳、伊恩·考尔德、米歇尔·科顿、拉尔斯·艾格特、埃里克·格雷、阿尔弗雷德·霍恩斯、罗斯·霍斯利、查理·考夫曼、埃里克·诺德马克、丹·罗马斯坎努、马克·汤斯利和杰夫·汤普森。
Section 2.1 discusses EUI-48 (Extended Unique Identifier 48) MAC identifiers, their relationship to OUIs and IABs, and allocations under the IANA OUI. Section 2.2 extends this to EUI-64 identifiers. Section 2.3 discusses other IETF MAC identifier use not under the IANA OUI.
第2.1节讨论EUI-48（扩展唯一标识符48）MAC标识符，它们与OUI和IAB的关系，以及IANA OUI下的分配。第2.2节将其扩展到EUI-64标识符。第2.3节讨论了IANA OUI之外的其他IETF MAC标识符使用。
48-bit MAC "addresses" are the most commonly used Ethernet interface identifiers. Those that are globally unique are also called EUI-48 identifiers. An EUI-48 is structured into an initial 3-octet OUI (Organizationally Unique Identifier) and an additional 3 octets assigned by the OUI holder. For organizations not requiring 3 octets' worth of identifiers, the IEEE allocates IABs (Individual Address Blocks) instead, where the first 4 1/2 octets (36 bits) are assigned, giving the holder of the IAB 1 1/2 octets (12 bits) they can control.
48位MAC“地址”是最常用的以太网接口标识符。全局唯一的标识符也称为EUI-48标识符。EUI-48被构造成初始的3个八位组OUI（组织唯一标识符）和由OUI持有者分配的额外3个八位组。对于不需要3个八位字节的标识符的组织，IEEE分配IAB（单个地址块），其中分配了前4个1/2八位字节（36位），使IAB的持有者可以控制1个1/2八位字节（12位）。
The IEEE describes its assignment procedures and policies for IEEE 802 related identifiers in [802_O&A].
IEEE在[802_O&A]中描述了其IEEE 802相关标识符的分配过程和策略。
Two bits within the initial 3 octets of an EUI-48 have special significance: the Group bit (01-00-00) and the Local bit (02-00-00). OUIs and IABs are allocated with the Local bit zero and the Group bit unspecified. Multicast identifiers may be constructed by turning on the Group bit, and unicast identifiers constructed by leaving the Group bit zero.
EUI-48初始3个八位字节中的两个位具有特殊意义：组位（01-00-00）和本地位（02-00-00）。OUI和IAB分配的本地位为零，组位未指定。多播标识符可以通过打开组位来构造，单播标识符可以通过将组位保留为零来构造。
For globally unique EUI-48 identifiers allocated by an OUI or IAB owner, the Local bit is zero. If the Local bit is a one, the identifier is considered by IEEE 802 to be a local identifier under the control of the local network administrator. If the Local bit is on, the holder of an OUI (or IAB) has no special authority over 48-bit MAC identifiers whose first 3 (or 4 1/2) octets correspond to their OUI (or IAB).
对于OUI或IAB所有者分配的全局唯一EUI-48标识符，本地位为零。如果本地比特是1，则IEEE 802认为该标识符是本地网络管理员控制下的本地标识符。如果本地位打开，OUI（或IAB）的持有者对其前3（或4 1/2）个八位组对应于其OUI（或IAB）的48位MAC标识符没有特殊权限。
The OUI 00-00-5E has been assigned to IANA as stated in Section 1.2.1 above. This includes 2**24 EUI-48 multicast identifiers from 01-00-5E-00-00-00 to 01-00-5E-FF-FF-FF and 2**24 EUI-48 unicast identifiers from 00-00-5E-00-00-00 to 00-00-5E-FF-FF-FF.
如上文第1.2.1节所述，OUI 00-00-5E已分配给IANA。这包括从01-00-5E-00-00到01-00-5E-FF-FF-FF的2**24 EUI-48多播标识符和从00-00-5E-00-00-00到00-00-5E-FF-FF的2**24 EUI-48单播标识符。
Of these EUI-48 identifiers, the following allocations have been made thus far:
在这些EUI-48标识符中，到目前为止已进行了以下分配：
o The 2**23 multicast identifiers from 01-00-5E-00-00-00 through 01-00-5E-7F-FF-FF have been allocated for IPv4 multicast [RFC1112].
o 从01-00-5E-00-00-00到01-00-5E-7F-FF-FF的2**23多播标识符已分配给IPv4多播[RFC1112]。
o The 2**20 multicast identifiers from 01-00-5E-80-00-00 through 01-00-5E-8F-FF-FF have been allocated for MPLS multicast [RFC5332].
o 从01-00-5E-80-00-00到01-00-5E-8F-FF-FF的2**20多播标识符已分配给MPLS多播[RFC5332]。
o The 2**8 unicast identifiers from 00-00-5E-00-00-00 through 00-00-5E-00-00-FF are reserved and require IESG Ratification for allocation (see Section 5.1).
o 保留从00-00-5E-00-00-00到00-00-5E-00-00-FF的2**8个单播标识符，并要求IESG批准分配（见第5.1节）。
o The 2**8 unicast identifiers from 00-00-5E-00-01-00 through 00-00-5E-00-01-FF have been allocated for the Virtual Router Redundancy Protocol (VRRP) [RFC3768].
o 从00-00-5E-00-01-00到00-00-5E-00-01-FF的2**8个单播标识符已分配给虚拟路由器冗余协议（VRRP）[RFC3768]。
EUI-48 allocations under the current or a future IANA OUI (see Section 5.2) must meet the following requirements:
当前或未来IANA OUI（见第5.2节）下的EUI-48分配必须满足以下要求：
o must be for standards purposes (either for an IETF Standard or other standard related to IETF work),
o 必须用于标准目的（IETF标准或与IETF工作相关的其他标准），
o must be for a block of a power-of-two identifiers starting at a boundary that is an equal or greater power of two, including the allocation of one (2**0) identifier,
o 必须适用于从等于或大于2的幂的边界开始的两个标识符的幂的块，包括一个（2**0）标识符的分配，
o must not be used to evade the requirement for vendors to obtain their own block of identifiers from the IEEE, and
o 不得用于规避供应商从IEEE获得自己的标识符块的要求，以及
o must be documented in an Internet-Draft or RFC.
o 必须记录在互联网草稿或RFC中。
In addition, approval must be obtained as follows (see the procedure in Section 5.1):
此外，必须获得以下批准（见第5.1节中的程序）：
Small to medium allocations of a block of 1, 2, 4, ..., 32768, 65536 (2**0, 2**1, 2**2, ..., 2**15, 2**16) EUI-48 identifiers require Expert Review.
1、2、4、…、32768、65536（2**0、2**1、2**2、…、2**15、2**16）EUI-48标识符块的中小型分配需要专家审查。
Large allocations of 131072 (2**17) or more EUI-48 identifiers require IESG Ratification (see Section 5.1).
大量分配131072（2**17）或更多EUI-48标识符需要IESG批准（见第5.1节）。
To simplify record keeping, all future allocations of 256 (2**8) or fewer identifiers shall have the Group bit unspecified, that is, shall be allocations of parallel equal-size blocks of multicast and unicast identifiers, even if one of these two types is not needed for the proposed use. The only exception is that requests for unicast-only identifier blocks of any size may be allocated out of the remaining identifiers in the large unicast range from 00-00-5E-00-02-00 to 00-00-5E-8F-FF-FF.
为了简化记录保存，256（2**8）或更少标识符的所有未来分配应具有未指定的组位，即，应为多播和单播标识符的并行等大小块的分配，即使提议的使用不需要这两种类型中的一种。唯一的例外是，对于任何大小的仅单播标识符块的请求可以从00-00-5E-00-02-00到00-00-5E-8F-FF-FF的大单播范围内的剩余标识符中分配。
IEEE also defines a system of 64-bit MAC identifiers including EUI-64s. Uptake of these "MAC-64" identifiers has been limited. They are currently used in constructing some IPv6 Interface Identifiers as described below and by the following IEEE standards:
IEEE还定义了包括EUI-64s在内的64位MAC标识符系统。这些“MAC-64”标识符的使用受到限制。它们目前用于构建一些IPv6接口标识符，如下所述，并符合以下IEEE标准：
o IEEE 1394 (also known as FireWire and i.Link),
o IEEE 1394（也称为FireWire和i.Link），
o IEEE 802.15.4 (also known as ZigBee).
o IEEE 802.15.4（也称为ZigBee）。
Adding a 5-octet (40-bit) extension to a 3-octet (24-bit) OUI forms an EUI-64 identifier under that OUI. As with EUI-48 identifiers, the OUI has the same Group/unicast and Local/Global bits.
将5-octet（40位）扩展添加到3-octet（24位）OUI下形成EUI-64标识符。与EUI-48标识符一样，OUI具有相同的组/单播和本地/全局位。
The discussion below is almost entirely in terms of the "Modified" form of EUI-64 identifiers; however, anyone allocated such an identifier also has the unmodified form and may use it as a MAC identifier on any link that uses such 64-bit identifiers for interfaces.
下面的讨论几乎完全是关于EUI-64标识符的“修改”形式；然而，任何分配了这种标识符的人也具有未修改的形式，并且可以在使用这种64位标识符作为接口的任何链路上使用它作为MAC标识符。
MAC-64 identifiers are used to form the lower 64 bits of some IPv6 addresses (Section 2.5.1 and Appendix A of [RFC4291] and Appendix A of [RFC5214]). When so used, the MAC-64 is modified by inverting the Local/Global bit to form an IETF "Modified EUI-64 identifier". Below
MAC-64标识符用于形成某些IPv6地址的低位64位（第2.5.1节和[RFC4291]的附录A和[RFC5214]的附录A）。当如此使用时，通过反转本地/全局位来修改MAC-64，以形成IETF“修改的EUI-64标识符”。在下面
is an illustration of a Modified EUI-64 identifier under the IANA OUI, where aa-bb-cc-dd-ee is the extension.
是IANA OUI下修改的EUI-64标识符的图示，其中aa bb cc dd ee是扩展。
02-00-5E-aa-bb-cc-dd-ee
02-00-5E-aa-bb-cc-dd-ee
The first octet is shown as 02 rather than 00 because, in Modified EUI-64 identifiers, the sense of the Local/Global bit is inverted compared with EUI-48 identifiers. It is the globally unique values (universal scope) that have the 02 bit on in the first octet, while those with this bit off are locally assigned and out of scope for global allocation.
第一个八位组显示为02而不是00，因为在修改的EUI-64标识符中，与EUI-48标识符相比，本地/全局位的意义是颠倒的。第一个八位字节中的02位为on的是全局唯一值（通用范围），而该位为off的值是本地分配的，超出了全局分配的范围。
The Local/Global bit was inverted to make it easier for network operators to type in local-scope identifiers. Thus, such Modified EUI-64 identifiers as 1, 2, etc. (ignoring leading zeros), are local. Without the modification, they would have to be 02-00-00-00-00-00-00-01, 02-00-00-00-00-00-00-02, etc., to be local.
本地/全局位被反转，以便于网络运营商键入本地范围标识符。因此，诸如1、2等修改的EUI-64标识符（忽略前导零）是本地的。如果不进行修改，它们必须是02-00-00-00-00-00-01、02-00-00-00-00-00-00-02等，才能是本地的。
As with MAC-48 identifiers, the 01 bit on in the first octet indicates a group identifier.
与MAC-48标识符一样，第一个八位组中的01位表示组标识符。
When the first two octets of the extension of a Modified EUI-64 identifier are FF-FE, the remainder of the extension is a 24-bit value as assigned by the OUI owner for an EUI-48. For example:
当修改后的EUI-64标识符扩展的前两个八位字节为FF-FE时，扩展的其余部分为OUI所有者为EUI-48分配的24位值。例如：
02-00-5E-FF-FE-yy-yy-yy or 03-00-5E-FF-FE-yy-yy-yy
02-00-5E-FF-FE-yy-yy-yy或03-00-5E-FF-FE-yy-yy-yy
where yy-yy-yy is the portion (of an EUI-48 global unicast or multicast identifier) that is assigned by the OUI owner (IANA in this case). Thus, any holder of one or more EUI-48 identifiers under the IANA OUI also has an equal number of Modified EUI-64 identifiers that can be formed by inserting FF-FE in the middle of their EUI-48 identifiers and inverting the Local/Global bit.
其中yy yy yy是OUI所有者（在本例中为IANA）分配的（EUI-48全局单播或多播标识符的）部分。因此，在IANA OUI下的一个或多个EU-48标识符的任何持有者也具有相同数目的修改的EU-64标识符，其可以通过在其EU-48标识符的中间插入FF-FE并反转局部/全局比特来形成。
(Note: [EUI-64] defines FF-FF as the bits to be inserted to create an IEEE EUI-64 identifier from a MAC-48 identifier. That document says the FF-FE value is used when starting with an EUI-48 identifier. The IETF uses only FF-FE to create Modified EUI-64 identifiers from 48-bit Ethernet station identifiers regardless of whether they are EUI-48 or MAC-48 local identifiers. EUI-48 and local MAC-48 identifiers are syntactically equivalent, and this doesn't cause any problems in practice.)
（注：[EUI-64]将FF-FF定义为要插入的位，以从MAC-48标识符创建IEEE EUI-64标识符。该文档称，从EUI-48标识符开始时使用FF-FE值。IETF仅使用FF-FE从48位以太网站点标识符创建修改的EUI-64标识符，无论它们是EUI-48还是MAC-48本地identifiers.EUI-48和本地MAC-48标识符在语法上是等价的，这在实践中不会引起任何问题。）
In addition, certain Modified EUI-64 identifiers under the IANA OUI are reserved for holders of IPv4 addresses as follows:
此外，IANA OUI下的某些修改的EUI-64标识符保留给IPv4地址的持有者，如下所示：
02-00-5E-FE-xx-xx-xx-xx
02-00-5E-FE-xx-xx-xx-xx
where xx-xx-xx-xx is a 32-bit IPv4 address. For Modified EUI-64 identifiers based on an IPv4 address, the Local/Global bit should be set to correspond to whether the IPv4 address is local or global. (Keep in mind that the sense of the Modified EUI-64 identifier Local/Global bit is reversed from that in (unmodified) MAC-64 identifiers.)
其中xx xx xx xx是32位IPv4地址。对于基于IPv4地址的修改的EUI-64标识符，本地/全局位应设置为与IPv4地址是本地还是全局相对应。（请记住，修改后的EUI-64标识符本地/全局位的含义与（未修改的）MAC-64标识符中的含义相反。）
The following table shows which Modified EUI-64 identifiers under the IANA OUI are reserved, used, or available as indicated.
下表显示了IANA OUI下保留、使用或可用的修改过的EUI-64标识符。
02-00-5E-00-00-00-00-00 to 02-00-5E-0F-FF-FF-FF-FF reserved
02-00-5E-00-00-00-00-00至02-00-5E-0F-FF-FF-FF-FF预留
02-00-5E-10-00-00-00-00 to 02-00-5E-EF-FF-FF-FF-FF available for allocation
02-00-5E-10-00-00-00-00至02-00-5E-EF-FF-FF-FF-FF可供分配
02-00-5E-F0-00-00-00-00 to 02-00-5E-FD-FF-FF-FF-FF reserved
02-00-5E-F0-00-00-00-00至02-00-5E-FD-FF-FF-FF保留
02-00-5E-FE-00-00-00-00 to 02-00-5E-FE-FF-FF-FF-FF used by IPv4 address holders as described above
如上所述，IPv4地址持有者使用02-00-5E-FE-00-00-00至02-00-5E-FE-FF-FF-FF-FF
02-00-5E-FF-00-00-00-00 to 02-00-5E-FF-FD-FF-FF-FF reserved
02-00-5E-FF-00-00-00至02-00-5E-FF-FD-FF-FF保留
02-00-5E-FF-FE-00-00-00 to 02-00-5E-FF-FE-FF-FF-FF used by holders of EUI-48 identifiers under the IANA OUI as described above
02-00-5E-FF-FE-00-00至02-00-5E-FF-FE-FF-FF-FF由IANA OUI下的EUI-48标识符持有人使用，如上所述
02-00-5E-FF-FF-00-00-00 to 02-00-5E-FF-FF-FF-FF-FF reserved
02-00-5E-FF-FF-00-00至02-00-5E-FF-FF-FF-FF-FF保留
The reserved identifiers above require IESG Ratification (see Section 5.1) for allocation. IANA EUI-64 identifier allocations under the IANA OUI must meet the following requirements:
上述保留标识符需要IESG批准（见第5.1节）进行分配。IANA OUI下的IANA EUI-64标识符分配必须满足以下要求：
o must be for standards purposes (either for an IETF Standard or other standard related to IETF work),
o 必须用于标准目的（IETF标准或与IETF工作相关的其他标准），
o must be for a block of a power-of-two identifiers starting at a boundary which is an equal or greater power of two, including the allocation of one (2**0) identifier,
o 必须适用于从等于或大于2的幂的边界开始的两个标识符的幂的块，包括一个（2**0）标识符的分配，
o must not be used to evade the requirement for vendors to obtain their own block of identifiers from the IEEE, and
o 不得用于规避供应商从IEEE获得自己的标识符块的要求，以及
o must be documented in an Internet Draft or RFC.
o 必须记录在互联网草稿或RFC中。
In addition, approval must be obtained as follows (see the procedure in Section 5.1):
此外，必须获得以下批准（见第5.1节中的程序）：
Small to medium allocations of a block of 1, 2, 4, ..., 134217728, 268435456 (2**0, 2**1, 2**2, ..., 2**27, 2**28) EUI-64 identifiers require Expert Review.
1、2、4、…、134217728、268435456（2**0、2**1、2**2、…、2**27、2**28）EUI-64标识符区块的中小型分配需要专家审查。
Allocations of any size, including 536870912 (2**29) or more EUI-64 identifiers, may be made with IESG Ratification (see Section 5.1).
任何规模的分配，包括536870912（2**29）或更多EUI-64标识符，均可通过IESG批准（见第5.1节）。
To simplify record keeping, all allocations of 65536 (2**16) or less EUI-64 identifiers shall have the Group bit unspecified, that is, shall be allocations of parallel equal size blocks of multicast and unicast identifiers, even if one of these two types is not needed for the proposed use.
为了简化记录保存，65536（2**16）或以下EUI-64标识符的所有分配应具有未指定的组位，即，应为多播和单播标识符的并行等大小块的分配，即使拟议用途不需要这两种类型之一。
There are two other blocks of MAC-48 identifiers that are used by the IETF as described below.
IETF使用的MAC-48标识符还有两块，如下所述。
All MAC-48 multicast identifiers prefixed "33-33" (that is, the 2**32 multicast MAC identifiers in the range from 33-33-00-00-00-00 to 33-33-FF-FF-FF-FF) are used by the IETF for global IPv6 multicast [RFC2464]. In all these identifiers, the Group bit (the bottom bit of the first octet) is on, as is required to work properly with existing hardware as a multicast identifier. They also have the Local bit on and are used for this purpose in IPv6 networks.
IETF将前缀为“33-33”的所有MAC-48多播标识符（即33-33-00-00-00-00至33-33-FF-FF-FF-FF范围内的2**32多播MAC标识符）用于全局IPv6多播[RFC2464]。在所有这些标识符中，组位（第一个八位组的底部位）为on，这是将现有硬件作为多播标识符正常工作所必需的。它们还具有本地位，并在IPv6网络中用于此目的。
(Historical note: It was the custom during IPv6 design to use "3" for unknown or example values, and 3333 Coyote Hill Road, Palo Alto, California, is the address of PARC (Palo Alto Research Center, formerly "Xerox PARC"). Ethernet was originally specified by Digital Equipment Corporation, Intel Corporation, and Xerox Corporation. The pre IEEE [802.3] Ethernet protocol has sometimes been known as "DIX" Ethernet from the first letters of the names of these companies.)
（历史注释：在IPv6设计过程中，习惯使用“3”表示未知值或示例值，而3333 Coyote Hill Road，Palo Alto，California是PARC（Palo Alto研究中心，前身为“Xerox PARC”）的地址。以太网最初由数字设备公司、英特尔公司和施乐公司指定。IEEE之前[802.3]以太网协议有时从这些公司名称的首字母起被称为“DIX”以太网。）
The Informational [RFC2153] declared the 3-octet values from CF-00-00 through CF-FF-FF to be OUIs available for allocation by IANA to software vendors for use in PPP [RFC1661] or for other uses where vendors do not otherwise need an IEEE-assigned OUI. It should be noted that, when used as MAC-48 prefixes, these values have the Local and Group bits on, while all IEEE-allocated OUIs have those bits off. The Group bit is meaningless in PPP. To quote [RFC2153]: "The 'CF0000' series was arbitrarily chosen to match the PPP NLPID 'CF', as a matter of mnemonic convenience."
信息[RFC2153]声明CF-00-00到CF-FF-FF的3个八位字节值为OUI，IANA可将其分配给软件供应商，用于PPP[RFC1661]中，或用于供应商不需要IEEE分配OUI的其他用途。应该注意的是，当用作MAC-48前缀时，这些值的本地位和组位处于打开状态，而所有IEEE分配的OUI的这些位处于关闭状态。组位在PPP中没有意义。引用[RFC2153]：“为了便于记忆，随意选择了‘CF0000’系列以匹配PPP NLPID‘CF’。”
CF-00-00 is reserved, and IANA lists multicast identifier CF-00-00-00-00-00 as used for Ethernet loopback tests.
CF-00-00是保留的，IANA列出了用于以太网环回测试的多播标识符CF-00-00-00-00。
In over a decade of availability, only a handful of values in the 'CF Series' have been allocated. (See http://www.iana.org under both Ethernet Parameters and PPP Parameters.)
在十多年的可用性中，仅分配了“CF系列”中的少数值。（见http://www.iana.org 在以太网参数和PPP参数下。）
The IANA Considerations in [RFC2153] are updated as follows (no technical changes are made): Use of these identifiers based on IANA allocation is deprecated. IANA is directed not to allocate any further values in the 'CF Series'.
[RFC2153]中的IANA注意事项更新如下（未做任何技术更改）：不推荐使用基于IANA分配的这些标识符。IANA不得在“CF系列”中分配任何进一步的值。
Ethernet protocol parameters provide a means of indicating the contents of a frame -- for example, that its contents are IPv4 or IPv6.
以太网协议参数提供了一种指示帧内容的方法，例如，其内容是IPv4或IPv6。
The concept has been extended to labeling by "tags". A tag in this sense is a prefix whose type is identified by an Ethertype that is then followed by either another tag, an Ethertype, or an LSAP protocol indicator for the "main" body of the frame, as described below. Traditionally in the [802_O&A] world, tags are fixed length and do not include any encoding of their own length. Thus, anything that is processing a frame cannot, in general, safely process anything in the frame past an Ethertype it does not understand. An example is the C-tag (formerly the Q-tag) [802.1Q]. It provides customer VLAN and priority information for a frame.
这一概念已扩展到“标签”标签。从这个意义上讲，标签是一个前缀，其类型由Ethertype标识，该Ethertype后面是另一个标签、Ethertype或帧“主体”的LSAP协议指示符，如下所述。传统上，在[802_O&A]世界中，标签是固定长度的，不包含任何自己长度的编码。因此，处理帧的任何东西通常都不能安全地处理帧中的任何东西，而不是它不理解的以太类型。例如，C-tag（以前的Q-tag）[802.1Q]。它提供客户VLAN和帧的优先级信息。
There are two types of protocol identifier parameters that can occur in Ethernet frames after the initial MAC-48 destination and source identifiers:
在初始MAC-48目标和源标识符之后的以太网帧中可能出现两种类型的协议标识符参数：
Ethertypes: These are 16-bit identifiers appearing as the initial two octets after the MAC destination and source (or after a tag) which, when considered as an unsigned integer, are equal to or larger than 0x0600.
Ethertypes：这是16位标识符，显示为MAC目标和源（或标记）后的初始两个八位字节，当视为无符号整数时，等于或大于0x0600。
LSAPs: These are 8-bit protocol identifiers that occur in pairs immediately after an initial 16-bit (two octet) remaining frame length, which is in turn after the MAC destination and source (or after a tag). Such a length must, when considered as an unsigned integer, be less than 0x5DC or it could be mistaken as an Ethertype. LSAPs (Link-Layer Subnet Access Points) occur in pairs where one is intended to indicate the source protocol handler and one the destination protocol handler; however, use cases where the two are different have been relatively rare.
LSAP：这是8位协议标识符，成对出现在初始16位（两个八位组）剩余帧长度之后，依次出现在MAC目标和源之后（或标记之后）。当将此长度视为无符号整数时，它必须小于0x5DC，否则可能会被误认为是Ethertype。LSAP（链路层子网接入点）成对出现，其中一个用于指示源协议处理程序，另一个用于指示目标协议处理程序；然而，两者不同的用例相对较少。
Neither Ethertypes nor LSAPs are allocated by IANA; instead, they are allocated by the IEEE Registration Authority (see Section 1.2 above and the Ethertype Annex below). However, both LSAPs and Ethertypes have extension mechanisms so that they can be used with five-octet Ethernet protocol identifiers under an OUI, including those allocated by IANA under the IANA OUI.
IANA既不分配以太网类型也不分配LSAP；相反，它们由IEEE注册机构分配（见上文第1.2节和下文附录）。但是，LSAP和Ethertype都有扩展机制，因此它们可以与OUI下的五个八位以太网协议标识符一起使用，包括IANA在IANA OUI下分配的标识符。
When using the IEEE 802 LLC format (SNAP) [802_O&A] for a frame, an OUI-based protocol identifier can be expressed as follows:
当对帧使用IEEE 802 LLC格式（SNAP）[802_O&A]时，基于OUI的协议标识符可以表示为：
xx-xx-AA-AA-03-yy-yy-yy-zz-zz
xx-xx-AA-AA-03-yy-yy-yy-zz-zz
where xx-xx is the frame length and, as above, must be small enough not to be confused with an Ethertype; "AA" is the LSAP that indicates this use and is sometimes referred to as the SNAP SAP; "03" is the LLC control octet indicating datagram service; yy-yy-yy is an OUI; and zz-zz is a protocol number, under that OUI, allocated by the OUI owner. The odd five-octet length for such OUI-based protocol identifiers was chosen so that, with the LLC control octet ("03"), the result is 16-bit aligned.
其中xx xx是帧长度，如上所述，必须足够小，以免与Ethertype混淆；“AA”是表示此用途的LSAP，有时称为SNAP SAP；“03”是指示数据报服务的LLC控制八位字节；yy yy yy是一个OUI；zz zz是协议编号，在该OUI下，由OUI所有者分配。选择这种基于OUI的协议标识符的奇数五个八位字节长度，以便使用LLC控制八位字节（“03”），结果是16位对齐的。
When using an Ethertype to indicate the main type for a frame body, the special "OUI Extended Ethertype" 88-B7 is available. Using this Ethertype, a frame body can begin with
当使用Ethertype指示框架主体的主要类型时，可以使用特殊的“OUI扩展Ethertype”88-B7。使用此Ethertype，框架主体可以从
88-B7-yy-yy-yy-zz-zz
88-B7-yy-yy-yy-zz-zz
where yy-yy-yy and zz-zz have the same meaning as in the SNAP format described above.
其中yy yy yy和zz zz的含义与上述快照格式中的含义相同。
It is also possible, within the SNAP format, to use an arbitrary Ethertype. Putting the Ethertype as the zz-zz field after an all zeros OUI (00-00-00) does this. It looks like
在快照格式中，也可以使用任意Ethertype。将Ethertype作为zz zz字段放在全零OUI（00-00-00）之后可以实现这一点。看起来像
xx-xx-AA-AA-03-00-00-00-zz-zz
xx-xx-AA-AA-03-00-00-00-zz-zz
where zz-zz is the Ethertype.
其中zz-zz是以太类型。
(Note that, at this point, the 802 protocol syntax facilities are sufficiently powerful that they could be chained indefinitely. Whether support for such chaining is generally required is not clear, but [802_O&A] requires support for
（请注意，此时，802协议语法功能足够强大，可以无限期链接。通常不清楚是否需要支持此类链接，但[802_O&A]需要支持
xx-xx-AA-AA-03-00-00-00-88-B7-yy-yy-yy-zz-zz
xx-xx-AA-AA-03-00-00-00-88-B7-yy-yy-yy-zz-zz
even though this could be more efficiently expressed by simply pinching out the "00-00-00-88-B7" in the middle.)
尽管这可以通过简单地把中间的“-00～-00—88B7”捏出来更有效地表达出来。
As well as labeling frame contents, 802 Protocol types appear within NBMA (Non-Broadcast Multi-Access) Next Hop Resolution Protocol [RFC2332] messages. Such messages have provisions for both two octet Ethertypes and OUI based protocol types.
除了标记帧内容外，802协议类型也出现在NBMA（非广播多址）下一跳解析协议[RFC2332]消息中。此类消息具有两种八位以太网类型和基于OUI的协议类型的规定。
Two-octet protocol numbers under the IANA OUI are available, as in
IANA OUI下有两个八位字节协议编号，如中所示
xx-xx-AA-AA-03-00-00-5E-zz-zz.
xx-xx-AA-AA-03-00-00-5E-zz-zz。
A number of such allocations have been made out of the 2**16 protocol numbers available from 00-00-5E-00-00 to 00-00-5E-FF-FF (see [IANA]). The extreme values of this range, 00-00-5E-00-00 and 00-00-5E-FF-FF, are reserved and require IESG Ratification for allocation (see Section 5.1). New allocations of SNAP SAP protocol (zz-zz) numbers under the IANA OUI must meet the following requirements:
从00-00-5E-00-00到00-00-5E-FF-FF（参见[IANA]）的2**16协议编号中已经进行了大量此类分配。保留该范围的极值00-00-5E-00-00和00-00-5E-FF-FF，并要求IESG批准分配（见第5.1节）。IANA OUI下SNAP SAP协议（zz zz）编号的新分配必须满足以下要求：
o the allocation must be for standards use (either for an IETF Standard or other standard related to IETF work),
o 分配必须用于标准使用（IETF标准或与IETF工作相关的其他标准），
o it must be documented in an Internet-Draft or RFC, and
o 必须在互联网草案或RFC中记录，以及
o such protocol numbers are not to be allocated for any protocol that has an Ethertype (because that can be expressed by putting an all zeros "OUI" before the Ethertype as described above).
o 此类协议编号不得分配给任何具有Ethertype的协议（因为可以通过在Ethertype之前放置一个全零“OUI”来表示，如上所述）。
In addition, the Expert Review (or IESG Ratification for the two reserved values) must be obtained using the procedure specified in Section 5.1.
此外，必须使用第5.1节规定的程序获得专家评审（或两个保留值的IESG批准）。
Some IEEE 802 and other protocols provide for parameters based on an OUI beyond those discussed above. Such parameters most commonly consist of an OUI plus one octet of additional value. They are usually called "vendor specific" parameters, although "organization specific" might be more accurate. They would look like
一些IEEE 802和其他协议提供了基于OUI的参数，超出了上述讨论的范围。这些参数通常由一个OUI加上一个附加值的八位字节组成。它们通常被称为“特定于供应商”的参数，尽管“特定于组织”可能更准确。他们看起来像
yy-yy-yy-zz
yy yy yy zz
where yy-yy-yy is the OUI and zz is the additional specifier. An example is the Cipher Suite Selector in IEEE 802.11 ([802.11], page 125).
其中yy yy yy是OUI，zz是附加说明符。IEEE 802.11（[802.11]，第125页）中的密码套件选择器就是一个例子。
Values may be allocated under the IANA OUI for such other OUI-based parameter usage by Expert Review except that, for each use, the additional specifier values consisting of all zero bits and all one bits (0x00 and 0xFF for a one-octet specifier) are reserved and require IESG Ratification (see Section 5.1) for allocation. The allocations must be for standards use (either for an IETF Standard or other standard related to IETF work) and be documented in an Internet-Draft or RFC. The first time a value is allocated for a particular parameter of this type, an IANA registry will be created to contain that allocation and any subsequent allocations of values for that parameter under the IANA OUI. The Expert will specify the name of the registry.
通过专家评审，可在IANA OUI下为此类其他基于OUI的参数使用分配值，但对于每次使用，保留由所有零位和所有一位组成的附加说明符值（对于一个八位说明符，0x00和0xFF），并要求IESG批准（见第5.1节）进行分配。分配必须用于标准使用（IETF标准或与IETF工作相关的其他标准），并记录在互联网草案或RFC中。首次为该类型的特定参数分配值时，将创建一个IANA注册表，以包含该分配以及IANA OUI下该参数的任何后续值分配。专家将指定登记处的名称。
(If a different policy from that above is required for such a parameter, a BCP or Standards Track RFC must be adopted updating this BCP and specifying the new policy and parameter.)
（如果此类参数需要与上述不同的策略，则必须采用BCP或标准跟踪RFC更新此BCP并指定新策略和参数。）
The entirety of this document concerns IANA Considerations for the allocation of Ethernet parameters in connection with the IANA OUI and related matters.
本文件的全部内容涉及IANA在分配与IANA OUI相关的以太网参数和相关事项时的注意事项。
Specifically:
明确地：
Section 1.2.1 provides information on the IANA-assigned OUI.
第1.2.1节提供了IANA分配的OUI信息。
Section 2.1.1 lists current EUI-48 assignments under this OUI.
第2.1.1节列出了本OUI下的当前EUI-48任务。
Section 2.1.2 specifies IANA considerations for EUI-48 assignments.
第2.1.2节规定了EUI-48任务的IANA注意事项。
Section 2.2.2 specifies IANA considerations for EUI-64 assignments.
第2.2.2节规定了EUI-64任务的IANA注意事项。
Section 3.1 provides a pointer to current protocol identifier assignments under the IANA OUI, and specifies IANA considerations for protocol identifier assignments.
第3.1节提供了指向IANA OUI下当前协议标识符分配的指针，并指定了协议标识符分配的IANA注意事项。
Section 4 briefly provides IANA considerations relating to OUI-based miscellaneous allocations.
第4节简要介绍了IANA对基于OUI的杂项分配的考虑。
This section specifies the procedure for Expert Review and IESG Ratification of MAC, protocol, and other IANA OUI-based identifiers. The Expert(s) referred to in this document shall consist of one or more persons appointed by and serving at the pleasure of the IESG. The procedure described for Expert Review allocations in this document is fully consistent with the IANA Expert Review policy described in Section 4.1 of [RFC5226].
本节规定了MAC、协议和其他基于IANA OUI的标识符的专家审查和IESG批准程序。本文件中提及的专家应由IESG任命的一名或多名人员组成，并根据IESG的意愿提供服务。本文件中描述的专家评审分配程序与[RFC5226]第4.1节中描述的IANA专家评审政策完全一致。
While finite, the universe of code points from which Expert judged allocations will be made is felt to be large enough that the requirements given in this document and the Experts' good judgment are sufficient guidance. The idea is for the Expert to provide a light sanity check for small allocations of EUI identifiers with increased scrutiny by the Expert for medium-sized allocations of EUI identifiers, and allocations of protocol identifiers and other IANA OUI based parameters. However, it can make sense to allocate very large portions of the MAC identifier code point space. (Note that existing allocations include one for 1/2 of the entire multicast code point space and one for 1/16 of the multicast code point space.) In those cases, and in cases of the allocation of "reserved" values, IESG Ratification of an Expert Review approval recommendation is required as described below. The procedure is as follows:
虽然有限，但专家判断分配所依据的代码点范围足够大，本文件中给出的要求和专家的良好判断足以作为指导。专家的想法是为EUI标识符的小型分配提供轻微的健全性检查，专家对EUI标识符的中型分配以及协议标识符和其他基于IANA OUI的参数的分配进行更多的审查。然而，分配非常大的MAC标识符代码点空间是有意义的。（注意，现有分配包括一个用于整个多播代码点空间的1/2，一个用于多播代码点空间的1/16。）在这些情况下，以及在分配“保留”值的情况下，需要IESG批准专家评审批准建议，如下所述。程序如下：
The applicant always completes the appropriate Template from the Template Annex below and sends it to IANA <iana@iana.org>.
申请人始终填写以下模板附件中的相应模板，并将其发送给IANA<iana@iana.org>.
IANA always sends the Template to an appointed Expert. If the Expert recuses themselves or is non-responsive, IANA may choose an alternative appointed Expert or, if none are available, will contact the IESG.
IANA总是将模板发送给指定的专家。如果专家回避或没有回应，IANA可以选择另一位指定专家，或者，如果没有，将联系IESG。
If the allocation is based on Expert Review:
如果分配基于专家审查：
If IANA receives a disapproval from an Expert selected to review an application Template, the application will be denied. If IANA receives approval and code points are available, IANA will make the requested allocation.
如果IANA收到被选中审查申请模板的专家的不批准，申请将被拒绝。如果IANA获得批准且代码点可用，IANA将进行请求的分配。
If the allocation is based on IESG Ratification, the procedure starts with the first two steps above for Expert Review. If the Expert disapproves the application, they simply inform IANA; however, if the Expert believes the application should be approved, or is uncertain and believes that the circumstances warrant the attention of the IESG, the Expert will inform IANA about their advice and IANA will forward the application, together with the reasons for approval or uncertainty, to the IESG. The IESG must decide whether the allocation will be granted. This can be accomplished by a management item in an IESG telechat as done for other types of requests. If the IESG decides not to ratify a favorable opinion by the Expert or decides against an application where the Expert is uncertain, the application is denied, otherwise it is granted. The IESG will communicate its decision to the Expert and to IANA.
如果分配以IESG批准为基础，则程序从上述前两个步骤开始，以供专家审查。如果专家不同意申请，他们只需通知IANA；但是，如果专家认为申请应获得批准，或者不确定，并且认为情况值得IESG注意，则专家将通知IANA他们的建议，IANA将把申请连同批准或不确定的原因转发给IESG。IESG必须决定是否批准分配。这可以通过IESG telechat中的管理项来完成，就像对其他类型的请求所做的那样。如果IESG决定不批准专家的有利意见，或在专家不确定的情况下决定反对申请，则该申请将被拒绝，否则将被批准。IESG将向专家和IANA传达其决定。
IANA also maintains an informational listing on its web site concerning Ethertypes, OUIs, and multicast addresses allocated under OUIs other than the IANA OUI. IANA shall update that list when changes are provided by the Expert.
IANA还在其网站上维护一个关于以太网类型、OUI和在除IANA OUI之外的OUI下分配的多播地址的信息列表。当专家提供变更时，IANA应更新该列表。
When the available space for either multicast or unicast EUI-48 identifiers under OUI 00-00-5E have been 90% or more exhausted, IANA should request an additional OUI from the IEEE Registration Authority (see Section 1.2) for further IANA allocation use.
当OUI 00-00-5E下用于多播或单播EUI-48标识符的可用空间已耗尽90%或更多时，IANA应向IEEE注册机构请求额外的OUI（见第1.2节），以进一步使用IANA分配。
This document is concerned with allocation of parameters under the IANA OUI and closely related matters. It is not directly concerned with security.
本文件涉及IANA OUI下的参数分配以及密切相关的事项。它与安全没有直接关系。
[802_O&A] "IEEE Standard for Local and Metropolitan Area Networks: Overview and Architecture", IEEE 802-2001, 8 March 2002.
[802_O&A]“局域网和城域网的IEEE标准：概述和体系结构”，IEEE 802-2001，2002年3月8日。
"IEEE Standard for Local and Metropolitan Area Networks: Overview and Architecture / Amendment 1: Ethertypes for Prototype and Vendor-Specific Protocol Development", IEEE 802a-2003, 18 September 2003.
“IEEE局域网和城域网标准：概述和体系结构/修改件1：原型和供应商特定协议开发的以太网类型”，IEEE 802a-2003，2003年9月18日。
[802.1Q] "IEEE Standard for Local and metropolitan area networks / Virtual Bridged Local Area Networks", IEEE 802.1Q-2005, 19 May 2006.
[802.1Q]“局域网和城域网/虚拟桥接局域网的IEEE标准”，IEEE 802.1Q-2005，2006年5月19日。
[802.3] "IEEE Standard for Information technology / Telecommunications and information exchange between systems / Local and metropolitan area networks / Specific requirements / Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications", IEEE 802.3-2005, 9 December 2005.
[802.3]“系统/局域网和城域网之间信息技术/电信和信息交换IEEE标准/具体要求/第3部分：带冲突检测的载波侦听多址（CSMA/CD）接入方法和物理层规范”，IEEE 802.3-2005，2005年12月9日。
[802.11] "IEEE Standard for Information technology / Telecommunications and information exchange between systems / Local and metropolitan area networks / Specific requirements / Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications", IEEE 802.11-2007, 11 June 2007.
[802.11]“系统/局域网和城域网之间信息技术/电信和信息交换的IEEE标准/特定要求/第11部分：无线LAN介质访问控制（MAC）和物理层（PHY）规范”，IEEE 802.11-2007，2007年6月11日。
[EUI-64] IEEE, "Guidelines for 64-bit Global Identifier (EUI-64) Registration Authority", <http://standards.ieee.org/ regauth/oui/tutorials/EUI64.html>, March 1997.
[EUI-64]IEEE，“64位全局标识符（EUI-64）注册机构指南”<http://standards.ieee.org/ regauth/oui/tutorials/EUI64.html>，1997年3月。
[IANA] Internet Assigned Numbers Authority, Ethernet Types, <http://www.iana.org>.
[IANA]互联网分配号码管理局，以太网类型<http://www.iana.org>.
[IEEE] Institute of Electrical and Electronics Engineers, <http://www.ieee.org>.
[IEEE]电气和电子工程师学会<http://www.ieee.org>.
[IEEE802] IEEE 802 LAN/MAN (Local Area Network / Metropolitan Area Network) Standards Committee, <http://www.ieee802.org>.
[IEEE802]IEEE 802 LAN/MAN（局域网/城域网）标准委员会<http://www.ieee802.org>.
[RFC1112] Deering, S., "Host Extensions for IP Multicasting", STD 5, RFC 1112, Stanford University, August 1989.
[RFC1112]Deering，S.，“IP多播的主机扩展”，STD 5，RFC 1112，斯坦福大学，1989年8月。
[RFC1661] Simpson, W., "The Point-to-Point Protocol (PPP)", STD 51, RFC 1661, July 1994.
[RFC1661]辛普森，W.“点对点协议（PPP）”，标准51，RFC1661，1994年7月。
[RFC2153] Simpson, W., "PPP Vendor Extensions", RFC 2153, May 1997.
[RFC2153]辛普森，W.，“PPP供应商扩展”，RFC 2153，1997年5月。
[RFC2332] Luciani, J., Katz, D., Piscitello, D., Cole, B., and N. Doraswamy, "NBMA Next Hop Resolution Protocol (NHRP)", RFC 2332, April 1998.
[RFC2332]Luciani，J.，Katz，D.，Piscitello，D.，Cole，B.，和N.Doraswamy，“NBMA下一跳解析协议（NHRP）”，RFC 2332，1998年4月。
[RFC2464] Crawford, M., "Transmission of IPv6 Packets over Ethernet Networks", RFC 2464, December 1998.
[RFC2464]克劳福德，M.，“通过以太网传输IPv6数据包”，RFC2464，1998年12月。
[RFC3768] Hinden, R., "Virtual Router Redundancy Protocol (VRRP)", RFC 3768, April 2004.
[RFC3768]Hinden，R.，“虚拟路由器冗余协议（VRRP）”，RFC 3768，2004年4月。
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing Architecture", RFC 4291, February 2006.
[RFC4291]Hinden，R.和S.Deering，“IP版本6寻址体系结构”，RFC 42912006年2月。
[RFC5214] Templin, F., Gleeson, T., and D. Thaler, "Intra-Site Automatic Tunnel Addressing Protocol (ISATAP)", RFC 5214, March 2008.
[RFC5214]Templin，F.，Gleeson，T.，和D.Thaler，“站点内自动隧道寻址协议（ISATAP）”，RFC 52142008年3月。
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008.
[RFC5226]Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 5226，2008年5月。
[RFC5332] Eckert, T., Rosen, E., Ed., Aggarwal, R., and Y. Rekhter, "MPLS Multicast Encapsulations", RFC 5332, August 2008.
[RFC5332]Eckert，T.，Rosen，E.，Ed.，Aggarwal，R.，和Y.Rekhter，“MPLS多播封装”，RFC 5332，2008年8月。
This annex provides the specific templates for IANA allocations of parameters. Explanatory words in parenthesis in the templates below may be deleted in a completed template as submitted to IANA.
本附件提供了IANA参数分配的具体模板。在提交给IANA的完整模板中，可删除以下模板中括号内的解释性词语。
Applicant Name:
申请人姓名：
Applicant Email:
申请人电邮：
Applicant Telephone: (starting with country code)
申请人电话：（以国家代码开头）
Use Name: (brief name of Parameter use such as "Foo Protocol")
使用名称：（参数使用的简要名称，如“Foo协议”）
Document: (ID or RFC specifying use to which the identifier or block of identifiers will be put.)
文档：（ID或RFC，指定标识符或标识符块的用途。）
Specify whether this is an application for EUI-48 or EUI-64 identifiers:
指定这是EUI-48还是EUI-64标识符的应用程序：
Size of Block requested: (must be a power-of-two-sized block, can be a block of size one (2**0))
请求的块大小：（必须是两个大小块的幂，可以是一个大小块（2**0））
Specify multicast, unicast, or both:
指定多播、单播或两者：
Applicant Name:
申请人姓名：
Applicant Email:
申请人电邮：
Applicant Telephone: (starting with country code)
申请人电话：（以国家代码开头）
Use Name: (brief name of use of code point such as "Foo Protocol")
使用名称：（代码点使用的简要名称，如“Foo协议”）
Document: (ID or RFC specifying use to which the protocol identifier will be put.)
文档：（ID或RFC，指定协议标识符将放置到的用途。）
Applicant Name:
申请人姓名：
Applicant Email:
申请人电邮：
Applicant Telephone: (starting with country code)
申请人电话：（以国家代码开头）
Protocol where the OUI Based Parameter for which a value is being requested appears: (such as: Cipher Suite selection in IEEE 802.11)
出现请求值的基于OUI的参数的协议：（例如：IEEE 802.11中的密码套件选择）
Use Name: (brief name of use of code point to be allocated, such as "Foo Cipher Suite")
使用名称：（要分配的代码点使用的简要名称，如“Foo密码套件”）
Document: (ID or RFC specifying use to which the other IANA OUI based parameter value will be put.)
文档：（ID或RFC，指定其他基于IANA OUI的参数值将用于哪个用途。）
This annex lists some Ethertypes specified for IETF Protocols or by IEEE 802 as known at the time of publication. A more up-to-date list may be available on the IANA web site, currently at [IANA]. The IEEE Registration Authority page of Ethertypes, http://standards.ieee.org/regauth/ethertype/eth.txt, may also be useful. See Section 3 above.
本附录列出了IETF协议或IEEE 802在发布时已知的一些以太网类型。IANA网站上可能有更为最新的列表，目前位于[IANA]。IEEE注册机构页面，共页，http://standards.ieee.org/regauth/ethertype/eth.txt，也可能有用。见上文第3节。
0x0800 Internet Protocol Version 4 (IPv4) 0x0806 Address Resolution Protocol (ARP) 0x0808 Frame Relay ARP 0x880B Point-to-Point Tunneling Protocol (PPTP) 0x880C General Switch Management Protocol (GSMP) 0x8035 Reverse Address Resolution Protocol (RARP) 0x86DD Internet Protocol Version 6 (IPv6) 0x8847 MPLS 0x8848 MPLS with upstream-assigned label 0x8861 Multicast Channel Allocation Protocol (MCAP) 0x8863 PPP over Ethernet (PPPoE) Discovery Stage 0x8864 PPP over Ethernet (PPPoE) Session Stage
0x0800 Internet协议版本4（IPv4）0x0806地址解析协议（ARP）0x0808帧中继ARP 0x880B点对点隧道协议（PPTP）0x880C通用交换机管理协议（GSMP）0x8035反向地址解析协议（RARP）0x86DD Internet协议版本6（IPv6）0x8847 MPLS 0x8848 MPLS，带上游分配标签0x8861多播信道分配协议（MCAP）0x8863以太网PPP（PPPoE）发现阶段0x8864以太网PPP（PPPoE）会话阶段
0x8100 IEEE Std 802.1Q - Customer VLAN Tag Type (C-Tag, formerly called the Q-Tag) 0x8808 IEEE Std 802.3 - Ethernet Passive Optical Network (EPON) 0x888E IEEE Std 802.1X - Port-based network access control 0x88A8 IEEE Std 802.1Q - Service VLAN tag identifier (S-Tag) 0x88B5 IEEE Std 802 - Local Experimental Ethertype 0x88B6 IEEE Std 802 - Local Experimental Ethertype 0x88B7 IEEE Std 802 - OUI Extended Ethertype 0x88C7 IEEE Std 802.11i - Pre-Authentication 0x88CC IEEE Std 802.1AB - Link Layer Discovery Protocol (LLDP) 0x88E5 IEEE Std 802.1AE - Media Access Control Security 0x88F5 IEEE Std 802.1ak - Multiple VLAN Registration Protocol (MVRP) 0x88F6 IEEE Std 802.1Q - Multiple Multicast Registration Protocol (MMRP) 0x890D IEEE 802.11r - Fast Roaming Remote Request
0x8100 IEEE Std 802.1Q-客户VLAN标记类型（C标记，以前称为Q标记）0x8808 IEEE Std 802.3-以太网无源光网络（EPON）0x888E IEEE Std 802.1X-基于端口的网络访问控制0x88A8 IEEE Std 802.1Q-服务VLAN标记标识符（S标记）0x88B5 IEEE标准802-本地实验以太网类型0x88B6 IEEE标准802-本地实验以太网类型0x88B7 IEEE标准802-OUI扩展以太网类型0x88C7 IEEE标准802.11i-预认证0x88CC IEEE标准802.1AB-链路层发现协议（LLDP）0x88E5 IEEE Std 802.1AE-媒体访问控制安全0x88F5 IEEE Std 802.1ak-多VLAN注册协议（MVRP）0x88F6 IEEE Std 802.1Q-多播注册协议（MMRP）0x890D IEEE 802.11r-快速漫游远程请求
Author's Address
作者地址
Donald E. Eastlake 3rd 155 Beaver Street Milford, MA 01757 USA
美国马萨诸塞州米尔福德市海狸街155号唐纳德E.东湖第三大道01757号
Phone: +1-508-634-2066
EMail: d3e3e3@gmail.com
Phone: +1-508-634-2066
EMail: d3e3e3@gmail.com
Full Copyright Statement
完整版权声明
Copyright (C) The IETF Trust (2008).
版权所有（C）IETF信托基金（2008年）。
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件及其包含的信息以“原样”为基础提供，贡献者、他/她所代表或赞助的组织（如有）、互联网协会、IETF信托基金和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.