Internet Engineering Task Force (IETF) S. Kashima
Request for Comments: 7133 NTT
Category: Standards Track A. Kobayashi, Ed.
ISSN: 2070-1721 NTT East
P. Aitken
Cisco Systems, Inc.
May 2014
Internet Engineering Task Force (IETF) S. Kashima
Request for Comments: 7133 NTT
Category: Standards Track A. Kobayashi, Ed.
ISSN: 2070-1721 NTT East
P. Aitken
Cisco Systems, Inc.
May 2014
Information Elements for Data Link Layer Traffic Measurement
数据链路层流量测量的信息元素
Abstract
摘要
This document describes Information Elements related to the data link layer. They are used by the IP Flow Information Export (IPFIX) protocol for encoding measured data link layer traffic information.
本文档描述了与数据链路层相关的信息元素。IP流信息导出（IPFIX）协议使用它们对测量的数据链路层流量信息进行编码。
Status of This Memo
关于下段备忘
This is an Internet Standards Track document.
这是一份互联网标准跟踪文件。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。有关互联网标准的更多信息，请参见RFC 5741第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7133.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc7133.
Copyright Notice
版权公告
Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2014 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction ....................................................4
1.1. Conventions Used in This Document ..........................4
2. Extended Ethernet Technology ....................................4
2.1. Wide-Area Ethernet Technology Summary ......................4
2.2. Virtual Ethernet Technology Summary ........................5
3. Modification and Addition of Information Elements
Related to Data Link Layer ......................................6
3.1. Existing Information Elements ..............................7
3.1.1. dataLinkFrameSize ...................................8
3.1.2. dataLinkFrameSection ................................9
3.1.3. layer2OctetDeltaCount ...............................9
3.1.4. layer2OctetTotalCount ..............................10
3.1.5. layer2FrameDeltaCount ..............................10
3.1.6. layer2FrameTotalCount ..............................11
3.2. New Information Elements ..................................11
3.2.1. dataLinkFrameType ..................................12
3.2.2. sectionOffset ......................................12
3.2.3. sectionExportedOctets ..............................13
3.2.4. dot1qServiceInstanceTag ............................13
3.2.5. dot1qServiceInstanceId .............................14
3.2.6. dot1qServiceInstancePriority .......................14
3.2.7. dot1qCustomerSourceMacAddress ......................15
3.2.8. dot1qCustomerDestinationMacAddress .................15
3.2.9. postL2OctetDeltaCount ..............................16
3.2.10. postMCastL2OctetDeltaCount ........................16
3.2.11. postL2OctetTotalCount .............................17
3.2.12. postMCastL2OctetTotalCount ........................17
3.2.13. minimumL2TotalLength ..............................18
3.2.14. maximumL2TotalLength ..............................18
3.2.15. droppedL2OctetDeltaCount ..........................19
3.2.16. droppedL2OctetTotalCount ..........................19
3.2.17. ignoredL2OctetTotalCount ..........................20
3.2.18. notSentL2OctetTotalCount ..........................20
3.2.19. layer2OctetDeltaSumOfSquares ......................21
3.2.20. layer2OctetTotalSumOfSquares ......................21
4. Modification of Existing Information Elements Related
to Packet Section ..............................................22
4.1. ipHeaderPacketSection .....................................22
4.2. ipPayloadPacketSection ....................................23
4.3. mplsLabelStackSection .....................................24
4.4. mplsPayloadPacketSection ..................................25
5. Modification of Existing Information Elements Related
to VLAN Tag ....................................................26
5.1. dot1qVlanId ...............................................26
5.2. dot1qPriority .............................................27
5.3. dot1qCustomerVlanId .......................................27
1. Introduction ....................................................4
1.1. Conventions Used in This Document ..........................4
2. Extended Ethernet Technology ....................................4
2.1. Wide-Area Ethernet Technology Summary ......................4
2.2. Virtual Ethernet Technology Summary ........................5
3. Modification and Addition of Information Elements
Related to Data Link Layer ......................................6
3.1. Existing Information Elements ..............................7
3.1.1. dataLinkFrameSize ...................................8
3.1.2. dataLinkFrameSection ................................9
3.1.3. layer2OctetDeltaCount ...............................9
3.1.4. layer2OctetTotalCount ..............................10
3.1.5. layer2FrameDeltaCount ..............................10
3.1.6. layer2FrameTotalCount ..............................11
3.2. New Information Elements ..................................11
3.2.1. dataLinkFrameType ..................................12
3.2.2. sectionOffset ......................................12
3.2.3. sectionExportedOctets ..............................13
3.2.4. dot1qServiceInstanceTag ............................13
3.2.5. dot1qServiceInstanceId .............................14
3.2.6. dot1qServiceInstancePriority .......................14
3.2.7. dot1qCustomerSourceMacAddress ......................15
3.2.8. dot1qCustomerDestinationMacAddress .................15
3.2.9. postL2OctetDeltaCount ..............................16
3.2.10. postMCastL2OctetDeltaCount ........................16
3.2.11. postL2OctetTotalCount .............................17
3.2.12. postMCastL2OctetTotalCount ........................17
3.2.13. minimumL2TotalLength ..............................18
3.2.14. maximumL2TotalLength ..............................18
3.2.15. droppedL2OctetDeltaCount ..........................19
3.2.16. droppedL2OctetTotalCount ..........................19
3.2.17. ignoredL2OctetTotalCount ..........................20
3.2.18. notSentL2OctetTotalCount ..........................20
3.2.19. layer2OctetDeltaSumOfSquares ......................21
3.2.20. layer2OctetTotalSumOfSquares ......................21
4. Modification of Existing Information Elements Related
to Packet Section ..............................................22
4.1. ipHeaderPacketSection .....................................22
4.2. ipPayloadPacketSection ....................................23
4.3. mplsLabelStackSection .....................................24
4.4. mplsPayloadPacketSection ..................................25
5. Modification of Existing Information Elements Related
to VLAN Tag ....................................................26
5.1. dot1qVlanId ...............................................26
5.2. dot1qPriority .............................................27
5.3. dot1qCustomerVlanId .......................................27
5.4. dot1qCustomerPriority .....................................27
6. The Relationship between Ethernet Header Fields and
Information Elements ...........................................28
7. Security Considerations ........................................29
8. IANA Considerations ............................................29
9. Acknowledgments ................................................30
10. References ....................................................30
10.1. Normative References .....................................30
10.2. Informative References ...................................31
Appendix A. Frame Formats ........................................32
Appendix B. Template Format Example ..............................40
5.4. dot1qCustomerPriority .....................................27
6. The Relationship between Ethernet Header Fields and
Information Elements ...........................................28
7. Security Considerations ........................................29
8. IANA Considerations ............................................29
9. Acknowledgments ................................................30
10. References ....................................................30
10.1. Normative References .....................................30
10.2. Informative References ...................................31
Appendix A. Frame Formats ........................................32
Appendix B. Template Format Example ..............................40
Ethernet [IEEE802.1D] and VLAN (Virtual LAN) technologies had been used only in Local Area Networks. Recently, they have been used in Wide Area Networks, e.g., Layer 2 VPN (L2 VPN) services. Accordingly, carrier networks using VLAN technologies have been enhanced to Provider Bridged Networks and Provider Backbone Bridged Networks [IEEE802.1Q]. In addition, Ethernet in data centers has also been enhanced for server virtualization and input/output (I/O) consolidation.
以太网[IEEE802.1D]和VLAN（虚拟局域网）技术仅用于局域网。最近，它们已用于广域网，例如第2层VPN（L2 VPN）服务。因此，使用VLAN技术的运营商网络已增强为提供商桥接网络和提供商主干桥接网络[IEEE802.1Q]。此外，数据中心中的以太网也得到了增强，用于服务器虚拟化和输入/输出（I/O）整合。
While these innovations provide flexibility, scalability, and mobility to an existing network architecture, they increase the complexity of traffic measurement due to the existence of various Ethernet header formats. To cope with this, a more sophisticated method of traffic measurement is required.
虽然这些创新为现有网络架构提供了灵活性、可扩展性和移动性，但由于存在各种以太网报头格式，它们增加了流量测量的复杂性。为了解决这个问题，需要一种更复杂的交通量测量方法。
IPFIX and Packet Sampling (PSAMP) help to resolve these problems. However, the PSAMP Information Model [RFC5477] and the IPFIX Information Model [RFC7011] don't yet contain enough Information Elements related to the data link layer, e.g., Ethernet header forms. This document describes existing and new Information Elements related to data link layers that enable a more sophisticated traffic measurement method.
IPFIX和数据包采样（PSAMP）有助于解决这些问题。然而，PSAMP信息模型[RFC5477]和IPFIX信息模型[RFC7011]还没有包含足够的与数据链路层相关的信息元素，例如以太网报头表单。本文档描述了与数据链路层相关的现有和新的信息元素，这些信息元素支持更复杂的流量测量方法。
Note that this document does not update [RFC5477] or [RFC7011] because IANA's IPFIX registry [IANA-IPFIX] is the ultimate Information Element reference, per Section 1 of [RFC7012].
请注意，本文件不更新[RFC5477]或[RFC7011]，因为根据[RFC7012]第1节，IANA的IPFIX注册表[IANA-IPFIX]是最终信息元素参考。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[RFC2119]中所述进行解释。
Provider Bridge and Provider Backbone Bridge [IEEE802.1Q], which are standards for Wide-Area Ethernet, are described below.
提供商网桥和提供商主干网桥[IEEE802.1Q]是广域以太网的标准，如下所述。
o In Provider Bridge [IEEE802.1Q], there are two VLAN IDs: Service VLAN Identifier (S-VID) and Customer VLAN Identifier (C-VID). S-VID is assigned to an Ethernet frame by a service provider, while C-VID is independently assigned to an Ethernet frame by a customer. Frame switching in a service provider network is based on only S-VID.
o 在提供者网桥[IEEE802.1Q]中，有两个VLAN ID：服务VLAN标识符（S-VID）和客户VLAN标识符（C-VID）。服务提供商将S-VID分配给以太网帧，而客户将C-VID独立分配给以太网帧。服务提供商网络中的帧交换仅基于S-VID。
o In Provider Backbone Bridge [IEEE802.1Q], new Ethernet fields, such as Backbone VLAN Identifier (B-VID) and Backbone Service Instance Identifier (I-SID), are introduced to overcome the limitations on the VLAN identifier space and to isolate the service provider and customer identifier spaces. Frame switching is based on a 12-bit B-VID, and customer identification is based on a 24-bit I-SID. A flexible network design has become possible because network management is separated from customer management. Other Ethernet fields that indicate quality of service (QoS) class are Backbone VLAN Priority Code Point (B-PCP), Backbone VLAN Drop Eligible Indicator (B-DEI), Backbone Service Instance Priority Code Point (I-PCP), and Backbone Service Instance Drop Eligible Indicator (I-DEI).
o 在提供商主干网桥[IEEE802.1Q]中，引入了新的以太网字段，如主干VLAN标识符（B-VID）和主干服务实例标识符（I-SID），以克服VLAN标识符空间的限制，并隔离服务提供商和客户标识符空间。帧切换基于12位B-VID，客户标识基于24位I-SID。由于网络管理与客户管理分离，灵活的网络设计成为可能。指示服务质量（QoS）类别的其他以太网字段包括主干VLAN优先级代码点（B-PCP）、主干VLAN丢弃合格指示符（B-DEI）、主干服务实例优先级代码点（I-PCP）和主干服务实例丢弃合格指示符（I-DEI）。
The Provider Backbone Bridge technologies have enhanced a Wide-Area Ethernet service from a flat network to a hierarchical network consisting of a Provider Bridged Network and Provider Backbone Bridged Network.
提供商主干网桥技术已将广域以太网服务从平面网络增强为由提供商桥接网络和提供商主干桥接网络组成的分层网络。
Frame formats used in Wide-Area Ethernet are shown in Appendix A.
广域以太网中使用的帧格式如附录A所示。
There have been several challenges in the existing virtual switches environment in a data center. One is the lack of network management visibility: limited features on virtual switches make it difficult to monitor traffic among virtual machines (VMs). Another is the lack of management scalability and flexibility: increasing the number of VMs for multi-tenant architecture causes an increase in the number of virtual switches and in the number of the traffic control policies, which reach the limitations of network management scalability and flexibility.
在数据中心的现有虚拟交换机环境中存在一些挑战。一个是缺乏网络管理可视性：虚拟交换机上的有限功能使得难以监控虚拟机（VM）之间的流量。另一个原因是缺乏管理的可伸缩性和灵活性：增加多租户体系结构的虚拟机数量会导致虚拟交换机数量和流量控制策略数量的增加，从而达到网络管理可伸缩性和灵活性的限制。
In this situation, the IEEE 802.1 working group is standardizing virtual bridging technologies such as Edge Virtual Bridging (EVB), including two kinds of Edge Relays: Virtual Edge Bridge (VEB) and Virtual Edge Port Aggregator (VEPA) [IEEE802.1Qbg]. The VEB is a bridge that provides bridging among multiple VMs and the external bridging environment. The VEPA is a bridge-like device on a host that forwards all internal traffic to the adjacent EVB bridge and then distributes any traffic received from the adjacent EVB bridge to VMs. The VEPA makes all the VM-to-VM traffic visible to the EVB bridge so that the traffic can be monitored and so that the EVB bridge can apply filtering to the traffic.
在这种情况下，IEEE 802.1工作组正在标准化边缘虚拟桥接（EVB）等虚拟桥接技术，包括两种边缘中继：虚拟边缘桥接（VEB）和虚拟边缘端口聚合器（VEPA）[IEEE802.1Qbg]。VEB是在多个VM和外部桥接环境之间提供桥接的桥接器。VEPA是主机上的一种类似网桥的设备，它将所有内部通信转发给相邻的EVB网桥，然后将从相邻EVB网桥接收到的任何通信分发给VM。VEPA使所有VM-to-VM流量对EVB网桥可见，以便可以监控流量，并使EVB网桥可以对流量应用过滤。
To improve flexibility, a virtual link between a host system and EVB bridge is standardized as S-channel. S-channel allows a bridge to treat the traffic in the virtual link as if it comes in on a separate
为了提高灵活性，主机系统和EVB网桥之间的虚拟链路被标准化为S通道。S通道允许网桥将虚拟链路中的流量视为在单独的网络上传输
port. For example, in the host, an S-channel may be attached to a VEB or a VEPA or directly to an internal port in order to apply each port-based filtering rule to the traffic. S-channel over the link between a host and its adjacent bridge uses Service VLAN Tag (S-TAG) [IEEE802.1Q]. When S-channel is in use, frames on the link carry an S-TAG to identify the S-channel.
港口城市例如，在主机中，S信道可以连接到VEB或VEPA，或者直接连接到内部端口，以便将每个基于端口的过滤规则应用于业务。主机与其相邻网桥之间链路上的S通道使用服务VLAN标签（S标签）[IEEE802.1Q]。当使用S通道时，链路上的帧携带S标签以识别S通道。
On the other hand, Bridge Port Extension emulates single Extended Bridge from multiple physical switches and virtual switches, and it also simplifies network management. Also, it solves the lack of network management visibility by forwarding all traffic into a central Controlling Bridge using E-channel. E-channel over the link between a Bridge Port Extender and a Controlling Bridge uses E-TAG defined in [IEEE802.1BR].
另一方面，网桥端口扩展模拟来自多个物理交换机和虚拟交换机的单个扩展网桥，并且简化了网络管理。此外，它还通过使用E通道将所有流量转发到中央控制网桥，解决了网络管理可见性不足的问题。网桥端口扩展器和控制网桥之间链路上的E通道使用[IEEE802.1BR]中定义的E标签。
Traffic monitoring over S-channel and E-channel is required in order to get visibility of VM-to-VM traffic and visibility of each channel's traffic on a virtual link.
需要通过S通道和E通道进行流量监控，以获得VM对VM流量的可见性以及虚拟链路上每个通道流量的可见性。
Frame formats with E-TAG used in E-channel and S-TAG used in S-channel are shown in Appendix A. Though these frames carry special tags while on the link, those tags identify a virtual port (or for multicast in the downstream direction, a set of virtual ports) to which they are destined. These tag values only have local meaning, and the Flow would be reported as sent and arriving on the corresponding virtual ports. Therefore, IPFIX does not need to monitor data based on these tags.
Frame formats with E-TAG used in E-channel and S-TAG used in S-channel are shown in Appendix A. Though these frames carry special tags while on the link, those tags identify a virtual port (or for multicast in the downstream direction, a set of virtual ports) to which they are destined. These tag values only have local meaning, and the Flow would be reported as sent and arriving on the corresponding virtual ports. Therefore, IPFIX does not need to monitor data based on these tags.translate error, please retry
3. Modification and Addition of Information Elements Related to Data Link Layer
3. 修改和添加与数据链路层相关的信息元素
The Information Elements listed in the upper section of Table 1 are necessary for enabling IPFIX and PSAMP traffic measurement for the data link layer, which is not limited to Ethernet because the method can be applied to other data link protocols as well.
表1上半部分列出的信息元素对于数据链路层启用IPFIX和PSAMP流量测量是必要的，数据链路层不限于以太网，因为该方法也可以应用于其他数据链路协议。
Information Elements in the middle section of Table 1 are necessary for enabling the IPFIX and PSAMP traffic measurement for [IEEE802.1Q].
表1的中间部分中的信息元素对于启用IEEE802.1q]的IPFIX和PSAMP流量测量是必要的。
Information Elements in the lower section of Table 1 are octet counter or packet length for layer 2, and they are necessary for enabling IPFIX and PSAMP traffic measurement for the data link layer.
表1下半部分中的信息元素是第2层的八位字节计数器或数据包长度，它们是为数据链路层启用IPFIX和PSAMP流量测量所必需的。
+-----+------------------------------------+
| ID | Name |
+-----+------------------------------------+
| 312 | dataLinkFrameSize |
| 315 | dataLinkFrameSection |
| 408 | dataLinkFrameType |
| 409 | sectionOffset |
| 410 | sectionExportedOctets |
+-----+------------------------------------+
| 411 | dot1qServiceInstanceTag |
| 412 | dot1qServiceInstanceId |
| 413 | dot1qServiceInstancePriority |
| 414 | dot1qCustomerSourceMacAddress |
| 415 | dot1qCustomerDestinationMacAddress |
+-----+------------------------------------+
| 352 | layer2OctetDeltaCount |
| 353 | layer2OctetTotalCount |
| 417 | postL2OctetDeltaCount |
| 418 | postMCastL2OctetDeltaCount |
| 420 | postL2OctetTotalCount |
| 421 | postMCastL2OctetTotalCount |
| 422 | minimumL2TotalLength |
| 423 | maximumL2TotalLength |
| 424 | droppedL2OctetDeltaCount |
| 425 | droppedL2OctetTotalCount |
| 426 | ignoredL2OctetTotalCount |
| 427 | notSentL2OctetTotalCount |
| 428 | layer2OctetDeltaSumOfSquares |
| 429 | layer2OctetTotalSumOfSquares |
| 430 | layer2FrameDeltaCount |
| 431 | layer2FrameTotalCount |
+-----+------------------------------------+
+-----+------------------------------------+
| ID | Name |
+-----+------------------------------------+
| 312 | dataLinkFrameSize |
| 315 | dataLinkFrameSection |
| 408 | dataLinkFrameType |
| 409 | sectionOffset |
| 410 | sectionExportedOctets |
+-----+------------------------------------+
| 411 | dot1qServiceInstanceTag |
| 412 | dot1qServiceInstanceId |
| 413 | dot1qServiceInstancePriority |
| 414 | dot1qCustomerSourceMacAddress |
| 415 | dot1qCustomerDestinationMacAddress |
+-----+------------------------------------+
| 352 | layer2OctetDeltaCount |
| 353 | layer2OctetTotalCount |
| 417 | postL2OctetDeltaCount |
| 418 | postMCastL2OctetDeltaCount |
| 420 | postL2OctetTotalCount |
| 421 | postMCastL2OctetTotalCount |
| 422 | minimumL2TotalLength |
| 423 | maximumL2TotalLength |
| 424 | droppedL2OctetDeltaCount |
| 425 | droppedL2OctetTotalCount |
| 426 | ignoredL2OctetTotalCount |
| 427 | notSentL2OctetTotalCount |
| 428 | layer2OctetDeltaSumOfSquares |
| 429 | layer2OctetTotalSumOfSquares |
| 430 | layer2FrameDeltaCount |
| 431 | layer2FrameTotalCount |
+-----+------------------------------------+
Table 1: Information Elements Related to Data Link Layer
表1：与数据链路层相关的信息元素
Some existing Information Elements are required for data link layer export. Their details are reproduced here from IANA's IPFIX registry [IANA-IPFIX]. Additions per this document appear between *.
数据链路层导出需要一些现有的信息元素。它们的详细信息在此从IANA的IPFIX注册表[IANA-IPFIX]复制。根据本文档添加的内容显示在*之间。
Section 3.1.1 introduces the missing Data Type Semantics for the dataLinkFrameSize Information Element, which is held to be an interoperable change per #4 in Section 5.2 of [RFC7013].
第3.1.1节介绍了dataLinkFrameSize信息元素缺少的数据类型语义，根据[RFC7013]第5.2节中的第4节，该信息元素被认为是可互操作的更改。
Section 3.1.2 extends the definition of the dataLinkFrameSection Information Element with reference to the new sectionOffset Information Element, which is also an interoperable change per #4 in Section 5.2 of [RFC7013].
第3.1.2节参考新的sectionOffset信息元素扩展了dataLinkFrameSection信息元素的定义，该信息元素也是[RFC7013]第5.2节第4节中的可互操作变更。
The layer2OctetDeltaCount Information Element reports the number of layer 2 octets since the previous report in incoming packets for this Flow, while the layer2OctetTotalCount Information Element reports the total number of layer 2 octets in incoming packets for this Flow. The layer2FrameDeltaCount Information Element reports the number of incoming layer 2 frames since the previous report for this Flow, while layer2FrameTotalCount Information Element reports the total number of incoming layer 2 frames for this Flow. All of these Information Elements are unchanged from the existing IANA [IANA-IPFIX] definitions, and are reproduced in Section 3.1.3 through Section 3.1.6 below for completeness.
layer2OctetDeltaCount信息元素报告此流的传入数据包中自上次报告以来的第2层八进制数，而layer2OctetTotalCount信息元素报告此流的传入数据包中第2层八进制数的总数。layer2FrameDeltaCount信息元素报告自上次报告以来此流的传入第2层帧数，而layer2FrameTotalCount信息元素报告此流的传入第2层帧总数。所有这些信息元素与现有IANA[IANA-IPFIX]定义相同，为完整起见，在下文第3.1.3节至第3.1.6节中进行了复制。
Therefore, these changes do not introduce any backward-compatibility issues.
因此，这些更改不会引入任何向后兼容性问题。
Per Section 5.2 of [RFC7013], for each of these changes, [RFC7133] has been appended to the requester in IANA's IPFIX registry [IANA-IPFIX], the Information Element's revision number has been incremented by one, and the Information Element's revision date column has been updated.
根据[RFC7013]第5.2节，对于每一项变更，[RFC7133]已附加到IANA的IPFIX注册表[IANA-IPFIX]中的请求者，信息元素的修订号已增加1，并且信息元素的修订日期列已更新。
Description:
说明：
This Information Element specifies the length of the selected data link frame.
此信息元素指定选定数据链路帧的长度。
The data link layer is defined in [ISO/IEC.7498-1:1994].
数据链路层在[ISO/IEC.7498-1:1994]中定义。
Abstract Data Type: unsigned16
抽象数据类型：unsigned16
*Data Type Semantics: quantity*
*Data Type Semantics: quantity*
ElementId: 312
元素ID:312
References: [ISO/IEC.7498-1:1994]
References: [ISO/IEC.7498-1:1994]
Status: current
状态：当前
Description:
说明：
This Information Element carries n octets from the data link frame of a selected frame, starting sectionOffset octets into the frame.
该信息元素从选定帧的数据链路帧中携带n个八位字节，从sectionOffset八位字节开始进入该帧。
*However, if no sectionOffset field corresponding to this Information Element is present, then a sectionOffset of zero applies, and the octets MUST be from the start of the data link frame.*
*但是，如果不存在与此信息元素对应的sectionOffset字段，则sectionOffset为零，并且八位字节必须从数据链路帧的开始处开始*
The sectionExportedOctets expresses how much data was observed, while the remainder is padding.
ExportedOctets部分表示观察到的数据量，其余部分为填充。
When the sectionExportedOctets field corresponding to this Information Element exists, this Information Element MAY have a fixed length and MAY be padded, or it MAY have a variable length.
当与此信息元素对应的sectionExportedOctets字段存在时，此信息元素可以具有固定长度，也可以填充，也可以具有可变长度。
When the sectionExportedOctets field corresponding to this Information Element does not exist, this Information Element SHOULD have a variable length and MUST NOT be padded. In this case, the size of the exported section may be constrained due to limitations in the IPFIX protocol.
当与此信息元素对应的sectionExportedOctets字段不存在时，此信息元素应具有可变长度且不得填充。在这种情况下，由于IPFIX协议中的限制，导出节的大小可能会受到限制。
Further Information Elements, i.e., dataLinkFrameType and dataLinkFrameSize, are needed to specify the data link type and the size of the data link frame of this Information Element. A set of these Information Elements MAY be contained in a structured data type, as expressed in [RFC6313]. Or a set of these Information Elements MAY be contained in one Flow Record as shown in Appendix B of [RFC7133].
需要进一步的信息元素，即dataLinkFrameType和dataLinkFrameSize，以指定此信息元素的数据链接类型和数据链接帧的大小。这些信息元素的集合可以包含在结构化数据类型中，如[RFC6313]所示。或者，这些信息元素的集合可以包含在[RFC7133]附录B所示的一个流量记录中。
The data link layer is defined in [ISO/IEC.7498-1:1994].
数据链路层在[ISO/IEC.7498-1:1994]中定义。
Abstract Data Type: octetArray
抽象数据类型：Octeraray
ElementId: 315
元素ID:315
References: [RFC6313] [RFC7133] [ISO/IEC.7498-1:1994]
References: [RFC6313] [RFC7133] [ISO/IEC.7498-1:1994]
Status: current
状态：当前
The layer2OctetDeltaCount Information Element is unchanged from the existing IANA [IANA-IPFIX] definition and is reproduced here for reference only.
Layer2OctedeltaCount信息元素与现有IANA[IANA-IPFIX]定义保持不变，此处复制该元素仅供参考。
Description
描述
The number of layer 2 octets since the previous report (if any) in incoming packets for this Flow at the Observation Point. The number of octets includes layer 2 header(s) and layer 2 payload.
自上一次报告（如果有）以来，观察点处此流的传入数据包中的第2层八位字节数。八位字节数包括第2层报头和第2层有效载荷。
Abstract Data Type: unsigned64
抽象数据类型：unsigned64
Data Type Semantics: deltaCounter
数据类型语义：deltaCounter
Units: octets
单位：八位字节
ElementId: 352
元素ID:352
Status: current
状态：当前
The layer2OctetTotalCount Information Element is unchanged from the existing IANA [IANA-IPFIX] definition and is reproduced here for reference only.
layer2OctetTotalCount信息元素与现有IANA[IANA-IPFIX]定义相同，此处复制该元素仅供参考。
Description:
说明：
The total number of layer 2 octets in incoming packets for this Flow at the Observation Point since the Metering Process (re-)initialization for this Observation Point. The number of octets includes layer 2 header(s) and layer 2 payload.
自该观测点的计量过程（重新）初始化以来，观测点处该流的传入数据包中的第2层八位字节总数。八位字节数包括第2层报头和第2层有效载荷。
Abstract Data Type: unsigned64
抽象数据类型：unsigned64
Data Type Semantics: totalCounter
数据类型语义：totalCounter
Units: octets
单位：八位字节
ElementId: 353
元素ID:353
Status: current
状态：当前
The layer2FrameDeltaCount Information Element is unchanged from the existing IANA [IANA-IPFIX] definition and is reproduced here for reference only.
layer2FrameDeltaCount信息元素与现有IANA[IANA-IPFIX]定义相同，此处复制该元素仅供参考。
Description:
说明：
The number of incoming layer 2 frames since the previous report (if any) for this Flow at the Observation Point.
自上一次报告（如果有）以来，观察点处此流的传入第2层帧数。
Abstract Data Type: unsigned64
抽象数据类型：unsigned64
Data Type Semantics: deltaCounter
数据类型语义：deltaCounter
Units: frames
单位：帧
ElementId: 430
元素ID:430
Status: current
状态：当前
The layer2FrameTotalCount Information Element is unchanged from the existing IANA [IANA-IPFIX] definition and is reproduced here for reference only.
layer2FrameTotalCount信息元素与现有的IANA[IANA-IPFIX]定义保持不变，此处复制该元素仅供参考。
Description:
说明：
The total number of incoming layer 2 frames for this Flow at the Observation Point since the Metering Process (re-)initialization for this Observation Point.
自该观测点的计量过程（重新）初始化以来，观测点处该流的传入第2层帧总数。
Abstract Data Type: unsigned64
抽象数据类型：unsigned64
Data Type Semantics: totalCounter
数据类型语义：totalCounter
Units: frames
单位：帧
ElementId: 431
元素ID:431
Status: current
状态：当前
The following new Information Elements have been added for data link layer monitoring.
为数据链路层监控添加了以下新信息元素。
In IANA's IPFIX registry [IANA-IPFIX], the Requester has been set to [RFC7133], the Information Element's Revision has been set to zero, and the Information Element's Date set to the date upon which the new Information Elements have been added to the registry. All other
在IANA的IPFIX注册表[IANA-IPFIX]中，请求者被设置为[RFC7133]，信息元素的版本被设置为零，信息元素的日期被设置为新信息元素添加到注册表的日期。所有其他
columns that are not explicitly mentioned below (e.g., Units, Range, References) are not applicable and are to be left blank since the registry does not explicitly record "not applicable".
以下未明确提及的列（例如，单位、范围、参考）不适用，应留空，因为注册表未明确记录“不适用”。
Description:
说明：
This Information Element specifies the type of the selected data link frame.
此信息元素指定所选数据链路帧的类型。
The following data link types are defined here:
此处定义了以下数据链路类型：
- 0x01 IEEE802.3 ETHERNET [IEEE802.3]
- 0x01 IEEE802.3以太网[IEEE802.3]
- 0x02 IEEE802.11 MAC Frame format [IEEE802.11]
- 0x02 IEEE802.11 MAC帧格式[IEEE802.11]
Further values may be assigned by IANA. Note that the assigned values are bits so that multiple observations can be OR'd together.
IANA可能会分配更多的值。请注意，分配的值是位，因此可以将多个观测值合并在一起。
The data link layer is defined in [ISO/IEC.7498-1:1994].
数据链路层在[ISO/IEC.7498-1:1994]中定义。
Abstract Data Type: unsigned16
抽象数据类型：unsigned16
Data Type Semantics: flags
数据类型语义：标志
ElementId: 408
元素ID:408
References: [IEEE802.3] [IEEE802.11] [ISO/IEC.7498-1:1994]
References: [IEEE802.3] [IEEE802.11] [ISO/IEC.7498-1:1994]
Status: current
状态：当前
Description:
说明：
This Information Element specifies the offset of the packet section (e.g., dataLinkFrameSection, ipHeaderPacketSection, ipPayloadPacketSection, mplsLabelStackSection, and mplsPayloadPacketSection). If this Information Element is omitted, it defaults to zero (i.e., no offset).
此信息元素指定数据包部分的偏移量（例如，dataLinkFrameSection、ipHeaderPacketSection、ipPayloadPacketSection、mplsLabelStackSection和mplsPayloadPacketSection）。如果省略此信息元素，则默认为零（即无偏移）。
If multiple sectionOffset Information Elements are specified within a single Template, then they apply to the packet section Information Elements in order: the first sectionOffset applies to the first packet section, the second to the second, and so on. Note that the "closest" sectionOffset and packet section
如果在单个模板中指定了多个sectionOffset信息元素，则它们将按顺序应用于数据包部分信息元素：第一个sectionOffset应用于第一个数据包部分，第二个应用于第二个数据包部分，依此类推。请注意，“最近的”部分偏移量和数据包部分
Information Elements within a given Template are not necessarily related. If there are fewer sectionOffset Information Elements than packet section Information Elements, then subsequent packet section Information Elements have no offset, i.e., a sectionOffset of zero applies to those packet section Information Elements. If there are more sectionOffset Information Elements than the number of packet section Information Elements, then the additional sectionOffset Information Elements are meaningless.
给定模板中的信息元素不一定相关。如果sectionOffset信息元素少于分组部分信息元素，则后续分组部分信息元素没有偏移，即sectionOffset为零应用于那些分组部分信息元素。如果存在的sectionOffset信息元素多于分组部分信息元素的数量，则附加的sectionOffset信息元素是无意义的。
Abstract Data Type: unsigned16
抽象数据类型：unsigned16
Data Type Semantics: quantity
数据类型语义：数量
ElementId: 409
ElementId:409
Status: current
状态：当前
Description:
说明：
This Information Element specifies the observed length of the packet section (e.g., dataLinkFrameSection, ipHeaderPacketSection, ipPayloadPacketSection, mplsLabelStackSection, and mplsPayloadPacketSection) when padding is used.
此信息元素指定使用填充时观察到的数据包段长度（例如，dataLinkFrameSection、ipHeaderPacketSection、ipPayloadPacketSection、mplsLabelStackSection和mplsPayloadPacketSection）。
The packet section may be of a fixed size larger than the sectionExportedOctets. In this case, octets in the packet section beyond the sectionExportedOctets MUST follow the [RFC7011] rules for padding (i.e., be composed of zero (0) valued octets).
数据包段的大小可以固定为大于ExportedOctets段的大小。在这种情况下，ExportedOctets部分之外的数据包部分中的八位字节必须遵循[RFC7011]填充规则（即，由零（0）个八位字节组成）。
Abstract Data Type: unsigned16
抽象数据类型：unsigned16
Data Type Semantics: quantity
数据类型语义：数量
ElementId: 410
元素ID:410
References: [RFC7011]
参考文献：[RFC7011]
Status: current
状态：当前
Description:
说明：
This Information Element, which is 16 octets long, represents the Backbone Service Instance Tag (I-TAG) Tag Control Information (TCI) field of an Ethernet frame as described in [IEEE802.1Q]. It
此信息元素长度为16个八位字节，表示[IEEE802.1Q]中所述的以太网帧的主干服务实例标记（I-Tag）标记控制信息（TCI）字段。信息技术
encodes the Backbone Service Instance Priority Code Point (I-PCP), Backbone Service Instance Drop Eligible Indicator (I-DEI), Use Customer Addresses (UCAs), Backbone Service Instance Identifier (I-SID), Encapsulated Customer Destination Address (C-DA), Encapsulated Customer Source Address (C-SA), and reserved fields. The structure and semantics within the Tag Control Information field are defined in [IEEE802.1Q].
对主干服务实例优先级代码点（I-PCP）、主干服务实例丢弃合格指示符（I-DEI）、使用客户地址（UCA）、主干服务实例标识符（I-SID）、封装客户目的地地址（C-DA）、封装客户源地址（C-SA）和保留字段进行编码。标签控制信息字段中的结构和语义在[IEEE802.1Q]中定义。
Abstract Data Type: octetArray
抽象数据类型：Octeraray
Data Type Semantics: default
数据类型语义：默认值
ElementId: 411
元素ID:411
References: [IEEE802.1Q]
参考文献：[IEEE802.1Q]
Status: current
状态：当前
Description:
说明：
The value of the 24-bit Backbone Service Instance Identifier (I-SID) portion of the Backbone Service Instance Tag (I-TAG) Tag Control Information (TCI) field of an Ethernet frame as described in [IEEE802.1Q].
如[IEEE802.1Q]中所述，以太网帧的主干服务实例标记（I-Tag）标记控制信息（TCI）字段的24位主干服务实例标识符（I-SID）部分的值。
Abstract Data Type: unsigned32
抽象数据类型：unsigned32
Data Type Semantics: identifier
数据类型语义：标识符
ElementId: 412
元素ID:412
References: [IEEE802.1Q]
参考文献：[IEEE802.1Q]
Status: current
状态：当前
Range: The valid range is 0 - 16777215 (i.e., 24 bits).
范围：有效范围为0-16777215（即24位）。
Description:
说明：
The value of the 3-bit Backbone Service Instance Priority Code Point (I-PCP) portion of the Backbone Service Instance Tag (I-TAG) Tag Control Information (TCI) field of an Ethernet frame as described in [IEEE802.1Q].
如[IEEE802.1Q]所述，以太网帧的主干服务实例标记（I-Tag）标记控制信息（TCI）字段的3位主干服务实例优先级代码点（I-PCP）部分的值。
Abstract Data Type: unsigned8
抽象数据类型：unsigned8
Data Type Semantics: identifier
数据类型语义：标识符
ElementId: 413
元素ID:413
References: [IEEE802.1Q]
参考文献：[IEEE802.1Q]
Status: current
状态：当前
Range: The valid range is 0-7.
范围：有效范围为0-7。
Description:
说明：
The value of the Encapsulated Customer Source Address (C-SA) portion of the Backbone Service Instance Tag (I-TAG) Tag Control Information (TCI) field of an Ethernet frame as described in [IEEE802.1Q].
如[IEEE802.1Q]所述，以太网帧的主干服务实例标记（I-Tag）标记控制信息（TCI）字段的封装客户源地址（C-SA）部分的值。
Abstract Data Type: macAddress
抽象数据类型：macAddress
Data Type Semantics: default
数据类型语义：默认值
ElementId: 414
元素ID:414
References: [IEEE802.1Q]
参考文献：[IEEE802.1Q]
Status: current
状态：当前
Description:
说明：
The value of the Encapsulated Customer Destination Address (C-DA) portion of the Backbone Service Instance Tag (I-TAG) Tag Control Information (TCI) field of an Ethernet frame as described in [IEEE802.1Q].
如[IEEE802.1Q]中所述，以太网帧的主干服务实例标签（I-Tag）标签控制信息（TCI）字段的封装客户目的地地址（C-DA）部分的值。
Abstract Data Type: macAddress
抽象数据类型：macAddress
Data Type Semantics: default
数据类型语义：默认值
ElementId: 415
元素ID:415
References: [IEEE802.1Q]
参考文献：[IEEE802.1Q]
Status: current
状态：当前
Description:
说明：
The definition of this Information Element is identical to the definition of the layer2OctetDeltaCount Information Element, except that it reports a potentially modified value caused by a middlebox function after the packet passed the Observation Point.
此信息元素的定义与layer2OctetDeltaCount信息元素的定义相同，只是它报告了数据包通过观察点后由中间盒函数引起的潜在修改值。
This Information Element is the layer 2 version of postOctetDeltaCount (ElementId #23).
此信息元素是postOctetDeltaCount（ElementId#23）的第2层版本。
Abstract Data Type: unsigned64
抽象数据类型：unsigned64
Data Type Semantics: deltaCounter
数据类型语义：deltaCounter
ElementId: 417
元素ID:417
References: [RFC5477]
参考文献：[RFC5477]
Status: current
状态：当前
Units: octets
单位：八位字节
Description:
说明：
The number of layer 2 octets since the previous report (if any) in outgoing multicast packets sent for packets of this Flow by a multicast daemon within the Observation Domain. This property cannot necessarily be observed at the Observation Point but may be retrieved by other means. The number of octets includes layer 2 header(s) and layer 2 payload.
观察域内的多播守护进程为此流的数据包发送的传出多播数据包中自上次报告（如果有）以来的第2层八位字节数。此属性不一定在观察点观察，但可以通过其他方式检索。八位字节数包括第2层报头和第2层有效载荷。
This Information Element is the layer 2 version of postMCastOctetDeltaCount (ElementId #20).
此信息元素是PostCastOcteTDeltaCount（ElementId#20）的第2层版本。
Abstract Data Type: unsigned64
抽象数据类型：unsigned64
Data Type Semantics: deltaCounter
数据类型语义：deltaCounter
ElementId: 418
元素ID:418
References: [RFC5477]
参考文献：[RFC5477]
Status: current
状态：当前
Units: octets
单位：八位字节
Description:
说明：
The definition of this Information Element is identical to the definition of the layer2OctetTotalCount Information Element, except that it reports a potentially modified value caused by a middlebox function after the packet passed the Observation Point.
此信息元素的定义与layer2OctetTotalCount信息元素的定义相同，只是它报告了数据包通过观察点后由中间盒函数引起的潜在修改值。
This Information Element is the layer 2 version of postOctetTotalCount (ElementId #171).
此信息元素是postOctetTotalCount（ElementId#171）的第2层版本。
Abstract Data Type: unsigned64
抽象数据类型：unsigned64
Data Type Semantics: totalCounter
数据类型语义：totalCounter
ElementId: 420
元素ID:420
References: [RFC5477]
参考文献：[RFC5477]
Status: current
状态：当前
Units: octets
单位：八位字节
Description:
说明：
The total number of layer 2 octets in outgoing multicast packets sent for packets of this Flow by a multicast daemon in the Observation Domain since the Metering Process (re-)initialization. This property cannot necessarily be observed at the Observation Point but may be retrieved by other means. The number of octets includes layer 2 header(s) and layer 2 payload.
自计量过程（重新）初始化以来，观测域中的多播守护进程为此流的数据包发送的传出多播数据包中的第2层八位字节总数。此属性不一定在观察点观察，但可以通过其他方式检索。八位字节数包括第2层报头和第2层有效载荷。
This Information Element is the layer 2 version of postMCastOctetTotalCount (ElementId #175).
此信息元素是PostCastOctettotalCount（ElementId#175）的第2层版本。
Abstract Data Type: unsigned64
抽象数据类型：unsigned64
Data Type Semantics: totalCounter
数据类型语义：totalCounter
ElementId: 421
元素ID:421
References: [RFC5477]
参考文献：[RFC5477]
Status: current
状态：当前
Units: octets
单位：八位字节
Description:
说明：
Layer 2 length of the smallest packet observed for this Flow. The packet length includes the length of the layer 2 header(s) and the length of the layer 2 payload.
第2层此流观察到的最小数据包的长度。分组长度包括层2报头的长度和层2有效载荷的长度。
This Information Element is the layer 2 version of minimumIpTotalLength (ElementId #25).
此信息元素是MinimumiPottalLength（ElementId#25）的第2层版本。
Abstract Data Type: unsigned64
抽象数据类型：unsigned64
ElementId: 422
元素ID:422
References: [RFC5477]
参考文献：[RFC5477]
Status: current
状态：当前
Units: octets
单位：八位字节
Description:
说明：
Layer 2 length of the largest packet observed for this Flow. The packet length includes the length of the layer 2 header(s) and the length of the layer 2 payload.
第2层此流观察到的最大数据包的长度。分组长度包括层2报头的长度和层2有效载荷的长度。
This Information Element is the layer 2 version of maximumIpTotalLength (ElementId #26).
此信息元素是MaximumiPottalLength（ElementId#26）的第2层版本。
Abstract Data Type: unsigned64
抽象数据类型：unsigned64
ElementId: 423
元素ID:423
References: [RFC5477]
参考文献：[RFC5477]
Status: current
状态：当前
Units: octets
单位：八位字节
Description:
说明：
The number of layer 2 octets since the previous report (if any) in packets of this Flow dropped by packet treatment. The number of octets includes layer 2 header(s) and layer 2 payload.
自上次报告（如果有）以来，通过数据包处理丢弃的该流数据包中的第2层八位字节数。八位字节数包括第2层报头和第2层有效载荷。
This Information Element is the layer 2 version of droppedOctetDeltaCount (ElementId #132).
此信息元素是droppedOctetDeltaCount（ElementId#132）的第2层版本。
Abstract Data Type: unsigned64
抽象数据类型：unsigned64
Data Type Semantics: deltaCounter
数据类型语义：deltaCounter
ElementId: 424
元素ID:424
References: [RFC5477]
参考文献：[RFC5477]
Status: current
状态：当前
Units: octets
单位：八位字节
Description:
说明：
The total number of octets in observed layer 2 packets (including the layer 2 header) that were dropped by packet treatment since the (re-)initialization of the Metering Process.
自计量过程（重新）初始化以来，通过数据包处理丢弃的观察到的第2层数据包（包括第2层报头）中的八位字节总数。
This Information Element is the layer 2 version of droppedOctetTotalCount (ElementId #134).
此信息元素是droppedOctetTotalCount（ElementId#134）的第2层版本。
Abstract Data Type: unsigned64
抽象数据类型：unsigned64
Data Type Semantics: totalCounter
数据类型语义：totalCounter
ElementId: 425
元素ID:425
References: [RFC5477]
参考文献：[RFC5477]
Status: current
状态：当前
Units: octets
单位：八位字节
Description:
说明：
The total number of octets in observed layer 2 packets (including the layer 2 header) that the Metering Process did not process since the (re-)initialization of the Metering Process.
自计量过程（重新）初始化以来，计量过程未处理的观察到的第2层数据包（包括第2层标头）中的八位字节总数。
This Information Element is the layer 2 version of ignoredOctetTotalCount (ElementId #165).
此信息元素是ignoredOctetTotalCount（ElementId#165）的第2层版本。
Abstract Data Type: unsigned64
抽象数据类型：unsigned64
Data Type Semantics: totalCounter
数据类型语义：totalCounter
ElementId: 426
元素ID:426
References: [RFC5477]
参考文献：[RFC5477]
Status: current
状态：当前
Units: octets
单位：八位字节
Description:
说明：
The total number of octets in observed layer 2 packets (including the layer 2 header) that the Metering Process did not process since the (re-)initialization of the Metering Process.
自计量过程（重新）初始化以来，计量过程未处理的观察到的第2层数据包（包括第2层标头）中的八位字节总数。
This Information Element is the layer 2 version of notSentOctetTotalCount (ElementId #168).
此信息元素是notSentOctetTotalCount（ElementId#168）的第2层版本。
Abstract Data Type: unsigned64
抽象数据类型：unsigned64
Data Type Semantics: totalCounter
数据类型语义：totalCounter
ElementId: 427
元素ID:427
References: [RFC5477]
参考文献：[RFC5477]
Status: current
状态：当前
Units: octets
单位：八位字节
Description:
说明：
The sum of the squared numbers of layer 2 octets per incoming packet since the previous report (if any) for this Flow at the Observation Point. The number of octets includes layer 2 header(s) and layer 2 payload.
自上一次报告（如有）以来，观察点处该流的每个传入数据包的第2层八位字节的平方数之和。八位字节数包括第2层报头和第2层有效载荷。
This Information Element is the layer 2 version of octetDeltaSumOfSquares (ElementId #198).
此信息元素是octetDeltaSumOfSquares（ElementId#198）的第2层版本。
Abstract Data Type: unsigned64
抽象数据类型：unsigned64
Data Type Semantics: deltaCounter
数据类型语义：deltaCounter
ElementId: 428
元素ID:428
References: [RFC5477]
参考文献：[RFC5477]
Status: current
状态：当前
Units: octets
单位：八位字节
Description:
说明：
The total sum of the squared numbers of layer 2 octets in incoming packets for this Flow at the Observation Point since the Metering Process (re-)initialization for this Observation Point. The number of octets includes layer 2 header(s) and layer 2 payload.
自该观测点的计量过程（重新）初始化以来，观测点处该流的传入数据包中第2层八位字节的平方数的总和。八位字节数包括第2层报头和第2层有效载荷。
This Information Element is the layer 2 version of octetTotalSumOfSquares (ElementId #199).
此信息元素是octetTotalSumOfSquares（ElementId#199）的第2层版本。
Abstract Data Type: unsigned64
抽象数据类型：unsigned64
Data Type Semantics: totalCounter
数据类型语义：totalCounter
ElementId: 429
元素ID:429
References: [RFC5477]
参考文献：[RFC5477]
Status: current
状态：当前
Units: octets
单位：八位字节
4. Modification of Existing Information Elements Related to Packet Section
4. 修改与包段相关的现有信息元素
The new Information Elements related to packet section (i.e., sectionOffset and sectionExportedOctets) can be applied to not only dataLinkFrameSection but also to all kinds of packet section (i.e., ipHeaderPacketSection, ipPayloadPacketSection, mplsLabelStackSection, and mplsPayloadPacketSection defined in [RFC5477]). Therefore, existing Information Elements Descriptions should be modified as follows.
与数据包部分（即sectionOffset和sectionExportedOctets）相关的新信息元素不仅可以应用于dataLinkFrameSection，还可以应用于所有类型的数据包部分（即，[RFC5477]中定义的ipHeaderPacketSection、ipPayloadPacketSection、mplsLabelStackSection和mplsPayloadPacketSection）。因此，现有的信息元素描述应该修改如下。
This Information Element is defined in [RFC5477]. The description has been updated from [RFC5477].
该信息元素在[RFC5477]中定义。说明已从[RFC5477]更新。
Description:
说明：
This Information Element carries a series of n octets from the IP header of a sampled packet, starting sectionOffset octets into the IP header.
此信息元素从采样数据包的IP报头携带一系列n个八位字节，从sectionOffset八位字节开始进入IP报头。
However, if no sectionOffset field corresponding to this Information Element is present, then a sectionOffset of zero applies, and the octets MUST be from the start of the IP header.
但是，如果不存在与此信息元素对应的sectionOffset字段，则sectionOffset为零，并且八位字节必须从IP头开始。
With sufficient length, this element also reports octets from the IP payload. However, full packet capture of arbitrary packet streams is explicitly out of scope per the Security Considerations sections of [RFC5477] and [RFC2804].
如果有足够的长度，该元素还报告来自IP有效负载的八位字节。但是，根据[RFC5477]和[RFC2804]的安全注意事项部分，任意数据包流的完整数据包捕获明显超出范围。
The sectionExportedOctets expresses how much data was exported, while the remainder is padding.
ExportedOctets部分表示导出了多少数据，其余部分是填充。
When the sectionExportedOctets field corresponding to this Information Element exists, this Information Element MAY have a fixed length and MAY be padded, or it MAY have a variable length.
当与此信息元素对应的sectionExportedOctets字段存在时，此信息元素可以具有固定长度，也可以填充，也可以具有可变长度。
When the sectionExportedOctets field corresponding to this Information Element does not exist, this Information Element SHOULD have a variable length and MUST NOT be padded. In this case, the size of the exported section may be constrained due to limitations in the IPFIX protocol.
当与此信息元素对应的sectionExportedOctets字段不存在时，此信息元素应具有可变长度且不得填充。在这种情况下，由于IPFIX协议中的限制，导出节的大小可能会受到限制。
Abstract Data Type: octetArray
抽象数据类型：Octeraray
ElementId: 313
元素ID:313
References: [RFC2804] [RFC5477]
参考文献：[RFC2804][RFC5477]
Status: current
状态：当前
This Information Element is defined in [RFC5477]. The description is updated from [RFC5477].
该信息元素在[RFC5477]中定义。说明从[RFC5477]更新。
Description:
说明：
This Information Element carries a series of n octets from the IP payload of a sampled packet, starting sectionOffset octets into the IP payload.
此信息元素从采样数据包的IP有效负载携带一系列n个八位字节，从sectionOffset八位字节开始进入IP有效负载。
However, if no sectionOffset field corresponding to this Information Element is present, then a sectionOffset of zero applies, and the octets MUST be from the start of the IP payload.
但是，如果不存在与此信息元素对应的sectionOffset字段，则sectionOffset为零，并且八位字节必须从IP有效负载的开始处开始。
The IPv4 payload is that part of the packet that follows the IPv4 header and any options, which [RFC0791] refers to as "data" or "data octets". For example, see the examples in [RFC0791], Appendix A.
IPv4有效负载是IPv4报头和任何选项后面的数据包部分，[RFC0791]将其称为“数据”或“数据八位字节”。例如，参见附录A[RFC0791]中的示例。
The IPv6 payload is the rest of the packet following the 40-octet IPv6 header. Note that any extension headers present are considered part of the payload. See [RFC2460] for the IPv6 specification.
IPv6有效负载是40个八位组IPv6报头之后的数据包的其余部分。请注意，存在的任何扩展头都被视为有效负载的一部分。有关IPv6规范，请参见[RFC2460]。
The sectionExportedOctets expresses how much data was observed, while the remainder is padding.
ExportedOctets部分表示观察到的数据量，其余部分为填充。
When the sectionExportedOctets field corresponding to this Information Element exists, this Information Element MAY have a fixed length and MAY be padded, or it MAY have a variable length.
当与此信息元素对应的sectionExportedOctets字段存在时，此信息元素可以具有固定长度，也可以填充，也可以具有可变长度。
When the sectionExportedOctets field corresponding to this Information Element does not exist, this Information Element SHOULD have a variable length and MUST NOT be padded. In this case, the size of the exported section may be constrained due to limitations in the IPFIX protocol.
当与此信息元素对应的sectionExportedOctets字段不存在时，此信息元素应具有可变长度且不得填充。在这种情况下，由于IPFIX协议中的限制，导出节的大小可能会受到限制。
Abstract Data Type: octetArray
抽象数据类型：Octeraray
ElementId: 314
元素ID:314
References: [RFC0791] [RFC2460]
参考文献：[RFC0791][RFC2460]
Status: current
状态：当前
This Information Element is defined in [RFC5477]. The description is updated from [RFC5477].
该信息元素在[RFC5477]中定义。说明从[RFC5477]更新。
Description:
说明：
This Information Element carries a series of n octets from the MPLS label stack of a sampled packet, starting sectionOffset octets into the MPLS label stack.
此信息元素从采样数据包的MPLS标签堆栈中携带一系列n个八位字节，从sectionOffset八位字节开始进入MPLS标签堆栈。
However, if no sectionOffset field corresponding to this Information Element is present, then a sectionOffset of zero applies, and the octets MUST be from the head of the MPLS label stack.
但是，如果不存在与此信息元素对应的sectionOffset字段，则sectionOffset为零，并且八位字节必须来自MPLS标签堆栈的头部。
With sufficient length, this element also reports octets from the MPLS payload. However, full packet capture of arbitrary packet streams is explicitly out of scope per the Security Considerations sections of [RFC5477] and [RFC2804].
如果有足够的长度，该元素还报告来自MPLS负载的八位字节。但是，根据[RFC5477]和[RFC2804]的安全注意事项部分，任意数据包流的完整数据包捕获明显超出范围。
See [RFC3031] for the specification of MPLS packets.
有关MPLS数据包的规范，请参见[RFC3031]。
See [RFC3032] for the specification of the MPLS label stack.
有关MPLS标签堆栈的规范，请参见[RFC3032]。
The sectionExportedOctets expresses how much data was observed, while the remainder is padding.
ExportedOctets部分表示观察到的数据量，其余部分为填充。
When the sectionExportedOctets field corresponding to this Information Element exists, this Information Element MAY have a fixed length and MAY be padded, or it MAY have a variable length.
当与此信息元素对应的sectionExportedOctets字段存在时，此信息元素可以具有固定长度，也可以填充，也可以具有可变长度。
When the sectionExportedOctets field corresponding to this Information Element does not exist, this Information Element SHOULD have a variable length and MUST NOT be padded. In this case, the size of the exported section may be constrained due to limitations in the IPFIX protocol.
当与此信息元素对应的sectionExportedOctets字段不存在时，此信息元素应具有可变长度且不得填充。在这种情况下，由于IPFIX协议中的限制，导出节的大小可能会受到限制。
Abstract Data Type: octetArray
抽象数据类型：Octeraray
ElementId: 316
元素ID:316
References: [RFC2804] [RFC3031] [RFC3032] [RFC5477]
参考文献：[RFC2804][RFC3031][RFC3032][RFC5477]
Status: current
状态：当前
This Information Element is defined in [RFC5477]. The description is updated from [RFC5477].
该信息元素在[RFC5477]中定义。说明从[RFC5477]更新。
Description:
说明：
The mplsPayloadPacketSection carries a series of n octets from the MPLS payload of a sampled packet, starting sectionOffset octets into the MPLS payload, as it is data that follows immediately after the MPLS label stack.
mplsPayloadPacketSection从采样数据包的MPLS有效负载携带一系列n个八位字节，从sectionOffset八位字节开始进入MPLS有效负载，因为它是紧跟在MPLS标签堆栈之后的数据。
However, if no sectionOffset field corresponding to this Information Element is present, then a sectionOffset of zero applies, and the octets MUST be from the start of the MPLS payload.
但是，如果不存在与此信息元素对应的sectionOffset字段，则sectionOffset为零，并且八位字节必须从MPLS有效负载的开始处开始。
See [RFC3031] for the specification of MPLS packets.
有关MPLS数据包的规范，请参见[RFC3031]。
See [RFC3032] for the specification of the MPLS label stack.
有关MPLS标签堆栈的规范，请参见[RFC3032]。
The sectionExportedOctets expresses how much data was observed, while the remainder is padding.
ExportedOctets部分表示观察到的数据量，其余部分为填充。
When the sectionExportedOctets field corresponding to this Information Element exists, this Information Element MAY have a fixed length and MAY be padded, or it MAY have a variable length.
当与此信息元素对应的sectionExportedOctets字段存在时，此信息元素可以具有固定长度，也可以填充，也可以具有可变长度。
When the sectionExportedOctets field corresponding to this Information Element does not exist, this Information Element SHOULD have a variable length and MUST NOT be padded. In this case, the size of the exported section may be constrained due to limitations in the IPFIX protocol.
当与此信息元素对应的sectionExportedOctets字段不存在时，此信息元素应具有可变长度且不得填充。在这种情况下，由于IPFIX协议中的限制，导出节的大小可能会受到限制。
Abstract Data Type: octetArray
抽象数据类型：Octeraray
ElementId: 317
元素ID:317
References: [RFC3031] [RFC3032]
参考文献：[RFC3031][RFC3032]
Status: current
状态：当前
The traffic measurement using IPFIX and PSAMP for a Provider Backbone Bridged Network requires the Information Elements related to Backbone Service Instance Tag (I-TAG) and Backbone VLAN Tag (B-TAG). The set of Information Elements related to I-TAG is added in Section 3, because I-TAG structure and semantics are different from that of Service VLAN Tag (S-TAG) and Customer VLAN Tag (C-TAG). The set of Information Elements related to B-TAG reuses the existing Information Elements, because B-TAG structure and semantics are identical to that of C-TAG and S-TAG. This section modifies existing descriptions and references related to C-TAG and S-TAG as follows.
使用IPFIX和PSAMP对提供商主干桥接网络进行流量测量需要与主干服务实例标记（I-Tag）和主干VLAN标记（B-Tag）相关的信息元素。第3节增加了与I-TAG相关的信息元素集，因为I-TAG的结构和语义不同于服务VLAN标签（S-TAG）和客户VLAN标签（C-TAG）。与B-TAG相关的信息元素集重用了现有的信息元素，因为B-TAG的结构和语义与C-TAG和S-TAG相同。本节修改了与C-TAG和S-TAG相关的现有描述和参考，如下所示。
Description:
说明：
The value of the 12-bit VLAN Identifier portion of the Tag Control Information field of an Ethernet frame. The structure and semantics within the Tag Control Information field are defined in [IEEE802.1Q]. In Provider Bridged Networks, it represents the Service VLAN identifier in the Service VLAN Tag (S-TAG) Tag Control Information (TCI) field or the Customer VLAN identifier in the Customer VLAN Tag (C-TAG) Tag Control Information (TCI) field as described in [IEEE802.1Q]. In Provider Backbone Bridged Networks, it represents the Backbone VLAN identifier in the Backbone VLAN Tag (B-TAG) Tag Control Information (TCI) field as described in [IEEE802.1Q]. In a virtual link between a host system and EVB bridge, it represents the Service VLAN identifier indicating S-channel as described in [IEEE802.1Qbg].
以太网帧的标记控制信息字段的12位VLAN标识符部分的值。标签控制信息字段中的结构和语义在[IEEE802.1Q]中定义。在提供商桥接网络中，它表示服务VLAN标记（S-Tag）标记控制信息（TCI）字段中的服务VLAN标识符或客户VLAN标记（C-Tag）标记控制信息（TCI）字段中的客户VLAN标识符，如[IEEE802.1Q]中所述。在提供商主干桥接网络中，它表示主干VLAN标记（B-Tag）标记控制信息（TCI）字段中的主干VLAN标识符，如[IEEE802.1Q]所述。在主机系统和EVB网桥之间的虚拟链路中，它表示指示S通道的服务VLAN标识符，如[IEEE802.1Qbg]中所述。
In the case of a multi-tagged frame, it represents the outer tag's VLAN identifier, except for I-TAG.
在多标签帧的情况下，它表示外部标签的VLAN标识符，I标签除外。
Abstract Data Type: unsigned16
抽象数据类型：unsigned16
Data Type Semantics: identifier
数据类型语义：标识符
ElementId: 243
元素ID:243
Status: current
状态：当前
References: [IEEE802.1Q] [IEEE802.1Qbg]
参考文献：[IEEE802.1Q][IEEE802.1Qbg]
Description:
说明：
The value of the 3-bit User Priority portion of the Tag Control Information field of an Ethernet frame. The structure and semantics within the Tag Control Information field are defined in [IEEE802.1Q]. In the case of a multi-tagged frame, it represents the 3-bit Priority Code Point (PCP) portion of the outer tag's Tag Control Information (TCI) field as described in [IEEE802.1Q], except for I-TAG.
以太网帧的标签控制信息字段的3位用户优先级部分的值。标签控制信息字段中的结构和语义在[IEEE802.1Q]中定义。在多标签帧的情况下，它表示外部标签的标签控制信息（TCI）字段的3位优先码点（PCP）部分，如[IEEE802.1Q]中所述，I标签除外。
Abstract Data Type: unsigned8
抽象数据类型：unsigned8
Data Type Semantics: identifier
数据类型语义：标识符
ElementId: 244
元素ID:244
Status: current
状态：当前
References: [IEEE802.1Q]
参考文献：[IEEE802.1Q]
Description:
说明：
The value represents the Customer VLAN identifier in the Customer VLAN Tag (C-TAG) Tag Control Information (TCI) field as described in [IEEE802.1Q].
该值表示[IEEE802.1Q]中所述的客户VLAN标签（C-Tag）标签控制信息（TCI）字段中的客户VLAN标识符。
Abstract Data Type: unsigned16
抽象数据类型：unsigned16
Data Type Semantics: identifier
数据类型语义：标识符
ElementId: 245
元素ID:245
Status: current
状态：当前
References: [IEEE802.1Q]
参考文献：[IEEE802.1Q]
Description:
说明：
The value represents the 3-bit Priority Code Point (PCP) portion of the Customer VLAN Tag (C-TAG) Tag Control Information (TCI) field as described in [IEEE802.1Q].
该值表示[IEEE802.1Q]中所述的客户VLAN标签（C-Tag）标签控制信息（TCI）字段的3位优先级代码点（PCP）部分。
Abstract Data Type: unsigned8
抽象数据类型：unsigned8
Data Type Semantics: identifier
数据类型语义：标识符
ElementId: 246
元素ID:246
Status: current
状态：当前
References: [IEEE802.1Q]
参考文献：[IEEE802.1Q]
6. The Relationship between Ethernet Header Fields and Information Elements
6. 以太网报头字段与信息元素之间的关系
The following figures show a summary of various Ethernet header fields and the Informational Elements that would be used to represent each of the fields.
下图显示了各种以太网报头字段的摘要以及用于表示每个字段的信息元素。
<-- 6 --> <-- 6 --> <-- 4 --> <---- 2 ---->
+---------+---------+---------+-------------+
| | | | |
| C-DA | C-SA | C-TAG | Length/Type |
| a | b | c | d |
+---------+---------+---------+-------------+
<-- 6 --> <-- 6 --> <-- 4 --> <---- 2 ---->
+---------+---------+---------+-------------+
| | | | |
| C-DA | C-SA | C-TAG | Length/Type |
| a | b | c | d |
+---------+---------+---------+-------------+
a.(Information Element) destinationMacAddress (80) b.(Information Element) sourceMacAddress (56) c.(Information Elements) dot1qVlanId (243), dot1qPriority (244) d.(Information Element) ethernetType (256)
a、 （信息元素）目的地址（80）b（信息元素）源地址（56）c（信息元素）dot1qVlanId（243），dot1qPriority（244）d（信息元素）ethernetType（256）
Figure 1: Customer-Tagged Frame Header Fields
图1：客户标记的帧头字段
<-- 6 --> <-- 6 --> <-- 4 --> <-- 4 --> <---- 2 ---->
+---------+---------+---------+---------+-------------+
| | | | | |
| C-DA | C-SA | S-TAG | C-TAG | Length/Type |
| a | b | c | d | e |
+---------+---------+---------+---------+-------------+
<-- 6 --> <-- 6 --> <-- 4 --> <-- 4 --> <---- 2 ---->
+---------+---------+---------+---------+-------------+
| | | | | |
| C-DA | C-SA | S-TAG | C-TAG | Length/Type |
| a | b | c | d | e |
+---------+---------+---------+---------+-------------+
a.(Information Element) destinationMacAddress (80) b.(Information Element) sourceMacAddress (56) c.(Information Elements) dot1qVlanId (243), dot1qPriority (244) d.(Information Elements) dot1qCustomerVlanId (245), dot1qCustomerPriority (246) e.(Information Element) ethernetType (256)
a、 （信息元素）目的地址（80）b（信息元素）源地址（56）c（信息元素）dot1qVlanId（243）、dot1qPriority（244）d（信息元素）dot1qCustomerVlanId（245）、dot1qCustomerPriority（246）e（信息元素）ethernetType（256）
Figure 2: Service-Tagged Frame Header Fields
图2：服务标记的帧头字段
<-- 6 --> <-- 6 --> <-- 4 --> <--- 16 ---> <-- 4 --> <---- 2 ---->
+---------+---------+---------+------------+---------+-------------+
| | | | | | |
| B-DA | B-SA | B-TAG | I-TAG | C-TAG | Length/Type |
| a | b | c | d | e | f |
+---------+---------+---------+------------+---------+-------------+
<-- 6 --> <-- 6 --> <-- 4 --> <--- 16 ---> <-- 4 --> <---- 2 ---->
+---------+---------+---------+------------+---------+-------------+
| | | | | | |
| B-DA | B-SA | B-TAG | I-TAG | C-TAG | Length/Type |
| a | b | c | d | e | f |
+---------+---------+---------+------------+---------+-------------+
a.(Information Element) destinationMacAddress (80) b.(Information Element) sourceMacAddress (56) c.(Information Elements) dot1qVlanId (243), dot1qPriority (244) d.(Information Elements) dot1qServiceInstanceTag (411), or a set of dot1qServiceInstanceId (412), dot1qServiceInstancePriority (413), dot1qCustomerSourceMacAddress (414) dot1qCustomerDestinationMacAddress (415), e.(Information Elements) dot1qCustomerVlanId (245), dot1qCustomerPriority (246) f.(Information Element) ethernetType (256)
a、 （信息元素）destinationMacAddress（80）b.（信息元素）sourceMacAddress（56）c.（信息元素）dot1qVlanId（243）、dot1qPriority（244）d.（信息元素）dot1qServiceInstanceTag（411）或一组dot1qServiceInstanceId（412）、dot1qServiceInstancePriority（413）、dot1qCustomerSourceMacAddress（414）dot1qCustomerDestinationMacAddress（415），e.（信息元素）dot1qCustomerVlanId（245），dot1qCustomerPriority（246）f.（信息元素）ethernetType（256）
Figure 3: Backbone-VLAN-Tagged Frame Header Fields
图3：主干VLAN标记的帧头字段
Reporting more granular data may increase the risk of DoS attacks against a Collector. Protection against DoS attacks is discussed in Section 11.4 of [RFC7011].
报告更细粒度的数据可能会增加针对收集器的DoS攻击的风险。[RFC7011]第11.4节讨论了DoS攻击防护。
The recommendations in this document do not otherwise introduce any additional security issues beyond those already mentioned in [RFC7011] and [RFC5477].
除[RFC7011]和[RFC5477]中已经提到的安全问题外，本文件中的建议不会引入任何其他安全问题。
Existing IPFIX Information Elements [IANA-IPFIX] have been modified as indicated in Sections 3.1, 4, and 5.
现有IPFIX信息元素[IANA-IPFIX]已按照第3.1、4和5节所述进行了修改。
Per Section 5.2 of [RFC7013], for each of these changes, [RFC7133] has been appended to the Requester in IANA's IPFIX registry [IANA-IPFIX], the Information Element's Revision number has been incremented by one, and the Information Element's revision Date column has been updated.
根据[RFC7013]第5.2节，对于每一项变更，[RFC7133]已附加到IANA的IPFIX注册表[IANA-IPFIX]中的请求者，信息元素的修订号已增加1，并且信息元素的修订日期列已更新。
New IPFIX Information Elements [IANA-IPFIX] have been allocated as shown in Section 3.2.
如第3.2节所示，已分配新的IPFIX信息元素[IANA-IPFIX]。
Thanks to Brian Trammell and the IPFIX working group participants who contributed to mailing-list discussions throughout the development of this document. Special thanks to Pat Thaler for her help with the IEEE 802 aspects of this work.
感谢Brian Trammell和IPFIX工作组的参与者，他们在本文档的整个开发过程中为邮件列表讨论做出了贡献。特别感谢Pat Thaler在这项工作的IEEE 802方面提供的帮助。
[IEEE802.11] IEEE, "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 Std 802.11-2012, March 2012.
[IEEE802.11]IEEE，“IEEE信息技术标准。系统局域网和城域网之间的电信和信息交换。具体要求第11部分：无线局域网介质访问控制（MAC）和物理层（PHY）规范”，IEEE标准802.11-2012，2012年3月。
[IEEE802.1BR] IEEE, "IEEE Standard for Local and metropolitan area networks: Virtual Bridged Local Area Networks: Bridge Port Extension", IEEE Std 802.1BR-2012, July 2012.
[IEEE802.1BR]IEEE，“局域网和城域网的IEEE标准：虚拟桥接局域网：网桥端口扩展”，IEEE标准802.1BR-2012，2012年7月。
[IEEE802.1Q] IEEE, "IEEE Standard for Local and metropolitan area networks: Media Access Control (MAC) Bridges and Virtual Bridged Local Area Networks", IEEE Std 802.1Q-2011, August 2011.
[IEEE802.1Q]IEEE，“局域网和城域网的IEEE标准：媒体访问控制（MAC）网桥和虚拟桥接局域网”，IEEE标准802.1Q-2011，2011年8月。
[IEEE802.1Qbg] IEEE, "IEEE Standard for Local and metropolitan area networks: Media Access Control (MAC) Bridges and Virtual Bridged Local Area Networks: Amendment 21: Edge Virtual Bridging", IEEE Std 802.1Qbg-2012, July 2012.
[IEEE802.1Qbg]IEEE，“局域网和城域网IEEE标准：媒体访问控制（MAC）网桥和虚拟桥接局域网：第21次修订：边缘虚拟桥接”，IEEE标准802.1Qbg-2012，2012年7月。
[IEEE802.3] IEEE, "IEEE Standard for Ethernet", IEEE Std 802.3-2012, December 2012.
[IEEE802.3]IEEE，“以太网的IEEE标准”，IEEE标准802.3-2012，2012年12月。
[RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, September 1981.
[RFC0791]Postel，J.，“互联网协议”，STD 5，RFC 7911981年9月。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 (IPv6) Specification", RFC 2460, December 1998.
[RFC2460]Deering，S.和R.Hinden，“互联网协议，第6版（IPv6）规范”，RFC 2460，1998年12月。
[RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol Label Switching Architecture", RFC 3031, January 2001.
[RFC3031]Rosen，E.，Viswanathan，A.，和R.Callon，“多协议标签交换体系结构”，RFC 30312001年1月。
[RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack Encoding", RFC 3032, January 2001.
[RFC3032]Rosen，E.，Tappan，D.，Fedorkow，G.，Rekhter，Y.，Farinaci，D.，Li，T.，和A.Conta，“MPLS标签堆栈编码”，RFC 3032，2001年1月。
[RFC5477] Dietz, T., Claise, B., Aitken, P., Dressler, F., and G. Carle, "Information Model for Packet Sampling Exports", RFC 5477, March 2009.
[RFC5477]Dietz，T.，Claise，B.，Aitken，P.，Dressler，F.，和G.Carle，“数据包抽样出口的信息模型”，RFC 5477，2009年3月。
[RFC6313] Claise, B., Dhandapani, G., Aitken, P., and S. Yates, "Export of Structured Data in IP Flow Information Export (IPFIX)", RFC 6313, July 2011.
[RFC6313]Claise，B.，Dhandapani，G.，Aitken，P.，和S.Yates，“IP流信息导出（IPFIX）中结构化数据的导出”，RFC 63132011年7月。
[RFC7011] Claise, B., Trammell, B., and P. Aitken, "Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of Flow Information", STD 77, RFC 7011, September 2013.
[RFC7011]Claise，B.，Trammell，B.，和P.Aitken，“流量信息交换的IP流量信息导出（IPFIX）协议规范”，STD 77，RFC 7011，2013年9月。
[IANA-IPFIX] IANA, "IP Flow Information Export (IPFIX) Entities", <http://www.iana.org/assignments/ipfix>.
[IANA-IPFIX]IANA，“IP流信息导出（IPFIX）实体”<http://www.iana.org/assignments/ipfix>.
[IEEE802.1D] IEEE, "IEEE Standard for Local and metropolitan area networks: Media Access Control (MAC) Bridges", IEEE Std 802.1D-2004, June 2004.
[IEEE802.1D]IEEE，“局域网和城域网的IEEE标准：媒体访问控制（MAC）网桥”，IEEE标准802.1D-2004，2004年6月。
[ISO/IEC.7498-1:1994] International Organization for Standardization, "Information technology -- Open Systems Interconnection -- Basic Reference Model: The Basic Mode", ISO Standard 7498-1:1994, June 1996.
[ISO/IEC.7498-1:1994]国际标准化组织，“信息技术——开放系统互连——基本参考模型：基本模式”，ISO标准7498-1:1994，1996年6月。
[RFC2804] IAB and IESG, "IETF Policy on Wiretapping", RFC 2804, May 2000.
[RFC2804]IAB和IESG，“IETF关于窃听的政策”，RFC28042000年5月。
[RFC7012] Claise, B. and B. Trammell, "Information Model for IP Flow Information Export (IPFIX)", RFC 7012, September 2013.
[RFC7012]Claise，B.和B.Trammell，“IP流信息导出（IPFIX）的信息模型”，RFC 7012，2013年9月。
[RFC7013] Trammell, B. and B. Claise, "Guidelines for Authors and Reviewers of IP Flow Information Export (IPFIX) Information Elements", BCP 184, RFC 7013, September 2013.
[RFC7013]Trammell，B.和B.Claise，“IP流信息导出（IPFIX）信息元素的作者和评审员指南”，BCP 184，RFC 7013，2013年9月。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| C-DA |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| C-SA |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length/Type | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| |
~ Customer Data ~
~ ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| C-DA |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| C-SA |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length/Type | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| |
~ Customer Data ~
~ ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure A-1: Untagged Frame Format
图A-1：未标记帧格式
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| C-DA |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| C-SA |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| C-TAG TPID=0x8100 |C-PCP|C| C-VID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length/Type | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| |
~ Customer Data ~
~ ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| C-DA |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| C-SA |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| C-TAG TPID=0x8100 |C-PCP|C| C-VID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length/Type | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| |
~ Customer Data ~
~ ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure A-2: C-TAG Tagging Frame Format
图A-2:C标签标签框架格式
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| C-DA |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| C-SA |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| S-TAG TPID=0x88a8 |S-PCP|D| S-VID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length/Type | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| |
~ Customer Data ~
~ ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| C-DA |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| C-SA |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| S-TAG TPID=0x88a8 |S-PCP|D| S-VID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length/Type | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| |
~ Customer Data ~
~ ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure A-3: S-TAG Tagging Frame Format in Provider Bridged Networks
图A-3：提供商桥接网络中的S标签标签帧格式
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| C-DA |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| C-SA |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| S-TAG TPID=0x88a8 |S-PCP|D| S-VID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| C-TAG TPID=0x8100 |C-PCP|C| C-VID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length/Type | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| |
~ Customer Data ~
~ ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| C-DA |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| C-SA |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| S-TAG TPID=0x88a8 |S-PCP|D| S-VID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| C-TAG TPID=0x8100 |C-PCP|C| C-VID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length/Type | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| |
~ Customer Data ~
~ ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure A-4: S-TAG and C-TAG Tagging Frame Format in Provider Bridged Networks
图A-4：提供商桥接网络中的S标签和C标签标签帧格式
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| B-DA |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| B-SA |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| B-TAG TPID=0x88a8 |B-PCP|D| B-VID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| I-TAG TPID=0x88e7 |I-PCP|D|U| Res | I-SID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| I-SID | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| C-DA |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| C-SA |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Length/Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Customer Data ~
~ ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| B-DA |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| B-SA |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| B-TAG TPID=0x88a8 |B-PCP|D| B-VID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| I-TAG TPID=0x88e7 |I-PCP|D|U| Res | I-SID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| I-SID | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| C-DA |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| C-SA |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Length/Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Customer Data ~
~ ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure A-5: B-TAG and I-TAG Tagging Frame Format in Provider Backbone Bridged Networks
图A-5：提供商主干桥接网络中的B标签和I标签标签帧格式
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| B-DA |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| B-SA |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| B-TAG TPID=0x88a8 |B-PCP|D| B-VID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| I-TAG TPID=0x88e7 |I-PCP|D|U| Res | I-SID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| I-SID | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| C-DA |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| C-SA |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | C-TAG TCI=0x8100 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|C-PCP|C| C-VID | Length/Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Customer Data ~
~ ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| B-DA |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| B-SA |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| B-TAG TPID=0x88a8 |B-PCP|D| B-VID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| I-TAG TPID=0x88e7 |I-PCP|D|U| Res | I-SID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| I-SID | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| C-DA |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| C-SA |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | C-TAG TCI=0x8100 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|C-PCP|C| C-VID | Length/Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Customer Data ~
~ ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure A-6: B-TAG, I-TAG, and C-TAG Tagging Frame Format in Provider Backbone Bridged Networks
图A-6：提供商主干桥接网络中的B标签、I标签和C标签标签帧格式
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| C-DA |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| C-SA |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| S-TAG TPID=0x88a8 |S-PCP|D| S-VID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length/Type | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| |
~ Customer Data ~
~ ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| C-DA |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| C-SA |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| S-TAG TPID=0x88a8 |S-PCP|D| S-VID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length/Type | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| |
~ Customer Data ~
~ ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure A-7: S-TAG Tagging Frame Format for S-channel over the Link between an End Station and Its Adjacent Bridge
图A-7：端站与其相邻桥梁之间链路上S通道的S标签标签帧格式
Note: The frame format in Figure A-7 is identical to the format in Figure A-3.
注：图A-7中的帧格式与图A-3中的格式相同。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| C-DA |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| C-SA |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| S-TAG TPID=0x88a8 |S-PCP|D| S-VID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| C-TAG TPID=0x8100 |C-PCP|C| C-VID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length/Type | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| |
~ Customer Data ~
~ ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| C-DA |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| C-SA |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| S-TAG TPID=0x88a8 |S-PCP|D| S-VID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| C-TAG TPID=0x8100 |C-PCP|C| C-VID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length/Type | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| |
~ Customer Data ~
~ ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure A-8: S-TAG and C-TAG Tagging Frame Format over the Link between an End Station and Its Adjacent Bridge
图A-8：端站与其相邻桥梁之间链路上的S标签和C标签标签帧格式
Note: The frame format in Figure A-8 is identical to the format in Figure A-4.
注：图A-8中的帧格式与图A-4中的格式相同。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| C-DA |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| C-SA |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| E-TAG TPID=0x893F |E-PCP|D| Ingress_E-CID_base |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Res|GRP| E-CID_base |Ingre_E-CID_ext| E-CID_ext |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length/Type | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| |
~ Customer Data ~
~ ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| C-DA |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| C-SA |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| E-TAG TPID=0x893F |E-PCP|D| Ingress_E-CID_base |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Res|GRP| E-CID_base |Ingre_E-CID_ext| E-CID_ext |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length/Type | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| |
~ Customer Data ~
~ ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure A-9: E-TAG Tagging Frame Format over the Link between a Controlling Bridge and a Bridge Port Extender
图A-9：控制网桥和网桥端口扩展器之间链路上的电子标签标签帧格式
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| C-DA |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| C-SA |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| E-TAG TPID=0x893F |E-PCP|D| Ingress_E-CID_base |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Res|GRP| E-CID_base |Ingre_E-CID_ext| E-CID_ext |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| C-TAG TPID=0x8100 |C-PCP|C| C-VID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length/Type | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| |
~ Customer Data ~
~ ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| C-DA |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| C-SA |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| E-TAG TPID=0x893F |E-PCP|D| Ingress_E-CID_base |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Res|GRP| E-CID_base |Ingre_E-CID_ext| E-CID_ext |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| C-TAG TPID=0x8100 |C-PCP|C| C-VID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length/Type | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| |
~ Customer Data ~
~ ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure A-10: E-TAG and C-TAG Tagging Frame Format over the Link between a Controlling Bridge and a Bridge Port Extender
图A-10：控制网桥和网桥端口扩展器之间链路上的电子标签和C标签标签帧格式
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID (2) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID (256) | Field Count (8) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ingressInterface (10) | Field Length (4) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| egressInterface (14) | Field Length (4) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| observationTimeSeconds (322) | Field Length (8) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| dataLinkFrameSize (312) | Field Length (2) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| dataLinkFrameSection (315) | Field Length (65535) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| dataLinkFrameType (408) | Field Length (2) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| sectionOffset (409) | Field Length (2) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| sectionExportedOctets (410) | Field Length (2) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID (2) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID (256) | Field Count (8) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ingressInterface (10) | Field Length (4) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| egressInterface (14) | Field Length (4) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| observationTimeSeconds (322) | Field Length (8) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| dataLinkFrameSize (312) | Field Length (2) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| dataLinkFrameSection (315) | Field Length (65535) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| dataLinkFrameType (408) | Field Length (2) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| sectionOffset (409) | Field Length (2) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| sectionExportedOctets (410) | Field Length (2) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure B-1: Template Format Example
图B-1：模板格式示例
Authors' Addresses
作者地址
Shingo Kashima Nippon Telegraph and Telephone Corporation 1-5-1 Otemachi Chiyoda-ku, Tokyo 100-8116 Japan
日本东京千代田区大町1-5-1号日本新鹿岛电报电话公司100-8116
Phone: +81 3 6838 5267
EMail: kashima@nttv6.net
Phone: +81 3 6838 5267
EMail: kashima@nttv6.net
Atsushi Kobayashi Nippon Telegraph and Telephone East Corporation 3-19-2 Nishi-shinjuku Shinjuku-ku, Tokyo 163-8019 Japan
日本东电报电话公司3-19-2西新宿新宿日本东京163-8019
Phone: +81 3 5359 4351
EMail: akoba@nttv6.net
Phone: +81 3 5359 4351
EMail: akoba@nttv6.net
Paul Aitken Cisco Systems, Inc. 96 Commercial Quay Commercial Street, Edinburgh EH6 6LX United Kingdom
Paul Aitken Cisco Systems，Inc.英国爱丁堡商业码头商业街96号EH6 6LX
Phone: +44 131 561 3616
EMail: paitken@cisco.com
Phone: +44 131 561 3616
EMail: paitken@cisco.com