Network Working Group E. Boschi
Request for Comments: 5610 B. Trammell
Category: Standards Track Hitachi Europe
L. Mark
Fraunhofer IFAM
T. Zseby
Fraunhofer FOKUS
July 2009
Network Working Group E. Boschi
Request for Comments: 5610 B. Trammell
Category: Standards Track Hitachi Europe
L. Mark
Fraunhofer IFAM
T. Zseby
Fraunhofer FOKUS
July 2009
Exporting Type Information for IP Flow Information Export (IPFIX) Information Elements
导出IP流信息导出（IPFIX）信息元素的类型信息
Abstract
摘要
This document describes an extension to the IP Flow Information Export (IPFIX) protocol, which is used to represent and transmit data from IP flow measurement devices for collection, storage, and analysis, to allow the encoding of IPFIX Information Model properties within an IPFIX Message stream. This enables the export of extended type information for enterprise-specific Information Elements and the storage of such information within IPFIX Files, facilitating interoperability and reusability among a wide variety of applications and tools.
本文档描述了IP流信息导出（IPFIX）协议的扩展，该协议用于表示和传输来自IP流测量设备的数据，以进行收集、存储和分析，从而允许在IPFIX消息流中对IPFIX信息模型属性进行编码。这样就可以导出企业特定信息元素的扩展类型信息，并将这些信息存储在IPFIX文件中，从而促进各种应用程序和工具之间的互操作性和可重用性。
Status of This Memo
关于下段备忘
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2009 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date of publication of this document (http://trustee.ietf.org/license-info). Please review these documents carefully, as they describe your rights and restrictions with respect to this document.
本文件受BCP 78和IETF信托在本文件出版之日生效的与IETF文件有关的法律规定的约束(http://trustee.ietf.org/license-info). 请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. IPFIX Documents Overview . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Type Information Export . . . . . . . . . . . . . . . . . . . 5
3.1. informationElementDataType . . . . . . . . . . . . . . . . 5
3.2. informationElementDescription . . . . . . . . . . . . . . 6
3.3. informationElementName . . . . . . . . . . . . . . . . . . 7
3.4. informationElementRangeBegin . . . . . . . . . . . . . . . 7
3.5. informationElementRangeEnd . . . . . . . . . . . . . . . . 7
3.6. informationElementSemantics . . . . . . . . . . . . . . . 8
3.7. informationElementUnits . . . . . . . . . . . . . . . . . 9
3.8. privateEnterpriseNumber . . . . . . . . . . . . . . . . . 9
3.9. Information Element Type Options Template . . . . . . . . 10
3.10. Data Type and Semantics Restrictions . . . . . . . . . . . 12
4. Security Considerations . . . . . . . . . . . . . . . . . . . 13
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
7.1. Normative References . . . . . . . . . . . . . . . . . . . 15
7.2. Informative References . . . . . . . . . . . . . . . . . . 16
Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . 17
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. IPFIX Documents Overview . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Type Information Export . . . . . . . . . . . . . . . . . . . 5
3.1. informationElementDataType . . . . . . . . . . . . . . . . 5
3.2. informationElementDescription . . . . . . . . . . . . . . 6
3.3. informationElementName . . . . . . . . . . . . . . . . . . 7
3.4. informationElementRangeBegin . . . . . . . . . . . . . . . 7
3.5. informationElementRangeEnd . . . . . . . . . . . . . . . . 7
3.6. informationElementSemantics . . . . . . . . . . . . . . . 8
3.7. informationElementUnits . . . . . . . . . . . . . . . . . 9
3.8. privateEnterpriseNumber . . . . . . . . . . . . . . . . . 9
3.9. Information Element Type Options Template . . . . . . . . 10
3.10. Data Type and Semantics Restrictions . . . . . . . . . . . 12
4. Security Considerations . . . . . . . . . . . . . . . . . . . 13
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
7.1. Normative References . . . . . . . . . . . . . . . . . . . 15
7.2. Informative References . . . . . . . . . . . . . . . . . . 16
Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . 17
IP Flow Information Export (IPFIX) provides a template mechanism for the flexible description of Data Records, by defining a record as a collection of Information Elements defined in an IANA registry, However, these Templates provide limited information about the type of described data; indeed, they encode only the size of the fields defined by these Information Elements. There presently exists no mechanism to provide full type information for these Information Elements, as is defined for the Information Elements in the IPFIX Information Model [RFC5102].
IP流信息导出（IPFIX）通过将记录定义为IANA注册表中定义的信息元素集合，为数据记录的灵活描述提供了一种模板机制，但是，这些模板提供了有关所描述数据类型的有限信息；实际上，它们只编码由这些信息元素定义的字段的大小。目前不存在为这些信息元素提供完整类型信息的机制，正如IPFIX信息模型[RFC5102]中为信息元素定义的那样。
This especially limits the interoperability of enterprise-specific Information Elements. It is not possible to use analysis tools on IPFIX records containing these partially defined Information Elements that have not been developed with a priori knowledge of their types, since such tools will not be able to decode them; these tools can only treat and store them as opaque octet arrays. However, if richer information is available, additional operations such as efficient storage, display, and limited analysis of records containing enterprise-specific Information Elements become possible, even for Collecting Processes that have not been specifically developed to understand them.
这尤其限制了企业特定信息元素的互操作性。不可能对包含这些部分定义的信息元素的IPFIX记录使用分析工具，这些信息元素不是在事先了解其类型的情况下开发的，因为此类工具将无法对其进行解码；这些工具只能将它们作为不透明的八位字节数组处理和存储。但是，如果有更丰富的信息可用，则可以进行其他操作，例如对包含特定于企业的信息元素的记录进行高效存储、显示和有限的分析，甚至可以收集尚未专门开发以理解这些信息元素的过程。
This document defines a general mechanism to encode the full set of properties available for the definition of Information Elements within the IPFIX Information Model inline within an IPFIX Message stream using IPFIX Options. This mechanism may be used to fully define type information for Information Elements used within a message stream, without resorting to an external reference or reliance on out-of-band configuration, thereby improving the interoperability of enterprise-specific Information Elements.
本文档定义了一种通用机制，用于使用IPFIX选项对IPFIX消息流中的IPFIX信息模型内联信息元素定义的完整属性集进行编码。该机制可用于为消息流中使用的信息元素完全定义类型信息，而无需求助于外部引用或依赖带外配置，从而提高企业特定信息元素的互操作性。
Note that the solution described in this document is not intended as a replacement for registration with IANA of generally useful Information Elements. It introduces overhead and does not lead to real interoperability as provided by standardization. Therefore, we highly recommend standardizing all new generally useful Information Elements by registering them with IANA. Standardization is straightforward, and the type information that needs to be specified in order to support the proposed solution provides a perfect basis for the description required for standardizing the Information Element.
请注意，本文档中描述的解决方案并不打算替代IANA中的一般有用信息元素。它引入了开销，不会像标准化所提供的那样带来真正的互操作性。因此，我们强烈建议通过向IANA注册来标准化所有新的、普遍有用的信息元素。标准化很简单，为了支持建议的解决方案而需要指定的类型信息为标准化信息元素所需的描述提供了完美的基础。
It might happen that an Information Element previously described by the mechanism in this document later becomes an IANA-registered, standard Information Element. In such environments, old and new versions of the Information Element can coexist. A translation
可能会发生这样的情况，即本文档中的机制之前描述的信息元素后来成为IANA注册的标准信息元素。在这样的环境中，信息元素的新旧版本可以共存。译文
between Information Elements expressed by the described solution and standardized Information Elements is therefore not necessary and is out of scope for this document.
因此，所述解决方案所表达的信息元素与标准化信息元素之间不存在差异，不在本文件范围之内。
"Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of IP Traffic Flow Information" [RFC5101] (informally, the IPFIX Protocol document) and its associated documents define the IPFIX Protocol, which provides network engineers and administrators with access to IP traffic flow information.
“用于交换IP流量信息的IP流量信息导出（IPFIX）协议规范”[RFC5101]（非正式地称为IPFIX协议文档）及其相关文档定义了IPFIX协议，该协议为网络工程师和管理员提供了访问IP流量信息的权限。
"Architecture for IP Flow Information Export" [RFC5470] (the IPFIX Architecture document) defines the architecture for the export of measured IP flow information out of an IPFIX Exporting Process to an IPFIX Collecting Process, and the basic terminology used to describe the elements of this architecture, per the requirements defined in "Requirements for IP Flow Information Export" [RFC3917]. The IPFIX Protocol document [RFC5101] then covers the details of the method for transporting IPFIX Data Records and Templates via a congestion-aware transport protocol from an IPFIX Exporting Process to an IPFIX Collecting Process.
“IP流信息导出体系结构”[RFC5470]（IPFIX体系结构文档）定义了将测量的IP流信息从IPFIX导出过程导出到IPFIX收集过程的体系结构，以及用于描述该体系结构元素的基本术语，符合中定义的要求“IP流信息导出要求”[RFC3917]。然后，IPFIX协议文档[RFC5101]详细介绍了通过拥塞感知传输协议将IPFIX数据记录和模板从IPFIX导出过程传输到IPFIX收集过程的方法。
"Information Model for IP Flow Information Export" [RFC5102] (informally, the IPFIX Information Model document) describes the Information Elements used by IPFIX, including details on Information Element naming, numbering, and data type encoding.
“IP流信息导出的信息模型”[RFC5102]（非正式地称为IPFIX信息模型文档）描述了IPFIX使用的信息元素，包括信息元素命名、编号和数据类型编码的详细信息。
This document references the Protocol and Architecture documents for terminology and extends the IPFIX Information Model to provide new Information Elements for the representation of Information Element properties. It draws data type definitions and data type semantics definitions from the Information Model; the encodings of these data types are defined in [RFC5101].
本文档参考了协议和体系结构文档中的术语，并扩展了IPFIX信息模型，为信息元素属性的表示提供了新的信息元素。它从信息模型中提取数据类型定义和数据类型语义定义；[RFC5101]中定义了这些数据类型的编码。
Terms used in this document that are defined in the Terminology section of the IPFIX Protocol [RFC5101] document are to be interpreted as defined there.
本文件中使用的IPFIX协议[RFC5101]文件术语部分中定义的术语应按照此处定义进行解释。
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]中所述进行解释。
This section describes the mechanism used to encode Information Element type information within an IPFIX Message stream. This mechanism consists of an Options Template Record used to define Information Element type records, and a set of Information Elements required by these type records. We first specify the necessary Information Elements, followed by the structure of the Options Template describing the type records.
本节描述用于在IPFIX消息流中编码信息元素类型信息的机制。该机制包括一个用于定义信息元素类型记录的选项模板记录，以及这些类型记录所需的一组信息元素。我们首先指定必要的信息元素，然后是描述类型记录的选项模板的结构。
Note that Information Element type records require one Information Element, informationElementId, that is defined in the Packet Sampling (PSAMP) Information Model [RFC5477]. This Information Element supports references only to IANA-defined Information Elements; the privateEnterpriseNumber Information Element is required alongside informationElementId to describe enterprise-specific Information Elements.
请注意，信息元素类型记录需要一个信息元素informationElementId，它在数据包采样（PSAMP）信息模型[RFC5477]中定义。此信息元素仅支持对IANA定义的信息元素的引用；PrivateEnterpriseEnumber信息元素与informationElementId一起需要，以描述特定于企业的信息元素。
Description: A description of the abstract data type of an IPFIX information element. These are taken from the abstract data types defined in Section 3.1 of the IPFIX Information Model [RFC5102]; see that section for more information on the types described below. This field may take the values defined in Table 1 below.
描述：IPFIX信息元素的抽象数据类型的描述。这些数据来自IPFIX信息模型[RFC5102]第3.1节中定义的抽象数据类型；有关以下所述类型的更多信息，请参阅该部分。该字段可采用下表1中定义的值。
+-------+----------------------+
| Value | Description |
+-------+----------------------+
| 0 | octetArray |
| 1 | unsigned8 |
| 2 | unsigned16 |
| 3 | unsigned32 |
| 4 | unsigned64 |
| 5 | signed8 |
| 6 | signed16 |
| 7 | signed32 |
| 8 | signed64 |
| 9 | float32 |
| 10 | float64 |
| 11 | boolean |
| 12 | macAddress |
| 13 | string |
| 14 | dateTimeSeconds |
| 15 | dateTimeMilliseconds |
| 16 | dateTimeMicroseconds |
| 17 | dateTimeNanoseconds |
| 18 | ipv4Address |
| 19 | ipv6Address |
+-------+----------------------+
+-------+----------------------+
| Value | Description |
+-------+----------------------+
| 0 | octetArray |
| 1 | unsigned8 |
| 2 | unsigned16 |
| 3 | unsigned32 |
| 4 | unsigned64 |
| 5 | signed8 |
| 6 | signed16 |
| 7 | signed32 |
| 8 | signed64 |
| 9 | float32 |
| 10 | float64 |
| 11 | boolean |
| 12 | macAddress |
| 13 | string |
| 14 | dateTimeSeconds |
| 15 | dateTimeMilliseconds |
| 16 | dateTimeMicroseconds |
| 17 | dateTimeNanoseconds |
| 18 | ipv4Address |
| 19 | ipv6Address |
+-------+----------------------+
Table 1: IE Data Type Values
表1:IE数据类型值
These types are registered in the IANA IPFIX Information Element Data Type subregistry. This subregistry is intended to assign numbers for type names, not to provide a mechanism for adding data types to the IPFIX Protocol, and as such requires a Standards Action [RFC5226] to modify.
这些类型在IANA IPFIX信息元素数据类型子区域中注册。该子区域旨在为类型名称分配编号，而不是提供向IPFIX协议添加数据类型的机制，因此需要标准操作[RFC5226]进行修改。
Abstract Data Type: unsigned8
抽象数据类型：unsigned8
ElementId: 339
元素ID:339
Status: current
状态：当前
Reference: Section 3.1 of the IPFIX Information Model [RFC5102]
参考：IPFIX信息模型[RFC5102]第3.1节
Description: A UTF-8 [RFC3629] encoded Unicode string containing a human-readable description of an Information Element. The content of the informationElementDescription MAY be annotated with one or more language tags [RFC4646], encoded in-line [RFC2482] within the UTF-8 string, in order to specify the language in which the
描述：UTF-8[RFC3629]编码的Unicode字符串，包含信息元素的可读描述。informationElementDescription的内容可以用一个或多个语言标记[RFC4646]注释，并在UTF-8字符串内以行[RFC2482]编码，以指定使用的语言
description is written. Description text in multiple languages MAY tag each section with its own language tag; in this case, the description information in each language SHOULD have equivalent meaning. In the absence of any language tag, the "i-default" [RFC2277] language SHOULD be assumed. See the Security Considerations (Section 4) for notes on string handling for Information Element type records.
描述是书面的。多种语言的描述文本可以用自己的语言标记每个部分；在这种情况下，每种语言中的描述信息应具有相同的含义。在没有任何语言标记的情况下，应采用“i-default”[RFC2277]语言。有关信息元素类型记录的字符串处理说明，请参见安全注意事项（第4节）。
Abstract Data Type: string
抽象数据类型：string
ElementId: 340
元素ID:340
Status: current
状态：当前
Description: A UTF-8 [RFC3629] encoded Unicode string containing the name of an Information Element, intended as a simple identifier. See the Security Considerations (Section 4) for notes on string handling for Information Element type records.
描述：UTF-8[RFC3629]编码的Unicode字符串，包含信息元素的名称，用作简单标识符。有关信息元素类型记录的字符串处理说明，请参见安全注意事项（第4节）。
Abstract Data Type: string
抽象数据类型：string
ElementId: 341
元素ID:341
Status: current
状态：当前
Description: Contains the inclusive low end of the range of acceptable values for an Information Element.
描述：包含信息元素可接受值范围的包含性低端。
Abstract Data Type: unsigned64
抽象数据类型：unsigned64
Data Type Semantics: quantity
数据类型语义：数量
ElementId: 342
元素ID:342
Status: current
状态：当前
Description: Contains the inclusive high end of the range of acceptable values for an Information Element.
描述：包含信息元素可接受值范围的包含高端。
Abstract Data Type: unsigned64
抽象数据类型：unsigned64
Data Type Semantics: quantity
数据类型语义：数量
ElementId: 343
元素ID:343
Status: current
状态：当前
Description: A description of the semantics of an IPFIX Information Element. These are taken from the data type semantics defined in Section 3.2 of the IPFIX Information Model [RFC5102]; see that section for more information on the types described below. This field may take the values in Table 2 below. The special value 0x00 (default) is used to note that no semantics apply to the field; it cannot be manipulated by a Collecting Process or File Reader that does not understand it a priori.
描述：IPFIX信息元素的语义描述。这些来自IPFIX信息模型[RFC5102]第3.2节中定义的数据类型语义；有关以下所述类型的更多信息，请参阅该部分。该字段可采用下表2中的值。特殊值0x00（默认值）用于说明字段没有语义；收集过程或文件读取器无法对其进行操作，因为它们无法事先理解它。
+-------+--------------+
| Value | Description |
+-------+--------------+
| 0 | default |
| 1 | quantity |
| 2 | totalCounter |
| 3 | deltaCounter |
| 4 | identifier |
| 5 | flags |
+-------+--------------+
+-------+--------------+
| Value | Description |
+-------+--------------+
| 0 | default |
| 1 | quantity |
| 2 | totalCounter |
| 3 | deltaCounter |
| 4 | identifier |
| 5 | flags |
+-------+--------------+
Table 2: IE Semantics Values
表2:IE语义值
These semantics are registered in the IANA IPFIX Information Element Semantics subregistry. This subregistry is intended to assign numbers for semantics names, not to provide a mechanism for adding semantics to the IPFIX Protocol, and as such requires a Standards Action [RFC5226] to modify.
这些语义在IANA IPFIX信息元素语义子区中注册。该子区域旨在为语义名称分配编号，而不是提供向IPFIX协议添加语义的机制，因此需要标准操作[RFC5226]进行修改。
Abstract Data Type: unsigned8
抽象数据类型：unsigned8
ElementId: 344
元素ID:344
Status: current
状态：当前
Reference: Section 3.2 of the IPFIX Information Model [RFC5102]
参考：IPFIX信息模型[RFC5102]第3.2节
Description: A description of the units of an IPFIX Information Element. These correspond to the units implicitly defined in the Information Element definitions in Section 5 of the IPFIX Information Model [RFC5102]; see that section for more information on the types described below. This field may take the values in Table 3 below; the special value 0x00 (none) is used to note that the field is unitless.
描述：IPFIX信息元素单位的描述。这些对应于IPFIX信息模型[RFC5102]第5节信息元素定义中隐含定义的单位；有关以下所述类型的更多信息，请参阅该部分。该字段可采用下表3中的值；特殊值0x00（无）用于说明字段是无单位的。
+-------+---------------+---------------------------+
| Value | Name | Notes |
+-------+---------------+---------------------------+
| 0 | none | |
| 1 | bits | |
| 2 | octets | |
| 3 | packets | |
| 4 | flows | |
| 5 | seconds | |
| 6 | milliseconds | |
| 7 | microseconds | |
| 8 | nanoseconds | |
| 9 | 4-octet words | for IPv4 header length |
| 10 | messages | for reliability reporting |
| 11 | hops | for TTL |
| 12 | entries | for MPLS label stack |
+-------+---------------+---------------------------+
+-------+---------------+---------------------------+
| Value | Name | Notes |
+-------+---------------+---------------------------+
| 0 | none | |
| 1 | bits | |
| 2 | octets | |
| 3 | packets | |
| 4 | flows | |
| 5 | seconds | |
| 6 | milliseconds | |
| 7 | microseconds | |
| 8 | nanoseconds | |
| 9 | 4-octet words | for IPv4 header length |
| 10 | messages | for reliability reporting |
| 11 | hops | for TTL |
| 12 | entries | for MPLS label stack |
+-------+---------------+---------------------------+
Table 3: IE Units Values
表3:IE单位值
These types are registered in the IANA IPFIX Information Element Units subregistry; new types may be added on a First Come First Served [RFC5226] basis.
这些类型在IANA IPFIX信息元素单位子区注册；可在先到先得[RFC5226]的基础上添加新类型。
Abstract Data Type: unsigned16
抽象数据类型：unsigned16
ElementId: 345
元素ID:345
Status: current
状态：当前
Reference: Section 5 of the IPFIX Information Model [RFC5102]
参考：IPFIX信息模型第5节[RFC5102]
Description: A private enterprise number, as assigned by IANA. Within the context of an Information Element Type record, this element can be used along with the informationElementId element to scope properties to a specific Information Element. To export
描述：由IANA分配的私营企业编号。在信息元素类型记录的上下文中，此元素可以与informationElementId元素一起使用，以将属性范围化到特定的信息元素。输出
type information about an IANA-assigned Information Element, set the privateEnterpriseNumber to 0, or do not export the privateEnterpriseNumber in the type record. To export type information about an enterprise-specific Information Element, export the enterprise number in privateEnterpriseNumber, and export the Information Element number with the Enterprise bit cleared in informationElementId. The Enterprise bit in the associated informationElementId Information Element MUST be ignored by the Collecting Process.
键入有关IANA分配的信息元素的信息，将PrivateEnterpriseEnumber设置为0，或者不在类型记录中导出PrivateEnterpriseEnumber。要导出有关特定于企业的信息元素的类型信息，请在PrivateEnterpriseEnumber中导出企业编号，并在informationElementId中导出清除了企业位的信息元素编号。收集过程必须忽略关联的informationElementId信息元素中的企业位。
Abstract Data Type: unsigned32
抽象数据类型：unsigned32
Data Type Semantics: identifier
数据类型语义：标识符
ElementId: 346
元素ID:346
Status: current
状态：当前
Reference: Sections 3.2 and 3.4.1 of the IPFIX Protocol [RFC5101]; Section 8.2.3 of the PSAMP Information Model [RFC5477].
参考：IPFIX协议[RFC5101]第3.2节和第3.4.1节；PSAMP信息模型[RFC5477]第8.2.3节。
The Information Element Type Options Template attaches type information to Information Elements used within Template Records, as scoped to an Observation Domain within a Transport Session. This provides a mechanism for representing an IPFIX Information Model inline within an IPFIX Message stream. Data Records described by this template are referred to as Information Element type records.
“信息元素类型选项”模板将类型信息附加到模板记录中使用的信息元素，范围为传输会话中的观察域。这提供了一种在IPFIX消息流中内联表示IPFIX信息模型的机制。此模板描述的数据记录称为信息元素类型记录。
In deployments in which interoperability across vendor implementations of IPFIX is important, an Exporting Process exporting data using Templates containing enterprise-specific Information Elements SHOULD export an Information Element type record for each enterprise-specific Information Element it exports. Collecting Processes MAY use these type records to improve handling of unknown enterprise-specific Information Elements. Exporting Processes using enterprise-specific Information Elements to implement proprietary features MAY omit type records for those Information Elements.
在跨供应商IPFIX实现的互操作性非常重要的部署中，使用包含企业特定信息元素的模板导出数据的导出过程应为其导出的每个企业特定信息元素导出信息元素类型记录。收集流程可以使用这些类型记录来改进未知企业特定信息元素的处理。导出使用特定于企业的信息元素来实现专有功能的流程可能会忽略这些信息元素的类型记录。
Information Element type records MUST be handled by Collecting Processes as scoped to the Transport Session in which they are sent; this facility is not intended to provide a method for the permanent definition of Information Elements.
信息元素类型的记录必须由收集进程处理，收集进程的作用域为发送它们的传输会话；该设施的目的不是提供一种永久定义信息元素的方法。
Similarly, for security reasons, type information for a given Information Element MUST NOT be redefined by Information Element type records, and a Collecting Process MUST NOT allow an Information
类似地，出于安全原因，给定信息元素的类型信息不得由信息元素类型记录重新定义，并且收集过程不得允许
Element type record to replace its own internal definition of an Information Element. Information Element type records SHOULD NOT be duplicated in a given Observation Domain within a Transport Session. Once an Information Element type record has been exported for a given Information Element within a given Transport Session, all subsequent type records for that Information Element MUST be identical. Information Elements for which a Collecting Process receives conflicting semantic or type information MUST be ignored.
元素类型记录，以替换其自身的信息元素内部定义。信息元素类型记录不应在传输会话中的给定观察域中重复。一旦为给定传输会话中的给定信息元素导出了信息元素类型记录，该信息元素的所有后续类型记录必须相同。必须忽略收集过程接收冲突语义或类型信息的信息元素。
Note that while this template MAY be used to export information about any Information Element, including those registered with IANA, Exporting Processes SHOULD NOT export any type records that could be reasonably assumed to duplicate type information available at the Collecting Process. This mechanism is not intended as a replacement for Exporting and Collecting Processes keeping up to date with changes to the IANA registry; such an update mechanism is out of scope for this document.
请注意，虽然此模板可用于导出有关任何信息元素的信息，包括在IANA注册的信息，但导出过程不应导出任何类型记录，这些类型记录可能被合理地假定为与收集过程中可用的类型信息重复。这一机制并不打算取代导出和收集过程，以跟上IANA注册表的变化；这种更新机制超出了本文档的范围。
The template SHOULD contain the Information Elements in Table 4, below, as defined in the PSAMP Information Model [RFC5477] and in this document, above.
模板应包含以下表4中的信息元素，如PSAMP信息模型[RFC5477]和上述本文件中所定义。
+-------------------------------+-----------------------------------+
| IE | Description |
+-------------------------------+-----------------------------------+
| informationElementId [scope] | The Information Element |
| | identifier of the Information |
| | Element described by this type |
| | record. This Information Element |
| | MUST be defined as a Scope Field. |
| | See the PSAMP Information Model |
| | [RFC5477] for a definition of |
| | this field. |
| privateEnterpriseNumber | The Private Enterprise number of |
| [scope] | the Information Element described |
| | by this type record. This |
| | Information Element MUST be |
| | defined as a Scope Field. |
| informationElementDataType | The storage type of the specified |
| | Information Element. |
| informationElementSemantics | The semantic type of the |
| | specified Information Element. |
| informationElementUnits | The units of the specified |
| | Information Element. This |
| | element SHOULD be omitted if the |
| | Information Element is a unitless |
| | quantity, or a not a quantity or |
| | counter. |
+-------------------------------+-----------------------------------+
| IE | Description |
+-------------------------------+-----------------------------------+
| informationElementId [scope] | The Information Element |
| | identifier of the Information |
| | Element described by this type |
| | record. This Information Element |
| | MUST be defined as a Scope Field. |
| | See the PSAMP Information Model |
| | [RFC5477] for a definition of |
| | this field. |
| privateEnterpriseNumber | The Private Enterprise number of |
| [scope] | the Information Element described |
| | by this type record. This |
| | Information Element MUST be |
| | defined as a Scope Field. |
| informationElementDataType | The storage type of the specified |
| | Information Element. |
| informationElementSemantics | The semantic type of the |
| | specified Information Element. |
| informationElementUnits | The units of the specified |
| | Information Element. This |
| | element SHOULD be omitted if the |
| | Information Element is a unitless |
| | quantity, or a not a quantity or |
| | counter. |
+-------------------------------+-----------------------------------+
| IE (Continued) | Description (Continued) |
+-------------------------------+-----------------------------------+
| informationElementRangeBegin | The low end of the range of |
| | acceptable values for the |
| | specified Information Element. |
| | This element SHOULD be omitted if |
| | the beginning of the Information |
| | Element's acceptable range is |
| | defined by its data type. |
| informationElementRangeEnd | The high end of the range of |
| | acceptable values for the |
| | specified Information Element. |
| | This element SHOULD be omitted if |
| | the end Information Element's |
| | acceptable range is defined by |
| | its data type. |
| informationElementName | The name of the specified |
| | Information Element. |
| informationElementDescription | A human-readable description of |
| | the specified Information |
| | Element. This element MAY be |
| | omitted in the interest of export |
| | efficiency. |
+-------------------------------+-----------------------------------+
+-------------------------------+-----------------------------------+
| IE (Continued) | Description (Continued) |
+-------------------------------+-----------------------------------+
| informationElementRangeBegin | The low end of the range of |
| | acceptable values for the |
| | specified Information Element. |
| | This element SHOULD be omitted if |
| | the beginning of the Information |
| | Element's acceptable range is |
| | defined by its data type. |
| informationElementRangeEnd | The high end of the range of |
| | acceptable values for the |
| | specified Information Element. |
| | This element SHOULD be omitted if |
| | the end Information Element's |
| | acceptable range is defined by |
| | its data type. |
| informationElementName | The name of the specified |
| | Information Element. |
| informationElementDescription | A human-readable description of |
| | the specified Information |
| | Element. This element MAY be |
| | omitted in the interest of export |
| | efficiency. |
+-------------------------------+-----------------------------------+
Table 4: IE Type Options
表4：IE类型选项
Note that the informationElementSemantics values defined in Section 3.2 of [RFC5102] are primarily intended to differentiate semantic interpretation of numeric values, and that not all combinations of the informationElementDataType and informationElementSemantics Information Elements are valid; e.g., a counter cannot be encoded as an IPv4 address. The following are acceptable values of informationElementSemantics:
请注意，[RFC5102]第3.2节中定义的informationElementSemantics值主要用于区分数值的语义解释，并且并非informationElementDataType和informationElementSemantics信息元素的所有组合都有效；e、 例如，计数器不能编码为IPv4地址。以下是informationElementSemantics的可接受值：
o Any value is valid for unsigned informationElementDataType values ("unsigned8", "unsigned16", "unsigned32", or "unsigned64").
o 任何值都对未签名的informationElementDataType值（“未签名8”、“未签名16”、“未签名32”或“未签名64”）有效。
o Any value except "flags" is valid for signed informationElementDataType values ("signed8", "signed16", "signed32", or "signed64").
o 除“flags”之外的任何值对signed informationElementDataType值（“signed8”、“signed16”、“signed32”或“signed64”）有效。
o Any value except "identifier" or "flags" is valid for floating-point informationElementDataType values ("float32" or "float64").
o 除了“标识符”或“标志”之外的任何值都对浮点信息ElementDataType值（“float32”或“float64”）有效。
o Only "default" is valid for all other informationElementDataType values ("octetArray", "boolean", "macAddress", "string", "dateTimeSeconds", "dateTimeMilliseconds", "dateTimeMicroseconds", "dateTimeNanoseconds", "ipv4Address", or "ipv6Address").
o 只有“default”对所有其他informationElementDataType值有效（“octetArray”、“boolean”、“macAddress”、“string”、“dateTimeSeconds”、“DateTimeMilliconds”、“dateTimeMicroseconds”、“dateTimeNanoseconds”、“ipv4Address”或“ipv6Address”）。
Information Element type records containing invalid combinations of informationElementSemantics and informationElementDataType MUST NOT be sent by Exporting Processes, and MUST be ignored by Collecting Processes.
导出进程不能发送包含informationElementSemantics和informationElementDataType无效组合的信息元素类型记录，收集进程必须忽略这些记录。
Future Standards Actions that modify the Information Element Data Type subregistry or the Information Element Semantics subregistry should contain a Data Type and Semantics Restrictions section such as this one to define allowable combinations of type and semantics information.
修改信息元素数据类型子区或信息元素语义子区的未来标准操作应包含一个数据类型和语义限制部分，如此部分，以定义类型和语义信息的允许组合。
The same security considerations as for the IPFIX Protocol [RFC5101] apply.
适用与IPFIX协议[RFC5101]相同的安全注意事项。
In addition, attention must be paid to the handling of Information Element type records at the Collecting Process. Type information precedence rules defined above (a Collecting Process' current knowledge overrides type records; types are not redefinable during a session) are designed to minimize the opportunity for an attacker to maliciously redefine the data model.
此外，在收集过程中必须注意信息元素类型记录的处理。上面定义的类型信息优先规则（收集进程的当前知识覆盖类型记录；类型在会话期间不可重新定义）旨在最大限度地减少攻击者恶意重新定义数据模型的机会。
Note that Information Element type records may contain two strings describing Information Elements: informationElementName and informationElementDescription. IPFIX strings on the wire are length-prefixed and UTF-8 [RFC3629] encoded, most often within an IPFIX variable-length Information Element, which mitigates the risk of unterminated-string attacks against IPFIX Collecting Processes. However, care should still be taken when handling strings within the type system of the Collecting Process.
请注意，信息元素类型记录可能包含两个描述信息元素的字符串：informationElementName和informationElementDescription。线路上的IPFIX字符串带有长度前缀，并进行UTF-8[RFC3629]编码，通常在IPFIX可变长度信息元素中，这降低了针对IPFIX收集进程的未终止字符串攻击的风险。但是，在收集过程的类型系统内处理字符串时仍应小心。
First, Collecting Processes should pay particular attention to buffer sizes converting between length-prefixed and null-terminated strings. Exporting Processes MUST NOT export, and Collecting Processes MUST ignore, any informationElementName or informationElementDescription content that contains null characters (U+0000) in order to ensure buffer and string lengths are consistent.
首先，收集过程应该特别注意长度前缀字符串和空终止字符串之间的缓冲区大小转换。导出进程不得导出，收集进程必须忽略任何包含空字符（U+0000）的informationElementName或informationElementDescription内容，以确保缓冲区和字符串长度一致。
Also, note that there is no limit to IPFIX string length beyond that inherent in the protocol. The maximum IPFIX string length is 65512 octets (maximum message length (65535), minus message header (16), minus set header (4), minus long variable length field (3)).
另外，请注意，IPFIX字符串长度没有超出协议固有长度的限制。最大IPFIX字符串长度为65512个八位字节（最大消息长度（65535），减去消息头（16），减去集合头（4），减去长可变长度字段（3））。
Specifically, although the informationElementName of all IANA Information Elements at the time of this writing is less than about 40 octets, and the informationElementDescription is less than 4096 octets, either of these Information Elements may contain strings up to 65512 octets long.
具体而言，尽管在撰写本文时，所有IANA信息元素的informationElementName小于约40个八位字节，informationElementDescription小于4096个八位字节，但这些信息元素中的任何一个都可能包含长达65512个八位字节的字符串。
This document specifies several new IPFIX Information Elements in the IPFIX Information Element registry as defined in Section 3 above. IANA has assigned the following Information Element numbers for their respective Information Elements as specified below:
本文档在IPFIX信息元素注册表中指定了几个新的IPFIX信息元素，如上文第3节所定义。IANA为其各自的信息元素分配了以下信息元素编号，具体如下：
o Information Element Number 339 for the informationElementDataType Information Element
o InformationElement数据类型信息元素的信息元素编号339
o Information Element Number 340 for the informationElementDescription Information Element
o 信息元素描述信息元素的信息元素编号340
o Information Element Number 341 for the informationElementName Information Element
o informationElementName信息元素的信息元素编号341
o Information Element Number 342 for the informationElementRangeBegin Information Element
o informationElementRangeBegin信息元素的信息元素编号342
o Information Element Number 343 for the informationElementRangeEnd Information Element
o informationElementRangeEnd信息元素的信息元素编号343
o Information Element Number 344 for the informationElementSemantics Information Element
o InformationElement语义信息元素的信息元素编号344
o Information Element Number 345 for the informationElementUnits Information Element
o informationElementUnits信息元素的信息元素编号345
o Information Element Number 346 for the privateEnterpriseNumber Information Element
o PrivateEnterpriseEnumber信息元素编号346
IANA has created an Information Element Data Type subregistry for the values defined for the informationElementDataType Information Element. Entries may be added to this subregistry subject to a Standards Action [RFC5226].
IANA已经为informationElementDataType信息元素定义的值创建了一个信息元素数据类型子域。根据标准行动[RFC5226]，可将条目添加到此子地区。
IANA has created an Information Element Semantics subregistry for the values defined for the informationElementSemantics Information Element. Entries may be added to this subregistry subject to a Standards Action [RFC5226].
IANA已经为informationElementSemantics信息元素定义的值创建了一个信息元素语义子区。根据标准行动[RFC5226]，可将条目添加到此子地区。
IANA has created an Information Element Units subregistry for the values defined for the informationElementUnits Information Element. Entries may be added to this subregistry on an Expert Review [RFC5226] basis.
IANA已经为informationElementUnits信息元素定义的值创建了一个信息元素Units子区域。在专家评审[RFC5226]的基础上，可将条目添加到此分区域。
Thanks to Paul Aitken and Gerhard Muenz for the detailed reviews, and to David Moore for first raising this issue to the IPFIX mailing list. Thanks to the PRISM project for its support of this work.
感谢Paul Aitken和Gerhard Muenz的详细评论，以及David Moore首次将此问题提交到IPFIX邮件列表。感谢PRISM项目对这项工作的支持。
[RFC5101] Claise, B., "Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of IP Traffic Flow Information", RFC 5101, January 2008.
[RFC5101]Claise，B.，“用于交换IP流量信息的IP流量信息导出（IPFIX）协议规范”，RFC 5101，2008年1月。
[RFC5102] Quittek, J., Bryant, S., Claise, B., Aitken, P., and J. Meyer, "Information Model for IP Flow Information Export", RFC 5102, January 2008.
[RFC5102]Quitek，J.，Bryant，S.，Claise，B.，Aitken，P.，和J.Meyer，“IP流信息导出的信息模型”，RFC 5102，2008年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月。
[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO 10646", STD 63, RFC 3629, November 2003.
[RFC3629]Yergeau，F.，“UTF-8，ISO 10646的转换格式”，STD 63，RFC 3629，2003年11月。
[RFC2277] Alvestrand, H., "IETF Policy on Character Sets and Languages", BCP 18, RFC 2277, January 1998.
[RFC2277]Alvestrand，H.，“IETF字符集和语言政策”，BCP 18，RFC 2277，1998年1月。
[RFC2482] Whistler, K. and G. Adams, "Language Tagging in Unicode Plain Text", RFC 2482, January 1999.
[RFC2482]Whistler，K.和G.Adams，“Unicode纯文本中的语言标记”，RFC2482，1999年1月。
[RFC4646] Phillips, A. and M. Davis, "Tags for Identifying Languages", BCP 47, RFC 4646, September 2006.
[RFC4646]Phillips，A.和M.Davis，“识别语言的标记”，BCP 47，RFC 46462006年9月。
[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月。
[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月。
[RFC3917] Quittek, J., Zseby, T., Claise, B., and S. Zander, "Requirements for IP Flow Information Export (IPFIX)", RFC 3917, October 2004.
[RFC3917]Quitek，J.，Zseby，T.，Claise，B.，和S.Zander，“IP流信息导出（IPFIX）的要求”，RFC 39172004年10月。
[RFC5470] Sadasivan, G., Brownlee, N., Claise, B., and J. Quittek, "Architecture for IP Flow Information Export", RFC 5470, March 2009.
[RFC5470]Sadasivan，G.，Brownlee，N.，Claise，B.，和J.Quitek，“IP流信息导出架构”，RFC 54702009年3月。
The following example illustrates how the type information extension mechanism defined in this document may be used to describe the semantics of enterprise-specific Information Elements. The Information Elements used in this example are as follows:
下面的示例说明了如何使用本文中定义的类型信息扩展机制来描述特定于企业的信息元素的语义。本示例中使用的信息元素如下所示：
o initialTCPFlags, an example private IE 14, 1 octet, the TCP flags on the first TCP packet in the flow.
o initialTCPFlags，一个示例私有IE 14，1个八位组，流中第一个TCP数据包上的TCP标志。
o unionTCPFlags, an example private IE 15, 1 octet, the union of the TCP flags on all packets after the first TCP packet in the flow.
o unionTCPFlags，一个示例私有IE 15，1个八位组，流中第一个TCP数据包之后所有数据包上TCP标志的并集。
An Exporting Process exporting flows containing these Information Elements might use a Template like the following:
导出包含这些信息元素的流的导出流程可能会使用如下模板：
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 = 52 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 256 | Field Count = 9 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| flowStartSeconds 150 | Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| sourceIPv4Address 8 | Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| destinationIPv4Address 12 | Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| sourceTransportPort 7 | Field Length = 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| destinationTransportPort 11 | Field Length = 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| octetTotalCount 85 | Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|1| (initialTCPFlags) 14 | Field Length = 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Private Enterprise Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|1| (unionTCPFlags) 15 | Field Length = 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Private Enterprise Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| protocolIdentifier 4 | Field Length = 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 = 52 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 256 | Field Count = 9 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| flowStartSeconds 150 | Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| sourceIPv4Address 8 | Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| destinationIPv4Address 12 | Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| sourceTransportPort 7 | Field Length = 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| destinationTransportPort 11 | Field Length = 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| octetTotalCount 85 | Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|1| (initialTCPFlags) 14 | Field Length = 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Private Enterprise Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|1| (unionTCPFlags) 15 | Field Length = 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Private Enterprise Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| protocolIdentifier 4 | Field Length = 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: Template with Enterprise-Specific IEs
图1：具有企业特定IEs的模板
However, a Collecting Process receiving Data Sets described by this Template can only treat the enterprise-specific Information Elements as opaque octets; specifically, there is no hint to the collector that they contain flag information. To use the type information extension mechanism to address this problem, the Exporting Process would first export the Information Element Type Options Template described in Section 3.9 above:
然而，接收此模板描述的数据集的收集过程只能将特定于企业的信息元素视为不透明的八位字节；具体地说，没有提示收集器它们包含标志信息。要使用类型信息扩展机制解决此问题，导出过程将首先导出上文第3.9节所述的信息元素类型选项模板：
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 = 3 | Length = 26 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 257 | Field Count = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope Field Count = 2 |0| priv.EnterpriseNumber 346 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |0| informationElementId 303 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 2 |0| inf.El.DataType 339 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 1 |0| inf.El.Semantics 344 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 1 |0| inf.El.Name 341 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 65536 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 = 3 | Length = 26 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 257 | Field Count = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope Field Count = 2 |0| priv.EnterpriseNumber 346 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |0| informationElementId 303 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 2 |0| inf.El.DataType 339 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 1 |0| inf.El.Semantics 344 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 1 |0| inf.El.Name 341 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 65536 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: Example Information Element Type Options Template
图2：示例信息元素类型选项模板
Then, the Exporting Process would export two records described by the Example Information Element Type Options Template to describe the enterprise-specific Information Elements:
然后，导出过程将导出示例信息元素类型选项模板描述的两条记录，以描述特定于企业的信息元素：
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 = 257 | Length = 50 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Private Enterprise Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|X| IE 14 |0x01 unsigned8 |0x05 flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 15 length | |
+-+-+-+-+-+-+-+-+ |
| "initialTCPFlags" |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Private Enterprise Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|X| IE 15 |0x01 unsigned8 |0x05 flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 13 length | |
+-+-+-+-+-+-+-+-+ "unionTCPFlags" |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 = 257 | Length = 50 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Private Enterprise Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|X| IE 14 |0x01 unsigned8 |0x05 flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 15 length | |
+-+-+-+-+-+-+-+-+ |
| "initialTCPFlags" |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Private Enterprise Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|X| IE 15 |0x01 unsigned8 |0x05 flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 13 length | |
+-+-+-+-+-+-+-+-+ "unionTCPFlags" |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3: Type Record Example
图3：类型记录示例
Authors' Addresses
作者地址
Elisa Boschi Hitachi Europe c/o ETH Zurich Gloriastrasse 35 8092 Zurich Switzerland
Elisa Boschi Hitachi Europe，转交ETH苏黎世Gloriastrasse 35 8092苏黎世瑞士
Phone: +41 44 632 70 57
EMail: elisa.boschi@hitachi-eu.com
Phone: +41 44 632 70 57
EMail: elisa.boschi@hitachi-eu.com
Brian Trammell Hitachi Europe c/o ETH Zurich Gloriastrasse 35 8092 Zurich Switzerland
Brian Trammell Hitachi Europe转交苏黎世ETH Gloriastrasse 35 8092苏黎世瑞士
Phone: +41 44 632 70 13
EMail: brian.trammell@hitachi-eu.com
Phone: +41 44 632 70 13
EMail: brian.trammell@hitachi-eu.com
Lutz Mark Fraunhofer Institute for Manufacturing Technology and Applied Materials Research Wiener Str. 12 28359 Bremen Germany
德国不莱梅市卢茨马克·弗劳恩霍夫制造技术和应用材料研究所维纳街12 28359号
Phone: +49 421 2246206
EMail: lutz.mark@ifam.fraunhofer.de
Phone: +49 421 2246206
EMail: lutz.mark@ifam.fraunhofer.de
Tanja Zseby Fraunhofer Institute for Open Communication Systems Kaiserin-Augusta-Allee 31 10589 Berlin Germany
Tanja Zseby Fraunhofer开放通信系统研究所Kaiserin Augusta Allee 31 10589德国柏林
Phone: +49 30 3463 7153
EMail: tanja.zseby@fokus.fraunhofer.de
Phone: +49 30 3463 7153
EMail: tanja.zseby@fokus.fraunhofer.de