Network Working Group B. Claise, Ed.
Request for Comments: 5476 A. Johnson
Category: Standards Track Cisco Systems, Inc.
J. Quittek
NEC Europe Ltd.
March 2009
Network Working Group B. Claise, Ed.
Request for Comments: 5476 A. Johnson
Category: Standards Track Cisco Systems, Inc.
J. Quittek
NEC Europe Ltd.
March 2009
Packet Sampling (PSAMP) Protocol Specifications
数据包采样（PSAMP）协议规范
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 document specifies the export of packet information from a Packet SAMPling (PSAMP) Exporting Process to a PSAMP Collecting Process. For export of packet information, the IP Flow Information eXport (IPFIX) protocol is used, as both the IPFIX and PSAMP architecture match very well, and the means provided by the IPFIX protocol are sufficient. The document specifies in detail how the IPFIX protocol is used for PSAMP export of packet information.
本文档指定将数据包信息从数据包采样（PSAMP）导出过程导出到PSAMP收集过程。对于数据包信息的导出，使用IP流信息导出（IPFIX）协议，因为IPFIX和PSAMP体系结构非常匹配，并且IPFIX协议提供的手段足够。本文档详细说明了IPFIX协议如何用于数据包信息的PSAMP导出。
Table of Contents
目录
1. Introduction ....................................................3
1.1. Conventions Used in This Document ..........................3
2. PSAMP Documents Overview ........................................4
3. Terminology .....................................................4
3.1. IPFIX Terminology ..........................................4
3.2. PSAMP Terminology ..........................................5
3.2.1. Packet Streams and Packet Content ...................5
3.2.2. Selection Process ...................................6
3.2.3. Reporting ...........................................7
3.2.4. Metering Process ....................................8
3.2.5. Exporting Process ...................................8
3.2.6. PSAMP Device ........................................8
3.2.7. Collector ...........................................8
3.2.8. Selection Methods ...................................9
3.3. IPFIX and PSAMP Terminology Comparison ....................11
3.3.1. IPFIX and PSAMP Processes ..........................11
3.3.2. Packet Report, Packet Interpretation, and
Data Record ........................................12
4. Differences between PSAMP and IPFIX ............................12
4.1. Architecture Point of View ................................12
4.2. Protocol Point of View ....................................14
4.3. Information Model Point of View ...........................14
5. PSAMP Requirements versus the IPFIX Solution ...................14
5.1. High-Level View of the Integration ........................15
6. Using the IPFIX Protocol for PSAMP .............................16
6.1. Selector ID ...............................................17
6.2. The Selection Sequence ID .................................17
6.3. The Exporting Process .....................................17
6.4. Packet Report .............................................17
6.4.1. Basic Packet Report ................................17
6.4.2. Extended Packet Report .............................21
6.5. Report Interpretation .....................................22
6.5.1. Selection Sequence Report Interpretation ...........23
6.5.2. Selector Report Interpretation .....................25
6.5.2.1. Systematic Count-Based Sampling ...........25
6.5.2.2. Systematic Time-Based Sampling ............27
1. Introduction ....................................................3
1.1. Conventions Used in This Document ..........................3
2. PSAMP Documents Overview ........................................4
3. Terminology .....................................................4
3.1. IPFIX Terminology ..........................................4
3.2. PSAMP Terminology ..........................................5
3.2.1. Packet Streams and Packet Content ...................5
3.2.2. Selection Process ...................................6
3.2.3. Reporting ...........................................7
3.2.4. Metering Process ....................................8
3.2.5. Exporting Process ...................................8
3.2.6. PSAMP Device ........................................8
3.2.7. Collector ...........................................8
3.2.8. Selection Methods ...................................9
3.3. IPFIX and PSAMP Terminology Comparison ....................11
3.3.1. IPFIX and PSAMP Processes ..........................11
3.3.2. Packet Report, Packet Interpretation, and
Data Record ........................................12
4. Differences between PSAMP and IPFIX ............................12
4.1. Architecture Point of View ................................12
4.2. Protocol Point of View ....................................14
4.3. Information Model Point of View ...........................14
5. PSAMP Requirements versus the IPFIX Solution ...................14
5.1. High-Level View of the Integration ........................15
6. Using the IPFIX Protocol for PSAMP .............................16
6.1. Selector ID ...............................................17
6.2. The Selection Sequence ID .................................17
6.3. The Exporting Process .....................................17
6.4. Packet Report .............................................17
6.4.1. Basic Packet Report ................................17
6.4.2. Extended Packet Report .............................21
6.5. Report Interpretation .....................................22
6.5.1. Selection Sequence Report Interpretation ...........23
6.5.2. Selector Report Interpretation .....................25
6.5.2.1. Systematic Count-Based Sampling ...........25
6.5.2.2. Systematic Time-Based Sampling ............27
6.5.2.3. Random n-out-of-N Sampling ................28
6.5.2.4. Uniform Probabilistic Sampling ............29
6.5.2.5. Property Match Filtering ..................31
6.5.2.6. Hash-Based Filtering ......................33
6.5.2.7. Other Selection Methods ...................36
6.5.3. Selection Sequence Statistics Report
Interpretation .....................................37
6.5.4. Accuracy Report Interpretation .....................39
7. Security Considerations ........................................43
8. IANA Considerations ............................................43
8.1. IPFIX-Related Considerations ..............................43
8.2. PSAMP-Related Considerations ..............................43
9. References .....................................................44
9.1. Normative References ......................................44
9.2. Informative References ....................................44
10. Acknowledgments ...............................................45
6.5.2.3. Random n-out-of-N Sampling ................28
6.5.2.4. Uniform Probabilistic Sampling ............29
6.5.2.5. Property Match Filtering ..................31
6.5.2.6. Hash-Based Filtering ......................33
6.5.2.7. Other Selection Methods ...................36
6.5.3. Selection Sequence Statistics Report
Interpretation .....................................37
6.5.4. Accuracy Report Interpretation .....................39
7. Security Considerations ........................................43
8. IANA Considerations ............................................43
8.1. IPFIX-Related Considerations ..............................43
8.2. PSAMP-Related Considerations ..............................43
9. References .....................................................44
9.1. Normative References ......................................44
9.2. Informative References ....................................44
10. Acknowledgments ...............................................45
The name PSAMP is a contraction of the phrase "Packet Sampling". The word "Sampling" captures the idea that only a subset of all packets passing a network element will be selected for reporting. PSAMP selection operations include random selection, deterministic selection, and deterministic approximations to random selection (Hash-based Selection).
PSAMP的名称是短语“数据包采样”的缩写。“采样”一词抓住了这样一个概念，即只有通过网元的所有数据包的子集才会被选择用于报告。PSAMP选择操作包括随机选择、确定性选择和随机选择的确定性近似（基于散列的选择）。
The IP Flow Information eXport (IPFIX) protocol specified in [RFC5101] exports IP traffic information [RFC5102] observed at network devices. This matches the general protocol requirements outlined in the PSAMP framework [RFC5474]. However, there are some architectural differences between IPFIX and PSAMP in the requirements for an export protocol. While the IPFIX architecture [RFC5470] is focused on gathering and exporting IP traffic flow information, the focus of the PSAMP framework [RFC5474] is on exporting information on individual packets. This basic difference and a set of derived differences in protocol requirements are outlined in Section 4. Despite these differences, the IPFIX protocol is well suited for the PSAMP protocol. Section 5 specifies how the IPFIX protocol is used for the export of packet samples. Required extensions of the IPFIX information model are specified in the PSAMP information model [RFC5477].
[RFC5101]中指定的IP流量信息导出（IPFIX）协议导出在网络设备上观察到的IP流量信息[RFC5102]。这符合PSAMP框架[RFC5474]中概述的一般协议要求。然而，在导出协议的要求方面，IPFIX和PSAMP之间存在一些架构上的差异。IPFIX体系结构[RFC5470]的重点是收集和导出IP流量信息，而PSAMP框架[RFC5474]的重点是导出单个数据包的信息。第4节概述了协议要求中的这一基本差异和一系列衍生差异。尽管存在这些差异，IPFIX协议仍然非常适合PSAMP协议。第5节指定如何使用IPFIX协议导出数据包样本。PSAMP信息模型[RFC5477]中规定了IPFIX信息模型所需的扩展。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[RFC2119]中所述进行解释。
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支持的数据包选择技术集。
RFC 5476 (this document): "Packet Sampling (PSAMP) Protocol Specifications" specifies the export of packet information from a PSAMP Exporting Process to a PSAMP Collecting Process.
RFC 5476（本文档）：“数据包采样（PSAMP）协议规范”指定将数据包信息从PSAMP导出过程导出到PSAMP收集过程。
[RFC5477]: "Information Model for Packet Sampling Exports" defines an information and data model for PSAMP.
[RFC5477]：“数据包采样导出的信息模型”定义了PSAMP的信息和数据模型。
As the IPFIX export protocol is used to export the PSAMP information, the relevant IPFIX terminology from [RFC5101] is copied over in this document. All terms defined in this section have their first letter capitalized when used in this document. The terminology summary table in Section 3.1 gives a quick overview of the relationships between the different IPFIX terms. The PSAMP terminology defined here is fully consistent with all terms listed in [RFC5475] and [RFC5474], but only definitions that are relevant to the PSAMP protocol appear here. Section 3.3 applies the PSAMP terminology to the IPFIX protocol terminology.
由于IPFIX导出协议用于导出PSAMP信息，本文档中复制了[RFC5101]中的相关IPFIX术语。本节中定义的所有术语在本文件中使用时，其首字母大写。第3.1节中的术语汇总表快速概述了不同IPFIX术语之间的关系。此处定义的PSAMP术语与[RFC5475]和[RFC5474]中列出的所有术语完全一致，但此处仅显示与PSAMP协议相关的定义。第3.3节将PSAMP术语应用于IPFIX协议术语。
IPFIX-specific terminology used in this document is defined in Section 2 of [RFC5101]. The only exceptions are the Metering Process, Exporting Process, and the Collector terms, which are defined more precisely in the PSAMP terminology section. In this document, as in [RFC5101], the first letter of each IPFIX-specific term is capitalized.
[RFC5101]第2节定义了本文件中使用的IPFIX专用术语。唯一的例外是计量过程、导出过程和收集器术语，它们在PSAMP术语部分中有更精确的定义。在本文件中，与[RFC5101]中一样，每个IPFIX特定术语的首字母大写。
+------------------+---------------------------------------------+
| | contents |
| +--------------------+------------------------+
| Set | Template | record |
+------------------+--------------------+------------------------+
| Data Set | / | Data Record(s) |
+------------------+--------------------+------------------------+
| Template Set | Template Record(s) | / |
+------------------+--------------------+------------------------+
| Options Template | Options Template | / |
| Set | Record(s) | |
+------------------+--------------------+------------------------+
+------------------+---------------------------------------------+
| | contents |
| +--------------------+------------------------+
| Set | Template | record |
+------------------+--------------------+------------------------+
| Data Set | / | Data Record(s) |
+------------------+--------------------+------------------------+
| Template Set | Template Record(s) | / |
+------------------+--------------------+------------------------+
| Options Template | Options Template | / |
| Set | Record(s) | |
+------------------+--------------------+------------------------+
Figure A: Terminology Summary Table
图A：术语汇总表
The PSAMP terminology section has been copied from [RFC5475].
PSAMP术语部分已从[RFC5475]复制。
* Observed Packet Stream
* 观测数据包流
The Observed Packet Stream is the set of all packets observed at the Observation Point.
观察到的分组流是在观察点处观察到的所有分组的集合。
* Packet Stream
* 包流
A Packet Stream denotes a set of packets from the Observed Packet Stream that flows past some specified point within the Metering Process. An example of a Packet Stream is the output of the Selection Process. Note that packets selected from a stream, e.g., by Sampling, do not necessarily possess a property by which they can be distinguished from packets that have not been selected. For this reason, the term "stream" is favored over "flow", which is defined as a set of packets with common properties [RFC3917].
数据包流表示来自观测数据包流的一组数据包，这些数据包流经过计量过程中的某个指定点。分组流的一个示例是选择过程的输出。注意，例如通过采样从流中选择的分组不一定具有可通过其与未选择的分组区分的属性。因此，术语“流”优于“流”，后者被定义为具有公共属性的一组数据包[RFC3917]。
* Packet Content
* 数据包内容
The Packet Content denotes the union of the packet header (which includes link layer, network layer, and other encapsulation headers) and the packet payload. Note that, depending on the Observation Point, the link layer information might not be available.
分组内容表示分组报头（包括链路层、网络层和其他封装报头）和分组有效载荷的联合。请注意，根据观测点的不同，链路层信息可能不可用。
* Selection Process
* 选择过程
A Selection Process takes the Observed Packet Stream as its input and selects a subset of that stream as its output.
选择过程将观察到的分组流作为其输入，并选择该流的子集作为其输出。
* Selection State
* 选择状态
A Selection Process may maintain state information for use by the Selection Process. At a given time, the Selection State may depend on packets observed at and before that time, and other variables. Examples include:
选择过程可以维护状态信息以供选择过程使用。在给定时间，选择状态可能取决于在该时间和之前观察到的数据包以及其他变量。例子包括：
(i) sequence numbers of packets at the input of Selectors;
(i) 选择器输入端的数据包序列号；
(ii) a timestamp of observation of the packet at the Observation Point;
（ii）在观察点观察分组的时间戳；
(iii) iterators for pseudorandom number generators;
（iii）伪随机数生成器的迭代器；
(iv) hash values calculated during selection;
（iv）选择期间计算的哈希值；
(v) indicators of whether the packet was selected by a given Selector.
(v) 指示数据包是否由给定选择器选择的指示器。
Selection Processes may change portions of the Selection State as a result of processing a packet. Selection state for a packet is to reflect the state after processing the packet.
选择过程可作为处理分组的结果而改变选择状态的部分。数据包的选择状态反映处理数据包后的状态。
* Selector
* 选择器
A Selector defines the action of a Selection Process on a single packet of its input. If selected, the packet becomes an element of the output Packet Stream.
选择器定义选择过程对其输入的单个数据包的操作。如果选择，则数据包成为输出数据包流的一个元素。
The Selector can make use of the following information in determining whether a packet is selected:
选择器可以利用以下信息来确定是否选择了分组：
(i) the Packet Content;
(i) 分组内容；
(ii) information derived from the packet's treatment at the Observation Point;
（ii）从观察点的数据包处理中获得的信息；
(iii) any selection state that may be maintained by the Selection Process.
（iii）选择过程可能维持的任何选择状态。
* Composite Selector
* 复合选择器
A Composite Selector is an ordered composition of Selectors, in which the output Packet Stream issuing from one Selector forms the input Packet Stream to the succeeding Selector.
复合选择器是选择器的有序组合，其中从一个选择器发出的输出数据包流形成到后续选择器的输入数据包流。
* Primitive Selector
* 基本选择器
A Selector is primitive if it is not a Composite Selector.
如果选择器不是复合选择器，则它是基本选择器。
* Selector ID
* 选择器ID
The Selector ID is the unique ID identifying a Primitive Selector. The ID is unique within the Observation Domain.
选择器ID是标识基元选择器的唯一ID。ID在观察域中是唯一的。
* Selection Sequence
* 选择序列
From all the packets observed at an Observation Point, only a few packets are selected by one or more Selectors. The Selection Sequence is a unique value per Observation Domain describing the Observation Point and the Selector IDs through which the packets are selected.
从一个观察点观察到的所有数据包中，只有少数数据包被一个或多个选择器选择。选择序列是每个观察域的唯一值，用于描述观察点和选择数据包的选择器ID。
* Packet Reports
* 数据包报告
Packet Reports comprise a configurable subset of a packet's input to the Selection Process, including the Packet Content, information relating to its treatment (for example, the output interface), and its associated selection state (for example, a hash of the Packet Content).
分组报告包括分组对选择过程的输入的可配置子集，包括分组内容、与其处理相关的信息（例如，输出接口）及其关联的选择状态（例如，分组内容的散列）。
* Report Interpretation
* 报告解释
Report Interpretation comprises subsidiary information, relating to one or more packets, that is used for interpretation of their Packet Reports. Examples include configuration parameters of the Selection Process.
报告解释包括用于解释其数据包报告的与一个或多个数据包相关的辅助信息。示例包括选择过程的配置参数。
* Report Stream
* 报告流
The Report Stream is the output of a Metering Process, comprising two distinguished types of information: Packet Reports and Report Interpretation.
报告流是计量过程的输出，包括两种不同类型的信息：数据包报告和报告解释。
* Metering Process
* 计量过程
A Metering Process selects packets from the Observed Packet Stream using a Selection Process, and produces as output a Report Stream concerning the selected packets.
计量处理使用选择处理从观察到的分组流中选择分组，并产生关于所选分组的报告流作为输出。
The PSAMP Metering Process can be viewed as analogous to the IPFIX Metering Process [RFC5101], which produces Flow Records as its output, with the difference that the PSAMP Metering Process always contains a Selection Process. The relationship between PSAMP and IPFIX is further described in [RFC5477] and [RFC5474].
PSAMP计量过程可被视为类似于IPFIX计量过程[RFC5101]，该过程产生流量记录作为其输出，不同之处在于PSAMP计量过程始终包含一个选择过程。[RFC5477]和[RFC5474]中进一步描述了PSAMP和IPFIX之间的关系。
* Exporting Process
* 导出过程
An Exporting Process sends, in the form of Export Packets, the output of one or more Metering Processes to one or more Collectors.
导出过程以导出包的形式将一个或多个计量过程的输出发送到一个或多个收集器。
* Export Packet
* 导出包
An Export Packet is a combination of Report Interpretation(s) and/or one or more Packet Reports that are bundled by the Exporting Process into an Export Packet for exporting to a Collector.
导出数据包是报告解释和/或一个或多个数据包报告的组合，这些报告由导出过程捆绑到导出数据包中，以导出到收集器。
* PSAMP Device
* PSAMP装置
A PSAMP Device is a device hosting at least an Observation Point, a Selection Process, and an Exporting Process. Typically, corresponding Observation Point(s), Selection Process(es), and Exporting Process(es) are co-located at this device, for example, at a router.
PSAMP设备是至少承载观察点、选择过程和导出过程的设备。通常，相应的观察点、选择过程和导出过程共同位于该设备上，例如路由器上。
* Collector
* 收藏家
A Collector receives a Report Stream exported by one or more Exporting Processes. In some cases, the host of the Metering and/or Exporting Processes may also serve as the Collector.
收集器接收由一个或多个导出进程导出的报告流。在某些情况下，计量和/或导出过程的主机也可以用作收集器。
* Filtering
* 过滤
A filter is a Selector that selects a packet deterministically based on the Packet Content, or its treatment, or functions of these occurring in the Selection State. Two examples are:
过滤器是一个选择器，它基于包内容或其处理或选择状态中出现的这些内容或处理的功能来确定地选择包。两个例子是：
(i) Property Match Filtering: A packet is selected if a specific field in the packet equals a predefined value.
(i) 属性匹配筛选：如果数据包中的特定字段等于预定义值，则选择数据包。
(ii) Hash-based Selection: A Hash Function is applied to the Packet Content, and the packet is selected if the result falls in a specified range.
（ii）基于散列的选择：对数据包内容应用散列函数，如果结果在指定范围内，则选择数据包。
* Sampling
* 取样
A Selector that is not a filter is called a Sampling operation. This reflects the intuitive notion that if the selection of a packet cannot be determined from its content alone, there must be some type of Sampling taking place.
不是过滤器的选择器称为采样操作。这反映了一个直观的概念，即如果不能仅从数据包的内容来确定数据包的选择，则必须进行某种类型的采样。
* Content-Independent Sampling
* 内容无关抽样
A Sampling operation that does not use Packet Content (or quantities derived from it) as the basis for selection is called a Content-independent Sampling operation. Examples include systematic Sampling, and uniform pseudorandom Sampling driven by a pseudorandom number whose generation is independent of Packet Content. Note that in Content-independent Sampling, it is not necessary to access the Packet Content in order to make the selection decision.
不使用数据包内容（或从中导出的数量）作为选择依据的采样操作称为与内容无关的采样操作。示例包括系统采样和由伪随机数驱动的均匀伪随机采样，伪随机数的生成与数据包内容无关。注意，在与内容无关的采样中，不必为了做出选择决策而访问分组内容。
* Content-Dependent Sampling
* 内容相关抽样
A Sampling operation where selection is dependent on Packet Content is called a Content-dependent Sampling operation. An example is pseudorandom selection according to a probability that depends on the contents of a packet field. Note that this is not a filter, because the selection is not deterministic.
选择依赖于数据包内容的采样操作称为依赖于内容的采样操作。一个例子是根据依赖于分组字段的内容的概率的伪随机选择。请注意，这不是一个过滤器，因为选择是不确定的。
* Hash Domain
* 散列域
A Hash Domain is a subset of the Packet Content and the packet treatment, viewed as an N-bit string for some positive integer N.
散列域是数据包内容和数据包处理的子集，被视为某个正整数N的N位字符串。
* Hash Range
* 散列范围
A Hash Range is a set of M-bit strings for some positive integer M that define the range of values the result of the hash operation can take.
哈希范围是某个正整数M的一组M位字符串，它定义了哈希操作结果可以采用的值的范围。
* Hash Function
* 散列函数
A Hash Function defines a deterministic map from the Hash Domain into the Hash Range.
散列函数定义从散列域到散列范围的确定性映射。
* Hash Selection Range
* 散列选择范围
A Hash Selection Range is a subset of the Hash Range. The packet is selected if the action of the Hash Function on the Hash Domain for the packet yields a result in the Hash Selection Range.
哈希选择范围是哈希范围的子集。如果对分组的哈希域的哈希函数的操作产生哈希选择范围内的结果，则选择分组。
* Hash-based Selection
* 基于散列的选择
A Hash-based Selection is Filtering specified by a Hash Domain, a Hash Function, a Hash Range, and a Hash Selection Range.
基于散列的选择是由散列域、散列函数、散列范围和散列选择范围指定的过滤。
* Approximative Selection
* 近似选择
Selectors in any of the above categories may be approximated by operations in the same or another category for the purposes of implementation. For example, uniform pseudorandom Sampling may be approximated by Hash-based Selection, using a suitable Hash Function and Hash Domain. In this case, the closeness of the approximation depends on the choice of Hash Function and Hash Domain.
为了实现的目的，上述任何类别中的选择器可以通过相同或另一类别中的操作来近似。例如，均匀伪随机采样可以通过使用合适的散列函数和散列域的基于散列的选择来近似。在这种情况下，近似值的接近程度取决于哈希函数和哈希域的选择。
* Population
* 人口
A Population is a Packet Stream, or a subset of a Packet Stream. A Population can be considered as a base set from which packets are selected. An example is all packets in the Observed Packet Stream that are observed within some specified time interval.
填充是数据包流或数据包流的子集。可以将总体视为从中选择数据包的基本集。一个示例是在某个指定的时间间隔内观察到的所观察的分组流中的所有分组。
* Population Size
* 人口规模
The Population Size is the number of all packets in the Population.
填充大小是填充中所有数据包的数量。
* Sample Size
* 样本量
The Sample Size is the number of packets selected from the Population by a Selector.
样本大小是选择器从总体中选择的数据包数。
* Configured Selection Fraction
* 配置选择分数
The Configured Selection Fraction is the expected ratio of the Sample Size to the Population Size, as based on the configured selection parameters.
配置的选择分数是基于配置的选择参数的样本大小与总体大小的预期比率。
* Attained Selection Fraction
* 获得的选择分数
The Attained Selection Fraction is the ratio of the actual Sample Size to the Population Size. For some Sampling methods, the Attained Selection Fraction can differ from the Configured Selection Fraction due to, for example, the inherent statistical variability in Sampling decisions of probabilistic Sampling and Hash-based Selection. Nevertheless, for large Population Sizes and properly configured Selectors, the Attained Selection Fraction usually approaches the Configured Selection Fraction.
获得的选择分数是实际样本量与总体规模的比率。对于一些抽样方法，由于例如概率抽样和基于散列的选择的抽样决策中固有的统计可变性，所获得的选择分数可以不同于所配置的选择分数。然而，对于较大的总体规模和正确配置的选择器，获得的选择分数通常接近配置的选择分数。
The PSAMP terminology has been specified with an IPFIX background, as PSAMP and IPFIX have similar terms. However, this section clarifies the terms between the IPFIX and PSAMP terminology.
PSAMP术语是在IPFIX背景下指定的，因为PSAMP和IPFIX具有类似的术语。但是，本节澄清了IPFIX和PSAMP术语之间的术语。
Figure B indicates the sequence of the IPFIX processes (Metering and Exporting) within the PSAMP Device.
图B显示了PSAMP设备内IPFIX进程（计量和导出）的顺序。
+------------------+
| Metering Process |
| +-----------+ | +-----------+
Observed | | Selection | | | Exporting |
Packet--->| | Process |--------->| Process |--->Collector
Stream | +-----------+ | +-----------+
+------------------+
+------------------+
| Metering Process |
| +-----------+ | +-----------+
Observed | | Selection | | | Exporting |
Packet--->| | Process |--------->| Process |--->Collector
Stream | +-----------+ | +-----------+
+------------------+
Figure B: PSAMP Processes
图B:PSAMP过程
The Selection Process, which takes an Observed Packet Stream as its input, is an integral part of the Metering Process. The Selection Process chooses which packets from its input Packet Stream will be
选择过程以观察到的分组流为输入，是计量过程的一个组成部分。选择过程从其输入数据包流中选择将接收的数据包
reported on by the rest of the Metering Process. Note that a "Process" is not necessarily implemented as a separate CPU thread.
由计量过程的其余部分报告。请注意，“进程”不一定作为单独的CPU线程实现。
The PSAMP terminology speaks of Packet Report and Packet Interpretation, while the IPFIX terminology speaks of Data Record and (Options) Template Record. The PSAMP Packet Report, which comprises information about the observed packet, can be viewed as analogous to the IPFIX Data Record defined by a Template Record. The PSAMP Report Interpretation, which comprises subsidiary information used for the interpretation of the Packet Reports, can be viewed as analogous to the IPFIX Data Record defined by an Options Template Record. This Options Template Record contains subsidiary information, applicable to the observed packet sent into the PSAMP Packet Report.
PSAMP术语涉及数据包报告和数据包解释，而IPFIX术语涉及数据记录和（选项）模板记录。PSAMP数据包报告包含有关观察到的数据包的信息，可被视为类似于模板记录定义的IPFIX数据记录。PSAMP报告解释包括用于解释数据包报告的辅助信息，可被视为类似于由选项模板记录定义的IPFIX数据记录。此选项模板记录包含辅助信息，适用于发送到PSAMP数据包报告中的观察数据包。
The output of the IPFIX working group relevant for this document is structured into three documents:
与本文件相关的IPFIX工作组的输出分为三个文件：
- IP Flow information architecture [RFC5470]
- IP流信息体系结构[RFC5470]
- IPFIX protocol specifications [RFC5101]
- IPFIX协议规范[RFC5101]
- IP Flow information export information model [RFC5102]
- IP流信息导出信息模型[RFC5102]
In the following sections, we investigate the differences between IPFIX and PSAMP for each of those aspects.
在下面的部分中，我们将研究IPFIX和PSAMP在这些方面的差异。
Traffic Flow measurement as described in the IPFIX requirements [RFC3917] and the IPFIX architecture [RFC5470] can be separated into two stages: packet processing and Flow processing. Figure C illustrates these stages.
IPFIX要求[RFC3917]和IPFIX架构[RFC5470]中描述的流量测量可分为两个阶段：数据包处理和流量处理。图C说明了这些阶段。
In stage 1, all processing steps act on packets. Packets are captured, timestamped, selected by one or more selection steps, and finally forwarded to packet classification that maps packets to Flows. The packets' selection steps may include Filtering and Sampling functions.
在阶段1中，所有处理步骤都作用于数据包。数据包被捕获、加时间戳、通过一个或多个选择步骤进行选择，并最终转发到将数据包映射到流的数据包分类。分组的选择步骤可以包括过滤和采样功能。
In stage 2, all processing steps act on Flows. After packets are classified (mapped to Flows), Flows are generated (or updated if they exist already). Flow generation and update steps may be performed repeatedly for aggregating Flows. Finally, Flows are exported.
在阶段2中，所有处理步骤都作用于流。在对数据包进行分类（映射到流）之后，将生成流（如果已经存在，则更新流）。可以重复执行流生成和更新步骤以聚合流。最后，输出流。
Packet Sampling as described in the PSAMP framework [RFC5474] covers only stage 1 of the IPFIX architecture with the packet classification replaced by Packet Report export, while IPFIX covers stage 2 also, as it generates Flow Records out of the selected packets.
PSAMP框架[RFC5474]中描述的数据包采样仅涵盖IPFIX体系结构的第1阶段，数据包分类由数据包报告导出取代，而IPFIX也涵盖第2阶段，因为它从所选数据包生成流记录。
IPFIX architecture PSAMP framework
IPFIX体系结构PSAMP框架
packet header packet header
capturing \ capturing
| | |
timestamping | timestamping
| | |
v | v
+------>+ | stage 1: +------>+
| | > packet | |
| packet | processing | packet
| selection | | selection
| | | | |
+-------+ | +-------+
| | |
v | v
packet / Packet Report
classification \ export
| |
v |
+------>+ |
| | |
| Flow generation |
| and update | stage 2:
| | > Flow
| v | processing
| Flow |
| selection |
| | |
+-------+ |
| |
v |
Flow Record /
export
packet header packet header
capturing \ capturing
| | |
timestamping | timestamping
| | |
v | v
+------>+ | stage 1: +------>+
| | > packet | |
| packet | processing | packet
| selection | | selection
| | | | |
+-------+ | +-------+
| | |
v | v
packet / Packet Report
classification \ export
| |
v |
+------>+ |
| | |
| Flow generation |
| and update | stage 2:
| | > Flow
| v | processing
| Flow |
| selection |
| | |
+-------+ |
| |
v |
Flow Record /
export
Figure C: Comparison of IPFIX Architecture and PSAMP Framework
图C:IPFIX体系结构与PSAMP框架的比较
Concerning the protocol, the major difference between IPFIX and PSAMP is that the IPFIX protocol exports Flow Records while the PSAMP protocol exports Packet Reports. From a pure export point of view, IPFIX will not distinguish a Flow Record composed of several packets aggregated together from a Flow Record composed of a single packet.
关于协议，IPFIX和PSAMP之间的主要区别在于IPFIX协议导出流记录，而PSAMP协议导出数据包报告。从纯导出的角度来看，IPFIX不会区分由多个数据包聚合而成的流记录和由单个数据包组成的流记录。
So the PSAMP export can be seen as a special IPFIX Flow Record containing information about a single packet.
因此，PSAMP导出可以看作是一个特殊的IPFIX流记录，其中包含关于单个数据包的信息。
All extensions of the IPFIX protocol that are required to satisfy the PSAMP requirements have already been incorporated in the IPFIX protocol [RFC5101], which was developed in parallel with the PSAMP protocol. An example is the need for a data type for protocol fields that have flexible length, such as an octet array. This was added to the IPFIX protocol specification in order to meet the requirement of the PSAMP protocol to report content of captured packets, for example, the first octets of a packet.
满足PSAMP要求所需的IPFIX协议的所有扩展已并入IPFIX协议[RFC5101]，该协议与PSAMP协议并行开发。例如，对于具有灵活长度的协议字段（如八位字节数组），需要一种数据类型。这被添加到IPFIX协议规范中，以满足PSAMP协议报告捕获数据包内容的要求，例如，数据包的第一个八位组。
From the information model point of view, the overlap between both the IPFIX and PSAMP protocols is quite large. Most of the Information Elements in the IPFIX protocol are also relevant for exporting packet information, for example, all fields reporting packet header properties. Only a few Information Elements, such as observedFlowTotalCount (whose value will always be 1 for PSAMP), etc., cannot be used in a meaningful way by the PSAMP protocol. Also, IPFIX protocol requirements concerning stage 2 of Figure C do not apply to the PSAMP Metering Process.
从信息模型的角度来看，IPFIX和PSAMP协议之间的重叠非常大。IPFIX协议中的大多数信息元素也与导出数据包信息相关，例如，报告数据包头属性的所有字段。只有少数信息元素，如observedFlowTotalCount（对于PSAMP，其值始终为1）不能被PSAMP协议以有意义的方式使用。此外，图C第2阶段的IPFIX协议要求不适用于PSAMP计量过程。
Further required extensions apply to the information model. Even if the IPFIX charter speaks of Sampling, no Sampling-related Information Elements are specified in [RFC5102]. The task of specifying them was intentionally left for the PSAMP information model [RFC5477]. A set of several additional fields is required for satisfying the requirements for the PSAMP information model [RFC5475].
进一步需要的扩展适用于信息模型。即使IPFIX章程提到采样，在[RFC5102]中也没有指定与采样相关的信息元素。指定它们的任务特意留给PSAMP信息模型[RFC5477]。为了满足PSAMP信息模型[RFC5475]的要求，需要一组额外的字段。
Exploiting the extensibility of the IPFIX information model, the required extension is covered by the PSAMP information model specified in [RFC5477].
利用IPFIX信息模型的可扩展性，[RFC5477]中指定的PSAMP信息模型涵盖了所需的扩展。
The [RFC5474] contains PSAMP protocol requirements throughout the document, with a special focus in Section 4, "Generic Requirements for PSAMP", and its subsections.
[RFC5474]包含整个文件中的PSAMP协议要求，第4节“PSAMP的通用要求”及其子节中有一个特别的重点。
Section 4 of [RFC5474] describes one requirement that, if not directly related to the export protocol, will put some constraints on it. Parallel Measurements: multiple independent Selection Processes at the same entity.
[RFC5474]第4节描述了一个要求，如果与导出协议没有直接关系，将对其施加一些约束。平行测量：在同一实体上有多个独立的选择过程。
[RFC5474] also describes a series of requirements specifying the different Information Elements that MUST and SHOULD be reported to the Collector. Nevertheless, IPFIX, being a generic export protocol, can export any Information Elements as long as they are described in the information model. So these requirements are mainly targeted for [RFC5477].
[RFC5474]还描述了一系列要求，规定了必须和应该向收集器报告的不同信息元素。然而，IPFIX作为一种通用的导出协议，可以导出任何信息元素，只要它们在信息模型中有描述。因此，这些要求主要针对[RFC5477]。
The PSAMP protocol specification meets almost all the protocol requirements stated in the PSAMP framework document [RFC5474]:
PSAMP协议规范几乎满足PSAMP框架文件[RFC5474]中规定的所有协议要求：
* Extensibility
* 扩展性
* Parallel selection processes
* 并行选择过程
* Encrypted packets
* 加密包
* Indication of information loss
* 信息丢失指示
* Accuracy
* 精确
* Privacy
* 隐私
* Timeliness
* 及时性
* Congestion avoidance
* 拥塞避免
* Secure export
* 安全出口
* Export rate limit
* 出口税率限制
* Microsecond timestamp resolution
* 微秒时间戳分辨率
The only requirement that is not met is Export Packet compression. With the choice of IPFIX as the PSAMP export protocol, the Export Packet compression option mentioned in the Section 8.5 of the framework document [RFC5474] is not addressed.
唯一未满足的要求是导出数据包压缩。选择IPFIX作为PSAMP导出协议时，框架文件[RFC5474]第8.5节中提到的导出数据包压缩选项未被提及。
The Template Record in the Template Set is used to describe the different PSAMP Information Elements that will be exported to the Collector. The Collector decodes the Template Record in the Template Set and knows which Information Elements to expect when it receives
模板集中的模板记录用于描述将导出到收集器的不同PSAMP信息元素。收集器对模板集中的模板记录进行解码，并知道在接收到时预期的信息元素
the Data Records in the PSAMP Packet Report Data Set. Typically, in the base level of the PSAMP functionality, the Template Set will contain the input sequence number, the packet fragment (some number of contiguous bytes from the start of the packet or from the start of the payload), and the Selection Sequence.
PSAMP数据包报告数据集中的数据记录。通常，在PSAMP功能的基本级别中，模板集将包含输入序列号、数据包片段（从数据包开始或从有效负载开始的一些连续字节数）和选择序列。
The Options Template Record in the Options Template Set is used to describe the different PSAMP Information Elements that concern the Metering Process itself: Sampling and/or Filtering functions, and the associated parameters. The Collector decodes the Options Template Records in the Options Template Set and knows which Information Elements to expect when it receives the Data Records in the PSAMP Report Interpretation Data Set. Typically, the Options Template would contain the Selection Sequence, the Sampling or Filtering functions, and the Sampling or Filtering associated parameters.
选项模板集中的选项模板记录用于描述与计量过程本身有关的不同PSAMP信息元素：采样和/或过滤功能以及相关参数。收集器对选项模板集中的选项模板记录进行解码，并知道在接收PSAMP报告解释数据集中的数据记录时需要哪些信息元素。通常，选项模板将包含选择序列、采样或过滤功能以及采样或过滤相关参数。
PSAMP requires all the different possibilities of the IPFIX protocol specifications [RFC5101], that is, the three types of Sets (Data Set, Template Set, and Options Templates Set) with the two types of Template Records (Template Record and Options Template Record), as described in Figure A. As a consequence, PSAMP can't rely on a subset of the IPFIX protocol specifications described in [RFC5101]. The entire IPFIX protocol specifications [RFC5101] MUST be implemented for the PSAMP protocol.
PSAMP需要IPFIX协议规范[RFC5101]的所有不同可能性，即三种类型的集（数据集、模板集和选项模板集）和两种类型的模板记录（模板记录和选项模板记录），如图A所示。因此，PSAMP不能依赖[RFC5101]中描述的IPFIX协议规范的子集。PSAMP协议必须执行整个IPFIX协议规范[RFC5101]。
In this section, we describe the usage of the IPFIX protocol for PSAMP. We describe the record formats and the additional requirements that must be met. PSAMP uses two different types of messages:
在本节中，我们将介绍IPFIX协议在PSAMP中的用法。我们描述了记录格式和必须满足的附加要求。PSAMP使用两种不同类型的消息：
- Packet Reports
- 数据包报告
- Report Interpretation
- 报告解释
The format of Packet Reports is defined in IPFIX Template Records. The PSAMP data is transferred as Information Elements in IPFIX Data Records as described by the Template Record. There are two different types of Packet Reports. Basic Packet Reports contain only the basic Information Elements required for PSAMP reporting. Extended Packet Reports MAY contain other Information Elements, and do not necessarily include Packet Content (See section 6.4.2).
数据包报告的格式在IPFIX模板记录中定义。PSAMP数据作为IPFIX数据记录中的信息元素传输，如模板记录所述。有两种不同类型的数据包报告。基本数据包报告仅包含PSAMP报告所需的基本信息元素。扩展数据包报告可能包含其他信息元素，不一定包括数据包内容（见第6.4.2节）。
The format of Report Interpretations is defined in the IPFIX Options Template Record. The Information Elements are transferred in IPFIX Data Records as described by the Options Template Record. There are four different types of Report Interpretation messages:
报告解释的格式在IPFIX选项模板记录中定义。信息元素在IPFIX数据记录中传输，如选项模板记录所述。有四种不同类型的报告解释消息：
- Selection Sequence Report Interpretation
- 选择顺序报告解释
- Selector Report Interpretation
- 选择器报告解释
- Selection Sequence Statistics Report Interpretation
- 选择序列统计报告解释
- Accuracy Report Interpretation
- 精度报告解释
A description and examples about the usage of those reports are given below.
下面给出了这些报告的使用说明和示例。
The Selector ID is the unique ID identifying a Primitive Selector. Each Primitive Selector MUST have a unique ID within the Observation Domain. The Selector ID is represented by the selectorId Information Element [RFC5477].
选择器ID是标识基元选择器的唯一ID。每个基元选择器在观察域中必须具有唯一的ID。选择器ID由选择器ID信息元素[RFC5477]表示。
From all the packets observed at an Observation Point, a subset of packets is selected by one or more Selectors. The Selection Sequence is the combination of an Observation Point and one or more Selector(s) through which the packets are selected. The Selection Sequence ID is a unique value representing that combination. The Selection Sequence ID is represented by the selectionSequenceId Information Element [RFC5477].
从在观察点观察到的所有数据包中，一个或多个选择器选择数据包的子集。选择序列是观察点和一个或多个选择器的组合，通过该选择器选择分组。选择序列ID是表示该组合的唯一值。选择序列ID由selectionSequenceId信息元素[RFC5477]表示。
An Exporting Process MUST be able to limit the export rate according to a configurable value. The Exporting Process MAY limit the export rate on a per Collecting Process basis.
导出过程必须能够根据可配置的值限制导出速率。出口流程可能会在每个收集流程的基础上限制出口率。
For each Selection Sequence, for each selected packet, a Packet Report MUST be created. The format of the Packet Report is specified in a Template Record contained in a Template Set.
对于每个选择序列，必须为每个选定的数据包创建数据包报告。数据包报告的格式在模板集中包含的模板记录中指定。
There are two types of Packet Report, as described in [RFC5474]: the basic Packet Report and the extended Packet Report.
有两种类型的数据包报告，如[RFC5474]所述：基本数据包报告和扩展数据包报告。
For each selected packet, the Packet Report MUST contain the following information:
对于每个选定的数据包，数据包报告必须包含以下信息：
- The selectionSequenceId Information Element If there is a digest function in the Selection Sequence, the Packet Report MUST contain the hash value (digestHashValue Information Element) generated by the digest Hash Function for each selected packet. If there is more than one digest function, then each hash value MUST be included in the same order as they appear in the Selection Sequence. If there are no digest functions in the Selection Sequence, no element for the digest needs to be sent.
- selectionSequenceId信息元素如果选择序列中有摘要函数，则数据包报告必须包含摘要哈希函数为每个选定数据包生成的哈希值（digestHashValue信息元素）。如果有多个摘要函数，则每个哈希值必须按照它们在选择序列中出现的顺序包含。如果选择序列中没有摘要函数，则不需要发送摘要元素。
- Some number of contiguous bytes from the start of the packet, including the packet header (which includes link layer, network layer, and other encapsulation headers) and some subsequent bytes of the packet payload. Alternatively, the number of contiguous bytes may start at the beginning of the payload. The dataLinkFrameSection, mplsLabelStackSection, mplsPayloadPacketSection, ipPacketSection, and ipPayloadPacketSection PSAMP Information Elements are available for this use.
- 从数据包开始的一些连续字节数，包括数据包报头（包括链路层、网络层和其他封装报头）和数据包有效载荷的一些后续字节。或者，连续字节的数量可以从有效负载的开始处开始。dataLinkFrameSection、mplsLabelStackSection、mplsPayloadPacketSection、ipPacketSection和ipPayloadPacketSection PSAMP信息元素可用于此用途。
For each selected packet, the Packet Report SHOULD contain a time-related Information Element that matches the Metering Process time accuracy. Typically, the observationTimeMicroseconds Information Element. Other possible Information Elements are the observationTimeSeconds, the observationTimeMilliseconds, or the observationTimeNanoseconds.
对于每个选定的数据包，数据包报告应包含与计量过程时间精度相匹配的时间相关信息元素。通常，observationTimeMicroseconds信息元素。其他可能的信息元素是observationTimeSeconds、ObservationTimeMilliconds或observationTimeNanoseconds。
In the Packet Report, the PSAMP Device MUST be capable of exporting the number of observed packets and the number of packets selected by each instance of its Primitive Selectors (as described by the non-scope Information Elements of the Selection Sequence Statistics Report Interpretation), although it MAY be a configurable option not to include them. If exported, the Attained Selection Fraction may be calculated precisely for the Observed Packet Stream. The Packet Report MAY include only the final selector packetSelected, to act as an index for that Selection Sequence in the Selection Sequence Statistics Report Interpretation, which also allows the calculation of the Attained Selection Fraction.
在数据包报告中，PSAMP设备必须能够导出观察到的数据包数量以及由其原语选择器的每个实例选择的数据包数量（如选择序列统计报告解释的非范围信息元素所述），尽管不包括它们可能是一个可配置的选项。如果导出，可以针对观察到的分组流精确地计算获得的选择分数。分组报告可仅包括最终选择器packetSelected，以在选择序列统计报告解释中用作该选择序列的索引，其还允许计算所获得的选择分数。
The contiguous Information Elements (dataLinkFrameSection, mplsLabelStackSection, mplsPayloadPacketSection, ipPacketSection, and ipPayloadPacketSection) MAY be encoded with a fixed-length field or with a variable-sized field. If one of these Information Elements is encoded with a fixed-length field whose length is too long for the number of contiguous bytes in the selected packet, padding MUST NOT be used. In this case, the Exporting Process MUST export the information either in a new Template Record with the correct fixed-length field or in a new Template Record with a variable-length field.
连续信息元素（dataLinkFrameSection、mplsLabelStackSection、mplsPayloadPacketSection、ipPacketSection和ipPayloadPacketSection）可以使用固定长度字段或可变大小字段进行编码。如果这些信息元素之一使用固定长度字段编码，该字段的长度对于所选数据包中的连续字节数来说太长，则不得使用填充。在这种情况下，导出过程必须将信息导出到具有正确固定长度字段的新模板记录或具有可变长度字段的新模板记录中。
Here is an example of a basic Packet Report, with a SelectionSequenceId value of 9 and dataLinkFrameSection Information Element of 12 bytes, 0x4500 005B A174 0000 FF11 832E, encoded with a fixed-length field.
下面是一个基本数据包报告的示例，SelectionSequenceId值为9，dataLinkFrameSection信息元素为12字节，0x4500005B A174 0000 FF11 832E，用固定长度字段编码。
IPFIX Template Record:
IPFIX模板记录：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 2 | Length = 24 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 260 | Field Count = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| selectionSequenceId = 301 | Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| digestHashValue = 326 | Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| dataLinkFrameSection = 315 | Field Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|observationTimeMicroseconds=324| Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 2 | Length = 24 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 260 | Field Count = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| selectionSequenceId = 301 | Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| digestHashValue = 326 | Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| dataLinkFrameSection = 315 | Field Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|observationTimeMicroseconds=324| Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The associated IPFIX Data Record:
关联的IPFIX数据记录：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 260 | Length = 32 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 9 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0x9123 0613 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0x4500 005B |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0xA174 0000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0xFF11 832E |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| observation time ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... encoded as dateTimeMicroSeconds [RFC5101] |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 260 | Length = 32 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 9 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0x9123 0613 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0x4500 005B |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0xA174 0000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0xFF11 832E |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| observation time ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... encoded as dateTimeMicroSeconds [RFC5101] |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure D: Example of a Basic Packet Report
图D：基本数据包报告示例
Here is an example of a basic Packet Report, with a SelectionSequenceId value of 9 and ipHeaderPacketSection Information Element of 12 bytes, 0x4500 005B A174 0000 FF11 832E, encoded with a variable-sized field.
下面是一个基本数据包报告的示例，SelectionSequenceId值为9，ipHeaderPacketSection信息元素为12字节，0x4500005B A174 0000 FF11 832E，用可变大小的字段编码。
IPFIX Template Record:
IPFIX模板记录：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 2 | Length = 16 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 261 | Field Count = 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| selectionSequenceId = 301 | Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ipHeaderPacketSection = 313 | Field Length = 65535 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 2 | Length = 16 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 261 | Field Count = 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| selectionSequenceId = 301 | Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ipHeaderPacketSection = 313 | Field Length = 65535 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The associated IPFIX Data Record:
关联的IPFIX数据记录：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 261 | Length = 21 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 9 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length = 12 | 0x4500 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... 005B | 0xA174 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... 0000 | 0xFF11 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... 832E |
+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 261 | Length = 21 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 9 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length = 12 | 0x4500 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... 005B | 0xA174 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... 0000 | 0xFF11 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... 832E |
+-+-+-+-+-+-+-+-+
Figure E: Example of a Basic Packet Report with a Variable-Sized Field
图E：具有可变大小字段的基本数据包报告示例
Alternatively to the basic Packet Report, the extended Packet Report MAY contain other Information Elements related to the protocols used in the packet (such as source and destination IP addresses), related to the packet treatment (such as output interface, destination BGP autonomous system [RFC4271]), or related to the Selection State associated with the packet (such as timestamp, hash value).
作为基本分组报告的替代，扩展分组报告可以包含与分组中使用的协议（例如源和目的地IP地址）相关的、与分组处理（例如输出接口、目的地BGP自治系统[RFC4271]）相关的其他信息元素，或与与数据包关联的选择状态相关（例如时间戳、哈希值）。
It is envisaged that selection of fields for extended Packet Reports may be used to reduce reporting bandwidth, in which case the option to report some number of contiguous bytes from the start of the packet, mandatory in the basic Packet Report, may not be exercised. In this case, the Packet Content MAY be omitted. Note this configuration is quite similar to an IPFIX Device for which a Template Record containing information about a single packet is reported.
可以设想，可以使用为扩展分组报告选择字段来减少报告带宽，在这种情况下，可以不执行在基本分组报告中强制执行的从分组开始报告一些连续字节数的选项。在这种情况下，可以省略分组内容。注意：此配置与IPFIX设备非常相似，IPFIX设备报告包含单个数据包信息的模板记录。
Example of a detailed Extended Packet Report:
详细扩展数据包报告示例：
IPFIX Template Record:
IPFIX模板记录：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 2 | Length = 32 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 261 | Field Count = 6 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| selectionSequenceId = 301 | Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| sourceIPv4Address = 8 | Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| destinationIPv4Address = 12 | Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| totalLengthIPv4 = 190 | Field Length = 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| tcpSourcePort = 182 | Field Length = 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| tcpDestinationPort = 183 | Field Length = 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 2 | Length = 32 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 261 | Field Count = 6 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| selectionSequenceId = 301 | Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| sourceIPv4Address = 8 | Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| destinationIPv4Address = 12 | Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| totalLengthIPv4 = 190 | Field Length = 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| tcpSourcePort = 182 | Field Length = 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| tcpDestinationPort = 183 | Field Length = 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The associated IPFIX Data Record:
关联的IPFIX数据记录：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 261 | Length = 20 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 9 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 192.0.2.1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 192.0.2.106 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 72 | 1372 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 80 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 261 | Length = 20 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 9 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 192.0.2.1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 192.0.2.106 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 72 | 1372 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 80 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure F: Example of an Extended Packet Report
图F：扩展数据包报告示例
To make full sense of the Packet Reports, there are a number of additional pieces of information that must be communicated to the Collector:
为了充分理解数据包报告，必须向采集器传达许多附加信息：
- The details about which Selectors and Observation Points are being used within a Selection Sequence MUST be provided using the Selection Sequence Report Interpretation.
- 必须使用选择序列报告解释提供选择序列中使用的选择器和观察点的详细信息。
- The configuration details of each Selector MUST be provided using the Selector Report Interpretation.
- 必须使用选择器报告解释提供每个选择器的配置详细信息。
- The Selector ID statistics MUST be provided using the Selection Sequence Statistics Report Interpretation.
- 必须使用选择序列统计报告解释提供选择器ID统计信息。
- The accuracies of the reported fields MUST be provided using the Accuracy Report Interpretation.
- 必须使用精度报告解释提供报告字段的精度。
Each Packet Report contains a selectionSequenceId Information Element that identifies the particular combination of Observation Point and Selector(s) used for its selection. For every selectionSequenceId Information Element in use, the PSAMP Device MUST export a Selection Sequence Report Interpretation using an Options Template with the following Information Elements:
每个数据包报告都包含一个selectionSequenceId信息元素，用于标识用于选择的观察点和选择器的特定组合。对于使用中的每个selectionSequenceId信息元素，PSAMP设备必须使用包含以下信息元素的选项模板导出选择序列报告解释：
Scope: selectionSequenceId Non-Scope: one Information Element mapping the Observation Point selectorId (one or more)
范围：selectionSequenceId非范围：映射观察点selectorId的一个信息元素（一个或多个）
An Information Element representing the Observation Point would typically be taken from the ingressInterface, egressInterface, lineCardId, exporterIPv4Address, or exporterIPv6Address Information Elements (specified in [RFC5102]), but is not limited to those: any Information Element specified in [RFC5102] or [RFC5477] can potentially be used. In case of more complex Observation Points (such as a list of interfaces, a bus, etc.), a new Information Element describing the new type of Observation Point must be specified, along with an Options Template Record describing it in more detail (if necessary).
代表观测点的信息元素通常取自入口接口、出口接口、lineCardId、exporterIPv4Address或exporterIPv6Address信息元素（在[RFC5102]中指定），但不限于以下内容：可以使用[RFC5102]或[RFC5477]中指定的任何信息元素。对于更复杂的观测点（如接口列表、总线等），必须指定描述新类型观测点的新信息元素，以及更详细描述它的选项模板记录（如有必要）。
If the packets are selected by a Composite Selector, the Selection Sequence is composed of several Primitive Selectors. In such a case, the Selection Sequence Report Interpretation MUST contain the list of all the Primitive Selector IDs in the Selection Sequence. If multiple Selectors are contained in the Selection Sequence Report Interpretation, the selectorId's MUST be identified in the order they are used.
如果数据包由复合选择器选择，则选择序列由几个基本选择器组成。在这种情况下，选择序列报告解释必须包含选择序列中所有基本选择器ID的列表。如果选择序列报告解释中包含多个选择器，则必须按照使用顺序标识选择器ID。
Example of two Selection Sequences:
两个选择序列的示例：
Selection Sequence 7 (Filter->Sampling): ingressInterface 5 selectorId 5 (Filter, match IPV4SourceAddress 192.0.2.1) selectorId 10 (Sampler, Random 1 out-of ten)
选择顺序7（过滤器->采样）：入口接口5选择器ID 5（过滤器，匹配IPV4SourceAddress 192.0.2.1）选择器ID 10（采样器，随机1/10）
Selection Sequence 9 (Sampling->Filtering): ingressInterface 5 selectorId 10 (Sampler, Random 1 out-of ten) selectorId 5 (Filter, match IPV4SourceAddress 192.0.2.1)
选择顺序9（采样->过滤）：入口接口5选择器ID 10（采样器，随机1/10）选择器ID 5（过滤器，匹配IPV4源地址192.0.2.1）
IPFIX Options Template Record:
IPFIX选项模板记录：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 3 | Length = 26 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 262 | Field Count = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope Field Count = 1 |0| selectionSequenceId = 301 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope 1 Length = 4 |0| ingressInterface = 10 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |0| selectorId = 302 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |0| selectorId = 302 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 3 | Length = 26 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 262 | Field Count = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope Field Count = 1 |0| selectionSequenceId = 301 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope 1 Length = 4 |0| ingressInterface = 10 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |0| selectorId = 302 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |0| selectorId = 302 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The associated IPFIX Data Record:
关联的IPFIX数据记录：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 262 | Length = 36 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 7 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 5 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 5 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 10 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 9 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 5 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 10 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 5 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 262 | Length = 36 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 7 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 5 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 5 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 10 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 9 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 5 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 10 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 5 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure G: Example of a Selection Sequence Report Interpretation
图G：选择序列报告解释示例
Notes:
笔记：
* There are two Records here in the same Data Set. Each record defines a different Selection Sequence.
* 在同一数据集中有两条记录。每个记录定义不同的选择序列。
* If, for example, a different Selection Sequence is composed of three Selectors, then a different Options Template with three selectorId Information Elements (instead of two) must be used.
* 例如，如果不同的选择序列由三个选择器组成，则必须使用具有三个选择器ID信息元素（而不是两个）的不同选项模板。
An IPFIX Data Record, defined by an Options Template Record, MUST be used to send the configuration details of every Selector in use. The Options Template Record MUST contain the selectorId Information Element as the Scope field and the SelectorAlgorithm Information Element followed by some specific configuration parameters:
必须使用由选项模板记录定义的IPFIX数据记录来发送正在使用的每个选择器的配置详细信息。选项模板记录必须包含selectorId信息元素作为范围字段，以及SelectorAlgorithm信息元素，后跟一些特定的配置参数：
Scope: selectorId Non-scope: selectorAlgorithm algorithm-specific Information Elements
作用域：selectorId非作用域：selectorAlgorithm算法特定信息元素
The algorithm-specific Information Elements are specified in the following subsections, depending on the selection method represented by the value of the selectorAlgorithm [RFC5477].
根据selectorAlgorithm[RFC5477]值表示的选择方法，在以下小节中指定了特定于算法的信息元素。
In systematic count-based Sampling, the start and stop triggers for the Sampling interval are defined in accordance with the spatial packet position (packet count) [RFC5475].
在基于系统计数的采样中，根据空间数据包位置（数据包计数）[RFC5475]定义采样间隔的启动和停止触发器。
The REQUIRED algorithm-specific Information Elements in the case of systematic count-based Sampling are:
在基于系统计数的抽样情况下，所需的算法特定信息元素为：
samplingPacketInterval: number of packets selected in a row samplingPacketSpace: number of packets between selections
samplingPacketInterval:行中选择的数据包数samplingPacketSpace:选择之间的数据包数
Example of a simple 1 out-of 10 systematic count-based Selector definition, where the samplingPacketInterval is 1 and the samplingPacketSpace is 9.
简单的基于10取1系统计数的选择器定义示例，其中samplingPacketInterval为1，samplingPacketSpace为9。
IPFIX Options Template Record:
IPFIX选项模板记录：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 3 | Length = 26 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 263 | Field Count = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope Field Count = 1 |0| selectorId = 302 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope 1 Length = 4 |0| selectorAlgorithm = 304 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 1 |0|samplingPacketInterval = 305 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 1 |0| samplingPacketSpace = 306 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 3 | Length = 26 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 263 | Field Count = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope Field Count = 1 |0| selectorId = 302 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope 1 Length = 4 |0| selectorAlgorithm = 304 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 1 |0|samplingPacketInterval = 305 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 1 |0| samplingPacketSpace = 306 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Associated IPFIX Data Record:
关联的IPFIX数据记录：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 263 | Length = 11 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 15 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 1 | 1 | 9 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 263 | Length = 11 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 15 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 1 | 1 | 9 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure H: Example of the Selector Report Interpretation for Systematic Count-Based Sampling
图H：基于系统计数抽样的选择器报告解释示例
Notes:
笔记：
* A selectorAlgorithm value of 1 represents systematic count-based Sampling.
* selectorAlgorithm值为1表示基于系统计数的采样。
* samplingPacketInterval and samplingPacketSpace are of type unsigned32 but are compressed down to one octet here, as allowed by the IPFIX protocol specifications [RFC5101].
* samplingPacketInterval和samplingPacketSpace的类型为unsigned32，但根据IPFIX协议规范[RFC5101]的允许，此处压缩为一个八位字节。
In systematic time-based Sampling, the start and stop triggers are used to define the Sampling intervals [RFC5475]. The REQUIRED algorithm-specific Information Elements in the case of systematic time-based Sampling are:
在基于时间的系统采样中，启动和停止触发器用于定义采样间隔[RFC5475]。在基于时间的系统抽样的情况下，所需的特定于算法的信息元素为：
samplingTimeInterval: time (in microseconds) when packets are selected samplingTimeSpace: time (in microseconds) between selections
samplingTimeInterval:选择数据包时的时间samplingTimeSpace:选择之间的时间（微秒）
Example of a 100 microsecond out-of 1000 microsecond systematic time-based Selector definition, where the samplingTimeInterval is 100 and the samplingTimeSpace is 900.
1000微秒系统时间选择器定义中的100微秒示例，其中samplingTimeInterval为100，samplingTimeSpace为900。
IPFIX Options Template Record:
IPFIX选项模板记录：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 3 | Length = 26 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 264 | Field Count = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope Field Count = 1 |0| selectorId = 302 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope 1 Length = 4 |0| selectorAlgorithm = 304 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 1 |0| samplingTimeInterval = 307 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 1 |0| samplingTimeSpace = 308 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 3 | Length = 26 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 264 | Field Count = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope Field Count = 1 |0| selectorId = 302 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope 1 Length = 4 |0| selectorAlgorithm = 304 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 1 |0| samplingTimeInterval = 307 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 1 |0| samplingTimeSpace = 308 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Associated IPFIX Data Record:
关联的IPFIX数据记录：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 264 | Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 16 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 2 | 100 | 900 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 264 | Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 16 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 2 | 100 | 900 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure I: Example of the Selector Report Interpretation
图一：选择器报告解释示例
for Systematic Time-Based Sampling
用于基于时间的系统采样
Notes:
笔记：
* A selectorAlgorithm value of 2 represents systematic time-based Sampling.
* selectorAlgorithm值为2表示系统的基于时间的采样。
* samplingTimeInterval and samplingTimeSpace are of type unsigned32 but are compressed down here.
* samplingTimeInterval和samplingTimeSpace的类型为unsigned32，但在此处被压缩。
In random n-out-of-N Sampling, n elements are selected out of the parent Population that consists of N elements [RFC5475]. The REQUIRED algorithm-specific Information Elements in case of random n-out-of-N Sampling are:
在随机n取n抽样中，从由n个元素组成的父总体中选择n个元素[RFC5475]。随机n取n抽样情况下所需的算法特定信息元素为：
samplingSize: number of packets selected samplingPopulation: number of packets in selection Population
samplingSize:所选数据包数samplingPopulation:所选数据包数
Example of a 1 out-of 10 random n-out-of-N Sampling Selector:
10取1随机n取n采样选择器示例：
IPFIX Options Template Record:
IPFIX选项模板记录：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 3 | Length = 26 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 265 | Field Count = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope Field Count = 1 |0| selectorId = 302 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope 1 Length = 4 |0| selectorAlgorithm = 304 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 1 |0| samplingSize = 309 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 1 |0| samplingPopulation = 310 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 3 | Length = 26 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 265 | Field Count = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope Field Count = 1 |0| selectorId = 302 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope 1 Length = 4 |0| selectorAlgorithm = 304 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 1 |0| samplingSize = 309 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 1 |0| samplingPopulation = 310 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Associated IPFIX Data Record:
关联的IPFIX数据记录：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 265 | Length = 11 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 17 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 3 | 1 | 10 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 265 | Length = 11 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 17 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 3 | 1 | 10 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure J: Example of the Selector Report Interpretation for Random n-out-of-N Sampling
图J：随机n取n抽样的选择器报告解释示例
Notes:
笔记：
* A selectorAlgorithm value of 3 represents Random n-out-of-N Sampling.
* selectorAlgorithm值为3表示n取n随机采样。
* samplingSize and samplingPopulation are of type unsigned32 but are compressed down to one octet here.
* samplingSize和samplingPopulation的类型为unsigned32，但此处压缩为一个八位字节。
In uniform probabilistic Sampling, each element has the same probability p of being selected from the parent Population [RFC5475]. The algorithm-specific Information Element in case of uniform probabilistic Sampling is:
在均匀概率抽样中，每个元素从父总体中选择的概率p相同[RFC5475]。在均匀概率抽样的情况下，特定于算法的信息元素为：
samplingProbability: a floating point number for the Sampling probability.
采样概率：采样概率的浮点数。
Example of a 15% uniform probability Sampling Selector:
15%均匀概率抽样选择器示例：
IPFIX Options Template Record:
IPFIX选项模板记录：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 3 | Length = 22 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 271 | Field Count = 3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope Field Count = 1 |0| selectorId = 302 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |0| selectorAlgorithm = 304 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 1 |0| samplingProbability = 311 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 3 | Length = 22 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 271 | Field Count = 3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope Field Count = 1 |0| selectorId = 302 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |0| selectorAlgorithm = 304 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 1 |0| samplingProbability = 311 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Associated IPFIX Data Record:
关联的IPFIX数据记录：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 271 | Length = 11 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 20 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 4 | 0.15 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 271 | Length = 11 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 20 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 4 | 0.15 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+-+-+-+-+-+-+-+-+
Figure K: Example of the Selector Report Interpretation for Uniform Probabilistic Sampling
图K：均匀概率抽样的选择器报告解释示例
Notes:
笔记：
* A selectorAlgorithm value of 4 represents Uniform Probabilistic Sampling.
* selectorAlgorithm值为4表示均匀概率抽样。
* samplingProbability is of type float64 but is compressed down to a float32 here.
* 采样概率为float64类型，但在此处压缩为float32。
This classification includes match(es) on field(s) within a packet and/or on properties of the router state. With this method, a packet is selected if a specific field in the packet equals a predefined value.
该分类包括数据包内字段和/或路由器状态属性的匹配。使用此方法，如果数据包中的特定字段等于预定义值，则选择数据包。
The algorithm-specific Information Elements defining configuration parameters for Property Match Filtering are taken from the full range of available Information Elements.
定义属性匹配筛选配置参数的特定于算法的信息元素取自所有可用信息元素。
When multiple different Information Elements are defined, the filter acts as a logical AND. Note that the logical OR is not covered by these PSAMP specifications. The Property Match Filtering Options Template Record MUST NOT have multiple identical Information Elements. The result of the filter is independent from the order of the Information Elements in the Options Template Record, but the order may be important for implementation purposes, as the first filter will have to work at a higher rate. In any case, an implementation is not constrained to respect the filter ordering as long as the result is the same, and it may even implement the composite Filtering in one single step.
当定义了多个不同的信息元素时，过滤器充当逻辑AND。请注意，这些PSAMP规范不包括逻辑OR。属性匹配筛选选项模板记录不能有多个相同的信息元素。过滤器的结果独立于选项模板记录中信息元素的顺序，但顺序对于实现目的可能很重要，因为第一个过滤器必须以更高的速度工作。在任何情况下，只要结果相同，一个实现就不必遵守过滤器顺序，甚至可以在一个步骤中实现复合过滤。
Since encryption alters the meaning of encrypted fields, when the Property Match Filtering classification is based on the encrypted field(s) in the packet, it MUST be able to recognize that the field(s) are not available and MUST NOT select those packets unless specifically directed by the Information Element description. Even if they are ignored, the encrypted packets MUST be accounted for in the Selector packetsObserved Information Element [RFC5477], part of the Selection Sequence Statistics Report Interpretation.
由于加密改变了加密字段的含义，当属性匹配过滤分类基于数据包中的加密字段时，必须能够识别字段不可用，并且不得选择这些数据包，除非信息元素描述明确指示。即使忽略它们，加密的数据包也必须在选择器数据包服务信息元素[RFC5477]中进行说明，该元素是选择序列统计信息报告解释的一部分。
Example of a match-based filter Selector, whose rules are: IPv4 Source Address = 192.0.2.1 IPv4 Next-Hop Address = 192.0.2.129
基于匹配的筛选器选择器示例，其规则为：IPv4源地址=192.0.2.1 IPv4下一跳地址=192.0.2.129
IPFIX Options Template Record:
IPFIX选项模板记录：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 3 | Length = 26 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 266 | Field Count = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope Field Count = 1 |0| selectorId = 302 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope 1 Length = 4 |0| selectorAlgorithm = 304 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 1 |0| sourceIPv4Address = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |0| ipNextHopIPv4Address = 15 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 3 | Length = 26 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 266 | Field Count = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope Field Count = 1 |0| selectorId = 302 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope 1 Length = 4 |0| selectorAlgorithm = 304 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 1 |0| sourceIPv4Address = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |0| ipNextHopIPv4Address = 15 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Associated IPFIX Data Record:
关联的IPFIX数据记录：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 266 | Length = 11 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 21 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 5 | 192.0.2 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... .1 | 192.0.2 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... .129 |
+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 266 | Length = 11 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 21 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 5 | 192.0.2 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... .1 | 192.0.2 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... .129 |
+-+-+-+-+-+-+-+-+
Figure L: Example of the Selector Report Interpretation for Match-Based and Router State Filtering
图L：基于匹配和路由器状态筛选的选择器报告解释示例
Notes:
笔记：
* A selectorAlgorithm value of 5 represents Property Match Filtering.
* selectorAlgorithm值为5表示属性匹配筛选。
* In this filter, there is a mix of information from the packet and information from the router.
* 在这个过滤器中，来自包的信息和来自路由器的信息混合在一起。
In Hash-based Selection, a Hash Function is run on IPv4 traffic. The following fields MUST be used as input to that Hash Function:
在基于哈希的选择中，哈希函数在IPv4流量上运行。以下字段必须用作该哈希函数的输入：
- IP identification field
- IP标识字段
- Flags field
- 标志字段
- Fragment offset
- 碎片偏移量
- Source IP address
- 源IP地址
- Destination IP address
- 目标IP地址
- A number of bytes from the IP payload. The number of bytes and starting offset MUST be configurable if the Hash Function supports it.
- 来自IP有效负载的字节数。如果哈希函数支持，字节数和起始偏移量必须是可配置的。
For the bytes taken from the IP payload, IPSX has a fixed offset of 0 bytes and a fixed size of 8 bytes. The number and offset of payload bytes in the BOB function MUST be configurable.
对于从IP有效负载获取的字节，IPSX具有0字节的固定偏移量和8字节的固定大小。BOB函数中的有效负载字节数和偏移量必须是可配置的。
The minimum configuration ranges MUST be as follows:
最小配置范围必须如下所示：
Number of bytes: from 8 to 32 Offset: from 0 to 64
字节数：从8到32偏移量：从0到64
If the selected payload bytes are not available and the Hash Function can take a variable-sized input, then the Hash Function MUST be run with the information that is available and a shorter size. Passing 0 as a substitute for missing payload bytes is only acceptable if the Hash Function takes a fixed size as is the case with IPSX.
如果选定的有效负载字节不可用，并且哈希函数可以接受可变大小的输入，则必须使用可用的信息和较短的大小运行哈希函数。只有当哈希函数采用固定大小时（如IPSX），才可以将0作为丢失的有效负载字节的替代传递。
If the Hash Function can take an initialization value, then this value MUST be configurable.
如果哈希函数可以采用初始化值，则该值必须是可配置的。
A Hash-based Selection function MAY be configurable as a digest function. Any Selection Process that is configured as a digest function MUST have the output value included in the basic Packet Report for any selected packet.
基于散列的选择函数可以配置为摘要函数。任何配置为摘要函数的选择过程都必须在任何选定数据包的基本数据包报告中包含输出值。
Each Hash Function used as a Hash-based Selection Selector requires its own value for the selectorAlgorithm. Currently, we have BOB (6), IPSX (7), and CRC (8) defined and any MAY be used for either Filtering or creating a Packet Digest. Only BOB is recommended though and SHOULD be used.
用作基于哈希的选择选择器的每个哈希函数都要求selectorAlgorithm具有自己的值。目前，我们已经定义了BOB（6）、IPSX（7）和CRC（8），任何一个都可以用于过滤或创建数据包摘要。不过，建议只使用BOB，并且应该使用BOB。
The REQUIRED algorithm-specific Information Elements in case of Hash-based Selection are:
在基于散列的选择情况下，所需的特定于算法的信息元素为：
hashIPPayloadOffset - The payload offset used by a Hash-based Selection Selector
hashIPPayloadOffset—基于哈希的选择选择器使用的有效负载偏移量
hashIPPayloadSize - The payload size used by a Hash-based Selection Selector
hashIPPayloadSize—基于哈希的选择选择器使用的有效负载大小
hashOutputRangeMin - One or more values for the beginning of each potential output range.
hashOutputRangeMin-每个潜在输出范围开头的一个或多个值。
hashOutputRangeMax - One or more values for the end of each potential output range.
hashOutputRangeMax—每个潜在输出范围末尾的一个或多个值。
hashSelectedRangeMin - One or more values for the beginning of each selected range.
hashSelectedRangeMin-每个选定范围开头的一个或多个值。
hashSelectedRangeMax - One or more values for the end of each selected range.
hashSelectedRangeMax—每个选定范围末尾的一个或多个值。
hashDigestOutput - A boolean value, TRUE if the output from this Selector has been configured to be included in the Packet Report as a packet digest.
hashDigestOutput—一个布尔值，如果此选择器的输出已配置为作为数据包摘要包含在数据包报告中，则为TRUE。
Note: If more than one selection or output range needs to be sent, then the minimum and maximum elements may be repeated as needed. These MUST make one or more non-overlapping ranges. The elements SHOULD be sent as pairs of minimum and maximum in ascending order; however, if they are sent out of order, then there will only be one way to interpret the ranges to produce a non-overlapping range and the Collecting Process MUST be prepared to accept and decode this.
注：如果需要发送多个选择或输出范围，则可根据需要重复最小和最大元素。这些必须形成一个或多个非重叠范围。元素应以最小值和最大值对的升序发送；但是，如果它们的发送顺序不正确，那么只有一种方法可以解释这些范围以产生一个不重叠的范围，并且收集过程必须准备好接受和解码这一点。
The following algorithm-specific Information Element MAY be sent, but is optional for security considerations:
可以发送以下特定于算法的信息元素，但出于安全考虑，这是可选的：
hashInitialiserValue - The initialiser value to the Hash Function.
HashInitializerValue—哈希函数的初始化器值。
Since encryption alters the meaning of encrypted fields, when the Hash-based Filtering classification is based on the encrypted field(s) in the packet, it MUST be able to recognize that the field(s) are not available and MUST NOT select those packets. Even if they are ignored, the encrypted packets MUST be accounted for in the Selector packetsObserved Information Element [RFC5477], which is part of the Selection Sequence Statistics Report Interpretation.
由于加密改变了加密字段的含义，当基于散列的过滤分类基于数据包中的加密字段时，它必须能够识别字段不可用并且不能选择那些数据包。即使忽略了加密包，也必须在选择器包服务信息元素[RFC5477]中说明加密包，该元素是选择序列统计信息报告解释的一部分。
Example of a Hash-based Filter Selector, whose configuration is: Hash Function = BOB Hash IP Payload Offset = 0 Hash IP Payload Size = 16 Hash Initialiser Value = 0x9A3F9A3F Hash Output Range = 0 to 0xFFFFFFFF Hash Selected Range = 100 to 200 and 400 to 500
基于哈希的筛选器选择器示例，其配置为：哈希函数=BOB哈希IP有效负载偏移量=0哈希IP有效负载大小=16哈希初始化器值=0x9A3F9A3F哈希输出范围=0到0xFFFFFF哈希选择范围=100到200和400到500
IPFIX Options Template Record:
IPFIX选项模板记录：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 3 | Length = 50 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 269 | Field Count = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope Field Count = 1 |0| selectorId = 302 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope 1 Length = 4 |0| selectorAlgorithm = 302 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 1 |0| hashIPpayloadOffset = 327 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |0| hashIPpayloadSize = 328 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |0| hashInitialiserValue = 329 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |0| hashOutputRangeMin = 330 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |0| hashOutputRangeMax = 331 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |0| hashSeletionRangeMin = 332 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |0| hashSeletionRangeMax = 333 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |0| hashSeletionRangeMin = 332 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |0| hashSeletionRangeMax = 333 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 3 | Length = 50 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 269 | Field Count = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope Field Count = 1 |0| selectorId = 302 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope 1 Length = 4 |0| selectorAlgorithm = 302 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 1 |0| hashIPpayloadOffset = 327 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |0| hashIPpayloadSize = 328 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |0| hashInitialiserValue = 329 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |0| hashOutputRangeMin = 330 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |0| hashOutputRangeMax = 331 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |0| hashSeletionRangeMin = 332 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |0| hashSeletionRangeMax = 333 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |0| hashSeletionRangeMin = 332 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |0| hashSeletionRangeMax = 333 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Associated IPFIX Data Record:
关联的IPFIX数据记录：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 266 | Length = 45 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 22 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 6 | ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... 0 | ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... 16 | 0x9A3F9A ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... 3F | ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... 0 | 0xFFFFFF ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... FF | ... 100 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... | ... 200 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... | ... 400 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... | ... 500 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... |
+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 266 | Length = 45 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 22 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 6 | ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... 0 | ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... 16 | 0x9A3F9A ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... 3F | ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... 0 | 0xFFFFFF ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... FF | ... 100 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... | ... 200 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... | ... 400 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... | ... 500 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... |
+-+-+-+-+-+-+-+-+
Figure M: Example of the Selector Report Interpretation for Hash-based Filtering
图M：基于哈希的筛选的选择器报告解释示例
Notes:
笔记：
* A selectorAlgorithm value of 6 represents Hash-based Filtering using the BOB algorithm.
* selectorAlgorithm值6表示使用BOB算法的基于哈希的过滤。
Some potential new selection methods MAY be added. Some of the new selection methods, such as non-uniform probabilistic Sampling and flow-state-dependent Sampling, are described in [RFC5475], with further references.
可能会添加一些潜在的新选择方法。[RFC5475]中描述了一些新的选择方法，如非均匀概率抽样和流量状态相关抽样，并提供了进一步的参考资料。
Each new selection method MUST be assigned a unique value for the selectorAlgorithm Information Element. Its configuration parameter(s), along with the way to report it/them with an Options Template, MUST be clearly specified.
每个新的选择方法必须为selectorAlgorithm信息元素指定一个唯一的值。必须明确指定其配置参数以及使用选项模板报告的方式。
A Selector MAY be used in multiple Selection Sequences. However, each use of a Selector must be independent, so each separate logical instance of a Selector MUST maintain its own individual Selection State and statistics.
选择器可用于多个选择序列。但是，选择器的每次使用都必须是独立的，因此选择器的每个独立逻辑实例必须维护其各自的选择状态和统计信息。
The Selection Sequence Statistics Report Interpretation MUST include the number of observed packets (Population Size) and the number of packets selected (Sample Size) by each instance of its Primitive Selectors.
选择序列统计报告解释必须包括观察到的数据包数量（总体大小）和由其原语选择器的每个实例选择的数据包数量（样本大小）。
Within a Selection Sequence composed of several Primitive Selectors, the number of packets selected for one Selector is equal to the number of packets seen by the next Selector. The order of the Selectors in the Selection Sequence Statistics Report Interpretation MUST match the order of the Selectors in the Selection Sequence.
在由几个基本选择器组成的选择序列中，为一个选择器选择的数据包数等于下一个选择器看到的数据包数。选择序列统计信息报表解释中选择器的顺序必须与选择序列中选择器的顺序相匹配。
If the full set of statistics is not sent as part of the Basic Packet Reports, the PSAMP Device MUST export a Selection Sequence Statistics Report Interpretation for every Selection Sequence, using an Options Template containing the following Information Elements:
如果完整的统计数据集未作为基本数据包报告的一部分发送，PSAMP设备必须使用包含以下信息元素的选项模板导出每个选择序列的选择序列统计数据报告解释：
Scope: selectionSequenceId Non-scope: packetsObserved packetsSelected (first Selector) ... packetsSelected (last Selector)
作用域：selectionSequenceId非作用域：packetsObserved packetsSelected（第一个选择器）。。。已选择包（最后一个选择器）
The packetsObserved Information Element [RFC5477] MUST contain the number of packets seen at the Observation Point, and as a consequence passed to the first Selector in the Selection Sequence. The packetsSelected Information Element [RFC5477] contains the number of packets selected by a Selector in the Selection Sequence.
packetsObserved信息元素[RFC5477]必须包含在观察点看到的数据包数量，并因此传递给选择序列中的第一个选择器。packetsSelected信息元素[RFC5477]包含选择器在选择序列中选择的数据包数量。
The Attained Selection Fraction for the Selection Sequence is calculated by dividing the number of selected packets (packetsSelected Information Element) for the last Selector by the number of observed packets (packetsObserved Information Element). The Attained Selection Fraction can be calculated for each Selector by dividing the number of packets selected for that Selector by the value for the previous Selector.
通过将最后一个选择器的选定数据包（packetsSelected信息元素）的数量除以观察到的数据包（packetsObserved信息元素）的数量来计算所获得的选择序列的选择分数。通过将为该选择器选择的数据包数量除以前一个选择器的值，可以为每个选择器计算获得的选择分数。
The statistics for the whole sequence SHOULD be taken at a single logical point in time; the input value for a Selector MUST equal the output value of the previous Selector.
整个序列的统计应在单个逻辑时间点进行；选择器的输入值必须等于上一个选择器的输出值。
The Selection Sequence Statistics Report Interpretation MUST be exported periodically.
必须定期导出选择序列统计信息报告解释。
Example of Selection Sequence Statistics Report Interpretation:
选择序列统计报告解释示例：
Selection Sequence 7 (Filter->Sampling):
选择顺序7（过滤器->采样）：
Observed 100 (observationPointId 1, Interface 5) Selected 50 (selectorId 5, match IPV4SourceAddress 192.0.2.1) Selected 6 (selectorId 10, Sampler: Random one out-of ten)
观察100（观察点ID 1，接口5）选择50（selectorId 5，匹配IPV4SourceAddress 192.0.2.1）选择6（selectorId 10，采样器：十分之一随机）
Selection Sequence 9 (Sampling->Filtering):
选择顺序9（采样->过滤）：
Observed 100 (observationPointId 1, Interface 5) Selected 10 (selectorId 10, Sampler: Random one out-of ten) Selected 3 (selectorId 5, match IPV4SourceAddress 192.0.2.1)
观察100（观察点ID 1，接口5）选择10（selectorId 10，采样器：随机十选一）选择3（selectorId 5，匹配IPV4SourceAddress 192.0.2.1）
IPFIX Options Template Record:
IPFIX选项模板记录：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 3 | Length = 26 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 267 | Field Count = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope Field Count = 1 |0| selectionSequenceId = 301 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope 1 Length = 4 |0| packetsObserved = 318 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |0| packetsSelected = 319 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |0| packetsSelected = 319 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 3 | Length = 26 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 267 | Field Count = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope Field Count = 1 |0| selectionSequenceId = 301 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope 1 Length = 4 |0| packetsObserved = 318 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |0| packetsSelected = 319 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |0| packetsSelected = 319 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The associated IPFIX Data Record:
关联的IPFIX数据记录：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 267 | Length = 36 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 7 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 100 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 50 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 6 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 9 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 100 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 10 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 267 | Length = 36 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 7 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 100 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 50 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 6 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 9 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 100 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 10 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure N: Example of the Selection Sequence Statistics Report Interpretation
图N：选择序列统计报告解释示例
Notes:
笔记：
* The Attained Selection Fractions for Selection Sequence 7 are: Filter 10: 50/100 Sampler 5: 6/50 Number of samples selected: 6
* 获得的选择序列7的选择分数为：过滤器10:50/100取样器5:6/50选择的样本数：6
* The Attained Selection Fractions for Selection Sequence 9 are: Sampler 5: 10/100 Filter 10: 3/10 Number of samples selected: 3
* 获得的选择序列9的选择分数为：取样器5:10/100过滤器10:3/10选择的样本数：3
In order for the Collecting Process to determine the inherent accuracy of the reported quantities (for example, timestamps), the PSAMP Device SHOULD send an Accuracy Report Interpretation.
为了让采集过程确定报告数量的固有准确性（例如，时间戳），PSAMP设备应发送精度报告解释。
The Accuracy Report Interpretation MUST be exported by an Options Template Record with a scope that contains the Information Element for which the accuracy is required. In case the accuracy is specific
精度报告解释必须通过选项模板记录导出，其范围包含要求精度的信息元素。如果准确度是特定的
to a template, a second scope containing the templateId value MUST be added to the Options Template Record. The accuracy SHOULD be reported either with the absoluteError Information Element [RFC5477] or with the relativeError Information Element [RFC5477].
对于模板，必须将包含templateId值的第二个作用域添加到选项模板记录中。应使用绝对误差信息元素[RFC5477]或相对误差信息元素[RFC5477]报告精度。
Accuracy Report Interpretation using the absoluteError Information Element: Scope: informationElementId Non-scope: absoluteError
使用绝对错误信息元素的精度报告解释：范围：信息元素ID非范围：绝对错误
Accuracy Report Interpretation using the absoluteError Information Element and a double scope: Scope: templateId informationElementId Non-scope: absoluteError
使用absoluteError信息元素和双作用域：作用域：templateId信息元素ID非作用域：absoluteError解释精度报告
Accuracy Report Interpretation using the relativeError Information Element: Scope: informationElementId Non-scope: relativeError
使用relativeError信息元素的精度报告解释：范围：信息元素ID非范围：relativeError
Accuracy Report Interpretation using the relativeError Information Element and a double scope: Scope: templateId informationElementId Non-scope: relativeError
使用relativeError信息元素和双作用域：scope:templateId informationElementId非作用域：relativeError解释精度报告
For example, the accuracy of an Information Element whose Abstract Data Type is dateTimeMilliseconds [RFC5102], for which the unit is specified as milliseconds, can be specified with the absoluteError Information Element with the milliseconds units. In this case, the error interval is the Information Element value +/- the value reported in the absoluteError.
例如，抽象数据类型为DateTimeMillicles[RFC5102]的信息元素的精度（单位指定为毫秒）可以使用绝对错误信息元素和毫秒单位指定。在这种情况下，错误间隔是信息元素值+/-绝对错误中报告的值。
For example, the accuracy of an Information Element to estimate the accuracy of a sampled flow, for which the unit would be specified in octets, can be specified with the relativeError Information Element with the octet units. In this case, the error interval is the Information Element value +/- the value reported in the relativeError times the reported Information Element value.
例如，用于估计采样流精度的信息元素的精度（单位将以八位字节为单位指定）可以使用具有八位字节单位的相对误差信息元素来指定。在这种情况下，错误间隔是信息元素值+/-relativeError中报告的值乘以报告的信息元素值。
An alternative to reporting either the absoluteError Information Element or the relativeError Information Element in the Accuracy Report Interpretation, is to report both. For this case whatever is least accurate for the reported value should be used.
在精度报告解释中报告绝对错误信息元素或相对错误信息元素的另一种方法是报告两者。在这种情况下，应使用最不准确的报告值。
If the accuracy of a reported quantity changes on the Metering Process, a new Accuracy Report Interpretation MUST be generated. The
如果计量过程中报告数量的精度发生变化，则必须生成新的精度报告解释。这个
Collecting Process MUST keep the accuracy of the latest Accuracy Report Interpretation.
收集过程必须保持最新准确度报告解释的准确性。
Example of an Accuracy Report Interpretation using the absoluteError Information Element and a double scope: the timeMicroseconds contained in the Template 5 has an accuracy of +/- 2 ms, represented by the absoluteError Information Element.
使用绝对误差信息元素和双范围的精度报告解释示例：模板5中包含的时间微秒的精度为+/-2 ms，由绝对误差信息元素表示。
Scope: templateId = 6
informationElementId = timeMicroseconds
Non-scope: absoluteError = 2 ms
Scope: templateId = 6
informationElementId = timeMicroseconds
Non-scope: absoluteError = 2 ms
IPFIX Options Template Record:
IPFIX选项模板记录：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 3 | Length = 22 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 267 | Field Count = 3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope Field Count = 2 |0| templateId = 145 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope 1 Length = 2 |0| InformationElementId = 303 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope 2 Length = 2 |0| absoluteError = 320 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 3 | Length = 22 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 267 | Field Count = 3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope Field Count = 2 |0| templateId = 145 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope 1 Length = 2 |0| InformationElementId = 303 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope 2 Length = 2 |0| absoluteError = 320 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The associated IPFIX Data Record:
关联的IPFIX数据记录：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 267 | Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 5 | 324 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 2 (encoded as a float32) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 267 | Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 5 | 324 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 2 (encoded as a float32) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure O: Example of the Selection Sequence Statistics Report Interpretation
图O：选择序列统计报告解释示例
Notes:
笔记：
* absoluteError is of type float64 but is compressed down to a float32 here.
* absoluteError的类型为float64，但在这里被压缩为float32。
The second example displays an Accuracy Report Interpretation using the relativeError Information Element and a single scope: the timeMicroseconds has an error of 5%, represented by the proportionalAccuracy Information Element.
第二个示例显示了使用relativeError信息元素和单个范围的精度报告解释：timeMicroseconds的误差为5%，由比例精度信息元素表示。
Scope: informationElementId = timeMicroseconds
Non-scope: relativeError = 0.05
Scope: informationElementId = timeMicroseconds
Non-scope: relativeError = 0.05
IPFIX Options Template Record:
IPFIX选项模板记录：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 3 | Length = 18 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 268 | Field Count = 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope Field Count = 1 |0| InformationElementId = 303 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope 1 Length = 2 |0| relativeError= 321 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 3 | Length = 18 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 268 | Field Count = 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope Field Count = 1 |0| InformationElementId = 303 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope 1 Length = 2 |0| relativeError= 321 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The associated IPFIX Data Record:
关联的IPFIX数据记录：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 267 | Length = 10 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 324 | 0.05 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ...(encoded as a float32) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 267 | Length = 10 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 324 | 0.05 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ...(encoded as a float32) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure P: Example of the Selection Sequence Statistics Report Interpretation
图P：选择序列统计报告解释示例
Notes:
笔记：
* relativeError is of type float64 but is compressed down to a float32 here.
* relativeError的类型为float64，但在这里被压缩为float32。
As IPFIX has been selected as the PSAMP export protocol and as the PSAMP security requirements are not stricter than the IPFIX security requirements, refer to the IPFIX export protocol [RFC5101] for the security considerations.
由于IPFIX已被选为PSAMP导出协议，且PSAMP安全要求并不比IPFIX安全要求更严格，有关安全注意事项，请参阅IPFIX导出协议[RFC5101]。
In the basic Packet Report, a PSAMP Device exports some number of contiguous bytes from the start of the packet, including the packet header (which includes link layer, network layer, and other encapsulation headers) and some subsequent bytes of the packet payload. The PSAMP Device SHOULD NOT export the full payload of conversations, as this would mean wiretapping [RFC2804]. The PSAMP Device MUST respect local privacy laws.
在基本分组报告中，PSAMP设备从分组的开始导出一定数量的连续字节，包括分组报头（包括链路层、网络层和其他封装报头）和分组有效载荷的一些后续字节。PSAMP设备不应导出会话的全部有效负载，因为这意味着窃听[RFC2804]。PSAMP设备必须遵守当地隐私法。
The PSAMP protocol, 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 [RFC5226], "Guidelines for IANA Considerations".
如本文件所述，PSAMP协议有两组指定编号。本节将使用[RFC5226]“IANA注意事项指南”中规定的示例策略讨论分配注意事项。
As the PSAMP protocol uses the IPFIX protocol, refer to the IANA considerations section in [RFC5101] for the assignments of numbers used in the protocol and for the numbers used in the information model.
由于PSAMP协议使用IPFIX协议，请参阅[RFC5101]中的IANA注意事项部分，了解协议中使用的编号分配和信息模型中使用的编号。
Each new selection method MUST be assigned a unique value for the selectorAlgorithm Information Element [RFC5477]. Initial contents of this registry are found in Section 8.2.1 in [RFC5477]. Its configuration parameter(s), along with the way to report them with an Options Template, MUST be clearly specified.
每个新的选择方法必须为selectorAlgorithm信息元素[RFC5477]指定一个唯一的值。该注册表的初始内容见[RFC5477]第8.2.1节。必须明确指定其配置参数以及使用选项模板报告这些参数的方法。
New assignments for the PSAMP selection method will be administered by IANA, on a First Come First Served basis [RFC5226], 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. These experts will initially be drawn from the Working Group Chairs and document editors of the IPFIX and PSAMP Working Groups.
PSAMP选择方法的新任务将由IANA管理，先到先得[RFC5226]，并接受专家评审[RFC5226]。专家组必须使用已定义的信息元素对信息元素定义进行双重检查，以确保其完整性、准确性和冗余性。这些专家最初将来自IPFIX和PSAMP工作组的工作组主席和文件编辑。
[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月。
[RFC5101] Claise, B., Ed., "Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of IP Traffic Flow Information", RFC 5101, January 2008.
[RFC5101]Claise，B.，Ed.，“交换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月。
[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月。
[RFC5475] Zseby, T., Molina, M., Duffield, N., Niccolini, S., and F. Raspall, "Sampling and Filtering Techniques for IP Packet Selection", RFC 5475, March 2009.
[RFC5475]Zseby，T.，Molina，M.，Duffield，N.，Niccolini，S.，和F.Raspall，“IP数据包选择的采样和过滤技术”，RFC 5475，2009年3月。
[RFC5477] Dietz, T., Claise, B., Aitken, P., Dressler, F., and G. Carle, "Information Model for Packet Sampling Exports", RFC 5477, March 2009.
[RFC5477]Dietz，T.，Claise，B.，Aitken，P.，Dressler，F.，和G.Carle，“数据包抽样出口的信息模型”，RFC 5477，2009年3月。
[RFC2804] IAB and IESG, "IETF Policy on Wiretapping", RFC 2804, May 2000.
[RFC2804]IAB和IESG，“IETF关于窃听的政策”，RFC28042000年5月。
[RFC3917] Quittek, J., Zseby, T., Claise, B., and S. Zander, "Requirements for IP Flow Information Export (IPFIX)", RFC 3917, October 2004.
[RFC3917]Quitek，J.，Zseby，T.，Claise，B.，和S.Zander，“IP流信息导出（IPFIX）的要求”，RFC 39172004年10月。
[RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A Border Gateway Protocol 4 (BGP-4)", RFC 4271, January 2006.
[RFC4271]Rekhter，Y.，Ed.，Li，T.，Ed.，和S.Hares，Ed.，“边境网关协议4（BGP-4）”，RFC 42712006年1月。
[RFC5470] Sadasivan, G., Brownlee, N., Claise, B., and J. Quittek, "Architecture for IP Flow Information Export" RFC 5470, March 2009.
[RFC5470]Sadasivan，G.，Brownlee，N.，Claise，B.，和J.Quitek，“IP流信息导出架构”，RFC 54702009年3月。
[RFC5474] Duffield, N., Ed., "A Framework for Packet Selection and Reporting", RFC 5474, March 2009.
[RFC5474]Duffield，N.，Ed.“数据包选择和报告框架”，RFC 5474，2009年3月。
The authors would like to thank the PSAMP group, especially Paul Aitken for fruitful discussions and for proofreading the document several times.
作者要感谢PSAMP小组，特别是Paul Aitken，他们进行了富有成效的讨论，并多次校对了文件。
Authors' Addresses
作者地址
Benoit Claise Cisco Systems De Kleetlaan 6a b1 1831 Diegem Belgium
Benoit Claise Cisco Systems De Kleetlaan 6a b1 1831 Diegem比利时
Phone: +32 2 704 5622
EMail: bclaise@cisco.com
Phone: +32 2 704 5622
EMail: bclaise@cisco.com
Juergen Quittek NEC Europe Ltd. Network Laboratories Kurfuersten-Anlage 36 69115 Heidelberg Germany
德国海德堡Juergen Quittek NEC欧洲有限公司网络实验室Kurfuersten Anlage 36 69115
Phone: +49 6221 90511-15
EMail: quittek@nw.neclab.eu
Phone: +49 6221 90511-15
EMail: quittek@nw.neclab.eu
Andrew Johnson Cisco Systems 96 Commercial Quay Edinburgh EH6 6LX Scotland
安德鲁·约翰逊思科系统96商业码头爱丁堡EH6 6LX苏格兰
Phone: +44 131 561 3641
EMail: andrjohn@cisco.com
Phone: +44 131 561 3641
EMail: andrjohn@cisco.com