Network Working Group T. Dietz
Request for Comments: 5477 NEC Europe Ltd.
Category: Standards Track B. Claise
P. Aitken
Cisco Systems, Inc.
F. Dressler
University of Erlangen-Nuremberg
G. Carle
Technical University of Munich
March 2009
Network Working Group T. Dietz
Request for Comments: 5477 NEC Europe Ltd.
Category: Standards Track B. Claise
P. Aitken
Cisco Systems, Inc.
F. Dressler
University of Erlangen-Nuremberg
G. Carle
Technical University of Munich
March 2009
Information Model for Packet Sampling Exports
分组抽样导出的信息模型
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). 请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。
This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English.
本文件可能包含2008年11月10日之前发布或公开的IETF文件或IETF贡献中的材料。控制某些材料版权的人员可能未授予IETF信托允许在IETF标准流程之外修改此类材料的权利。在未从控制此类材料版权的人员处获得充分许可的情况下，不得在IETF标准流程之外修改本文件，也不得在IETF标准流程之外创建其衍生作品，除了将其格式化以RFC形式发布或将其翻译成英语以外的其他语言。
Abstract
摘要
This memo defines an information model for the Packet SAMPling (PSAMP) protocol. It is used by the PSAMP protocol for encoding sampled packet data and information related to the Sampling process. As the PSAMP protocol is based on the IP Flow Information eXport (IPFIX) protocol, this information model is an extension to the IPFIX information model.
此备忘录定义了数据包采样（PSAMP）协议的信息模型。PSAMP协议使用它对采样包数据和与采样过程相关的信息进行编码。由于PSAMP协议基于IP流信息导出（IPFIX）协议，因此此信息模型是IPFIX信息模型的扩展。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. PSAMP Documents Overview . . . . . . . . . . . . . . . . . . . 4
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1. Conventions Used in This Document . . . . . . . . . . . . 5
4. Relationship between PSAMP and IPFIX . . . . . . . . . . . . . 5
5. Properties of a PSAMP Information Element . . . . . . . . . . 5
6. Type Space . . . . . . . . . . . . . . . . . . . . . . . . . . 5
7. Overloading Information Elements . . . . . . . . . . . . . . . 6
8. The PSAMP Information Elements . . . . . . . . . . . . . . . . 6
8.1. Identifiers (301-303) . . . . . . . . . . . . . . . . . . 7
8.1.1. selectionSequenceId . . . . . . . . . . . . . . . . . 7
8.1.2. selectorId . . . . . . . . . . . . . . . . . . . . . . 8
8.1.3. informationElementId . . . . . . . . . . . . . . . . . 8
8.2. Sampling Configuration (304-311) . . . . . . . . . . . . . 9
8.2.1. selectorAlgorithm . . . . . . . . . . . . . . . . . . 9
8.2.2. samplingPacketInterval . . . . . . . . . . . . . . . . 11
8.2.3. samplingPacketSpace . . . . . . . . . . . . . . . . . 11
8.2.4. samplingTimeInterval . . . . . . . . . . . . . . . . . 12
8.2.5. samplingTimeSpace . . . . . . . . . . . . . . . . . . 12
8.2.6. samplingSize . . . . . . . . . . . . . . . . . . . . . 13
8.2.7. samplingPopulation . . . . . . . . . . . . . . . . . . 13
8.2.8. samplingProbability . . . . . . . . . . . . . . . . . 13
8.3. Hash Configuration (326-334) . . . . . . . . . . . . . . . 14
8.3.1. digestHashValue . . . . . . . . . . . . . . . . . . . 14
8.3.2. hashIPPayloadOffset . . . . . . . . . . . . . . . . . 15
8.3.3. hashIPPayloadSize . . . . . . . . . . . . . . . . . . 15
8.3.4. hashOutputRangeMin . . . . . . . . . . . . . . . . . . 15
8.3.5. hashOutputRangeMax . . . . . . . . . . . . . . . . . . 16
8.3.6. hashSelectedRangeMin . . . . . . . . . . . . . . . . . 16
8.3.7. hashSelectedRangeMax . . . . . . . . . . . . . . . . . 16
8.3.8. hashDigestOutput . . . . . . . . . . . . . . . . . . . 17
8.3.9. hashInitialiserValue . . . . . . . . . . . . . . . . . 17
8.4. Timestamps (322-325) . . . . . . . . . . . . . . . . . . . 18
8.4.1. observationTimeSeconds . . . . . . . . . . . . . . . . 18
8.4.2. observationTimeMilliseconds . . . . . . . . . . . . . 18
8.4.3. observationTimeMicroseconds . . . . . . . . . . . . . 19
8.4.4. observationTimeNanoseconds . . . . . . . . . . . . . . 19
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. PSAMP Documents Overview . . . . . . . . . . . . . . . . . . . 4
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1. Conventions Used in This Document . . . . . . . . . . . . 5
4. Relationship between PSAMP and IPFIX . . . . . . . . . . . . . 5
5. Properties of a PSAMP Information Element . . . . . . . . . . 5
6. Type Space . . . . . . . . . . . . . . . . . . . . . . . . . . 5
7. Overloading Information Elements . . . . . . . . . . . . . . . 6
8. The PSAMP Information Elements . . . . . . . . . . . . . . . . 6
8.1. Identifiers (301-303) . . . . . . . . . . . . . . . . . . 7
8.1.1. selectionSequenceId . . . . . . . . . . . . . . . . . 7
8.1.2. selectorId . . . . . . . . . . . . . . . . . . . . . . 8
8.1.3. informationElementId . . . . . . . . . . . . . . . . . 8
8.2. Sampling Configuration (304-311) . . . . . . . . . . . . . 9
8.2.1. selectorAlgorithm . . . . . . . . . . . . . . . . . . 9
8.2.2. samplingPacketInterval . . . . . . . . . . . . . . . . 11
8.2.3. samplingPacketSpace . . . . . . . . . . . . . . . . . 11
8.2.4. samplingTimeInterval . . . . . . . . . . . . . . . . . 12
8.2.5. samplingTimeSpace . . . . . . . . . . . . . . . . . . 12
8.2.6. samplingSize . . . . . . . . . . . . . . . . . . . . . 13
8.2.7. samplingPopulation . . . . . . . . . . . . . . . . . . 13
8.2.8. samplingProbability . . . . . . . . . . . . . . . . . 13
8.3. Hash Configuration (326-334) . . . . . . . . . . . . . . . 14
8.3.1. digestHashValue . . . . . . . . . . . . . . . . . . . 14
8.3.2. hashIPPayloadOffset . . . . . . . . . . . . . . . . . 15
8.3.3. hashIPPayloadSize . . . . . . . . . . . . . . . . . . 15
8.3.4. hashOutputRangeMin . . . . . . . . . . . . . . . . . . 15
8.3.5. hashOutputRangeMax . . . . . . . . . . . . . . . . . . 16
8.3.6. hashSelectedRangeMin . . . . . . . . . . . . . . . . . 16
8.3.7. hashSelectedRangeMax . . . . . . . . . . . . . . . . . 16
8.3.8. hashDigestOutput . . . . . . . . . . . . . . . . . . . 17
8.3.9. hashInitialiserValue . . . . . . . . . . . . . . . . . 17
8.4. Timestamps (322-325) . . . . . . . . . . . . . . . . . . . 18
8.4.1. observationTimeSeconds . . . . . . . . . . . . . . . . 18
8.4.2. observationTimeMilliseconds . . . . . . . . . . . . . 18
8.4.3. observationTimeMicroseconds . . . . . . . . . . . . . 19
8.4.4. observationTimeNanoseconds . . . . . . . . . . . . . . 19
8.5. Packet Data (313-314, 316-317) . . . . . . . . . . . . . . 19
8.5.1. ipHeaderPacketSection . . . . . . . . . . . . . . . . 20
8.5.2. ipPayloadPacketSection . . . . . . . . . . . . . . . . 20
8.5.3. mplsLabelStackSection . . . . . . . . . . . . . . . . 21
8.5.4. mplsPayloadPacketSection . . . . . . . . . . . . . . . 21
8.6. Statistics (318-321, 336-338) . . . . . . . . . . . . . . 22
8.6.1. selectorIdTotalPktsObserved . . . . . . . . . . . . . 22
8.6.2. selectorIdTotalPktsSelected . . . . . . . . . . . . . 23
8.6.3. absoluteError . . . . . . . . . . . . . . . . . . . . 23
8.6.4. relativeError . . . . . . . . . . . . . . . . . . . . 24
8.6.5. upperCILimit . . . . . . . . . . . . . . . . . . . . . 24
8.6.6. lowerCILimit . . . . . . . . . . . . . . . . . . . . . 25
8.6.7. confidenceLevel . . . . . . . . . . . . . . . . . . . 26
9. Security Considerations . . . . . . . . . . . . . . . . . . . 26
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27
10.1. Related Considerations . . . . . . . . . . . . . . . . . . 27
10.2. PSAMP-Related Considerations . . . . . . . . . . . . . . . 27
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 27
11.1. Normative References . . . . . . . . . . . . . . . . . . . 27
11.2. Informative References . . . . . . . . . . . . . . . . . . 28
Appendix A. Formal Specification of PSAMP Information Elements . 29
8.5. Packet Data (313-314, 316-317) . . . . . . . . . . . . . . 19
8.5.1. ipHeaderPacketSection . . . . . . . . . . . . . . . . 20
8.5.2. ipPayloadPacketSection . . . . . . . . . . . . . . . . 20
8.5.3. mplsLabelStackSection . . . . . . . . . . . . . . . . 21
8.5.4. mplsPayloadPacketSection . . . . . . . . . . . . . . . 21
8.6. Statistics (318-321, 336-338) . . . . . . . . . . . . . . 22
8.6.1. selectorIdTotalPktsObserved . . . . . . . . . . . . . 22
8.6.2. selectorIdTotalPktsSelected . . . . . . . . . . . . . 23
8.6.3. absoluteError . . . . . . . . . . . . . . . . . . . . 23
8.6.4. relativeError . . . . . . . . . . . . . . . . . . . . 24
8.6.5. upperCILimit . . . . . . . . . . . . . . . . . . . . . 24
8.6.6. lowerCILimit . . . . . . . . . . . . . . . . . . . . . 25
8.6.7. confidenceLevel . . . . . . . . . . . . . . . . . . . 26
9. Security Considerations . . . . . . . . . . . . . . . . . . . 26
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27
10.1. Related Considerations . . . . . . . . . . . . . . . . . . 27
10.2. PSAMP-Related Considerations . . . . . . . . . . . . . . . 27
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 27
11.1. Normative References . . . . . . . . . . . . . . . . . . . 27
11.2. Informative References . . . . . . . . . . . . . . . . . . 28
Appendix A. Formal Specification of PSAMP Information Elements . 29
Packet Sampling techniques are required for various measurement scenarios. The Packet Sampling (PSAMP) protocol provides mechanisms for packet selection using different Filtering and Sampling techniques. A standardized way for the export and storage of the Information Elements defined in Section 8 is required. The definition of the PSAMP information and data model is based on the IPFIX information model [RFC5102]. The PSAMP protocol document [RFC5476] specifies how to use the IPFIX protocol in the PSAMP context.
各种测量场景都需要数据包采样技术。数据包采样（PSAMP）协议使用不同的过滤和采样技术提供数据包选择机制。需要第8节中定义的信息元素的导出和存储的标准化方法。PSAMP信息和数据模型的定义基于IPFIX信息模型[RFC5102]。PSAMP协议文档[RFC5476]指定了如何在PSAMP上下文中使用IPFIX协议。
This document examines the IPFIX information model [RFC5102] and extends it to meet the PSAMP requirements. Therefore, the structure of this document is strongly based on the IPFIX document. It complements the PSAMP protocol specification by providing an appropriate PSAMP information model. The main part of this document, Section 8, defines the list of Information Elements to be transmitted by the PSAMP protocol. Sections 5 and 6 describe the data types and Information Element properties used within this document and their relationship to the IPFIX information model.
本文档检查IPFIX信息模型[RFC5102]，并对其进行扩展以满足PSAMP要求。因此，本文档的结构以IPFIX文档为基础。它通过提供适当的PSAMP信息模型来补充PSAMP协议规范。本文件的主要部分，第8节，定义了通过PSAMP协议传输的信息元素列表。第5节和第6节描述了本文档中使用的数据类型和信息元素属性及其与IPFIX信息模型的关系。
Although the PSAMP charter specified no requirements for measuring packet errors (such as drops, malformed, etc.), and this document does not cover such data, if there is need for collecting and exporting packet error information, the appropriate Information
尽管PSAMP章程未规定测量数据包错误（如丢弃、格式错误等）的要求，且本文件不涵盖此类数据，但如果需要收集和导出数据包错误信息，则应提供适当的信息
Elements can be requested from IANA, and exported with the PSAMP protocol.
元素可以从IANA请求，并使用PSAMP协议导出。
The main body of Section 8 was generated from an XML document. The XML-based specification of the PSAMP Information Elements can be used for automatically checking syntactical correctness of the specification. Furthermore it can be used -- in combination with the IPFIX information model -- for automated code generation. The resulting code can be used in PSAMP protocol implementations to deal with processing PSAMP information elements.
第8节的主体部分是从一个XML文档生成的。基于XML的PSAMP信息元素规范可用于自动检查规范的语法正确性。此外，它还可以与IPFIX信息模型一起用于自动代码生成。生成的代码可以在PSAMP协议实现中用于处理PSAMP信息元素。
For that reason, the XML document that served as the source for Section 8 is attached to this document in Appendix A.
因此，作为第8节来源的XML文档附在本文档的附录A中。
Note that although partially generated from the attached XML documents, the main body of this document is normative while the appendix is informational.
请注意，尽管部分是从所附的XML文档生成的，但本文档的主体是规范性的，而附录是信息性的。
This document is one out of a series of documents from the PSAMP group.
本文档是PSAMP组的一系列文档之一。
[RFC5474]: "A Framework for Packet Selection and Reporting" describes the PSAMP framework for network elements to select subsets of packets by statistical and other methods, and to export a stream of reports on the selected packets to a Collector.
[RFC5474]：“数据包选择和报告框架”描述了PSAMP框架，用于网络元件通过统计和其他方法选择数据包子集，并将所选数据包的报告流导出到收集器。
[RFC5475]: "Sampling and Filtering Techniques for IP Packet Selection" describes the set of packet selection techniques supported by PSAMP.
[RFC5475]：“IP数据包选择的采样和过滤技术”描述了PSAMP支持的数据包选择技术集。
[RFC5476]: "Packet Sampling (PSAMP) Protocol Specifications" specifies the export of packet information from a PSAMP Exporting Process to a PSAMP Collecting Process.
[RFC5476]：“数据包采样（PSAMP）协议规范”指定将数据包信息从PSAMP导出进程导出到PSAMP收集进程。
RFC 5477 (this document): "Information Model for Packet Sampling Exports" defines an information and data model for PSAMP.
RFC 5477（本文档）：“数据包采样导出的信息模型”定义了PSAMP的信息和数据模型。
IPFIX-specific terminology used in this document is defined in Section 2 of [RFC5101]. PSAMP-specific terminology used in this document is defined in Section 3.2 of [RFC5476]. In this document, as in [RFC5101] and [RFC5476], the first letter of each IPFIX- and PSAMP-specific term is capitalized.
[RFC5101]第2节定义了本文件中使用的IPFIX专用术语。[RFC5476]第3.2节定义了本文件中使用的PSAMP专用术语。在本文件中，如[RFC5101]和[RFC5476]中所述，每个IPFIX和PSAMP特定术语的首字母大写。
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]中所述进行解释。
As described in the PSAMP protocol [RFC5476], a PSAMP Report can be seen as a very special IPFIX Data Record. It represents an IPFIX Flow containing only a single packet. Therefore, the IPFIX information model can be used as a basis for PSAMP Reports.
如PSAMP协议[RFC5476]所述，PSAMP报告可以被视为非常特殊的IPFIX数据记录。它表示仅包含单个数据包的IPFIX流。因此，IPFIX信息模型可以用作PSAMP报告的基础。
Nevertheless, there are properties required in PSAMP Reports that cannot be modeled using the current IPFIX information model. This document describes extensions to the IPFIX information model that allow the modeling of information and data required by PSAMP.
然而，PSAMP报告中需要的属性不能使用当前的IPFIX信息模型建模。本文档描述了IPFIX信息模型的扩展，它允许对PSAMP所需的信息和数据进行建模。
Some of these extensions allow the export of what may be considered sensitive information. Refer to the Security Considerations section for a fuller discussion.
其中一些扩展允许导出可能被视为敏感信息的内容。有关更全面的讨论，请参阅安全注意事项部分。
Note that the export of sampled or filtered PSAMP Reports may not need all the Information Elements defined by the IPFIX information model [RFC5102], as discussed in Sections 6.2 and 6.3 of the PSAMP Framework [RFC5474].
请注意，如PSAMP框架[RFC5474]第6.2节和第6.3节所述，采样或过滤PSAMP报告的导出可能不需要IPFIX信息模型[RFC5102]定义的所有信息元素。
The PSAMP Information Elements are defined in accordance with Sections 2.1 to 2.3 of the IPFIX information model [RFC5102] to which reference should be made for more information. Nevertheless, we strongly recommend defining the optional "units" property for every Information Element (if applicable).
PSAMP信息元素根据IPFIX信息模型[RFC5102]第2.1至2.3节定义，更多信息请参考该节。然而，我们强烈建议为每个信息元素定义可选的“units”属性（如果适用）。
The Data Types defined in Section 3.1 of the IPFIX information model [RFC5102] are also used for the PSAMP Information Elements.
IPFIX信息模型[RFC5102]第3.1节中定义的数据类型也用于PSAMP信息元素。
The PSAMP Information Elements MUST be constructed from the basic abstract data types and data type semantics described in Section 3 of the IPFIX information model [RFC5102]. To ensure consistency between IPFIX and PSAMP, the data types are not repeated in this document. The encoding of these data types is described in the IPFIX protocol [RFC5101].
PSAMP信息元素必须根据IPFIX信息模型[RFC5102]第3节中描述的基本抽象数据类型和数据类型语义构建。为确保IPFIX和PSAMP之间的一致性，本文档中不重复数据类型。IPFIX协议[RFC5101]中描述了这些数据类型的编码。
Information Elements SHOULD NOT be overloaded with multiple meanings or re-used for multiple purposes. Different Information Elements SHOULD be allocated for each requirement.
信息元素不应具有多重含义，也不应重复用于多种目的。应为每个需求分配不同的信息元素。
Although the presence of certain other Information Elements allows the selection method to be inferred, a separate Information Element is provided for the selectorAlgorithm to include as scope for the Selector Report Interpretation [RFC5476].
尽管某些其他信息元素的存在允许推断选择方法，但为选择器算法提供了一个单独的信息元素，作为选择器报告解释的范围[RFC5476]。
Even if the Information Elements are specified with a specific selection method (i.e., a specific value of selectorAlgorithm) in mind, these Information Elements are not restricted to the selection method and MAY be used for different selection methods in the future.
即使考虑到使用特定选择方法（即，selectorAlgorithm的特定值）指定信息元素，这些信息元素也不限于选择方法，并且将来可以用于不同的选择方法。
This section describes the Information Elements used by the PSAMP protocol.
本节介绍PSAMP协议使用的信息元素。
For each Information Element specified in Sections 8.1 - 8.6 below, a unique identifier is allocated in accordance with Section 4 of the IPFIX information model [RFC5102]. The assignments are controlled by IANA as an extension of the IPFIX information model.
对于下文第8.1-8.6节中规定的每个信息元素，根据IPFIX信息模型[RFC5102]第4节分配唯一标识符。这些分配由IANA控制，作为IPFIX信息模型的扩展。
The Information Elements specified by the IPFIX information model [RFC5102] are used by the PSAMP protocol where applicable. To avoid inconsistencies between the IPFIX and the PSAMP information and data models, only those Information Elements that are not already described by the IPFIX information model are defined here.
IPFIX信息模型[RFC5102]指定的信息元素在适用时由PSAMP协议使用。为避免IPFIX与PSAMP信息和数据模型之间的不一致，此处仅定义IPFIX信息模型尚未描述的信息元素。
Below is the list of additional PSAMP Information Elements:
以下是附加PSAMP信息元素的列表：
+-----+----------------------------+-----+----------------------------+
| ID | Name | ID | Name |
+-----+----------------------------+-----+----------------------------+
| 301 | selectionSequenceId | 321 | relativeError |
| 302 | selectorId | 322 | observationTimeSeconds |
| 303 | informationElementId | 323 | observationTimeMilliseconds|
| 304 | selectorAlgorithm | 324 | observationTimeMicroseconds|
| 305 | samplingPacketInterval | 325 | observationTimeNanoseconds |
| 306 | samplingPacketSpace | 326 | digestHashValue |
| 307 | samplingTimeInterval | 327 | hashIPPayloadOffset |
| 308 | samplingTimeSpace | 328 | hashIPPayloadSize |
| 309 | samplingSize | 329 | hashOutputRangeMin |
| 310 | samplingPopulation | 330 | hashOutputRangeMax |
| 311 | samplingProbability | 331 | hashSelectedRangeMin |
| 313 | ipHeaderPacketSection | 332 | hashSelectedRangeMax |
| 314 | ipPayloadPacketSection | 333 | hashDigestOutput |
| 316 | mplsLabelStackSection | 334 | hashInitialiserValue |
| 317 | mplsPayloadPacketSection | 336 | upperCILimit |
| 318 | selectorIdTotalPktsObserved| 337 | lowerCILimit |
| 319 | selectorIdTotalPktsSelected| 338 | confidenceLevel |
| 320 | absoluteError | | |
+-----+----------------------------+-----+----------------------------+
+-----+----------------------------+-----+----------------------------+
| ID | Name | ID | Name |
+-----+----------------------------+-----+----------------------------+
| 301 | selectionSequenceId | 321 | relativeError |
| 302 | selectorId | 322 | observationTimeSeconds |
| 303 | informationElementId | 323 | observationTimeMilliseconds|
| 304 | selectorAlgorithm | 324 | observationTimeMicroseconds|
| 305 | samplingPacketInterval | 325 | observationTimeNanoseconds |
| 306 | samplingPacketSpace | 326 | digestHashValue |
| 307 | samplingTimeInterval | 327 | hashIPPayloadOffset |
| 308 | samplingTimeSpace | 328 | hashIPPayloadSize |
| 309 | samplingSize | 329 | hashOutputRangeMin |
| 310 | samplingPopulation | 330 | hashOutputRangeMax |
| 311 | samplingProbability | 331 | hashSelectedRangeMin |
| 313 | ipHeaderPacketSection | 332 | hashSelectedRangeMax |
| 314 | ipPayloadPacketSection | 333 | hashDigestOutput |
| 316 | mplsLabelStackSection | 334 | hashInitialiserValue |
| 317 | mplsPayloadPacketSection | 336 | upperCILimit |
| 318 | selectorIdTotalPktsObserved| 337 | lowerCILimit |
| 319 | selectorIdTotalPktsSelected| 338 | confidenceLevel |
| 320 | absoluteError | | |
+-----+----------------------------+-----+----------------------------+
Information Elements in this section serve as identifiers. All of them have an integral abstract data type and data type semantics "identifier".
本节中的信息元素用作标识符。它们都有一个完整的抽象数据类型和数据类型语义“标识符”。
+-----+----------------------------+-----+----------------------------+
| ID | Name | ID | Name |
+-----+----------------------------+-----+----------------------------+
| 301 | selectionSequenceId | 303 | informationElementId |
| 302 | selectorId | | |
+-----+----------------------------+-----+----------------------------+
+-----+----------------------------+-----+----------------------------+
| ID | Name | ID | Name |
+-----+----------------------------+-----+----------------------------+
| 301 | selectionSequenceId | 303 | informationElementId |
| 302 | selectorId | | |
+-----+----------------------------+-----+----------------------------+
Description:
说明：
From all the packets observed at an Observation Point, a subset of the packets is selected by a sequence of one or more Selectors. The selectionSequenceId is a unique value per Observation Domain, specifying the Observation Point and the sequence of Selectors through which the packets are selected.
从在观察点观察到的所有分组中，分组的子集由一个或多个选择器的序列选择。selectionSequenceId是每个观察域的唯一值，指定观察点和选择数据包的选择器序列。
Abstract Data Type: unsigned64
抽象数据类型：unsigned64
Data Type Semantics: identifier
数据类型语义：标识符
ElementId: 301
元素ID:301
Status: current
状态：当前
Description:
说明：
The Selector ID is the unique ID identifying a Primitive Selector. Each Primitive Selector must have a unique ID in the Observation Domain.
选择器ID是标识基元选择器的唯一ID。每个基元选择器在观察域中必须具有唯一的ID。
Abstract Data Type: unsigned16
抽象数据类型：unsigned16
Data Type Semantics: identifier
数据类型语义：标识符
ElementId: 302
元素ID:302
Status: current
状态：当前
Description:
说明：
This Information Element contains the ID of another Information Element.
此信息元素包含另一个信息元素的ID。
Abstract Data Type: unsigned16
抽象数据类型：unsigned16
Data Type Semantics: identifier
数据类型语义：标识符
ElementId: 303
元素ID:303
Status: current
状态：当前
Information Elements in this section can be used for describing the Sampling configuration of a Selection Process.
本节中的信息元素可用于描述选择过程的采样配置。
+-----+----------------------------+-----+----------------------------+
| ID | Name | ID | Name |
+-----+----------------------------+-----+----------------------------+
| 304 | selectorAlgorithm | 308 | samplingTimeSpace |
| 305 | samplingPacketInterval | 309 | samplingSize |
| 306 | samplingPacketSpace | 310 | samplingPopulation |
| 307 | samplingTimeInterval | 311 | samplingProbability |
+-----+----------------------------+-----+----------------------------+
+-----+----------------------------+-----+----------------------------+
| ID | Name | ID | Name |
+-----+----------------------------+-----+----------------------------+
| 304 | selectorAlgorithm | 308 | samplingTimeSpace |
| 305 | samplingPacketInterval | 309 | samplingSize |
| 306 | samplingPacketSpace | 310 | samplingPopulation |
| 307 | samplingTimeInterval | 311 | samplingProbability |
+-----+----------------------------+-----+----------------------------+
Description:
说明：
This Information Element identifies the packet selection methods (e.g., Filtering, Sampling) that are applied by the Selection Process.
该信息元素标识由选择过程应用的分组选择方法（例如，过滤、采样）。
Most of these methods have parameters. Further Information Elements are needed to fully specify packet selection with these methods and all their parameters.
大多数方法都有参数。需要更多的信息元素来使用这些方法及其所有参数完全指定数据包选择。
The methods listed below are defined in [RFC5475]. For their parameters, Information Elements are defined in the information model document. The names of these Information Elements are listed for each method identifier.
[RFC5475]中定义了下列方法。对于其参数，信息元素在信息模型文档中定义。为每个方法标识符列出了这些信息元素的名称。
Further method identifiers may be added to the list below. It might be necessary to define new Information Elements to specify their parameters.
进一步的方法标识符可以添加到下面的列表中。可能需要定义新的信息元素来指定其参数。
The selectorAlgorithm registry is maintained by IANA. New assignments for the registry will be administered by IANA and are subject to Expert Review [RFC5226].
selectorAlgorithm注册表由IANA维护。注册处的新任务将由IANA管理，并接受专家审查[RFC5226]。
The registry can be updated when specifications of the new method(s) and any new Information Elements are provided.
当提供新方法的规范和任何新信息元素时，可以更新注册表。
The group of experts must double check the selectorAlgorithm definitions and Information Elements with already defined selectorAlgorithms and Information Elements for completeness, accuracy, and redundancy. Those experts will initially be drawn from the Working Group Chairs and document editors of the IPFIX and PSAMP Working Groups.
专家组必须使用已定义的selectorAlgorithm和信息元素对selectorAlgorithm定义和信息元素的完整性、准确性和冗余性进行双重检查。这些专家最初将来自IPFIX和PSAMP工作组的工作组主席和文件编辑。
The following packet selection methods identifiers are defined here:
此处定义了以下数据包选择方法标识符：
+----+------------------------+------------------------+
| ID | Method | Parameters |
+----+------------------------+------------------------+
| 1 | Systematic count-based | samplingPacketInterval |
| | Sampling | samplingPacketSpace |
+----+------------------------+------------------------+
| 2 | Systematic time-based | samplingTimeInterval |
| | Sampling | samplingTimeSpace |
+----+------------------------+------------------------+
| 3 | Random n-out-of-N | samplingSize |
| | Sampling | samplingPopulation |
+----+------------------------+------------------------+
| 4 | Uniform probabilistic | samplingProbability |
| | Sampling | |
+----+------------------------+------------------------+
| 5 | Property Match | no agreed parameters |
| | Filtering | |
+----+------------------------+------------------------+
| Hash-based Filtering | hashInitialiserValue |
+----+------------------------+ hashIPPayloadOffset |
| 6 | using BOB | hashIPPayloadSize |
+----+------------------------+ hashSelectedRangeMin |
| 7 | using IPSX | hashSelectedRangeMax |
+----+------------------------+ hashOutputRangeMin |
| 8 | using CRC | hashOutputRangeMax |
+----+------------------------+------------------------+
+----+------------------------+------------------------+
| ID | Method | Parameters |
+----+------------------------+------------------------+
| 1 | Systematic count-based | samplingPacketInterval |
| | Sampling | samplingPacketSpace |
+----+------------------------+------------------------+
| 2 | Systematic time-based | samplingTimeInterval |
| | Sampling | samplingTimeSpace |
+----+------------------------+------------------------+
| 3 | Random n-out-of-N | samplingSize |
| | Sampling | samplingPopulation |
+----+------------------------+------------------------+
| 4 | Uniform probabilistic | samplingProbability |
| | Sampling | |
+----+------------------------+------------------------+
| 5 | Property Match | no agreed parameters |
| | Filtering | |
+----+------------------------+------------------------+
| Hash-based Filtering | hashInitialiserValue |
+----+------------------------+ hashIPPayloadOffset |
| 6 | using BOB | hashIPPayloadSize |
+----+------------------------+ hashSelectedRangeMin |
| 7 | using IPSX | hashSelectedRangeMax |
+----+------------------------+ hashOutputRangeMin |
| 8 | using CRC | hashOutputRangeMax |
+----+------------------------+------------------------+
There is a broad variety of possible parameters that could be used for Property match Filtering (5), but currently there are no agreed parameters specified.
有多种可能的参数可用于属性匹配筛选（5），但目前没有指定商定的参数。
Abstract Data Type: unsigned16
抽象数据类型：unsigned16
Data Type Semantics: identifier
数据类型语义：标识符
ElementId: 304
元素ID:304
Status: current
状态：当前
Description:
说明：
This Information Element specifies the number of packets that are consecutively sampled. A value of 100 means that 100 consecutive packets are sampled.
此信息元素指定连续采样的数据包数。值100表示对100个连续数据包进行采样。
For example, this Information Element may be used to describe the configuration of a systematic count-based Sampling Selector.
例如，该信息元素可用于描述基于系统计数的采样选择器的配置。
Abstract Data Type: unsigned32
抽象数据类型：unsigned32
Data Type Semantics: quantity
数据类型语义：数量
ElementId: 305
元素ID:305
Status: current
状态：当前
Units: packets
单位：小包
Description:
说明：
This Information Element specifies the number of packets between two "samplingPacketInterval"s. A value of 100 means that the next interval starts 100 packets (which are not sampled) after the current "samplingPacketInterval" is over.
此信息元素指定两个“samplingPacketInterval”之间的数据包数。值100表示当前“samplingPacketInterval”结束后，下一个间隔开始100个数据包（未采样）。
For example, this Information Element may be used to describe the configuration of a systematic count-based Sampling Selector.
例如，该信息元素可用于描述基于系统计数的采样选择器的配置。
Abstract Data Type: unsigned32
抽象数据类型：unsigned32
Data Type Semantics: quantity
数据类型语义：数量
ElementId: 306
元素ID:306
Status: current
状态：当前
Units: packets
单位：小包
Description:
说明：
This Information Element specifies the time interval in microseconds during which all arriving packets are sampled.
此信息元素指定对所有到达的数据包进行采样的时间间隔（以微秒为单位）。
For example, this Information Element may be used to describe the configuration of a systematic time-based Sampling Selector.
例如，该信息元素可用于描述系统的基于时间的采样选择器的配置。
Abstract Data Type: unsigned32
抽象数据类型：unsigned32
Data Type Semantics: quantity
数据类型语义：数量
ElementId: 307
元素ID:307
Status: current
状态：当前
Units: microseconds
单位：微秒
Description:
说明：
This Information Element specifies the time interval in microseconds between two "samplingTimeInterval"s. A value of 100 means that the next interval starts 100 microseconds (during which no packets are sampled) after the current "samplingTimeInterval" is over.
此信息元素指定两个“samplingTimeInterval”之间的时间间隔（以微秒为单位）。值100表示当前“samplingTimeInterval”结束后，下一个间隔开始100微秒（在此期间没有对数据包进行采样）。
For example, this Information Element may used to describe the configuration of a systematic time-based Sampling Selector.
例如，该信息元素可用于描述系统的基于时间的采样选择器的配置。
Abstract Data Type: unsigned32
抽象数据类型：unsigned32
Data Type Semantics: quantity
数据类型语义：数量
ElementId: 308
元素ID:308
Status: current
状态：当前
Units: microseconds
单位：微秒
Description:
说明：
This Information Element specifies the number of elements taken from the parent Population for random Sampling methods.
此信息元素指定随机抽样方法从父总体中获取的元素数。
For example, this Information Element may be used to describe the configuration of a random n-out-of-N Sampling Selector.
例如，该信息元素可用于描述随机n取n采样选择器的配置。
Abstract Data Type: unsigned32
抽象数据类型：unsigned32
Data Type Semantics: quantity
数据类型语义：数量
ElementId: 309
元素ID:309
Status: current
状态：当前
Units: packets
单位：小包
Description:
说明：
This Information Element specifies the number of elements in the parent Population for random Sampling methods.
此信息元素指定随机抽样方法的父总体中的元素数。
For example, this Information Element may be used to describe the configuration of a random n-out-of-N Sampling Selector.
例如，该信息元素可用于描述随机n取n采样选择器的配置。
Abstract Data Type: unsigned32
抽象数据类型：unsigned32
Data Type Semantics: quantity
数据类型语义：数量
ElementId: 310
元素ID:310
Status: current
状态：当前
Units: packets
单位：小包
Description:
说明：
This Information Element specifies the probability that a packet is sampled, expressed as a value between 0 and 1. The probability is equal for every packet. A value of 0 means no packet was sampled since the probability is 0.
此信息元素指定对数据包进行采样的概率，表示为0到1之间的值。每个包的概率都是相等的。值为0表示没有对数据包进行采样，因为概率为0。
For example, this Information Element may be used to describe the configuration of a uniform probabilistic Sampling Selector.
例如，该信息元素可用于描述均匀概率采样选择器的配置。
Abstract Data Type: float64
抽象数据类型：float64
Data Type Semantics: quantity
数据类型语义：数量
ElementId: 311
元素ID:311
Status: current
状态：当前
The following Information Elements can be used for describing the Sampling configuration of a Selection Process. The individual parameters are explained in more detail in Sections 6.2, 3.8, and 7.1 of [RFC5475].
以下信息元素可用于描述选择过程的采样配置。[RFC5475]第6.2、3.8和7.1节对各个参数进行了更详细的解释。
+-----+----------------------------+-----+----------------------------+
| ID | Name | ID | Name |
+-----+----------------------------+-----+----------------------------+
| 326 | digestHashValue | 331 | hashSelectedRangeMin |
| 327 | hashIPPayloadOffset | 332 | hashSelectedRangeMax |
| 328 | hashIPPayloadSize | 333 | hashDigestOutput |
| 329 | hashOutputRangeMin | 334 | hashInitialiserValue |
| 330 | hashOutputRangeMax | | |
+-----+----------------------------+-----+----------------------------+
+-----+----------------------------+-----+----------------------------+
| ID | Name | ID | Name |
+-----+----------------------------+-----+----------------------------+
| 326 | digestHashValue | 331 | hashSelectedRangeMin |
| 327 | hashIPPayloadOffset | 332 | hashSelectedRangeMax |
| 328 | hashIPPayloadSize | 333 | hashDigestOutput |
| 329 | hashOutputRangeMin | 334 | hashInitialiserValue |
| 330 | hashOutputRangeMax | | |
+-----+----------------------------+-----+----------------------------+
Description:
说明：
This Information Element specifies the value from the digest hash function.
此信息元素指定摘要哈希函数中的值。
See also Sections 6.2, 3.8, and 7.1 of [RFC5475].
另见[RFC5475]第6.2、3.8和7.1节。
Abstract Data Type: unsigned64
抽象数据类型：unsigned64
Data Type Semantics: quantity
数据类型语义：数量
ElementId: 326
元素ID:326
Status: current
状态：当前
Description:
说明：
This Information Element specifies the IP payload offset used by a Hash-based Selection Selector.
此信息元素指定基于哈希的选择选择器使用的IP有效负载偏移量。
See also Sections 6.2, 3.8, and 7.1 of [RFC5475].
另见[RFC5475]第6.2、3.8和7.1节。
Abstract Data Type: unsigned64
抽象数据类型：unsigned64
Data Type Semantics: quantity
数据类型语义：数量
ElementId: 327
ElementId:327
Status: current
状态：当前
Description:
说明：
This Information Element specifies the IP payload size used by a Hash-based Selection Selector.
此信息元素指定基于哈希的选择选择器使用的IP有效负载大小。
See also Sections 6.2, 3.8, and 7.1 of [RFC5475].
另见[RFC5475]第6.2、3.8和7.1节。
Abstract Data Type: unsigned64
抽象数据类型：unsigned64
Data Type Semantics: quantity
数据类型语义：数量
ElementId: 328
元素ID:328
Status: current
状态：当前
Description:
说明：
This Information Element specifies the value for the beginning of a hash function's potential output range.
此信息元素指定哈希函数的潜在输出范围的起始值。
See also Sections 6.2, 3.8, and 7.1 of [RFC5475].
另见[RFC5475]第6.2、3.8和7.1节。
Abstract Data Type: unsigned64
抽象数据类型：unsigned64
Data Type Semantics: quantity
数据类型语义：数量
ElementId: 329
ElementId:329
Status: current
状态：当前
Description:
说明：
This Information Element specifies the value for the end of a hash function's potential output range.
此信息元素指定哈希函数的潜在输出范围的结束值。
See also Sections 6.2, 3.8, and 7.1 of [RFC5475].
另见[RFC5475]第6.2、3.8和7.1节。
Abstract Data Type: unsigned64
抽象数据类型：unsigned64
Data Type Semantics: quantity
数据类型语义：数量
ElementId: 330
元素ID:330
Status: current
状态：当前
Description:
说明：
This Information Element specifies the value for the beginning of a hash function's selected range.
此信息元素指定哈希函数所选范围的起始值。
See also Sections 6.2, 3.8, and 7.1 of [RFC5475].
另见[RFC5475]第6.2、3.8和7.1节。
Abstract Data Type: unsigned64
抽象数据类型：unsigned64
Data Type Semantics: quantity
数据类型语义：数量
ElementId: 331
元素ID:331
Status: current
状态：当前
Description:
说明：
This Information Element specifies the value for the end of a hash function's selected range.
此信息元素指定哈希函数所选范围的结束值。
See also Sections 6.2, 3.8, and 7.1 of [RFC5475].
另见[RFC5475]第6.2、3.8和7.1节。
Abstract Data Type: unsigned64
抽象数据类型：unsigned64
Data Type Semantics: quantity
数据类型语义：数量
ElementId: 332
元素ID:332
Status: current
状态：当前
Description:
说明：
This Information Element contains a boolean value that is TRUE if the output from this hash Selector has been configured to be included in the packet report as a packet digest, else FALSE.
如果此哈希选择器的输出已配置为作为数据包摘要包含在数据包报告中，则此信息元素包含布尔值，否则为FALSE。
See also Sections 6.2, 3.8, and 7.1 of [RFC5475].
另见[RFC5475]第6.2、3.8和7.1节。
Abstract Data Type: boolean
抽象数据类型：布尔型
Data Type Semantics: quantity
数据类型语义：数量
ElementId: 333
元素ID:333
Status: current
状态：当前
Description:
说明：
This Information Element specifies the initialiser value to the hash function.
此信息元素指定哈希函数的初始化器值。
See also Sections 6.2, 3.8, and 7.1 of [RFC5475].
另见[RFC5475]第6.2、3.8和7.1节。
Abstract Data Type: unsigned64
抽象数据类型：unsigned64
Data Type Semantics: quantity
数据类型语义：数量
ElementId: 334
元素ID:334
Status: current
状态：当前
The Information Elements listed below contain timestamps. They can be used for reporting the observation time of a single packet.
下面列出的信息元素包含时间戳。它们可用于报告单个数据包的观察时间。
+-----+----------------------------+-----+----------------------------+
| ID | Name | ID | Name |
+-----+----------------------------+-----+----------------------------+
| 322 | observationTimeSeconds | 324 | observationTimeMicroseconds|
| 323 | observationTimeMilliseconds| 325 | observationTimeNanoseconds |
+-----+----------------------------+-----+----------------------------+
+-----+----------------------------+-----+----------------------------+
| ID | Name | ID | Name |
+-----+----------------------------+-----+----------------------------+
| 322 | observationTimeSeconds | 324 | observationTimeMicroseconds|
| 323 | observationTimeMilliseconds| 325 | observationTimeNanoseconds |
+-----+----------------------------+-----+----------------------------+
Description:
说明：
This Information Element specifies the absolute time in seconds of an observation.
此信息元素指定观察的绝对时间（以秒为单位）。
Abstract Data Type: dateTimeSeconds
抽象数据类型：dateTimeSeconds
Data Type Semantics: quantity
数据类型语义：数量
ElementId: 322
ElementId:322
Status: current
状态：当前
Units: seconds
单位：秒
Description:
说明：
This Information Element specifies the absolute time in milliseconds of an observation.
此信息元素指定观察的绝对时间（以毫秒为单位）。
Abstract Data Type: dateTimeMilliseconds
抽象数据类型：DateTimeMillenses
Data Type Semantics: quantity
数据类型语义：数量
ElementId: 323
元素ID:323
Status: current
状态：当前
Units: milliseconds
单位：毫秒
Description:
说明：
This Information Element specifies the absolute time in microseconds of an observation.
此信息元素指定观测的绝对时间（以微秒为单位）。
Abstract Data Type: dateTimeMicroseconds
抽象数据类型：dateTimeMicroseconds
Data Type Semantics: quantity
数据类型语义：数量
ElementId: 324
元素ID:324
Status: current
状态：当前
Units: microseconds
单位：微秒
Description:
说明：
This Information Element specifies the absolute time in nanoseconds of an observation.
此信息元素指定观测的绝对时间（以纳秒为单位）。
Abstract Data Type: dateTimeNanoseconds
抽象数据类型：dateTimeNanoseconds
Data Type Semantics: quantity
数据类型语义：数量
ElementId: 325
元素ID:325
Status: current
状态：当前
Units: nanoseconds
单位：纳秒
The following Information Elements are all used for reporting raw content of a packet. All Information Elements containing sections of the observed packet can also be used in IPFIX [RFC5101]. If the values for those sections vary for different packets in a Flow, then the Flow Report will contain the value observed in the first packet of the Flow.
以下信息元素都用于报告数据包的原始内容。包含观察到的数据包部分的所有信息元素也可以在IPFIX[RFC5101]中使用。如果流中不同数据包的这些部分的值不同，那么流报告将包含在流的第一个数据包中观察到的值。
+-----+----------------------------+-----+----------------------------+
| ID | Name | ID | Name |
+-----+----------------------------+-----+----------------------------+
| 313 | ipHeaderPacketSection | 316 | mplsLabelStackSection |
| 314 | ipPayloadPacketSection | 317 | mplsPayloadPacketSection |
+-----+----------------------------+-----+----------------------------+
+-----+----------------------------+-----+----------------------------+
| ID | Name | ID | Name |
+-----+----------------------------+-----+----------------------------+
| 313 | ipHeaderPacketSection | 316 | mplsLabelStackSection |
| 314 | ipPayloadPacketSection | 317 | mplsPayloadPacketSection |
+-----+----------------------------+-----+----------------------------+
Description:
说明：
This Information Element, which may have a variable length, carries a series of octets from the start of the IP header of a sampled packet.
该信息元素可能具有可变长度，从采样数据包的IP报头开始携带一系列八位字节。
With sufficient length, this element also reports octets from the IP payload, subject to [RFC2804]. See the Security Considerations section.
在足够长的情况下，该元素还根据[RFC2804]报告来自IP有效负载的八位字节。请参阅安全注意事项部分。
The size of the exported section may be constrained due to limitations in the IPFIX protocol.
由于IPFIX协议中的限制，导出节的大小可能会受到限制。
The data for this field MUST NOT be padded.
不得填充此字段的数据。
Abstract Data Type: octetArray
抽象数据类型：Octeraray
ElementId: 313
元素ID:313
Status: current
状态：当前
Description:
说明：
This Information Element, which may have a variable length, carries a series of octets from the start of the IP payload of a sampled packet.
该信息元素可以具有可变长度，从采样数据包的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 size of the exported section may be constrained due to limitations in the IPFIX protocol.
由于IPFIX协议中的限制，导出节的大小可能会受到限制。
The data for this field MUST NOT be padded.
不得填充此字段的数据。
Abstract Data Type: octetArray
抽象数据类型：Octeraray
ElementId: 314
元素ID:314
Status: current
状态：当前
Description:
说明：
This Information Element, which may have a variable length, carries the first n octets from the MPLS label stack of a sampled packet.
该信息元素可以具有可变长度，携带来自采样分组的MPLS标签栈的前n个八位字节。
With sufficient length, this element also reports octets from the MPLS payload, subject to [RFC2804]. See the Security Considerations section.
在足够长的情况下，该元素还根据[RFC2804]报告来自MPLS负载的八位字节。请参阅安全注意事项部分。
See [RFC3031] for the specification of MPLS packets.
有关MPLS数据包的规范，请参见[RFC3031]。
See [RFC3032] for the specification of the MPLS label stack.
有关MPLS标签堆栈的规范，请参见[RFC3032]。
The size of the exported section may be constrained due to limitations in the IPFIX protocol.
由于IPFIX协议中的限制，导出节的大小可能会受到限制。
The data for this field MUST NOT be padded.
不得填充此字段的数据。
Abstract Data Type: octetArray
抽象数据类型：Octeraray
ElementId: 316
元素ID:316
Status: current
状态：当前
Description:
说明：
This Information Element, which may have a variable length, carries the first n octets from the MPLS payload of a sampled packet, being data that follows immediately after the MPLS label stack.
该信息元素可以具有可变长度，携带来自采样分组的MPLS有效载荷的前n个八位字节，即紧跟在MPLS标签栈之后的数据。
See [RFC3031] for the specification of MPLS packets.
有关MPLS数据包的规范，请参见[RFC3031]。
See [RFC3032] for the specification of the MPLS label stack.
有关MPLS标签堆栈的规范，请参见[RFC3032]。
The size of the exported section may be constrained due to limitations in the IPFIX protocol.
由于IPFIX协议中的限制，导出节的大小可能会受到限制。
The data for this field MUST NOT be padded.
不得填充此字段的数据。
Abstract Data Type: octetArray
抽象数据类型：Octeraray
ElementId: 317
元素ID:317
Status: current
状态：当前
Information Elements in this section can be used for reporting statistics from the Metering Process.
本节中的信息元素可用于报告计量过程中的统计信息。
+-----+----------------------------+-----+----------------------------+
| ID | Name | ID | Name |
+-----+----------------------------+-----+----------------------------+
| 318 | selectorIdTotalPktsObserved| 336 | upperCILimit |
| 319 | selectorIdTotalPktsSelected| 337 | lowerCILimit |
| 320 | absoluteError | 338 | confidenceLevel |
| 321 | relativeError | | |
+-----+----------------------------+-----+----------------------------+
+-----+----------------------------+-----+----------------------------+
| ID | Name | ID | Name |
+-----+----------------------------+-----+----------------------------+
| 318 | selectorIdTotalPktsObserved| 336 | upperCILimit |
| 319 | selectorIdTotalPktsSelected| 337 | lowerCILimit |
| 320 | absoluteError | 338 | confidenceLevel |
| 321 | relativeError | | |
+-----+----------------------------+-----+----------------------------+
Description:
说明：
This Information Element specifies the total number of packets observed by a Selector, for a specific value of SelectorId.
此信息元素指定选择器观察到的特定SelectorId值的数据包总数。
This Information Element should be used in an Options Template scoped to the observation to which it refers. See Section 3.4.2.1 of the IPFIX protocol document [RFC5101].
此信息元素应在一个选项模板中使用，该模板的作用域为它所引用的观测值。参见IPFIX协议文件[RFC5101]第3.4.2.1节。
Abstract Data Type: unsigned64
抽象数据类型：unsigned64
Data Type Semantics: totalCounter
数据类型语义：totalCounter
ElementId: 318
元素ID:318
Status: current
状态：当前
Units: packets
单位：小包
Description:
说明：
This Information Element specifies the total number of packets selected by a Selector, for a specific value of SelectorId.
此信息元素指定选择器为特定值SelectorId选择的数据包总数。
This Information Element should be used in an Options Template scoped to the observation to which it refers. See Section 3.4.2.1 of the IPFIX protocol document [RFC5101].
此信息元素应在一个选项模板中使用，该模板的作用域为它所引用的观测值。参见IPFIX协议文件[RFC5101]第3.4.2.1节。
Abstract Data Type: unsigned64
抽象数据类型：unsigned64
Data Type Semantics: totalCounter
数据类型语义：totalCounter
ElementId: 319
元素ID:319
Status: current
状态：当前
Units: packets
单位：小包
Description:
说明：
This Information Element specifies the maximum possible measurement error of the reported value for a given Information Element. The absoluteError has the same unit as the Information Element with which it is associated. The real value of the metric can differ by absoluteError (positive or negative) from the measured value.
此信息元素指定给定信息元素报告值的最大可能测量误差。绝对错误的单位与其关联的信息元素相同。度量的实际值可能与测量值存在绝对误差（正或负）。
This Information Element provides only the error for measured values. If an Information Element contains an estimated value (from Sampling), the confidence boundaries and confidence level have to be provided instead, using the upperCILimit, lowerCILimit, and confidenceLevel Information Elements.
此信息元素仅提供测量值的误差。如果信息元素包含估计值（来自采样），则必须使用上限、下限和置信水平信息元素提供置信边界和置信水平。
This Information Element should be used in an Options Template scoped to the observation to which it refers. See section 3.4.2.1 of the IPFIX protocol document [RFC5101].
此信息元素应在一个选项模板中使用，该模板的作用域为它所引用的观测值。参见IPFIX协议文件[RFC5101]第3.4.2.1节。
Abstract Data Type: float64
抽象数据类型：float64
Data Type Semantics: quantity
数据类型语义：数量
ElementId: 320
元素ID:320
Status: current
状态：当前
Units: The units of the Information Element for which the error is specified.
单位：为其指定错误的信息元素的单位。
Description:
说明：
This Information Element specifies the maximum possible positive or negative error ratio for the reported value for a given Information Element as a percentage of the measured value. The real value of the metric can differ by relativeError percent (positive or negative) from the measured value.
此信息元素指定给定信息元素报告值的最大可能正或负错误率（以测量值的百分比表示）。度量的实际值可能与测量值相差相对误差百分比（正或负）。
This Information Element provides only the error for measured values. If an Information Element contains an estimated value (from Sampling), the confidence boundaries and confidence level have to be provided instead, using the upperCILimit, lowerCILimit, and confidenceLevel Information Elements.
此信息元素仅提供测量值的误差。如果信息元素包含估计值（来自采样），则必须使用上限、下限和置信水平信息元素提供置信边界和置信水平。
This Information Element should be used in an Options Template scoped to the observation to which it refers. See Section 3.4.2.1 of the IPFIX protocol document [RFC5101].
此信息元素应在一个选项模板中使用，该模板的作用域为它所引用的观测值。参见IPFIX协议文件[RFC5101]第3.4.2.1节。
Abstract Data Type: float64
抽象数据类型：float64
Data Type Semantics: quantity
数据类型语义：数量
ElementId: 321
元素ID:321
Status: current
状态：当前
Description:
说明：
This Information Element specifies the upper limit of a confidence interval. It is used to provide an accuracy statement for an estimated value. The confidence limits define the range in which the real value is assumed to be with a certain probability p. Confidence limits always need to be associated with a confidence level that defines this probability p. Please note that a confidence interval only provides a probability that the real value lies within the limits. That means the real value can lie outside the confidence limits.
此信息元素指定置信区间的上限。它用于提供估计值的准确性声明。置信限定义了假设实际值具有一定概率p的范围。置信限始终需要与定义概率p的置信水平相关联。请注意，置信区间仅提供实际值在限制范围内的概率。这意味着实际价值可能超出置信限。
The upperCILimit, lowerCILimit, and confidenceLevel Information Elements should all be used in an Options Template scoped to the observation to which they refer. See Section 3.4.2.1 of the IPFIX protocol document [RFC5101].
上限、下限和信心级别信息元素都应在选项模板中使用，其作用域应与它们所引用的观察值相关。参见IPFIX协议文件[RFC5101]第3.4.2.1节。
Note that the upperCILimit, lowerCILimit, and confidenceLevel are all required to specify confidence, and should be disregarded unless all three are specified together.
请注意，上限、下限和信心级别都是指定信心所必需的，除非同时指定这三个，否则应忽略它们。
Abstract Data Type: float64
抽象数据类型：float64
Data Type Semantics: quantity
数据类型语义：数量
ElementId: 336
元素ID:336
Status: current
状态：当前
Description:
说明：
This Information Element specifies the lower limit of a confidence interval. For further information, see the description of upperCILimit.
此信息元素指定置信区间的下限。有关更多信息，请参阅upperCILimit的说明。
The upperCILimit, lowerCILimit, and confidenceLevel Information Elements should all be used in an Options Template scoped to the observation to which they refer. See Section 3.4.2.1 of the IPFIX protocol document [RFC5101].
上限、下限和信心级别信息元素都应在选项模板中使用，其作用域应与它们所引用的观察值相关。参见IPFIX协议文件[RFC5101]第3.4.2.1节。
Note that the upperCILimit, lowerCILimit, and confidenceLevel are all required to specify confidence, and should be disregarded unless all three are specified together.
请注意，上限、下限和信心级别都是指定信心所必需的，除非同时指定这三个，否则应忽略它们。
Abstract Data Type: float64
抽象数据类型：float64
Data Type Semantics: quantity
数据类型语义：数量
ElementId: 337
元素ID:337
Status: current
状态：当前
Description:
说明：
This Information Element specifies the confidence level. It is used to provide an accuracy statement for estimated values. The confidence level provides the probability p with which the real value lies within a given range. A confidence level always needs to be associated with confidence limits that define the range in which the real value is assumed to be.
此信息元素指定置信水平。它用于提供估计值的准确性声明。置信水平提供了实际值位于给定范围内的概率p。置信水平始终需要与定义实际值假设范围的置信限相关联。
The upperCILimit, lowerCILimit, and confidenceLevel Information Elements should all be used in an Options Template scoped to the observation to which they refer. See Section 3.4.2.1 of the IPFIX protocol document [RFC5101].
上限、下限和信心级别信息元素都应在选项模板中使用，其作用域应与它们所引用的观察值相关。参见IPFIX协议文件[RFC5101]第3.4.2.1节。
Note that the upperCILimit, lowerCILimit, and confidenceLevel are all required to specify confidence, and should be disregarded unless all three are specified together.
请注意，上限、下限和信心级别都是指定信心所必需的，除非同时指定这三个，否则应忽略它们。
Abstract Data Type: float64
抽象数据类型：float64
Data Type Semantics: quantity
数据类型语义：数量
ElementId: 338
元素ID:338
Status: current
状态：当前
The PSAMP information model itself does not directly introduce security issues. Rather, it defines a set of attributes that may for privacy or business issues be considered sensitive information.
PSAMP信息模型本身并不直接引入安全问题。相反，它定义了一组属性，对于隐私或业务问题，这些属性可能被视为敏感信息。
For example, exporting values of header fields may make attacks possible for the receiver of this information, which would otherwise only be possible for direct observers of the reported Flows along the data path. Specifically, the Information Elements pertaining to packet sections MUST target no more than the packet header, some subsequent bytes of the packet, and encapsulating headers if present. Full packet capture of arbitrary packet streams is explicitly out of scope, per [RFC2804].
例如，导出报头字段的值可能会使该信息的接收者有可能进行攻击，否则这只可能用于沿数据路径报告的流的直接观察者。具体地说，与包部分相关的信息元素的目标不能超过包头、包的一些后续字节和封装头（如果存在）。根据[RFC2804]，任意数据包流的完整数据包捕获明显超出范围。
The underlying protocol used to exchange the information described here MUST therefore apply appropriate procedures to guarantee the integrity and confidentiality of the exported information. Such procedures are defined in separate documents, specifically the IPFIX protocol document [RFC5101].
因此，用于交换此处所述信息的基础协议必须采用适当的程序来保证导出信息的完整性和机密性。这些程序在单独的文件中定义，特别是IPFIX协议文件[RFC5101]。
The PSAMP information model, as set out in this document, has two sets of assigned numbers. Considerations for assigning them are discussed in this section, using the example policies as set out in the "Guidelines for IANA Considerations" document [RFC5226].
如本文件所述，PSAMP信息模型有两组指定编号。本节将使用“IANA注意事项指南”文件[RFC5226]中规定的示例策略讨论分配注意事项。
As the PSAMP protocol uses the IPFIX protocol, refer to the IANA Considerations section in [RFC5102] for the assignments of numbers used in the protocol and for the numbers used in the information model.
由于PSAMP协议使用IPFIX协议，请参阅[RFC5102]中的IANA注意事项部分，了解协议中使用的编号分配和信息模型中使用的编号。
This document specifies an initial set of PSAMP Information Elements fulfilling the needs specified in [RFC5475], as an extension to the IPFIX Information Elements [RFC5102].
本文档指定了满足[RFC5475]中规定需求的初始PSAMP信息元素集，作为IPFIX信息元素[RFC5102]的扩展。
Note that the PSAMP Information Element IDs were initially started at value 301, in order to leave a gap for any ongoing IPFIX work requiring new Information Elements. It is expected that this gap in the Information Element numbering will be filled in by IANA with new IPFIX Information Elements.
请注意，PSAMP信息元素ID最初是在值301处启动的，以便为需要新信息元素的任何正在进行的IPFIX工作留出间隙。预计IANA将用新的IPFIX信息元素填补信息元素编号方面的空白。
Each new selection method MUST be assigned a unique value in the selectorAlgorithm registry. Its configuration parameter(s), along with the way to report them with an Options Template, MUST be clearly specified. The initial content of the selectorAlgorithm registry is found in Section 8.2.1.
必须在selectorAlgorithm注册表中为每个新的选择方法分配一个唯一的值。必须明确指定其配置参数以及使用选项模板报告这些参数的方法。selectorAlgorithm注册表的初始内容见第8.2.1节。
New assignments for the PSAMP selection method will be administered by IANA and are subject to Expert Review [RFC5226]. The group of experts must double check the Information Elements definitions with already defined Information Elements for completeness, accuracy, and redundancy. Those experts will initially be drawn from the Working Group Chairs and document editors of the IPFIX and PSAMP Working Groups. The selectorAlgorithm registry is maintained by IANA and can be updated as long as specifications of the new method(s) and any new Information Elements are provided.
PSAMP选择方法的新任务将由IANA管理，并接受专家评审[RFC5226]。专家组必须使用已定义的信息元素对信息元素定义进行双重检查，以确保其完整性、准确性和冗余性。这些专家最初将来自IPFIX和PSAMP工作组的工作组主席和文件编辑。selectorAlgorithm注册表由IANA维护，只要提供了新方法和任何新信息元素的规范，就可以对其进行更新。
[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月。
[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月。
[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月。
[RFC5475] Zseby, T., Molina, M., Duffield, D., Niccolini, S., and F. Rapall, "Sampling and Filtering Techniques for IP Packet Selection", RFC 5475, March 2009.
[RFC5475]Zseby，T.，Molina，M.，Duffield，D.，Niccolini，S.，和F.Rapall，“IP数据包选择的采样和过滤技术”，RFC 5475，2009年3月。
[RFC5476] Claise, B., Ed., "Packet Sampling (PSAMP) Protocol Specifications", RFC 5476, March 2009.
[RFC5476]Claise，B.，编辑，“数据包采样（PSAMP）协议规范”，RFC 54762009年3月。
[RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, September 1981.
[RFC0791]Postel，J.，“互联网协议”，STD 5，RFC 7911981年9月。
[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月。
[RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, June 1999.
[RFC2629]Rose，M.，“使用XML编写I-D和RFC”，RFC 26292999年6月。
[RFC2804] IAB and IESG, "IETF Policy on Wiretapping", RFC 2804, May 2000.
[RFC2804]IAB和IESG，“IETF关于窃听的政策”，RFC28042000年5月。
[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月。
[RFC5474] Duffield, N., Ed., "A Framework for Packet Selection and Reporting", RFC 5474, March 2009.
[RFC5474]Duffield，N.，Ed.“数据包选择和报告框架”，RFC 5474，2009年3月。
This appendix contains a formal description of the PSAMP information model XML document. Note that this appendix is of informational nature, while the text in Section 8 generated from this appendix is normative.
本附录包含PSAMP信息模型XML文档的正式描述。请注意，本附录为信息性附录，而第8节中由本附录生成的文本为规范性附录。
Using a formal and machine-readable syntax for the information model enables the creation of PSAMP-aware tools that can automatically adapt to extensions to the information model, by simply reading updated information model specifications.
为信息模型使用正式且机器可读的语法可以创建支持PSAMP的工具，这些工具可以通过读取更新的信息模型规范自动适应信息模型的扩展。
The wide availability of XML-aware tools and libraries for client devices is a primary consideration for this choice. In particular, libraries for parsing XML documents are readily available. Also, mechanisms such as the Extensible Stylesheet Language (XSL) allow for transforming a source XML document into other documents. This draft was authored in XML and transformed according to [RFC2629].
为客户机设备广泛提供支持XML的工具和库是这一选择的主要考虑因素。特别是，用于解析XML文档的库随时可用。此外，可扩展样式表语言（XSL）等机制允许将源XML文档转换为其他文档。该草案是用XML编写的，并根据[RFC2629]进行了转换。
It should be noted that the use of XML in Exporters, Collectors, or other tools is not mandatory for the deployment of PSAMP. In particular, exporting processes do not produce or consume XML as part of their operation. It is expected that PSAMP Collectors MAY take advantage of the machine readability of the information model vs. hardcoding their behavior or inventing proprietary means for accommodating extensions.
应该注意的是，在导出器、收集器或其他工具中使用XML对于PSAMP的部署不是强制性的。特别是，导出过程不会在其操作中生成或使用XML。预计PSAMP收集器可以利用信息模型的机器可读性，而不是硬编码其行为或发明专有方法来容纳扩展。
<?xml version="1.0" encoding="UTF-8"?>
<!--
This XML document is a product of the IETF IPFIX Working Group.
Contact information:
WG charter:
http://www.ietf.org/html.charters/ipfix-charter.html
<?xml version="1.0" encoding="UTF-8"?>
<!--
This XML document is a product of the IETF IPFIX Working Group.
Contact information:
WG charter:
http://www.ietf.org/html.charters/ipfix-charter.html
Mailing Lists:
General Discussion: ipfix@ietf.org
To Subscribe: http://www1.ietf.org/mailman/listinfo/ipfix
Archive:
http://www1.ietf.org/mail-archive/web/ipfix/current/index.html
Mailing Lists:
General Discussion: ipfix@ietf.org
To Subscribe: http://www1.ietf.org/mailman/listinfo/ipfix
Archive:
http://www1.ietf.org/mail-archive/web/ipfix/current/index.html
Editor: Thomas Dietz NEC Europe Ltd. NEC Laboratories Europe Network Research Division Kurfuersten-Anlage 36 Heidelberg 69115 Germany
编辑：Thomas Dietz NEC欧洲有限公司NEC实验室欧洲网络研究部Kurfuersten Anlage 36海德堡69115德国
Phone: +49 6221 4342-128
Email: Thomas.Dietz@nw.neclab.eu
Phone: +49 6221 4342-128
Email: Thomas.Dietz@nw.neclab.eu
Benoit Claise Cisco Systems, Inc. De Kleetlaan 6a b1 Degem 1813 Belgium Phone: +32 2 704 5622 Email: bclaise@cisco.com
Benoit Claise Cisco Systems，Inc.De Kleetlaan 6a b1 Degem 1813比利时电话：+32 2 704 5622电子邮件：bclaise@cisco.com
Paul Aitken Cisco Systems, Inc. 96 Commercial Quay Edinburgh EH6 6LX Scotland Phone: +44 131 561 3616 Email: paitken@cisco.com URI: http://www.cisco.com
Paul Aitken Cisco Systems，Inc.96商业码头爱丁堡EH6 6LX苏格兰电话：+44 131 561 3616电子邮件：paitken@cisco.comURI:http://www.cisco.com
Falko Dressler University of Erlangen-Nuremberg Dept. of Computer Sciences Martensstr. 3 Erlangen 91058 Germany Phone: +49 9131 85-27914 Email: dressler@informatik.uni-erlangen.de URI: http://www7.informatik.uni-erlangen.de/~dressler
埃朗根德雷斯勒福尔克大学纽伦堡分校计算机科学系。3 Erlangen 91058德国电话：+49 9131 85-27914电子邮件：dressler@informatik.uni-erlangen.de URI：http://www7.informatik.uni-erlangen.de/~z~德莱斯勒
Georg Carle
Technical University of Munich
Institute for Informatics
Boltzmannstr. 3
Garching bei Muenchen 85737
Germany
Phone: +49 89 289-18030
EMail: carle@in.tum.de
URI: http://www.net.in.tum.de/~carle/
Georg Carle
Technical University of Munich
Institute for Informatics
Boltzmannstr. 3
Garching bei Muenchen 85737
Germany
Phone: +49 89 289-18030
EMail: carle@in.tum.de
URI: http://www.net.in.tum.de/~carle/
Abstract: This memo defines an information model for the Packet SAMPling (PSAMP) protocol. It is used by the PSAMP protocol for encoding sampled packet data and information related to the Sampling process. As the PSAMP protocol is based on the IPFIX protocol, this information model is an extension to the IPFIX information model.
摘要：本备忘录定义了数据包采样（PSAMP）协议的信息模型。PSAMP协议使用它对采样包数据和与采样过程相关的信息进行编码。由于PSAMP协议基于IPFIX协议，因此此信息模型是IPFIX信息模型的扩展。
Copyright (c) 2009 IETF Trust and the persons identified as authors of the code. All rights reserved.
版权所有（c）2009 IETF信托基金和被确定为代码作者的人员。版权所有。
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
在满足以下条件的情况下，允许以源代码和二进制格式重新分发和使用，无论是否修改：
- Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
- 源代码的重新分发必须保留上述版权声明、此条件列表和以下免责声明。
- Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
- 以二进制形式重新分发时，必须在分发时提供的文档和/或其他材料中复制上述版权声明、本条件列表和以下免责声明。
- Neither the name of Internet Society, IETF or IETF Trust, nor the names of specific contributors, may be used to endorse or promote products derived from this software without specific prior written permission.
- 未经事先书面许可，不得使用互联网协会、IETF或IETF Trust的名称或特定贡献者的名称来认可或推广源自本软件的产品。
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 'AS IS' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
本软件由版权所有者和贡献者“按原样”提供，不承担任何明示或暗示的担保，包括但不限于适销性和特定用途适用性的暗示担保。在任何情况下，版权所有人或贡献者均不对任何直接、间接、偶然、特殊、惩戒性或后果性损害（包括但不限于替代商品或服务的采购；使用、数据或利润的损失；或业务中断）负责，无论是在合同中还是在任何责任理论下，严格责任，或因使用本软件而产生的侵权行为（包括疏忽或其他），即使告知可能发生此类损害。
This version of the XML document is part of RFC 5477;
see the RFC itself for full legal notices.
-->
<fieldDefinitions xmlns="urn:ietf:params:xml:ns:ipfix-info"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:ietf:params:xml:ns:ipfix-info
ipfix-info.xsd">
<field name="selectionSequenceId" dataType="unsigned64"
dataTypeSemantics="identifier" elementId="301" status="current"
group="identifiers">
<description>
<paragraph>
From all the packets observed at an Observation Point, a subset
of the packets is selected by a sequence of one or more
Selectors. The selectionSequenceId is a unique value per
Observation Domain, specifying the Observation Point and the
This version of the XML document is part of RFC 5477;
see the RFC itself for full legal notices.
-->
<fieldDefinitions xmlns="urn:ietf:params:xml:ns:ipfix-info"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:ietf:params:xml:ns:ipfix-info
ipfix-info.xsd">
<field name="selectionSequenceId" dataType="unsigned64"
dataTypeSemantics="identifier" elementId="301" status="current"
group="identifiers">
<description>
<paragraph>
From all the packets observed at an Observation Point, a subset
of the packets is selected by a sequence of one or more
Selectors. The selectionSequenceId is a unique value per
Observation Domain, specifying the Observation Point and the
sequence of Selectors through which the packets are selected.
</paragraph>
</description>
</field>
sequence of Selectors through which the packets are selected.
</paragraph>
</description>
</field>
<field name="selectorId" dataType="unsigned16"
dataTypeSemantics="identifier" elementId="302" status="current"
group="identifiers">
<description>
<paragraph>
The Selector ID is the unique ID identifying a Primitive
Selector. Each Primitive Selector must have a unique ID in the
Observation Domain.
</paragraph>
</description>
</field>
<field name="selectorId" dataType="unsigned16"
dataTypeSemantics="identifier" elementId="302" status="current"
group="identifiers">
<description>
<paragraph>
The Selector ID is the unique ID identifying a Primitive
Selector. Each Primitive Selector must have a unique ID in the
Observation Domain.
</paragraph>
</description>
</field>
<field name="informationElementId" dataType="unsigned16"
dataTypeSemantics="identifier" elementId="303" status="current"
group="identifiers">
<description>
<paragraph>
This Information Element contains the ID of another Information
Element.
</paragraph>
</description>
</field>
<field name="informationElementId" dataType="unsigned16"
dataTypeSemantics="identifier" elementId="303" status="current"
group="identifiers">
<description>
<paragraph>
This Information Element contains the ID of another Information
Element.
</paragraph>
</description>
</field>
<field name="selectorAlgorithm" dataType="unsigned16" dataTypeSemantics="identifier" elementId="304" status="current" group="sampling configuration"> <description> <paragraph> This Information Element identifies the packet selection methods (e.g., Filtering, Sampling) that are applied by the Selection Process.
<field name=“selectorAlgorithm”dataType=“unsigned16”dataTypeSemantics=“identifier”elementId=“304”status=“current”group=“sampling configuration”><description><paragration>此信息元素标识选择过程应用的数据包选择方法（例如过滤、采样）。
Most of these methods have parameters. Further Information Elements are needed to fully specify packet selection with these methods and all their parameters.
大多数方法都有参数。需要更多的信息元素来使用这些方法及其所有参数完全指定数据包选择。
The methods listed below are defined in [RFC5475]. For their parameters, Information Elements are defined in the information model document. The names of these Information Elements are listed for each method identifier.
[RFC5475]中定义了下列方法。对于其参数，信息元素在信息模型文档中定义。为每个方法标识符列出了这些信息元素的名称。
Further method identifiers may be added to the list below. It might be necessary to define new Information Elements to specify their parameters.
进一步的方法标识符可以添加到下面的列表中。可能需要定义新的信息元素来指定其参数。
The selectorAlgorithm registry is maintained by IANA. New assignments for the registry will be administered by IANA and are subject to Expert Review [RFC5226].
selectorAlgorithm注册表由IANA维护。注册处的新任务将由IANA管理，并接受专家审查[RFC5226]。
The registry can be updated when specifications of the new method(s) and any new Information Elements are provided.
当提供新方法的规范和任何新信息元素时，可以更新注册表。
The group of experts must double check the selectorAlgorithm definitions and Information Elements with already defined selectorAlgorithms and Information Elements for completeness, accuracy, and redundancy. Those experts will initially be drawn from the Working Group Chairs and document editors of the IPFIX and PSAMP Working Groups.
专家组必须使用已定义的selectorAlgorithm和信息元素对selectorAlgorithm定义和信息元素的完整性、准确性和冗余性进行双重检查。这些专家最初将来自IPFIX和PSAMP工作组的工作组主席和文件编辑。
The following packet selection methods identifiers are defined here:
此处定义了以下数据包选择方法标识符：
+----+------------------------+------------------------+
| ID | Method | Parameters |
+----+------------------------+------------------------+
| 1 | Systematic count-based | samplingPacketInterval |
| | Sampling | samplingPacketSpace |
+----+------------------------+------------------------+
| 2 | Systematic time-based | samplingTimeInterval |
| | Sampling | samplingTimeSpace |
+----+------------------------+------------------------+
| 3 | Random n-out-of-N | samplingSize |
| | Sampling | samplingPopulation |
+----+------------------------+------------------------+
| 4 | Uniform probabilistic | samplingProbability |
| | Sampling | |
+----+------------------------+------------------------+
| 5 | Property Match | no agreed parameters |
| | Filtering | |
+----+------------------------+------------------------+
| Hash-based Filtering | hashInitialiserValue |
+----+------------------------+ hashIPPayloadOffset |
| 6 | using BOB | hashIPPayloadSize |
+----+------------------------+ hashSelectedRangeMin |
| 7 | using IPSX | hashSelectedRangeMax |
+----+------------------------+ hashOutputRangeMin |
| 8 | using CRC | hashOutputRangeMax |
+----+------------------------+------------------------+
+----+------------------------+------------------------+
| ID | Method | Parameters |
+----+------------------------+------------------------+
| 1 | Systematic count-based | samplingPacketInterval |
| | Sampling | samplingPacketSpace |
+----+------------------------+------------------------+
| 2 | Systematic time-based | samplingTimeInterval |
| | Sampling | samplingTimeSpace |
+----+------------------------+------------------------+
| 3 | Random n-out-of-N | samplingSize |
| | Sampling | samplingPopulation |
+----+------------------------+------------------------+
| 4 | Uniform probabilistic | samplingProbability |
| | Sampling | |
+----+------------------------+------------------------+
| 5 | Property Match | no agreed parameters |
| | Filtering | |
+----+------------------------+------------------------+
| Hash-based Filtering | hashInitialiserValue |
+----+------------------------+ hashIPPayloadOffset |
| 6 | using BOB | hashIPPayloadSize |
+----+------------------------+ hashSelectedRangeMin |
| 7 | using IPSX | hashSelectedRangeMax |
+----+------------------------+ hashOutputRangeMin |
| 8 | using CRC | hashOutputRangeMax |
+----+------------------------+------------------------+
There is a broad variety of possible parameters that could be
used for Property Match Filtering (5), but currently there are
no agreed parameters specified.
</paragraph>
</description>
</field>
There is a broad variety of possible parameters that could be
used for Property Match Filtering (5), but currently there are
no agreed parameters specified.
</paragraph>
</description>
</field>
<field name="samplingPacketInterval" dataType="unsigned32" dataTypeSemantics="quantity" elementId="305" status="current" group="sampling configuration"> <description> <paragraph> This Information Element specifies the number of packets that are consecutively sampled. A value of 100 means that 100 consecutive packets are sampled.
<field name=“samplingPacketInterval”dataType=“unsigned32”dataTypeSemantics=“quantity”elementId=“305”status=“current”group=“sampling configuration”><description><paration>此信息元素指定连续采样的数据包数量。值100表示对100个连续数据包进行采样。
For example, this Information Element may be used to describe
the configuration of a systematic count-based Sampling Selector.
</paragraph>
</description>
<units>packets</units>
</field>
For example, this Information Element may be used to describe
the configuration of a systematic count-based Sampling Selector.
</paragraph>
</description>
<units>packets</units>
</field>
<field name="samplingPacketSpace" dataType="unsigned32" dataTypeSemantics="quantity" elementId="306" status="current" group="sampling configuration"> <description> <paragraph> This Information Element specifies the number of packets between two "samplingPacketInterval"s. A value of 100 means that the next interval starts 100 packets (which are not sampled) after the current "samplingPacketInterval" is over.
<field name=“samplingPacketSpace”dataType=“unsigned32”dataTypeSemantics=“quantity”elementId=“306”status=“current”group=“sampling configuration”><description><paration>此信息元素指定两个“samplingPacketInterval”之间的数据包数。值100表示当前“samplingPacketInterval”结束后，下一个间隔开始100个数据包（未采样）。
For example, this Information Element may be used to describe
the configuration of a systematic count-based Sampling Selector.
</paragraph>
</description>
<units>packets</units>
</field>
For example, this Information Element may be used to describe
the configuration of a systematic count-based Sampling Selector.
</paragraph>
</description>
<units>packets</units>
</field>
<field name="samplingTimeInterval" dataType="unsigned32" dataTypeSemantics="quantity" elementId="307" status="current" group="sampling configuration"> <description> <paragraph> This Information Element specifies the time interval in microseconds during which all arriving packets are sampled.
<field name=“samplingTimeInterval”dataType=“unsigned32”dataTypeSemantics=“quantity”elementId=“307”status=“current”group=“sampling configuration”><description><paration>此信息元素指定对所有到达的数据包进行采样的时间间隔（以微秒为单位）。
For example, this Information Element may be used to describe
the configuration of a systematic time-based Sampling Selector.
</paragraph>
</description>
<units>microseconds</units>
</field>
For example, this Information Element may be used to describe
the configuration of a systematic time-based Sampling Selector.
</paragraph>
</description>
<units>microseconds</units>
</field>
<field name="samplingTimeSpace" dataType="unsigned32" dataTypeSemantics="quantity" elementId="308" status="current" group="sampling configuration"> <description> <paragraph> This Information Element specifies the time interval in microseconds between two "samplingTimeInterval"s. A value of 100 means that the next interval starts 100 microseconds (during which no packets are sampled) after the current "samplingTimeInterval" is over.
<field name=“samplingTimeSpace”dataType=“unsigned32”dataTypeSemantics=“quantity”elementId=“308”status=“current”group=“sampling configuration”><description><paration>此信息元素指定两个“samplingTimeInterval”之间的时间间隔（以微秒为单位）。值100表示当前“samplingTimeInterval”结束后，下一个间隔开始100微秒（在此期间没有对数据包进行采样）。
For example, this Information Element may used to describe the
configuration of a systematic time-based Sampling Selector.
</paragraph>
</description>
<units>microseconds</units>
</field>
For example, this Information Element may used to describe the
configuration of a systematic time-based Sampling Selector.
</paragraph>
</description>
<units>microseconds</units>
</field>
<field name="samplingSize" dataType="unsigned32" dataTypeSemantics="quantity" elementId="309" status="current" group="sampling configuration"> <description> <paragraph> This Information Element specifies the number of elements taken from the parent Population for random Sampling methods.
<field name=“samplingSize”dataType=“unsigned32”dataTypeSemantics=“quantity”elementId=“309”status=“current”group=“sampling configuration”><description><paragration>此信息元素指定随机抽样方法从父总体中获取的元素数。
For example, this Information Element may be used to describe
the configuration of a random n-out-of-N Sampling Selector.
</paragraph>
</description>
<units>packets</units>
</field>
For example, this Information Element may be used to describe
the configuration of a random n-out-of-N Sampling Selector.
</paragraph>
</description>
<units>packets</units>
</field>
<field name="samplingPopulation" dataType="unsigned32" dataTypeSemantics="quantity" elementId="310" status="current" group="sampling configuration"> <description> <paragraph> This Information Element specifies the number of elements in the parent Population for random Sampling methods.
<field name=“samplingPopulation”dataType=“unsigned32”dataTypeSemantics=“quantity”elementId=“310”status=“current”group=“sampling configuration”><description><paration>此信息元素指定随机抽样方法的父总体中的元素数。
For example, this Information Element may be used to describe
the configuration of a random n-out-of-N Sampling Selector.
</paragraph>
</description>
<units>packets</units>
</field>
For example, this Information Element may be used to describe
the configuration of a random n-out-of-N Sampling Selector.
</paragraph>
</description>
<units>packets</units>
</field>
<field name="samplingProbability" dataType="float64" dataTypeSemantics="quantity" elementId="311" status="current" group="sampling configuration"> <description> <paragraph> This Information Element specifies the probability that a packet is sampled, expressed as a value between 0 and 1. The probability is equal for every packet. A value of 0 means no packet was sampled since the probability is 0.
<field name=“samplingProbability”dataType=“float64”dataTypeSemantics=“quantity”elementId=“311”status=“current”group=“sampling configuration”><description><paration>此信息元素指定对数据包进行采样的概率，表示为0到1之间的值。每个包的概率都是相等的。值为0表示没有对数据包进行采样，因为概率为0。
For example, this Information Element may be used to describe
the configuration of a uniform probabilistic Sampling Selector.
</paragraph>
</description>
</field>
For example, this Information Element may be used to describe
the configuration of a uniform probabilistic Sampling Selector.
</paragraph>
</description>
</field>
<field name="ipHeaderPacketSection" dataType="octetArray" elementId="313" status="current" group="packet data"> <description> <paragraph> This Information Element, which may have a variable length, carries a series of octets from the start of the IP header of a sampled packet.
<field name=“ipHeaderPacketSection”dataType=“octetaray”elementId=“313”status=“current”group=“packet data”><description><paration>此信息元素可能具有可变长度，从采样数据包的IP报头开始携带一系列八位字节。
With sufficient length, this element also reports octets from the IP payload, subject to [RFC2804]. See the Security Considerations section.
在足够长的情况下，该元素还根据[RFC2804]报告来自IP有效负载的八位字节。请参阅安全注意事项部分。
The size of the exported section may be constrained due to limitations in the IPFIX protocol.
由于IPFIX协议中的限制，导出节的大小可能会受到限制。
The data for this field MUST NOT be padded.
</paragraph>
</description>
</field>
The data for this field MUST NOT be padded.
</paragraph>
</description>
</field>
<field name="ipPayloadPacketSection" dataType="octetArray" elementId="314" status="current" group="packet data"> <description> <paragraph> This Information Element, which may have a variable length,
<field name=“ipPayloadPacketSection”dataType=“octetaray”elementId=“314”status=“current”group=“packet data”><description><paration>此信息元素可能具有可变长度，
carries a series of octets from the start of the IP payload of a sampled packet.
从采样数据包的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 size of the exported section may be constrained due to limitations in the IPFIX protocol.
由于IPFIX协议中的限制，导出节的大小可能会受到限制。
The data for this field MUST NOT be padded.
</paragraph>
</description>
</field>
The data for this field MUST NOT be padded.
</paragraph>
</description>
</field>
<field name="mplsLabelStackSection" dataType="octetArray" elementId="316" status="current" group="packet data"> <description> <paragraph> This Information Element, which may have a variable length, carries the first n octets from the MPLS label stack of a sampled packet.
<field name=“mplsLabelStackSection”dataType=“octetaray”elementId=“316”status=“current”group=“packet data”><description><paragration>此信息元素可能具有可变长度，携带采样数据包的MPLS标签堆栈中的前n个八位字节。
With sufficient length, this element also reports octets from the MPLS payload, subject to [RFC2804]. See the Security Considerations section.
在足够长的情况下，该元素还根据[RFC2804]报告来自MPLS负载的八位字节。请参阅安全注意事项部分。
See [RFC3031] for the specification of MPLS packets.
有关MPLS数据包的规范，请参见[RFC3031]。
See [RFC3032] for the specification of the MPLS label stack.
有关MPLS标签堆栈的规范，请参见[RFC3032]。
The size of the exported section may be constrained due to limitations in the IPFIX protocol.
由于IPFIX协议中的限制，导出节的大小可能会受到限制。
The data for this field MUST NOT be padded.
</paragraph>
</description>
</field>
The data for this field MUST NOT be padded.
</paragraph>
</description>
</field>
<field name="mplsPayloadPacketSection" dataType="octetArray"
elementId="317" status="current" group="packet data">
<description>
<field name="mplsPayloadPacketSection" dataType="octetArray"
elementId="317" status="current" group="packet data">
<description>
<paragraph> This Information Element, which may have a variable length, carries the first n octets from the MPLS payload of a sampled packet, being data that follows immediately after the MPLS label stack.
<段落>该信息元素可以具有可变长度，携带来自采样分组的MPLS有效载荷的前n个八位字节，即紧跟在MPLS标签堆栈之后的数据。
See [RFC3031] for the specification of MPLS packets.
有关MPLS数据包的规范，请参见[RFC3031]。
See [RFC3032] for the specification of the MPLS label stack.
有关MPLS标签堆栈的规范，请参见[RFC3032]。
The size of the exported section may be constrained due to limitations in the IPFIX protocol.
由于IPFIX协议中的限制，导出节的大小可能会受到限制。
The data for this field MUST NOT be padded.
</paragraph>
</description>
</field>
The data for this field MUST NOT be padded.
</paragraph>
</description>
</field>
<field name="selectorIdTotalPktsObserved" dataType="unsigned64" dataTypeSemantics="totalCounter" elementId="318" status="current" group="statistics"> <description> <paragraph> This Information Element specifies the total number of packets observed by a Selector, for a specific value of SelectorId.
<field name=“selectoridtotalpktsoberved”dataType=“unsigned64”dataTypeSemantics=“totalCounter”elementId=“318”status=“current”group=“statistics”><description><paragration>此信息元素指定选择器观察到的特定SelectorId值的数据包总数。
This Information Element should be used in an Options Template
scoped to the observation to which it refers.
See Section 3.4.2.1 of the IPFIX protocol document [RFC5101].
</paragraph>
</description>
<units>packets</units>
</field>
This Information Element should be used in an Options Template
scoped to the observation to which it refers.
See Section 3.4.2.1 of the IPFIX protocol document [RFC5101].
</paragraph>
</description>
<units>packets</units>
</field>
<field name="selectorIdTotalPktsSelected" dataType="unsigned64" dataTypeSemantics="totalCounter" elementId="319" status="current" group="statistics"> <description> <paragraph> This Information Element specifies the total number of packets selected by a Selector, for a specific value of SelectorId.
<field name=“selectoridtotalpktselected”dataType=“unsigned64”dataTypeSemantics=“totalCounter”elementId=“319”status=“current”group=“statistics”><description><paragration>此信息元素指定选择器为特定值SelectorId选择的数据包总数。
This Information Element should be used in an Options Template
scoped to the observation to which it refers.
See Section 3.4.2.1 of the IPFIX protocol document [RFC5101].
</paragraph>
</description>
<units>packets</units>
This Information Element should be used in an Options Template
scoped to the observation to which it refers.
See Section 3.4.2.1 of the IPFIX protocol document [RFC5101].
</paragraph>
</description>
<units>packets</units>
</field>
</field>
<field name="absoluteError" dataType="float64" dataTypeSemantics="quantity" elementId="320" status="current" group="statistics"> <description> <paragraph> This Information Element specifies the maximum possible measurement error of the reported value for a given Information Element. The absoluteError has the same unit as the Information Element with which it is associated. The real value of the metric can differ by absoluteError (positive or negative) from the measured value.
<field name=“absoluteError”dataType=“float64”dataTypeSemantics=“quantity”elementId=“320”status=“current”group=“statistics”><description><paragration>此信息元素指定给定信息元素报告值的最大可能测量误差。绝对错误的单位与其关联的信息元素相同。度量的实际值可能与测量值存在绝对误差（正或负）。
This Information Element provides only the error for measured values. If an Information Element contains an estimated value (from Sampling), the confidence boundaries and confidence level have to be provided instead, using the upperCILimit, lowerCILimit, and confidenceLevel Information Elements.
此信息元素仅提供测量值的误差。如果信息元素包含估计值（来自采样），则必须使用上限、下限和置信水平信息元素提供置信边界和置信水平。
This Information Element should be used in an Options Template
scoped to the observation to which it refers.
See Section 3.4.2.1 of the IPFIX protocol document [RFC5101].
</paragraph>
</description>
<units>
The units of the Information Element for which the error is
specified.
</units>
</field>
This Information Element should be used in an Options Template
scoped to the observation to which it refers.
See Section 3.4.2.1 of the IPFIX protocol document [RFC5101].
</paragraph>
</description>
<units>
The units of the Information Element for which the error is
specified.
</units>
</field>
<field name="relativeError" dataType="float64" dataTypeSemantics="quantity" elementId="321" status="current" group="statistics"> <description> <paragraph> This Information Element specifies the maximum possible positive or negative error ratio for the reported value for a given Information Element as a percentage of the measured value. The real value of the metric can differ by relativeError percent (positive or negative) from the measured value.
<field name=“relativeError”dataType=“float64”dataTypeSemantics=“quantity”elementId=“321”status=“current”group=“statistics”><description><paragration>此信息元素指定给定信息元素报告值的最大可能正或负错误率，作为测量值的百分比。度量的实际值可能与测量值相差相对误差百分比（正或负）。
This Information Element provides only the error for measured values. If an Information Element contains an estimated value (from Sampling), the confidence boundaries and confidence level have to be provided instead, using the upperCILimit, lowerCILimit, and confidenceLevel Information Elements.
此信息元素仅提供测量值的误差。如果信息元素包含估计值（来自采样），则必须使用上限、下限和置信水平信息元素提供置信边界和置信水平。
This Information Element should be used in an Options Template
scoped to the observation to which it refers.
See Section 3.4.2.1 of the IPFIX protocol document [RFC5101].
</paragraph>
</description>
</field>
This Information Element should be used in an Options Template
scoped to the observation to which it refers.
See Section 3.4.2.1 of the IPFIX protocol document [RFC5101].
</paragraph>
</description>
</field>
<field name="observationTimeSeconds" dataType="dateTimeSeconds"
dataTypeSemantics="quantity" elementId="322" status="current"
group="timestamps">
<description>
<paragraph>
This Information Element specifies the absolute time in seconds
of an observation.
</paragraph>
</description>
<units>seconds</units>
</field>
<field name="observationTimeSeconds" dataType="dateTimeSeconds"
dataTypeSemantics="quantity" elementId="322" status="current"
group="timestamps">
<description>
<paragraph>
This Information Element specifies the absolute time in seconds
of an observation.
</paragraph>
</description>
<units>seconds</units>
</field>
<field name="observationTimeMilliseconds"
dataType="dateTimeMilliseconds" dataTypeSemantics="quantity"
elementId="323" status="current" group="timestamps">
<description>
<paragraph>
This Information Element specifies the absolute time in
milliseconds of an observation.
</paragraph>
</description>
<units>milliseconds</units>
</field>
<field name="observationTimeMilliseconds"
dataType="dateTimeMilliseconds" dataTypeSemantics="quantity"
elementId="323" status="current" group="timestamps">
<description>
<paragraph>
This Information Element specifies the absolute time in
milliseconds of an observation.
</paragraph>
</description>
<units>milliseconds</units>
</field>
<field name="observationTimeMicroseconds"
dataType="dateTimeMicroseconds" dataTypeSemantics="quantity"
elementId="324" status="current" group="timestamps">
<description>
<paragraph>
This Information Element specifies the absolute time in
microseconds of an observation.
</paragraph>
</description>
<units>microseconds</units>
</field>
<field name="observationTimeMicroseconds"
dataType="dateTimeMicroseconds" dataTypeSemantics="quantity"
elementId="324" status="current" group="timestamps">
<description>
<paragraph>
This Information Element specifies the absolute time in
microseconds of an observation.
</paragraph>
</description>
<units>microseconds</units>
</field>
<field name="observationTimeNanoseconds"
dataType="dateTimeNanoseconds" dataTypeSemantics="quantity"
elementId="325" status="current" group="timestamps">
<description>
<paragraph>
<field name="observationTimeNanoseconds"
dataType="dateTimeNanoseconds" dataTypeSemantics="quantity"
elementId="325" status="current" group="timestamps">
<description>
<paragraph>
This Information Element specifies the absolute time in
nanoseconds of an observation.
</paragraph>
</description>
<units>nanoseconds</units>
</field>
This Information Element specifies the absolute time in
nanoseconds of an observation.
</paragraph>
</description>
<units>nanoseconds</units>
</field>
<field name="digestHashValue" dataType="unsigned64" dataTypeSemantics="quantity" elementId="326" status="current" group="hash configuration"> <description> <paragraph> This Information Element specifies the value from the digest hash function.
<field name=“digestHashValue”dataType=“unsigned64”dataTypeSemantics=“quantity”elementId=“326”status=“current”group=“hash configuration”><description><paragration>此信息元素指定摘要哈希函数的值。
See also Sections 6.2, 3.8, and 7.1 of
[RFC5475].
</paragraph>
</description>
</field>
See also Sections 6.2, 3.8, and 7.1 of
[RFC5475].
</paragraph>
</description>
</field>
<field name="hashIPPayloadOffset" dataType="unsigned64" dataTypeSemantics="quantity" elementId="327" status="current" group="hash configuration"> <description> <paragraph> This Information Element specifies the IP payload offset used by a Hash-based Selection Selector.
<field name=“hashIPPayloadOffset”dataType=“unsigned64”dataTypeSemantics=“quantity”elementId=“327”status=“current”group=“hash configuration”><description><paragration>此信息元素指定基于哈希的选择选择器使用的IP有效负载偏移量。
See also Sections 6.2, 3.8, and 7.1 of
[RFC5475].
</paragraph>
</description>
</field>
See also Sections 6.2, 3.8, and 7.1 of
[RFC5475].
</paragraph>
</description>
</field>
<field name="hashIPPayloadSize" dataType="unsigned64"
dataTypeSemantics="quantity" elementId="328" status="current"
group="hash configuration">
<description>
<paragraph>
This Information Element specifies the IP payload size used by a
Hash-based Selection Selector.
See also Sections 6.2, 3.8, and 7.1 of
[RFC5475]
</paragraph>
</description>
</field>
<field name="hashIPPayloadSize" dataType="unsigned64"
dataTypeSemantics="quantity" elementId="328" status="current"
group="hash configuration">
<description>
<paragraph>
This Information Element specifies the IP payload size used by a
Hash-based Selection Selector.
See also Sections 6.2, 3.8, and 7.1 of
[RFC5475]
</paragraph>
</description>
</field>
<field name="hashOutputRangeMin" dataType="unsigned64"
dataTypeSemantics="quantity" elementId="329" status="current"
group="hash configuration">
<description>
<paragraph>
This Information Element specifies the value for the beginning
of a hash function's potential output range.
See also Sections 6.2, 3.8, and 7.1 of
[RFC5475].
</paragraph>
</description>
</field>
<field name="hashOutputRangeMin" dataType="unsigned64"
dataTypeSemantics="quantity" elementId="329" status="current"
group="hash configuration">
<description>
<paragraph>
This Information Element specifies the value for the beginning
of a hash function's potential output range.
See also Sections 6.2, 3.8, and 7.1 of
[RFC5475].
</paragraph>
</description>
</field>
<field name="hashOutputRangeMax" dataType="unsigned64" dataTypeSemantics="quantity" elementId="330" status="current" group="hash configuration"> <description> <paragraph> This Information Element specifies the value for the end of a hash function's potential output range.
<field name=“hashOutputRangeMax”dataType=“unsigned64”dataTypeSemantics=“quantity”elementId=“330”status=“current”group=“hash configuration”><description><paragration>此信息元素指定哈希函数的潜在输出范围的结束值。
See also Sections 6.2, 3.8, and 7.1 of
[RFC5475].
</paragraph>
</description>
</field>
See also Sections 6.2, 3.8, and 7.1 of
[RFC5475].
</paragraph>
</description>
</field>
<field name="hashSelectedRangeMin" dataType="unsigned64" dataTypeSemantics="quantity" elementId="331" status="current" group="hash configuration"> <description> <paragraph> This Information Element specifies the value for the beginning of a hash function's selected range.
<field name=“hashSelectedRangeMin”dataType=“unsigned64”dataTypeSemantics=“quantity”elementId=“331”status=“current”group=“hash configuration”><description><paragration>此信息元素指定哈希函数所选范围开头的值。
See also Sections 6.2, 3.8, and 7.1 of
[RFC5475].
</paragraph>
</description>
</field>
See also Sections 6.2, 3.8, and 7.1 of
[RFC5475].
</paragraph>
</description>
</field>
<field name="hashSelectedRangeMax" dataType="unsigned64" dataTypeSemantics="quantity" elementId="332" status="current" group="hash configuration"> <description> <paragraph> This Information Element specifies the value for the end of a hash function's selected range.
<field name=“hashSelectedRangeMax”dataType=“unsigned64”dataTypeSemantics=“quantity”elementId=“332”status=“current”group=“hash configuration”><description><paragration>此信息元素指定哈希函数所选范围的结束值。
See also Sections 6.2, 3.8, and 7.1 of
[RFC5475].
</paragraph>
</description>
</field>
See also Sections 6.2, 3.8, and 7.1 of
[RFC5475].
</paragraph>
</description>
</field>
<field name="hashDigestOutput" dataType="boolean" dataTypeSemantics="quantity" elementId="333" status="current" group="hash configuration"> <description> <paragraph> This Information Element contains a boolean value that is TRUE if the output from this hash Selector has been configured to be included in the packet report as a packet digest, else FALSE.
<field name=“hashDigestOutput”dataType=“boolean”dataTypeSemantics=“quantity”elementId=“333”status=“current”group=“hash configuration”><description><paration>如果此哈希选择器的输出已配置为作为数据包摘要包含在数据包报告中，则此信息元素包含一个布尔值，否则就错了。
See also Sections 6.2, 3.8, and 7.1 of
[RFC5475].
</paragraph>
</description>
</field>
See also Sections 6.2, 3.8, and 7.1 of
[RFC5475].
</paragraph>
</description>
</field>
<field name="hashInitialiserValue" dataType="unsigned64" dataTypeSemantics="quantity" elementId="334" status="current" group="hash configuration"> <description> <paragraph> This Information Element specifies the initialiser value to the hash function.
<field name=“hashInitializerValue”dataType=“unsigned64”dataTypeSemantics=“quantity”elementId=“334”status=“current”group=“hash configuration”><description><paragration>此信息元素指定哈希函数的初始值。
See also Sections 6.2, 3.8, and 7.1 of
[RFC5475].
</paragraph>
</description>
</field>
See also Sections 6.2, 3.8, and 7.1 of
[RFC5475].
</paragraph>
</description>
</field>
<field name="upperCILimit" dataType="float64" dataTypeSemantics="quantity" elementId="336" status="current" group="statistics"> <description> <paragraph> This Information Element specifies the upper limit of a confidence interval. It is used to provide an accuracy statement for an estimated value. The confidence limits define the range in which the real value is assumed to be with a certain probability p. Confidence limits always need to be associated with a confidence level that defines this probability p. Please note that a confidence interval only provides a probability that the real value lies within the
<field name=“upperCILimit”dataType=“float64”dataTypeSemantics=“quantity”elementId=“336”status=“current”group=“statistics”><description><paragration>此信息元素指定置信区间的上限。它用于提供估计值的准确性声明。置信限定义了假设实际值具有一定概率p的范围。置信限始终需要与定义概率p的置信水平相关联。请注意，置信区间仅提供实际值位于
limits. That means the real value can lie outside the confidence limits.
限制。这意味着实际价值可能超出置信限。
The upperCILimit, lowerCILimit, and confidenceLevel Information Elements should all be used in an Options Template scoped to the observation to which they refer. See Section 3.4.2.1 of the IPFIX protocol document [RFC5101].
上限、下限和信心级别信息元素都应在选项模板中使用，其作用域应与它们所引用的观察值相关。参见IPFIX协议文件[RFC5101]第3.4.2.1节。
Note that the upperCILimit, lowerCILimit, and confidenceLevel
are all required to specify confidence, and should be
disregarded unless all three are specified together.
</paragraph>
</description>
</field>
Note that the upperCILimit, lowerCILimit, and confidenceLevel
are all required to specify confidence, and should be
disregarded unless all three are specified together.
</paragraph>
</description>
</field>
<field name="lowerCILimit" dataType="float64" dataTypeSemantics="quantity" elementId="337" status="current" group="statistics"> <description> <paragraph> This Information Element specifies the lower limit of a confidence interval. For further information, see the description of upperCILimit.
<field name=“lowercimit”dataType=“float64”dataTypeSemantics=“quantity”elementId=“337”status=“current”group=“statistics”><description><paragration>此信息元素指定置信区间的下限。有关更多信息，请参阅upperCILimit的说明。
The upperCILimit, lowerCILimit, and confidenceLevel Information Elements should all be used in an Options Template scoped to the observation to which they refer. See Section 3.4.2.1 of the IPFIX protocol document [RFC5101].
上限、下限和信心级别信息元素都应在选项模板中使用，其作用域应与它们所引用的观察值相关。参见IPFIX协议文件[RFC5101]第3.4.2.1节。
Note that the upperCILimit, lowerCILimit, and confidenceLevel
are all required to specify confidence, and should be
disregarded unless all three are specified together.
</paragraph>
</description>
</field>
Note that the upperCILimit, lowerCILimit, and confidenceLevel
are all required to specify confidence, and should be
disregarded unless all three are specified together.
</paragraph>
</description>
</field>
<field name="confidenceLevel" dataType="float64" dataTypeSemantics="quantity" elementId="338" status="current" group="statistics"> <description> <paragraph> This Information Element specifies the confidence level. It is used to provide an accuracy statement for estimated values. The confidence level provides the probability p with which the real value lies within a given range. A confidence level always needs to be associated with confidence limits that define the range in which the real value is assumed to be.
<field name=“confidenceLevel”dataType=“float64”dataTypeSemantics=“quantity”elementId=“338”status=“current”group=“statistics”><description><paragration>此信息元素指定置信度。它用于提供估计值的准确性声明。置信水平提供了实际值位于给定范围内的概率p。置信水平始终需要与定义实际值假设范围的置信限相关联。
The upperCILimit, lowerCILimit, and confidenceLevel Information Elements should all be used in an Options Template scoped to the observation to which they refer. See Section 3.4.2.1 of the IPFIX protocol document [RFC5101].
上限、下限和信心级别信息元素都应在选项模板中使用，其作用域应与它们所引用的观察值相关。参见IPFIX协议文件[RFC5101]第3.4.2.1节。
Note that the upperCILimit, lowerCILimit, and confidenceLevel
are all required to specify confidence, and should be
disregarded unless all three are specified together.
</paragraph>
</description>
</field>
Note that the upperCILimit, lowerCILimit, and confidenceLevel
are all required to specify confidence, and should be
disregarded unless all three are specified together.
</paragraph>
</description>
</field>
</fieldDefinitions>
</fieldDefinitions>
Authors' Addresses
作者地址
Thomas Dietz NEC Europe Ltd. NEC Laboratories Europe Network Research Division Kurfuersten-Anlage 36 Heidelberg 69115 Germany
Thomas Dietz NEC欧洲有限公司NEC实验室欧洲网络研究部Kurfuersten Anlage 36海德堡69115德国
Phone: +49 6221 4342-128
EMail: Thomas.Dietz@nw.neclab.eu
URI: http://www.nw.neclab.eu
Phone: +49 6221 4342-128
EMail: Thomas.Dietz@nw.neclab.eu
URI: http://www.nw.neclab.eu
Benoit Claise Cisco Systems, Inc. De Kleetlaan 6a b1 Degem 1813 Belgium
Benoit Claise Cisco Systems，Inc.De Kleetlaan 6a b1 Degem 1813比利时
Phone: +32 2 704 5622
EMail: bclaise@cisco.com
Phone: +32 2 704 5622
EMail: bclaise@cisco.com
Paul Aitken Cisco Systems, Inc. 96 Commercial Quay Edinburgh EH6 6LX Scotland
Paul Aitken Cisco Systems，Inc.96爱丁堡商业码头EH6 6LX苏格兰
Phone: +44 131 561 3616
EMail: paitken@cisco.com
URI: http://www.cisco.com/
Phone: +44 131 561 3616
EMail: paitken@cisco.com
URI: http://www.cisco.com/
Falko Dressler University of Erlangen-Nuremberg Dept. of Computer Sciences Martensstr. 3 Erlangen 91058 Germany
埃朗根德雷斯勒福尔克大学纽伦堡分校计算机科学系。3爱尔兰根91058德国
Phone: +49 9131 85-27914
EMail: dressler@informatik.uni-erlangen.de
URI: http://www7.informatik.uni-erlangen.de/~dressler
Phone: +49 9131 85-27914
EMail: dressler@informatik.uni-erlangen.de
URI: http://www7.informatik.uni-erlangen.de/~dressler
Georg Carle Technical University of Munich Institute for Informatics Boltzmannstr. 3 Garching bei Muenchen 85737 Germany
格奥尔.卡尔慕尼黑工业大学信息学院博尔曼曼斯特。3加兴北慕尼黑85737德国
Phone: +49 89 289-18030
EMail: carle@in.tum.de
URI: http://www.net.in.tum.de/~carle/
Phone: +49 89 289-18030
EMail: carle@in.tum.de
URI: http://www.net.in.tum.de/~carle/