Network Working Group C. Schmoll
Request for Comments: 5471 Fraunhofer FOKUS
Category: Informational P. Aitken
B. Claise
Cisco Systems, Inc.
March 2009
Network Working Group C. Schmoll
Request for Comments: 5471 Fraunhofer FOKUS
Category: Informational P. Aitken
B. Claise
Cisco Systems, Inc.
March 2009
Guidelines for IP Flow Information Export (IPFIX) Testing
IP流信息导出（IPFIX）测试指南
Status of This Memo
关于下段备忘
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。
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 presents a list of tests for implementers of IP Flow Information eXport (IPFIX) compliant Exporting Processes and Collecting Processes. This document specifies guidelines for a series of tests that can be run on the IPFIX Exporting Process and Collecting Process in order to probe the conformity and robustness of the IPFIX protocol implementations. These tests cover all important functions, in order to gain a level of confidence in the IPFIX implementation. Therefore, they allow the implementer to perform interoperability or plug tests with other IPFIX Exporting Processes and Collecting Processes.
本文档为符合IP流信息导出（IPFIX）的导出过程和收集过程的实施者提供了测试列表。本文件规定了可在IPFIX导出过程和收集过程上运行的一系列测试的指南，以探索IPFIX协议实施的一致性和健壮性。这些测试涵盖了所有重要功能，以便在IPFIX实现中获得一定程度的信心。因此，它们允许实现者与其他IPFIX导出过程和收集过程执行互操作性或插件测试。
Table of Contents
目录
1. Introduction ....................................................4
1.1. Document Scope .............................................4
1.2. IPFIX Documents Overview ...................................5
2. Terminology .....................................................5
2.1. Conventions Used in This Document ..........................5
3. Test Specifications .............................................5
3.1. Exporting Process/Collecting Process Connectivity Tests ....6
3.1.1. Connectivity Tests between the Exporting
Process and Collecting ..............................6
3.2. Template and Data Record Tests .............................6
3.2.1. Transmission of Template with Fixed-Size
Information Elements ................................7
3.2.2. Transmission of Template with
Variable-Length Information Elements ................7
3.2.3. Set Padding .........................................7
3.2.4. Record Padding ......................................8
3.2.5. Template Withdrawal Message .........................9
3.3. Information Element Tests .................................11
3.3.1. Enterprise-Specific Information Elements ...........11
3.3.2. Reduced Size Encoding of Information Elements ......11
3.3.3. Multiple Instances of the Same Information
Element in One Template.............................12
3.4. Options Template Tests ....................................12
3.4.1. Using Any Information Elements as Scope ............12
3.4.2. Using Multiple Scopes ..............................13
3.4.3. Metering Process Statistics Option Template ........13
3.4.4. Metering Process Reliability Statistics
Option Template ....................................14
3.4.5. Exporting Process Reliability Statistics
Option Template ....................................14
3.4.6. Flow Keys Option Template ..........................14
1. Introduction ....................................................4
1.1. Document Scope .............................................4
1.2. IPFIX Documents Overview ...................................5
2. Terminology .....................................................5
2.1. Conventions Used in This Document ..........................5
3. Test Specifications .............................................5
3.1. Exporting Process/Collecting Process Connectivity Tests ....6
3.1.1. Connectivity Tests between the Exporting
Process and Collecting ..............................6
3.2. Template and Data Record Tests .............................6
3.2.1. Transmission of Template with Fixed-Size
Information Elements ................................7
3.2.2. Transmission of Template with
Variable-Length Information Elements ................7
3.2.3. Set Padding .........................................7
3.2.4. Record Padding ......................................8
3.2.5. Template Withdrawal Message .........................9
3.3. Information Element Tests .................................11
3.3.1. Enterprise-Specific Information Elements ...........11
3.3.2. Reduced Size Encoding of Information Elements ......11
3.3.3. Multiple Instances of the Same Information
Element in One Template.............................12
3.4. Options Template Tests ....................................12
3.4.1. Using Any Information Elements as Scope ............12
3.4.2. Using Multiple Scopes ..............................13
3.4.3. Metering Process Statistics Option Template ........13
3.4.4. Metering Process Reliability Statistics
Option Template ....................................14
3.4.5. Exporting Process Reliability Statistics
Option Template ....................................14
3.4.6. Flow Keys Option Template ..........................14
3.5. Stress/Load Tests .........................................15
3.5.1. Large Number of Records for One Template ...........15
3.5.2. Excessive Rate of Incoming Data Records ............15
3.5.3. Large Templates ....................................16
3.5.4. Many New Templates within the Data Template
Timeout Interval ...................................16
3.5.5. Multiple Exporting Processes Exporting to
One Collecting Process .............................17
3.5.6. Export from One Exporting Process to
Multiple Collecting Processes ......................17
3.6. Error Handling ............................................17
3.6.1. Temporary Network Disconnect .......................17
3.6.2. Exporting Process Termination and Restart
during Data Transmission ...........................18
3.6.3. Collecting Process Termination and Restart
during Data Transmission ...........................18
3.6.4. Incorrect Template Records and Options
Template Records ...................................19
3.6.5. Incorrect Data Record ..............................22
3.6.6. Export of Non-Matching Template and Data Records ...23
3.6.7. Unknown Set IDs ....................................23
3.6.8. Re-Using Template IDs ..............................24
3.7. TLS Connectivity and Policy Selection .....................28
3.7.1. TLS Test Setup .....................................28
3.7.2. TLS over TCP Connectivity Test .....................29
3.7.3. DTLS over UDP Connectivity Test ....................29
3.7.4. DTLS over PR-SCTP Connectivity Test ................29
3.7.5. TLS Bidirectional Authentication Policy Test .......30
3.7.6. Exporting Process Identity Mismatch TLS
Policy Test ........................................30
3.7.7. Collecting Process Identity Mismatch TLS
Policy Test ........................................30
4. Security Considerations ........................................30
5. Acknowledgments ................................................31
6. Normative References ...........................................31
3.5. Stress/Load Tests .........................................15
3.5.1. Large Number of Records for One Template ...........15
3.5.2. Excessive Rate of Incoming Data Records ............15
3.5.3. Large Templates ....................................16
3.5.4. Many New Templates within the Data Template
Timeout Interval ...................................16
3.5.5. Multiple Exporting Processes Exporting to
One Collecting Process .............................17
3.5.6. Export from One Exporting Process to
Multiple Collecting Processes ......................17
3.6. Error Handling ............................................17
3.6.1. Temporary Network Disconnect .......................17
3.6.2. Exporting Process Termination and Restart
during Data Transmission ...........................18
3.6.3. Collecting Process Termination and Restart
during Data Transmission ...........................18
3.6.4. Incorrect Template Records and Options
Template Records ...................................19
3.6.5. Incorrect Data Record ..............................22
3.6.6. Export of Non-Matching Template and Data Records ...23
3.6.7. Unknown Set IDs ....................................23
3.6.8. Re-Using Template IDs ..............................24
3.7. TLS Connectivity and Policy Selection .....................28
3.7.1. TLS Test Setup .....................................28
3.7.2. TLS over TCP Connectivity Test .....................29
3.7.3. DTLS over UDP Connectivity Test ....................29
3.7.4. DTLS over PR-SCTP Connectivity Test ................29
3.7.5. TLS Bidirectional Authentication Policy Test .......30
3.7.6. Exporting Process Identity Mismatch TLS
Policy Test ........................................30
3.7.7. Collecting Process Identity Mismatch TLS
Policy Test ........................................30
4. Security Considerations ........................................30
5. Acknowledgments ................................................31
6. Normative References ...........................................31
An IPFIX implementation, whether in software, firmware, or hardware, needs to be tested thoroughly in order to check its robustness and gain confidence in the conformity to the IPFIX documents on which it is based.
IPFIX实施，无论是在软件、固件还是硬件中，都需要进行彻底测试，以检查其健壮性，并对其所依据的IPFIX文档的一致性获得信心。
For a testable IPFIX software tool kit, one needs at least one IPFIX Exporting Process and one IPFIX Collecting Process. However, when one has, for example, only implemented a Collector, then it can be complemented with a third-party Exporter for these tests.
对于可测试的IPFIX软件工具包，至少需要一个IPFIX导出过程和一个IPFIX收集过程。但是，例如，如果只实现了收集器，则可以使用第三方导出器来补充这些测试。
This document specifies guidelines for a series of tests that can be run on the IPFIX Exporting Process and Collecting Process in order to probe the conformity and robustness of the IPFIX protocol implementations.
本文件规定了可在IPFIX导出过程和收集过程上运行的一系列测试的指南，以探索IPFIX协议实施的一致性和健壮性。
The tests listed here can form a valuable common basis for implementers involved in interoperability testing when all of them use these tests to check their own Exporting Process and Collecting Process implementation first.
当所有参与互操作性测试的实现者都使用这些测试来检查自己的导出流程和首先收集流程实现时，这里列出的测试可以为他们提供一个有价值的通用基础。
The tests can be executed in a testbed environment or on a live network.
这些测试可以在测试台环境或实时网络上执行。
However, care should be taken regarding the "stress/load test" and the "temporary network disconnect", as they might impact other systems in the network. We recommend that these specific tests should be executed only in a testbed environment.
但是，应注意“压力/负载测试”和“临时网络断开”，因为它们可能会影响网络中的其他系统。我们建议这些特定的测试只能在测试环境中执行。
This document lists tests intended to be performed between an implementation of an IPFIX Exporting Process and an IPFIX Collecting Process. For some tests, multiple instances of each of those components (Observation Points, Metering Process, Exporting Process, Collecting Process) are involved. The testing of those different IPFIX components complicates the testing as usually one tests his software against an existing implementation, which is proven to be compliant. In some cases, two unproven implementations of the Exporting Process and Collecting Process must be tested against each other. The tests range from basic transport connectivity to export of Template and associated Data Records, high load on the Collecting Process, and error condition situations. This document is not intended as a replacement for formal testing software procedures based on, e.g., TTCN3 (http://www.ttcn-3.org/) but as a best-practices approach to an informal testing of a developer's IPFIX implementation.
本文档列出了在IPFIX导出过程和IPFIX收集过程之间执行的测试。对于某些测试，每个组件（观察点、计量过程、导出过程、收集过程）都涉及多个实例。这些不同的IPFIX组件的测试使测试变得复杂，因为通常有人会针对现有的实现测试自己的软件，而现有的实现被证明是兼容的。在某些情况下，导出过程和收集过程的两个未经验证的实现必须相互测试。测试范围从基本传输连接到模板和相关数据记录的导出、收集过程的高负载以及错误情况。本文件不打算取代基于TTCN3等标准的正式测试软件程序(http://www.ttcn-3.org/)但作为对开发人员的IPFIX实现进行非正式测试的最佳实践方法。
The IPFIX protocol [RFC5101] provides network administrators with access to IP Flow information. The architecture for the export of measured IP Flow information out of an IPFIX Exporting Process to a Collecting Process is defined in [RFC5470], per the requirements specified in [RFC3917].
IPFIX协议[RFC5101]为网络管理员提供了访问IP流信息的权限。根据[RFC3917]中规定的要求，[RFC5470]中定义了将测量的IP流信息从IPFIX导出过程导出到收集过程的体系结构。
[RFC5470] specifies how IPFIX Data Records and Templates are carried via a congestion-aware transport protocol from IPFIX Exporting Processes to IPFIX Collecting Processes. IPFIX has a formal description of IPFIX Information Elements, their name, type, and additional semantic information, as specified in [RFC5102]. Finally, [RFC5472] describes what type of applications can use the IPFIX protocol and how they can use the information provided. It furthermore shows how the IPFIX framework relates to other architectures and frameworks.
[RFC5470]指定如何通过拥塞感知传输协议将IPFIX数据记录和模板从IPFIX导出进程传送到IPFIX收集进程。IPFIX对IPFIX信息元素、它们的名称、类型和附加语义信息进行了形式化描述，如[RFC5102]中所述。最后，[RFC5472]描述了什么类型的应用程序可以使用IPFIX协议，以及它们如何使用提供的信息。它还展示了IPFIX框架与其他体系结构和框架的关系。
IPFIX-specific terminology used in this document is defined in Section 2 of [RFC5101]. In this document, as in [RFC5101], the first letter of each IPFIX-specific term is capitalized.
[RFC5101]第2节定义了本文件中使用的IPFIX专用术语。在本文件中，与[RFC5101]中一样，每个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 [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[RFC2119]中所述进行解释。
The tests described in this section MAY be performed using an IPFIX Exporting Process on one host and an IPFIX Collecting Process on a different host. The configuration of the Observation Point, Metering Process, Exporting Process, and Collection Process SHOULD be recorded for every test along with the test results.
可以在一台主机上使用IPFIX导出进程，在另一台主机上使用IPFIX收集进程来执行本节中描述的测试。每次试验应记录观测点配置、计量过程、输出过程和收集过程以及试验结果。
The successful execution of all tests described in this section will give the tester a high confidence that the tested implementation is conformant with the IPFIX architecture and protocol. It does however not provide a 100% comprehensive coverage or formal proof of conformance.
成功执行本节中描述的所有测试将使测试人员对测试的实现符合IPFIX体系结构和协议有很高的信心。但是，它没有提供100%的全面覆盖范围或正式的合规性证明。
This section lists the basic tests that are preconditions for the more complex tests specified in later sections of this document.
本节列出了基本测试，这些测试是本文件后面章节中规定的更复杂测试的先决条件。
3.1.1. Connectivity Tests between the Exporting Process and Collecting Process
3.1.1. 导出进程和收集进程之间的连接测试
The tester must create one Exporting Process and one Collecting Process, must configure the Exporting Process to export at least one Template Set and associated Data Records to the Collecting Process, and must cause the Exporting Process to initiate the export.
测试仪必须创建一个导出流程和一个采集流程，必须配置导出流程以将至少一个模板集和相关数据记录导出到采集流程，并且必须使导出流程启动导出。
When the Exporting Process and Collecting Process are to be connected by a Stream Control Transmission Protocol (SCTP) transport, the tester must ensure that an SCTP association is established.
当导出过程和收集过程通过流控制传输协议（SCTP）传输连接时，测试仪必须确保建立SCTP关联。
When the Exporting Process and Collecting Process are to be connected by a TCP transport, the tester must ensure that a TCP connection is established.
当导出进程和收集进程通过TCP传输连接时，测试人员必须确保建立了TCP连接。
The tester must ensure that the Transport Session parameters (IP addresses and ports) are correct.
测试仪必须确保传输会话参数（IP地址和端口）正确。
Note that specifying instructions and tools on how to ensure that a Transport Session is correctly established and that the parameters are correct is out of the scope of this document.
请注意，指定有关如何确保正确建立传输会话以及参数正确的说明和工具超出了本文档的范围。
The tester must ensure that the Data Records are actually exported. The transmitted data might be observed online with an appropriate packet sniffing tool. Such a tool is also a viable help to check if the initial connection (SCTP, TCP) has been successfully established.
测试人员必须确保数据记录已实际导出。可以使用适当的数据包嗅探工具在线观察传输的数据。这样的工具还可以帮助检查初始连接（SCTP、TCP）是否已成功建立。
The tester must record which combinations of IPv4 and IPv6 transports, and UDP, SCTP, and TCP transmission protocols are supported, and should perform the test for all the supported combinations.
测试仪必须记录支持IPv4和IPv6传输以及UDP、SCTP和TCP传输协议的组合，并应对所有支持的组合执行测试。
This section lists tests for checking the correct transmission of IPFIX Template Sets and associated Data Sets.
本节列出了检查IPFIX模板集和相关数据集正确传输的测试。
The tester must create a Template with a few fixed-size Information Elements where each data type specified in Section 6.1 of [RFC5101] (octet, unsigned16, unsigned32 ...) is used at least once, and cause the Template and associated Data Records to be exported over all applicable combinations of transports and protocols in Section 3.1.
测试人员必须创建一个带有几个固定大小信息元素的模板，其中[RFC5101]第6.1节（八位字节，无符号16，无符号32…）中规定的每种数据类型至少使用一次，并通过第3.1节中所有适用的传输和协议组合导出模板和相关数据记录。
The tester must ensure that the Template and associated Data Records were correctly received and decoded by the Collecting Process. For this process, the use of verbose debugging output is suggested in order to allow a detailed comparison with the sent (and therefore expected) data.
测试人员必须确保采集过程正确接收并解码了模板和相关数据记录。对于此过程，建议使用详细调试输出，以便与发送的（因此也是预期的）数据进行详细比较。
3.2.2. Transmission of Template with Variable-Length Information Elements
3.2.2. 具有可变长度信息元素的模板传输
The tester must create a Template with a mixture of fixed-sized and variable-length Information Elements, as specified in Section 7 of [RFC5101], and cause the Template and associated Data Records to be exported over all applicable combinations of transports and protocols in Section 3.1.
按照[RFC5101]第7节的规定，测试人员必须创建一个混合了固定大小和可变长度信息元素的模板，并在第3.1节的所有适用传输和协议组合中导出模板和相关数据记录。
The tester must ensure that the Template contains at least:
测试仪必须确保模板至少包含：
o a single variable-length Information Element.
o 单个可变长度信息元素。
o a single variable-length Information Element followed by a fixed-length Information Element.
o 一个可变长度的信息元素，后跟一个固定长度的信息元素。
o a fixed-length Information Element followed by a variable-length Information Element.
o 固定长度的信息元素后跟可变长度的信息元素。
o multiple variable-length Information Elements.
o 多个可变长度信息元素。
The tester must ensure that the Template and associated Data Records were correctly received and decoded by the Collecting Process.
测试人员必须确保采集过程正确接收并解码了模板和相关数据记录。
Section 3.3.1 of [RFC5101] specifies IPFIX Set alignment using padding.
[RFC5101]第3.3.1节规定了使用填充的IPFIX集合对齐。
The tester must configure a packet generator to generate two Data Sets with padding in between consisting of zero valued octets, as shown in Figure 1. They must be exported to the Collecting Process, which must correctly decode the Data Sets and all the Data Records.
测试人员必须配置一个数据包生成器来生成两个数据集，两个数据集之间填充由零值八位字节组成，如图1所示。它们必须导出到采集过程，采集过程必须正确解码数据集和所有数据记录。
+--------------------------------------------------+
| Set Header #1 |
+--------------------------------------------------+
| Data Record |
+--------------------------------------------------+
| Data Record |
+--------------------------------------------------+
...
+--------------------------------------------------+
| Data Record |
+--------------------------------------------------+
| Padding with 0 valued octets |
+--------------------------------------------------+
| Set Header #2 |
+--------------------------------------------------+
| Data Record |
+--------------------------------------------------+
+--------------------------------------------------+
| Set Header #1 |
+--------------------------------------------------+
| Data Record |
+--------------------------------------------------+
| Data Record |
+--------------------------------------------------+
...
+--------------------------------------------------+
| Data Record |
+--------------------------------------------------+
| Padding with 0 valued octets |
+--------------------------------------------------+
| Set Header #2 |
+--------------------------------------------------+
| Data Record |
+--------------------------------------------------+
Figure 1
图1
The tester must configure a packet generator to generate a Template that contains the padding Information Element (i.e., paddingOctets). The Template and associated Data Records must be exported to the Collecting Process, over all applicable combinations of transports and protocols in Section 3.1.
测试人员必须配置数据包生成器，以生成包含填充信息元素（即paddingOctets）的模板。模板和相关数据记录必须通过第3.1节中所有适用的传输和协议组合导出到收集过程中。
The tester must repeat the test with various padding sizes, including padding to boundaries other than 4 or 8 octets.
测试人员必须使用不同的填充大小重复测试，包括填充到4或8个八位字节以外的边界。
The tester must ensure the Collecting Process correctly interprets cases where the Data Records are so short that the padding is equal to or longer than the length of the record, so the padding might otherwise be interpreted as another record (e.g., 1 byte TOS plus 3 bytes of padding). Refer to the specifications in Section 3.3.1 of [RFC5101]. Figure 2 depicts such a Template, while Figure 3 depicts a Data Record conforming to that Template.
测试人员必须确保采集过程正确地解释了以下情况：数据记录非常短，以至于填充长度等于或大于记录长度，因此填充可能会被解释为另一条记录（例如，1字节TOS加3字节填充）。参考[RFC5101]第3.3.1节中的规范。图2描述了这样一个模板，而图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 = 2 | Length = 16 octets |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID 256 | Field Count = 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| ipDiffServCodePoint = 195 | Field Length = 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| paddingOctets = 210 | Field Length = 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 = 2 | Length = 16 octets |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID 256 | Field Count = 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| ipDiffServCodePoint = 195 | Field Length = 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| paddingOctets = 210 | Field Length = 3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2
图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 = 256 | Length = 64 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 1 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 = 256 | Length = 64 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 1 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3
图3
The tester must test fixed-size padding (e.g., 12 bytes of data plus 2 bytes of padding) and variable-length padding (e.g., export a string and a variable number of padding bytes afterwards to align the next Information Element to a 4 byte boundary).
测试仪必须测试固定大小的填充（例如，12字节的数据加上2字节的填充）和可变长度的填充（例如，随后导出字符串和可变数量的填充字节，以便将下一个信息元素与4字节边界对齐）。
IPFIX Template management and Template Withdrawal are specified in Section 8 of [RFC5101].
[RFC5101]第8节规定了IPFIX模板管理和模板撤销。
The tester must create an IPFIX Template and cause that Template to be exported to an IPFIX Collector over a reliable transport.
测试人员必须创建IPFIX模板，并通过可靠的传输将该模板导出到IPFIX收集器。
The tester must check that the Template will be correctly received and decoded by the Collecting Process.
测试人员必须检查收集过程是否正确接收和解码模板。
The tester must cause the Exporting Process to send an IPFIX Template Withdrawal Message to the Collector in respect of the Template. The Template Withdrawal Message must be sent over the same Transport Session as the Template.
测试仪必须使导出过程向收集器发送有关模板的IPFIX模板撤回消息。模板撤回消息必须通过与模板相同的传输会话发送。
The tester must ensure that the Template Withdrawal Message was correctly received and decoded by the Collecting Process, and that the previously sent Template was discarded by the Collecting Process.
测试人员必须确保收集过程正确接收并解码了模板撤回消息，并且收集过程丢弃了先前发送的模板。
The tester must create, export, and withdraw an IPFIX Template as described in Section 3.2.5.1.
测试人员必须按照第3.2.5.1节所述创建、导出和撤消IPFIX模板。
The tester must cause the Exporting Process to send a second IPFIX Template Withdrawal Message to the Collector in respect of the same Template. The Template Withdrawal Message must be sent over the same Transport Session as the Template.
测试仪必须使导出过程向收集器发送关于同一模板的第二条IPFIX模板撤回消息。模板撤回消息必须通过与模板相同的传输会话发送。
The tester must ensure that the Collecting Process discards the IPFIX Message and shuts down the SCTP association or closes the TCP connection. The tester must check that the Collecting Process logged the error.
测试人员必须确保收集过程丢弃IPFIX消息并关闭SCTP关联或关闭TCP连接。测试仪必须检查采集过程是否记录了错误。
The tester must cause the Exporting Process to send an IPFIX Template Withdrawal Message to the Collector in respect of a Template that has not yet been exported. The Template Withdrawal Message must be sent over a reliable transport.
对于尚未导出的模板，测试仪必须使导出过程向收集器发送IPFIX模板撤回消息。模板撤回消息必须通过可靠的传输发送。
The tester must ensure that the Collecting Process discards the IPFIX Message and shuts down the SCTP association or closes the TCP connection. The tester must check that the Collecting Process logged the error.
测试人员必须确保收集过程丢弃IPFIX消息并关闭SCTP关联或关闭TCP连接。测试仪必须检查采集过程是否记录了错误。
The tester must create several IPFIX Templates and cause them to be exported to an IPFIX Collector over a reliable transport.
测试人员必须创建多个IPFIX模板，并通过可靠的传输将它们导出到IPFIX收集器。
The tester must ensure that the Templates were correctly received and decoded by the Collecting Process.
测试人员必须确保收集过程正确接收和解码了模板。
The tester must cause the Exporting Process to send an IPFIX All Data Templates Withdrawal Message to the Collector over the same Transport Session as the Templates.
测试仪必须使导出过程通过与模板相同的传输会话向收集器发送IPFIX All Data Templates RECUMENT消息。
The tester must ensure that the All Data Templates Withdrawal Message was correctly received and decoded by the Collecting Process, and that all the previously sent Templates were discarded by the Collecting Process.
测试仪必须确保收集过程正确接收并解码了所有数据模板撤回消息，并且收集过程丢弃了所有先前发送的模板。
The tester must create several IPFIX Option Templates and cause them to be exported to an IPFIX Collector over a reliable transport.
测试人员必须创建多个IPFIX选项模板，并通过可靠的传输将它们导出到IPFIX收集器。
The tester must ensure that the Option Templates were correctly received and decoded by the Collecting Process.
测试人员必须确保采集过程正确接收和解码了选项模板。
The tester must cause the Exporting Process to send an IPFIX All Option Templates Withdrawal Message to the Collector over the same Transport Session as the Templates.
测试仪必须使导出过程通过与模板相同的传输会话向收集器发送IPFIX All Option Templates RECUMENT消息。
The tester must ensure that the All Option Templates Withdrawal Message was correctly received and decoded by the Collecting Process, and that all the previously sent Option Templates were discarded by the Collecting Process.
测试仪必须确保收集过程正确接收并解码了所有选项模板撤回消息，并且收集过程丢弃了之前发送的所有选项模板。
This section lists the tests that cover the use of Information Elements.
本节列出了涵盖信息元素使用的测试。
The tester must cause the export of a Template and associated Data Record that makes use of Enterprise-specific Information Elements as specified in Section 3.2 of [RFC5101].
测试人员必须导出模板和相关数据记录，该模板和记录使用[RFC5101]第3.2节中规定的企业特定信息元素。
The tester must ensure that the Template and associated Data Record are correctly received and decoded by the Collecting Process, and it must ensure that Information Elements that are unknown to the Collecting Process are not silently discarded.
测试人员必须确保模板和相关数据记录被采集过程正确接收和解码，并且必须确保采集过程未知的信息元素不会被自动丢弃。
The tester must cause the export of a Template and associated Data Record containing Information Elements using reduced size encoding as specified in Section 6.2 of [RFC5101].
测试仪必须按照[RFC5101]第6.2节的规定，使用缩小尺寸编码导出包含信息元素的模板和相关数据记录。
The tester must ensure that in the case of Information Elements transmitted using reduced size encoding, the Collecting Process is aware of the real size of each Information Element and not only the reduced size used for its transmission.
测试仪必须确保在使用缩减编码传输信息元素的情况下，采集过程能够了解每个信息元素的实际大小，而不仅仅是用于传输的缩减大小。
3.3.3. Multiple Instances of the Same Information Element in One Template
3.3.3. 同一模板中同一信息元素的多个实例
The tester must cause the export of a Template and associated Data Record containing multiple instances of the same Information Element consecutively.
测试人员必须连续导出包含同一信息元素的多个实例的模板和相关数据记录。
The tester must ensure that the Collecting Process is able to parse the IPFIX Message, and that it stores all values received for all the Information Elements that appeared multiple times in the Template definition.
测试人员必须确保收集过程能够解析IPFIX消息，并且它存储为模板定义中多次出现的所有信息元素接收的所有值。
The tester must ensure that the Collecting Process reports the Information Elements in the same order as they were specified in the Template Record, as specified in Section 8 of [RFC5101].
测试人员必须确保收集过程按照[RFC5101]第8节规定的模板记录中规定的顺序报告信息元素。
The tester must cause the export of another Template and associated Data Record containing multiple instances of the same Information Element with other Information Elements in between.
测试人员必须导出另一个模板和关联的数据记录，其中包含同一信息元素的多个实例以及介于两者之间的其他信息元素。
The tester must ensure that the Collecting Process is able to parse the IPFIX Message, and that it stores all values received for all the Information Elements that appeared multiple times in the Template definition.
测试人员必须确保收集过程能够解析IPFIX消息，并且它存储为模板定义中多次出现的所有信息元素接收的所有值。
The tester must ensure that the Collecting Process reports the Information Elements in the same order as they were specified in the Template Record, as specified in Section 8 of [RFC5101].
测试人员必须确保收集过程按照[RFC5101]第8节规定的模板记录中规定的顺序报告信息元素。
This section lists the tests that cover the correct transfer of IPFIX Options Templates.
本节列出了涵盖IPFIX选项模板正确传输的测试。
Options Templates contain scope fields that give the context of the reported Information Elements in the corresponding Data Records. Scope fields are an Information Element specified in [RFC5102].
选项模板包含范围字段，这些字段提供相应数据记录中报告的信息元素的上下文。范围字段是[RFC5102]中指定的信息元素。
The tester SHOULD perform the export of Options Template Records containing various different Information Elements of each of the abstract data types specified in Section 6.1 of [RFC5101] (octet, unsigned16, unsigned32 ...) in their scope fields, and must export a Data Record using each Template.
测试人员应在其范围字段中导出选项模板记录，该模板记录包含[RFC5101]第6.1节中规定的每种抽象数据类型的各种不同信息元素（八位字节、无符号16、无符号32…），并且必须使用每个模板导出数据记录。
The tester must check that the Templates and the associated Data Records are correctly received and decoded by the Collecting Process.
测试人员必须检查收集过程是否正确接收并解码了模板和相关数据记录。
The tester must ensure that the Collecting Process accepts Information Elements in the scope field other than IPFIX Information Elements that have been recorded by IANA.
测试人员必须确保收集过程接受范围字段中的信息元素，而不是IANA记录的IPFIX信息元素。
The tester must ensure that the Collecting Process accepts an Enterprise-specific Information Element in the scope field.
测试人员必须确保收集过程在范围字段中接受特定于企业的信息元素。
As specified in Section 3.4.2.1 of [RFC5101], the Scope Field Count must NOT be zero. The tester must cause the export of an Options Template Record containing a Scope Field Count of zero.
根据[RFC5101]第3.4.2.1节的规定，范围字段计数不得为零。测试人员必须导出包含范围字段计数为零的选项模板记录。
The tester must ensure that the Collecting Process shuts down the SCTP association and discards the IPFIX Message. The tester should check that the Collecting Process logged the error.
测试人员必须确保收集过程关闭SCTP关联并丢弃IPFIX消息。测试仪应检查采集过程是否记录了错误。
The tester must cause the export of an Options Template Record containing multiple scope fields, and a Data Record conforming to that Template.
测试人员必须导出包含多个范围字段的选项模板记录和符合该模板的数据记录。
The tester must ensure that the Collecting Process reports the Information Elements in the same order as they were specified in the Options Template Record, as specified in Section 3.4.2.1 of [RFC5101].
测试人员必须确保收集过程按照[RFC5101]第3.4.2.1节中规定的选项模板记录中规定的顺序报告信息元素。
The tester must create a Metering Process Statistics Option Template, as specified in Section 4.1 of [RFC5101], and cause the Option Template and an associated Data Record to be exported.
测试仪必须按照[RFC5101]第4.1节的规定创建计量过程统计选项模板，并导出选项模板和相关数据记录。
The tester must ensure that the Collecting Process correctly receives and decodes the Option Template and associated Data Record.
测试仪必须确保采集过程正确接收并解码选项模板和相关数据记录。
The tester must also check that the optional meteringProcessId Scope Field is supported by the Collecting Process implementation.
测试人员还必须检查可选的meteringProcessId范围字段是否受收集过程实现的支持。
If several Metering Processes are available on the Exporter Observation Domain, the tester must create a Metering Process Statistics Option Template containing multiple scopes and an associated Data Record, must cause the Option Template and associated Data Record to be exported, and must ensure that the Collecting Process correctly receives and decodes the Option Template and associated Data Record.
如果Exporter观察域上有多个计量过程可用，测试人员必须创建一个计量过程统计选项模板，该模板包含多个作用域和关联的数据记录，必须导出选项模板和关联的数据记录，并且必须确保采集过程正确接收和解码选项模板和相关数据记录。
The tester must create a Metering Process Reliability Statistics Option Template, as specified in Section 4.2 of [RFC5101], and must cause the Option Template and an associated Data Record to be exported.
测试仪必须按照[RFC5101]第4.2节的规定创建计量过程可靠性统计选项模板，并且必须导出选项模板和相关数据记录。
The tester must ensure that the Collecting Process correctly receives and decodes the Option Template and associated Data Record.
测试仪必须确保采集过程正确接收并解码选项模板和相关数据记录。
The tester must also check that the optional meteringProcessId Scope Field is supported by the Collecting Process implementation.
测试人员还必须检查可选的meteringProcessId范围字段是否受收集过程实现的支持。
The tester must create an Exporting Process Reliability Statistics Option Template, as specified in Section 4.3 of [RFC5101], and must cause the Option Template and an associated Data Record to be exported.
测试人员必须按照[RFC5101]第4.3节的规定创建导出过程可靠性统计选项模板，并且必须导出选项模板和相关数据记录。
The tester must ensure that the Collecting Process correctly receives and decodes the Option Template and associated Data Record.
测试仪必须确保采集过程正确接收并解码选项模板和相关数据记录。
The tester must create a Flow Keys Option Template, as specified in Section 4.4 of [RFC5101], where the templateId refers to an existing Template, and must cause the Option Template and an associated Data Record to be exported.
测试仪必须按照[RFC5101]第4.4节的规定创建一个流键选项模板，其中templateId指的是一个现有模板，并且必须导出选项模板和相关数据记录。
The tester must ensure that the Collecting Process correctly receives and decodes the Option Template and associated Data Record, and it must ensure that the Collecting Process associates the Flow Keys with the right Data Record Information Elements.
测试仪必须确保采集过程正确接收和解码选项模板和相关数据记录，并且必须确保采集过程将流键与正确的数据记录信息元素相关联。
The tester must create another Flow Keys Data Record to be exported where the associated templateId has insufficient fields to satisfy the flowKeyIndicator.
如果关联的templateId没有足够的字段满足flowKeyIndicator的要求，测试仪必须创建另一个要导出的流键数据记录。
The tester must ensure that the Collecting Process discards the IPFIX Message and shuts down the SCTP association or closes the TCP connection. The tester must check that the Collecting Process logged the error.
测试人员必须确保收集过程丢弃IPFIX消息并关闭SCTP关联或关闭TCP连接。测试仪必须检查采集过程是否记录了错误。
The tester must create another Flow Keys Option Template, where the templateId refers to a non-existing Template, and must cause the Option Template and an associated Data Record to be exported.
测试人员必须创建另一个流键选项模板，其中templateId指的是不存在的模板，并且必须导出选项模板和相关数据记录。
The tester must ensure that the Collecting Process shuts down the SCTP association and discards the IPFIX Message. The tester should check that the Collecting Process logged the error.
测试人员必须确保收集过程关闭SCTP关联并丢弃IPFIX消息。测试仪应检查采集过程是否记录了错误。
Stress tests are used to check correct behavior and robustness of an IPFIX Collecting Process implementation when a number of Data Records arrive very quickly. This is especially important when IPFIX over UDP is used, since in that case a slow Collecting Process cannot block the IPFIX Exporting Processes from exporting because UDP is not congestion aware.
当大量数据记录很快到达时，压力测试用于检查IPFIX收集过程实现的正确行为和健壮性。当使用UDP上的IPFIX时，这一点尤其重要，因为在这种情况下，缓慢的收集进程无法阻止IPFIX导出进程的导出，因为UDP不知道拥塞。
The tests may be dependent upon the hardware and transport technology in use. Therefore, the tests may need to be scaled up or down to meet the needs of the particular implementation. However, the implementer must ensure that the implementation is stable under excessive traffic conditions, for whatever definition of "excessive" applies at their intended installation.
测试可能取决于使用的硬件和传输技术。因此，可能需要放大或缩小测试以满足特定实现的需要。但是，实现者必须确保实现在过度流量条件下是稳定的，因为“过度”的定义适用于其预期安装。
The implementer must ensure the correct operation of the Exporting Process and/or Collecting Process when the Collecting Process is incapable of processing records at the rate that they are received.
当收集过程无法以收到记录的速度处理记录时，实施者必须确保导出过程和/或收集过程的正确操作。
The tester should export many Data Records to the Collecting Process, all conforming to the same Template, in order to put the Collecting Process under stress.
测试人员应将许多数据记录导出到采集过程中，所有数据记录均符合同一模板，以便对采集过程施加压力。
Depending on what the Collecting Process does (save to file, store to database, analyze the data) the Collecting Process may use up a lot of memory.
根据收集过程的功能（保存到文件、存储到数据库、分析数据），收集过程可能会占用大量内存。
The tester must ensure that, if the Collecting Process runs out of memory, it shuts down the specific SCTP association or closes the TCP connection but remains available to receive data on other open Transport Sessions and also stays available for future Transport Sessions.
测试仪必须确保，如果采集进程内存不足，它会关闭特定的SCTP关联或关闭TCP连接，但仍可以在其他打开的传输会话上接收数据，并且还可以在将来的传输会话中使用。
The tester should perform a test where Data Records are exported to the Collecting Process with an increasing export rate.
测试人员应执行一项测试，其中数据记录以增加的输出速率导出到采集过程。
For TCP or SCTP in reliable mode, the tester must ensure that the export stalls the Exporting Process once the Collecting Process becomes fully loaded.
对于可靠模式下的TCP或SCTP，测试仪必须确保一旦收集进程完全加载，导出将暂停导出进程。
For UDP export, the tester must ensure that the Collecting Process drops records as it becomes overloaded, and must check that the Collecting Process logged a warning.
对于UDP导出，测试人员必须确保收集进程在过载时丢弃记录，并且必须检查收集进程是否记录了警告。
The tester must create Templates with the maximum possible number of Information Elements and cause these to be exported to the Collecting Process.
测试人员必须使用尽可能多的信息元素创建模板，并将其导出到收集过程中。
The total length field in the IP header is 16 bits, allowing a length up to 65535 octets in one application-level datagram. This limits the number of Information Elements one can specify in an IPFIX Template when using UDP export. SCTP and TCP are streaming protocols, so they do not impose much restriction on the packet level. UDP requires 20 octets for a minimal IPv4 header, 8 octets for the UDP header, 16 octets for the IPFIX header, 4 octets for the Set header, and 4 octets for the Template header, so the Template definition may be up to (65535 - 20 - 8 - 16 - 4 - 4) = 65483 octets long. The minimum IPFIX Information Element specification requires 4 octets: two for the Information Element ID and two for the field length. Therefore, the maximum number of IPFIX Information Elements in a single Template is 65483 / 4 = 16370. With this many Information Elements, the Template will be 65480 octets long, while the entire packet will be 65532 octets long.
IP报头中的总长度字段为16位，允许一个应用程序级数据报中的长度最多为65535个八位字节。这限制了使用UDP导出时可以在IPFIX模板中指定的信息元素数量。SCTP和TCP是流协议，因此它们对数据包级别没有太多限制。UDP需要20个八位字节用于最小IPv4报头，8个八位字节用于UDP报头，16个八位字节用于IPFIX报头，4个八位字节用于Set报头，4个八位字节用于模板报头，因此模板定义的长度可能高达（65535-20-8-16-4-4）=65483个八位字节。最小IPFIX信息元素规范需要4个八位字节：两个用于信息元素ID，两个用于字段长度。因此，单个模板中IPFIX信息元素的最大数量为65483/4=16370。有了这么多信息元素，模板的长度将是65480个八位字节，而整个数据包的长度将是65532个八位字节。
The tester must create Data Records conforming to this Template, and cause them to be exported. Note that, for the implementation, the associated Data Records might be smaller or larger than the Template Records depending on the length of the Information Elements defined by the Template and on the presence of variable-length Information Elements.
测试人员必须创建符合此模板的数据记录，并将其导出。注意，对于实现，相关联的数据记录可能小于或大于模板记录，这取决于模板定义的信息元素的长度以及可变长度信息元素的存在。
The tester must ensure that the Collecting Process correctly receives and decodes the Template and associated Data Records.
测试人员必须确保采集过程正确接收并解码模板和相关数据记录。
The tester should create a large number of different Templates and cause them to be exported to the Collecting Process to stress test the Collecting Process's memory consumption.
测试人员应该创建大量不同的模板，并将它们导出到收集进程，以对收集进程的内存消耗进行压力测试。
The tester must ensure that the Collecting Process gracefully discards Templates if it's running out of memory resources, and it should check that warnings are logged.
测试人员必须确保收集过程在内存资源不足时正常地丢弃模板，并且应该检查是否记录了警告。
The tester must configure multiple Exporting Processes to export Templates and associated Data Records to the same Collecting Process at the same time.
测试人员必须配置多个导出过程，以便将模板和相关数据记录同时导出到同一个采集过程。
The tester must ensure that all the Templates and associated Data Records are correctly received and decoded at the Collecting Process, and that no Exporting Process stalls or disconnects completely unless the Collecting Process runs out of memory.
测试人员必须确保在采集过程中正确接收并解码所有模板和相关数据记录，并且除非采集过程内存不足，否则任何导出过程都不会完全暂停或断开连接。
3.5.6. Export from One Exporting Process to Multiple Collecting Processes
3.5.6. 从一个导出进程导出到多个收集进程
If the Exporting Process supports multiple simultaneous export destinations, the tester must configure the Exporting Process to export Data Records in parallel to different Collecting Processes.
如果导出过程支持多个同时导出目的地，测试仪必须将导出过程配置为与不同的采集过程并行导出数据记录。
The tester must configure the use of a mixture of simple and complex Templates and ensure they are all correctly received and decoded by all the Collecting Processes.
测试人员必须配置简单和复杂模板的混合使用，并确保所有收集过程都正确接收和解码这些模板。
This section lists and describes a number of problems that might occur in either the network or data transmission or related to wrong information encoding, and that the IPFIX Exporting Process and Collecting Process must be capable of handling in a graceful way. It is intended to test the robustness and fault tolerance of the IPFIX Processes.
本节列出并描述了网络或数据传输中可能出现的问题，或与错误信息编码有关的问题，以及IPFIX导出过程和收集过程必须能够以优雅的方式处理的问题。它旨在测试IPFIX过程的健壮性和容错性。
The IPFIX Exporting Process and Collecting Process behavior must be checked upon interruptions of data transmission due to network failures (whether physical or logical, e.g., defective routing).
由于网络故障（无论是物理故障还是逻辑故障，例如路由故障）导致数据传输中断时，必须检查IPFIX导出进程和收集进程的行为。
The tester must configure continuous export over all applicable combinations of transports and protocols in Section 3.1, in turn.
测试人员必须依次在第3.1节中的所有适用传输和协议组合上配置连续导出。
For SCTP-based associations and TCP-based connections, the tester should create a short disconnect between the Exporting Process and the Collecting Process (e.g., by momentarily interrupting the network connection) and must ensure that export continues after the connection is repaired. The tester must then create a longer disconnection between the Exporting Process and Collecting Process, and it must ensure that export continues after the connection is repaired.
对于基于SCTP的关联和基于TCP的连接，测试仪应在导出过程和收集过程之间创建一个短断开连接（例如，通过暂时中断网络连接），并且必须确保在连接修复后继续导出。然后，测试仪必须在导出过程和收集过程之间创建更长的断开连接，并且必须确保在修复连接后继续导出。
For UDP-based data export, there is no noticeable connection loss, but data received with non-consecutive sequence numbers indicates data loss. Refer to the sequence number specifications in Section 3.1 of [RFC5101]. The tester should create a short disconnect between the Exporting Process and Collecting Process, and it must ensure that this is recognized and reported by the Collecting Process per Section 3.1 of [RFC5101].
对于基于UDP的数据导出，没有明显的连接丢失，但使用非连续序列号接收的数据表示数据丢失。参考[RFC5101]第3.1节中的序列号规范。测试仪应在导出过程和收集过程之间创建一个短断开连接，并且必须确保收集过程根据[RFC5101]第3.1节识别并报告该断开连接。
3.6.2. Exporting Process Termination and Restart during Data Transmission
3.6.2. 在数据传输期间导出进程终止和重新启动
An IPFIX Collecting Process might be confronted with a faulty Exporting Process implementation that suddenly crashes, dropping any open connections. The Exporting Process may be restarted again soon after the crash.
IPFIX收集进程可能会遇到错误的导出进程实现，该实现会突然崩溃，丢失任何打开的连接。崩溃后不久，可能会再次重新启动导出过程。
Such an event will only be visible to the Collecting Process when the IPFIX Messages (Templates and associated Data Records) are carried over TCP or SCTP. For export via UDP, no such test is available due to the connection-less nature of the transport.
只有当IPFIX消息（模板和相关数据记录）通过TCP或SCTP传输时，收集过程才能看到此类事件。对于通过UDP导出，由于传输的连接较少，因此没有此类测试可用。
The tester must configure continuous export over all applicable combinations of SCTP and TCP transports and protocols in Section 3.1, in turn. For each combination, the tester must establish export, then kill the active Exporting Process.
测试人员必须依次在第3.1节中的SCTP和TCP传输和协议的所有适用组合上配置连续导出。对于每个组合，测试人员必须建立导出，然后终止活动的导出过程。
The tester must ensure that the associated Collecting Process shuts down SCTP associations and closes TCP connections associated with that export after a suitable timeout period.
测试仪必须确保相关的收集过程在适当的超时时间后关闭SCTP关联，并关闭与该导出相关的TCP连接。
The tester must Ensure that the Collecting Process discards the Template(s) received on the killed transport session.
测试人员必须确保收集过程丢弃在终止的传输会话上接收的模板。
The tester must restart the Exporting Process again, and it must ensure that the Exporting Process exports the Templates again.
测试人员必须重新启动导出过程，并且必须确保导出过程再次导出模板。
The tester must ensure that the Collecting Process receives and accepts both Templates and associated Data Records from the new Exporting Process running at the same source host.
测试人员必须确保采集进程从运行在同一源主机上的新导出进程接收并接受模板和相关数据记录。
3.6.3. Collecting Process Termination and Restart during Data Transmission
3.6.3. 数据传输期间采集进程终止和重启
An IPFIX Exporting Process might be confronted with a faulty Collecting Process implementation that suddenly crashes, dropping any open Transport Sessions. The Collecting Process may be restarted again soon after the crash.
IPFIX导出进程可能会遇到错误的收集进程实现，该实现突然崩溃，丢弃任何打开的传输会话。收集过程可能在崩溃后不久重新启动。
The tester must set up an Exporting Process and Collecting Process and cause IPFIX Templates and associated Data Records to be exported over all applicable combinations of SCTP and TCP transports and protocols in Section 3.1, in turn. Via UDP, the restart of the Collecting Process will be invisible to the Exporting Process and have no effect.
测试人员必须设置导出过程和收集过程，并依次通过第3.1节中所有适用的SCTP和TCP传输组合和协议导出IPFIX模板和相关数据记录。通过UDP，收集进程的重新启动将对导出进程不可见，并且没有任何效果。
The tester must terminate the Collecting Process while the export is in progress, and must ensure that the Exporting Process shuts down SCTP associations and closes TCP connections associated with that Collecting Process.
测试人员必须在导出过程中终止收集过程，并且必须确保导出过程关闭SCTP关联并关闭与该收集过程关联的TCP连接。
The tester must restart the Collecting Process and ensure that the Exporting Process connects to the Collecting Process again and that it exports the IPFIX Templates again.
测试人员必须重新启动收集过程，并确保导出过程再次连接到收集过程，并且再次导出IPFIX模板。
The tester must ensure that the new Collecting Process correctly receives and decodes the IPFIX Data Records again.
测试仪必须确保新的采集过程再次正确接收并解码IPFIX数据记录。
These tests verify the Collecting Process's operation when it receives a Template Record or Options Template Record with an invalid message length. Refer to the specifications in Section 3.4.1 and 3.4.2 of [RFC5101], respectively.
这些测试验证收集进程在接收到消息长度无效的模板记录或选项模板记录时的操作。分别参考[RFC5101]第3.4.1节和第3.4.2节中的规范。
Consider the example Template Record shown in Figure 4. This Template record is missing one Information Element ID and one Information Element length field. There is insufficient data in the Set for the specified Set length, and the overall record is four octets too short for the specified total length.
考虑图4所示的示例模板记录。此模板记录缺少一个信息元素ID和一个信息元素长度字段。集合中的数据不足，无法满足指定集合长度的要求，并且总记录的长度比指定的总长度短四个八位字节。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version = 10 | Total Length = 32 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Export Time = 1155202151 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number = 0x12345678 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Observation Domain ID = 0x33334444 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 2 | Set Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 257 | Field Count = 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| Info Element Identifier = 8 | 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version = 10 | Total Length = 32 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Export Time = 1155202151 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number = 0x12345678 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Observation Domain ID = 0x33334444 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 2 | Set Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 257 | Field Count = 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| Info Element Identifier = 8 | Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4
图4
The tester must create and cause the Exporting Process to export the following IPFIX Templates, and must ensure the correct Collecting Process behavior for each of the transports and protocols in Section 3.1.
测试人员必须创建并使导出过程导出以下IPFIX模板，并且必须确保第3.1节中每个传输和协议的收集过程行为正确。
The tester must do the following:
测试仪必须执行以下操作：
o For SCTP transport, ensure that the Collecting Process discards the IPFIX Message, shuts down the SCTP association, and logs the error.
o 对于SCTP传输，请确保收集进程丢弃IPFIX消息，关闭SCTP关联并记录错误。
o For TCP transport, ensure that the Collecting Process discards the IPFIX Message, closes the TCP connection, and logs the error. Note that since TCP is a streaming (rather than record-based) protocol, template length errors cannot be detected and may cause framing to be lost, potentially rendering the remainder of the IPFIX stream unintelligible. Therefore, some of these tests are not applicable for TCP transport, as indicated.
o 对于TCP传输，请确保收集进程丢弃IPFIX消息，关闭TCP连接并记录错误。请注意，由于TCP是一种流（而不是基于记录）协议，因此无法检测到模板长度错误，并可能导致帧丢失，从而可能导致IPFIX流的其余部分无法理解。因此，如图所示，其中一些测试不适用于TCP传输。
o For UDP transport, ensure that the Collecting Process discards the IPFIX Message and logs the error.
o 对于UDP传输，请确保收集进程丢弃IPFIX消息并记录错误。
(a) The tester must create the IPFIX Template shown in Figure 4 and cause the Exporting Process to export it. The tester must ensure that the Collecting Process's behavior is as specified above for each transport type except for TCP, for which this test is not applicable.
(a) 测试人员必须创建如图4所示的IPFIX模板，并使导出过程将其导出。测试人员必须确保收集过程的行为与上述针对每种传输类型的行为相同，TCP除外，此测试不适用于TCP。
(b) Consider the IPFIX Template shown in Figure 4, modified with total length = 28. In this case, the IPFIX Message has to be rejected because the field count = 2 and there is no second Information Element record present in the Set. The available data is exhausted after reading the first Information Element record.
(b) 考虑图4所示的IpFIX模板，修改为总长＝28。在这种情况下，必须拒绝IPFIX消息，因为字段计数=2，并且集合中不存在第二条信息元素记录。读取第一条信息元素记录后，可用数据将耗尽。
The tester must create the modified Template and cause the Exporting Process to export it. The tester must ensure that the Collecting Process's behavior is as specified above for each transport type.
测试人员必须创建修改后的模板，并使导出过程将其导出。测试人员必须确保收集过程的行为符合上述针对每种传输类型的规定。
(c) Consider the IPFIX Template shown in Figure 4, modified with total length = 26. In this case, the IPFIX Message has to be rejected because the IPFIX Message length is too short. After the first Information Element, the IPFIX Message data is exhausted according to the total length information.
(c) 考虑图4所示的IpFIX模板，修改为总长＝26。在这种情况下，必须拒绝IPFIX消息，因为IPFIX消息长度太短。在第一个信息元素之后，根据总长度信息耗尽IPFIX消息数据。
The tester must create the modified Template and cause the Exporting Process to export it. The tester must ensure that the Collecting Process's behavior is as specified above for each transport type. The TCP connection used for this test must be manually reset after the test.
测试人员必须创建修改后的模板，并使导出过程将其导出。测试人员必须确保收集过程的行为符合上述针对每种传输类型的规定。用于此测试的TCP连接必须在测试后手动重置。
(d) Consider the IPFIX Template shown in Figure 4, modified with field count = 1. In this case, the IPFIX Message must be rejected because the total length is too large and does not match the amount of data available.
(d) 考虑图4所示的IpFIX模板，用字段计数＝1进行修改。在这种情况下，必须拒绝IPFIX消息，因为总长度太大，并且与可用数据量不匹配。
The tester must create the modified Template and cause the Exporting Process to export it. The tester must ensure that the Collecting Process's behavior is as specified above for each transport type. This test is not applicable for TCP transport.
测试人员必须创建修改后的模板，并使导出过程将其导出。测试人员必须确保收集过程的行为符合上述针对每种传输类型的规定。此测试不适用于TCP传输。
(e) Finally, when the IPFIX Template shown in Figure 4 is extended with the data shown in Figure 5, it becomes a correct IPFIX Template.
(e) 最后，当使用图5所示的数据扩展图4所示的IPFIX模板时，它将成为正确的IPFIX模板。
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| Info Element Identifier = 12| Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| Info Element Identifier = 12| Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 5
图5
The tester must create the modified Template and cause the Exporting Process to export it. The tester must ensure that the Template is accepted by the Collecting Process for each transport type.
测试人员必须创建修改后的模板，并使导出过程将其导出。测试人员必须确保每个运输类型的收集过程都接受模板。
The example Template record shown in Figure 6 must be dropped because the scope field count = 0.
图6所示的示例模板记录必须删除，因为范围字段count=0。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version = 10 | Total Length = 30 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Export Time = 1155202151 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number = 0x12345678 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Observation Domain ID = 0x33334444 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 3 | Set Length = 14 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 257 | Field Count = 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope Field Count = 0 |0| Info Element Identifier = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version = 10 | Total Length = 30 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Export Time = 1155202151 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number = 0x12345678 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Observation Domain ID = 0x33334444 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Set ID = 3 | Set Length = 14 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 257 | Field Count = 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope Field Count = 0 |0| Info Element Identifier = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 6
图6
The tester must create the Template shown in Figure 6 and cause the Exporting Process to export it. The tester must ensure that the IPFIX Message is discarded by the Collecting Process for each transport type, and must check that the Collecting Process logs an error. The tester must ensure that the Collecting Process also shuts down the SCTP association or closes the TCP connection.
测试人员必须创建如图6所示的模板，并使导出过程将其导出。测试人员必须确保每个传输类型的收集进程都会丢弃IPFIX消息，并且必须检查收集进程是否记录了错误。测试人员必须确保采集过程同时关闭SCTP关联或关闭TCP连接。
The tester must create an IPFIX Options Template where the field count is less than the scope field count, and cause the Exporting Process to export it. Use the above IPFIX Options Template with scope field count = 2. The tester must ensure that the Template is discarded by the Collecting Process for each transport type, and must check that the Collecting Process logs an error. The tester must ensure that the Collecting Process shuts down the SCTP association or closes the TCP connection.
测试人员必须创建一个IPFIX选项模板，其中字段计数小于范围字段计数，并使导出过程将其导出。使用上述IPFIX选项模板，范围字段计数为2。测试人员必须确保每个传输类型的收集过程都会丢弃模板，并且必须检查收集过程是否记录了错误。测试人员必须确保采集过程关闭SCTP关联或关闭TCP连接。
The tester must create the following invalid Data Records and cause them to be exported to the Collecting Process over all applicable combinations of transports and protocols in Section 3.1.
测试人员必须创建以下无效数据记录，并通过第3.1节中所有适用的传输和协议组合将其导出到采集过程中。
o IPFIX Message too short.
o IPFIX消息太短。
o Illegal use of reduced size encoding.
o 非法使用压缩编码。
o Invalid length specification in case of variable-length Information Elements.
o 对于可变长度信息元素，长度规范无效。
The tester must ensure that the Collecting Process discards the IPFIX Message and shuts down the SCTP association or closes the TCP connection.
测试人员必须确保收集过程丢弃IPFIX消息并关闭SCTP关联或关闭TCP连接。
The tester must create Templates and associated Data Records that fail to conform to those Templates in the following ways:
测试人员必须通过以下方式创建不符合这些模板的模板和相关数据记录：
o too few Information Elements in Data Record
o 数据记录中的信息元素太少
o too many Information Elements in Data Record
o 数据记录中的信息元素过多
The tester must cause the Templates and associated Data Records to be exported to the Collecting Process over all applicable combinations of transports and protocols in Section 3.1.
测试人员必须通过第3.1节中所有适用的传输和协议组合，将模板和相关数据记录导出到收集过程中。
The tester must ensure that the Collecting Process discards the IPFIX Message and shuts down the SCTP association or closes the TCP connection.
测试人员必须确保收集过程丢弃IPFIX消息并关闭SCTP关联或关闭TCP连接。
The tester must create Template Sets, Option Template Sets, and associated Data Sets using Set IDs which are unknown to the Collecting Process, and cause these to be exported to the Collecting Process over all applicable combinations of transports and protocols in Section 3.1.
测试人员必须使用采集过程未知的集合ID创建模板集、选项模板集和相关数据集，并通过第3.1节中所有适用的传输和协议组合将其导出到采集过程。
Per Section 3.3.2 of [RFC5101], only the Set ID values 2 and 3 denote valid Sets.
根据[RFC5101]第3.3.2节，只有集合ID值2和3表示有效集合。
The tester must ensure that the Collecting Process ignores the unknown Sets, logs a warning, and processes the remainder of the IPFIX Message.
测试人员必须确保收集过程忽略未知集合，记录警告，并处理IPFIX消息的其余部分。
Refer to Section 9 of [RFC5101] for the Collecting Process's SCTP Template management specifications.
有关采集流程的SCTP模板管理规范，请参阅[RFC5101]第9节。
The tester must create an IPFIX Template and cause it to be exported to a Collecting Process over SCTP transport.
测试人员必须创建一个IPFIX模板，并通过SCTP传输将其导出到收集过程中。
The tester must ensure that the Template was correctly received and decoded by the Collecting Process.
测试人员必须确保采集过程正确接收并解码了模板。
The tester must cause the same Template to be exported to the same Collecting Process over the same SCTP association, and must ensure that the Collecting Process resets the SCTP association and discards the IPFIX Message.
测试人员必须通过相同的SCTP关联将相同的模板导出到相同的收集进程，并且必须确保收集进程重置SCTP关联并丢弃IPFIX消息。
The tester must create another IPFIX template and cause it to be exported to the Collecting Process over SCTP transport.
测试人员必须创建另一个IPFIX模板，并通过SCTP传输将其导出到收集过程。
The tester must ensure that the Template was correctly received and decoded by the Collecting Process.
测试人员必须确保采集过程正确接收并解码了模板。
The tester must modify the Template contents while retaining the same Template ID.
测试仪必须修改模板内容，同时保留相同的模板ID。
The tester must cause the modified Template to be exported to the same Collecting Process over the SCTP same association, and must ensure that the Collecting Process resets the SCTP association and discards the IPFIX Message.
测试人员必须通过SCTP同一关联将修改后的模板导出到同一收集过程，并且必须确保收集过程重置SCTP关联并丢弃IPFIX消息。
The tester must check that an error was logged.
测试仪必须检查是否记录了错误。
The tester must create another IPFIX Template and cause it to be exported to the Collecting Process over SCTP transport.
测试人员必须创建另一个IPFIX模板，并通过SCTP传输将其导出到收集过程。
The tester must ensure that the Template was correctly received and decoded by the Collecting Process.
测试人员必须确保采集过程正确接收并解码了模板。
The tester must cause a Template Withdrawal Message for the Template to be sent to the Collecting Process over the same SCTP association, and must ensure that the Template has been discarded by the Collecting Process.
测试人员必须使模板的模板撤回消息通过同一SCTP关联发送到收集流程，并且必须确保收集流程已丢弃模板。
The tester must create Data Records conforming to the Template and cause them to be exported to the Collecting Process over the same SCTP association.
测试人员必须创建符合模板的数据记录，并通过同一SCTP关联将其导出到采集过程中。
The tester must ensure that the Collecting Process discards the Data Records and logs a warning.
测试人员必须确保收集过程丢弃数据记录并记录警告。
The tester must cause the same Template to be exported to the same Collecting Process over the same SCTP association.
测试人员必须通过相同的SCTP关联将相同的模板导出到相同的收集过程。
The tester must ensure that the Template was correctly received and decoded by the Collecting Process.
测试人员必须确保采集过程正确接收并解码了模板。
The tester must create Data Records conforming to the Template and cause them to be exported to the Collecting Process over the same SCTP association.
测试人员必须创建符合模板的数据记录，并通过同一SCTP关联将其导出到采集过程中。
The tester must ensure that the Collecting Process correctly receives and decodes the Data Records.
测试仪必须确保采集过程正确接收和解码数据记录。
Refer to Section 10.4.3 of [RFC5101] for the Collecting Process's TCP Template management specifications.
有关采集过程的TCP模板管理规范，请参阅[RFC5101]第10.4.3节。
The tester must create an IPFIX Template and cause it to be exported to a Collecting Process over TCP transport.
测试人员必须创建一个IPFIX模板，并通过TCP传输将其导出到收集进程。
The tester must ensure that the Template was correctly received and decoded by the Collecting Process.
测试人员必须确保采集过程正确接收并解码了模板。
The tester must cause the same Template to be exported to the same Collecting Process over the same TCP connection, and must ensure that the Collecting Process resets the TCP connection and discards the IPFIX Message.
测试人员必须通过相同的TCP连接将相同的模板导出到相同的收集进程，并且必须确保收集进程重置TCP连接并丢弃IPFIX消息。
The tester must create an IPFIX Template and cause it to be exported to the Collecting Process over TCP transport.
测试人员必须创建一个IPFIX模板，并通过TCP传输将其导出到收集过程中。
The tester must ensure that the Template was correctly received and decoded by the Collecting Process.
测试人员必须确保采集过程正确接收并解码了模板。
The tester must modify the Template contents while retaining the same Template ID.
测试仪必须修改模板内容，同时保留相同的模板ID。
The tester must cause the modified Template to be exported to the same Collecting Process over the same TCP connection, and must ensure that the Collecting Process resets the TCP connection and discards the IPFIX Message.
测试人员必须通过相同的TCP连接将修改后的模板导出到相同的收集进程，并且必须确保收集进程重置TCP连接并丢弃IPFIX消息。
The tester must check that an error was logged.
测试仪必须检查是否记录了错误。
The tester must create another IPFIX Template and cause it to be exported to the Collecting Process over TCP transport.
测试人员必须创建另一个IPFIX模板，并通过TCP传输将其导出到收集过程。
The tester must ensure that the Template was correctly received and decoded by the Collecting Process.
测试人员必须确保采集过程正确接收并解码了模板。
The tester must cause a Template Withdrawal Message for the Template to be sent to the Collecting Process over the same TCP connection, and must ensure that the Template has been discarded by the Collecting Process.
测试人员必须使模板的模板撤回消息通过相同的TCP连接发送到收集过程，并且必须确保收集过程已丢弃模板。
The tester must create Data Records conforming to the same Template and cause them to be exported to the same Collecting Process over the same TCP connection.
测试人员必须创建符合相同模板的数据记录，并通过相同的TCP连接将其导出到相同的采集过程。
The tester must ensure that the Collecting Process discards the Data Records and logs a warning.
测试人员必须确保收集过程丢弃数据记录并记录警告。
The tester must cause the same Template to be exported to the same Collecting Process over the same TCP connection.
测试人员必须通过相同的TCP连接将相同的模板导出到相同的收集过程。
The tester must ensure that the Template was correctly received and decoded by the Collecting Process.
测试人员必须确保采集过程正确接收并解码了模板。
The tester must create Data Records conforming to the Template and cause them to be exported to the same Collecting Process over the same TCP connection.
测试人员必须创建符合模板的数据记录，并通过相同的TCP连接将其导出到相同的采集过程。
The tester must ensure that the Collecting Process correctly receives and decodes the Data Records.
测试仪必须确保采集过程正确接收和解码数据记录。
Refer to Sections 10.3.6 and 10.3.7 of [RFC5101] for the UDP Template management specifications.
有关UDP模板管理规范，请参阅[RFC5101]第10.3.6节和第10.3.7节。
The tester must create an IPFIX Template and cause it to be exported to a Collecting Process over UDP transport.
测试人员必须创建一个IPFIX模板，并通过UDP传输将其导出到收集进程。
The tester must ensure that the Template was correctly received and decoded by the Collecting Process.
测试人员必须确保采集过程正确接收并解码了模板。
Before the Template lifetime expires on the Collecting Process, the tester must cause the same Template to be exported over the same UDP connection to the same Collecting Process and must ensure that the Collecting Process accepts the Template.
在收集进程的模板生存期到期之前，测试人员必须使相同的模板通过相同的UDP连接导出到相同的收集进程，并且必须确保收集进程接受该模板。
The tester must create a different Template with the same ID and must cause this to be exported to the same Collecting Process over the same UDP connection before the original Template lifetime expires.
测试人员必须使用相同的ID创建不同的模板，并且必须在原始模板生存期到期之前通过相同的UDP连接将其导出到相同的收集进程。
The tester must ensure that the Collecting Process does not reject the new Template.
测试人员必须确保收集过程不会拒绝新模板。
The tester must create Data Records conforming to the new Template and cause them to be exported to the same Collecting Process over the same UDP connection.
测试人员必须创建符合新模板的数据记录，并通过相同的UDP连接将其导出到相同的采集过程。
The tester must ensure that the Collecting Process correctly receives and decodes the Data Records.
测试仪必须确保采集过程正确接收和解码数据记录。
The tester must create an IPFIX Template and cause it to be exported to a Collecting Process over UDP transport.
测试人员必须创建一个IPFIX模板，并通过UDP传输将其导出到收集进程。
The tester must ensure that the Template was correctly received and decoded by the Collecting Process.
测试人员必须确保采集过程正确接收并解码了模板。
The tester must allow the received Template lifetime to expire on the Collecting Process.
测试人员必须允许接收的模板生存期在收集过程中过期。
The tester must create Data Records conforming to the Template and cause them to be exported to the same Collecting Process over the same UDP connection.
测试人员必须创建符合模板的数据记录，并通过相同的UDP连接将其导出到相同的采集过程。
The tester must ensure that the Collecting Process discards the Data Records.
测试人员必须确保收集过程丢弃数据记录。
The tester must check that the Collecting Process logs a warning.
测试仪必须检查采集过程是否记录了警告。
The tester must cause the same Template to be exported to the same Collecting Process over the same UDP connection.
测试人员必须通过相同的UDP连接将相同的模板导出到相同的收集进程。
The tester must ensure that the Template was correctly received and decoded by the Collecting Process.
测试人员必须确保采集过程正确接收并解码了模板。
The tester must create Data Records conforming to the Template and cause them to be exported to the same Collecting Process over the same UDP connection.
测试人员必须创建符合模板的数据记录，并通过相同的UDP连接将其导出到相同的采集过程。
The tester must ensure that the Collecting Process correctly receives and decodes the Data Records.
测试仪必须确保采集过程正确接收和解码数据记录。
This section lists tests that verify connectivity over TLS and Datagram Transport Layer Security (DTLS) and proper selection of TLS policies as specified in the IPFIX Protocol. It specifically does NOT purport to test the security of IPFIX Message transport over TLS or DTLS, as evaluating the security of a transport session is really a test of the TLS or DTLS implementation over which a given IPFIX implementation runs, and as such is out of scope for this document.
本节列出了验证TLS连接和数据报传输层安全性（DTLS）的测试，以及IPFIX协议中指定的TLS策略的正确选择。它并不是要测试TLS或DTL上的IPFIX消息传输的安全性，因为评估传输会话的安全性实际上是测试给定IPFIX实现运行的TLS或DTL实现，因此不在本文档的范围内。
Refer to Section 11 of [RFC5101] for the security specifications.
有关安全规范，请参阅[RFC5101]第11节。
Setting up for TLS connectivity and policy testing requires the creation of appropriate X.509 certificates and private keys for a test environment and the configuration of a DNS server to answer with consistent information for the hosts used in the test.
设置TLS连接和策略测试需要为测试环境创建适当的X.509证书和私钥，并配置DNS服务器，以使用测试中使用的主机的一致信息进行应答。
The tester must configure the following certificates:
测试仪必须配置以下证书：
1. A Certificate Authority (CA) certificate and associated private key for signing the following certificates.
1. 用于签署以下证书的证书颁发机构（CA）证书和相关私钥。
2. One certificate and associated private key, with a CN (Common Name) or subjectAltName extension of type dNSName containing the fully qualified domain name of the host, signed by the CA certificate in 1, for each IPFIX Exporting Process in the test.
2. 对于测试中的每个IPFIX导出过程，一个证书和相关私钥，带有CN（公共名称）或dNSName类型的subjectAltName扩展名，其中包含主机的完全限定域名，由CA证书在1中签名。
3. One certificate and associated private key, with a CN (common name) or subjectAltName extension of type dNSName containing the fully qualified domain name of the host, signed by the CA certificate in 1, for each IPFIX Collecting Process in the test.
3. 对于测试中的每个IPFIX收集过程，一个证书和相关私钥，带有CN（公共名称）或dNSName类型的subjectAltName扩展名，其中包含主机的完全限定域名，由CA证书在1中签名。
The tester must configure consistent forward (A, AAAA) DNS records for each host in the test on a DNS server used by the hosts for name resolution. Note that there is no need to configure reverse (PTR) DNS records for the hosts, as no part of the protocol uses reverse lookups.
测试人员必须在主机用于名称解析的DNS服务器上为测试中的每个主机配置一致的转发（A、AAAA）DNS记录。请注意，不需要为主机配置反向（PTR）DNS记录，因为协议的任何部分都不使用反向查找。
The tester must ensure that the Exporting Process and Collecting Process are on different hosts.
测试人员必须确保导出过程和收集过程位于不同的主机上。
The tester must set up certificates and DNS as in Section 3.7.1.
测试人员必须按照第3.7.1节的规定设置证书和DNS。
The tester must configure one Exporting Process and one Collecting Process with their appropriate certificates to transfer IPFIX Messages over TLS over TCP.
测试人员必须使用相应的证书配置一个导出进程和一个收集进程，以便通过TCP通过TLS传输IPFIX消息。
The tester must create an IPFIX Template and associated Data Record, and cause them to be exported over the TCP connection.
测试人员必须创建IPFIX模板和相关数据记录，并通过TCP连接导出它们。
The tester must ensure that a TCP connection and a TLS connection were established, must ensure that data was exchanged, and must ensure that the data received at the Collecting Process is correct.
测试仪必须确保建立了TCP连接和TLS连接，必须确保交换了数据，并且必须确保在采集过程中接收到的数据是正确的。
The tester must set up certificates and DNS as in Section 3.7.1.
测试人员必须按照第3.7.1节的规定设置证书和DNS。
The tester must configure one Exporting Process and one Collecting Process with their appropriate certificates to transfer IPFIX Messages over DTLS over UDP.
测试人员必须使用相应的证书配置一个导出进程和一个收集进程，以便通过UDP通过DTL传输IPFIX消息。
The tester must create an IPFIX Template and associated Data Record, and cause them to be exported over the UDP connection.
测试人员必须创建IPFIX模板和相关数据记录，并通过UDP连接导出它们。
The tester must ensure that UDP packets were sent and a DTLS connection was established, must ensure that data was exchanged, and must ensure that the data received at the Collecting Process is correct.
测试人员必须确保发送了UDP数据包并建立了DTLS连接，必须确保交换了数据，并且必须确保在采集过程中接收到的数据是正确的。
The tester must set up certificates and DNS as in Section 3.7.1.
测试人员必须按照第3.7.1节的规定设置证书和DNS。
The tester must configure one Exporting Process and one Collecting Process with their appropriate certificates to transfer IPFIX Messages over DTLS over the Partially Reliable-Stream Control Transmission Protocol (PR-SCTP).
测试人员必须配置一个导出进程和一个收集进程及其相应的证书，以便通过部分可靠的流控制传输协议（PR-SCTP）通过DTL传输IPFIX消息。
The tester must create an IPFIX Template and associated Data Record, and cause them to be exported over the SCTP association.
测试人员必须创建IPFIX模板和相关数据记录，并通过SCTP关联导出它们。
The tester must ensure that an SCTP association and a DTLS connection were established, must ensure that data was exchanged, and must ensure that the data received at the Collecting Process is correct.
测试仪必须确保建立了SCTP关联和DTLS连接，必须确保交换了数据，并且必须确保在采集过程中接收到的数据是正确的。
This is an optional test for Collecting Processes only; it requires the modification of an Exporting Process to NOT present a certificate.
这是一个可选测试，仅用于收集进程；它要求修改导出过程以不显示证书。
The tester must modify an Exporting Process to NOT present a certificate.
测试人员必须修改导出过程以不显示证书。
The tester must perform the connectivity tests in Sections 3.7.2, 3.7.3, and 3.7.4.
测试仪必须执行第3.7.2、3.7.3和3.7.4节中的连接测试。
The tester must ensure that the Collecting Process rejects the TLS or DTLS connection establishment.
测试人员必须确保收集过程拒绝TLS或DTLS连接建立。
The tester must set up certificates and DNS as in Section 3.7.1.
测试人员必须按照第3.7.1节的规定设置证书和DNS。
The tester must use a certificate for the Exporting Process that does NOT match the fully qualified domain name of the host on which the Exporting Process runs.
测试人员必须为导出进程使用与运行导出进程的主机的完全限定域名不匹配的证书。
The tester must Perform the connectivity tests in Sections 3.7.2, 3.7.3, and 3.7.4.
测试仪必须执行第3.7.2、3.7.3和3.7.4节中的连接测试。
The tester must ensure that the Collecting Process rejects the TLS or DTLS connection establishment.
测试人员必须确保收集过程拒绝TLS或DTLS连接建立。
The tester must set up certificates and DNS as in Section 3.7.1.
测试人员必须按照第3.7.1节的规定设置证书和DNS。
The tester must use a certificate for the Collecting Process that does NOT match the fully qualified domain name of the host on which the Collecting Process runs.
测试人员必须为收集进程使用与运行收集进程的主机的完全限定域名不匹配的证书。
The tester must perform the connectivity tests in Sections 3.7.2, 3.7.3, and 3.7.4.
测试仪必须执行第3.7.2、3.7.3和3.7.4节中的连接测试。
The tester must ensure that the Exporting Process rejects the TLS or DTLS connection establishment.
测试人员必须确保导出过程拒绝TLS或DTLS连接建立。
This memo raises no security issues.
这份备忘录没有提出任何安全问题。
The authors wish to thank Brian Trammell for contributing the initial text for Section 3.7.
作者希望感谢Brian Trammell为第3.7节提供了初始文本。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC3917] Quittek, J., Zseby, T., Claise, B., and S. Zander, "Requirements for IP Flow Information Export (IPFIX)", RFC 3917, October 2004.
[RFC3917]Quitek，J.，Zseby，T.，Claise，B.，和S.Zander，“IP流信息导出（IPFIX）的要求”，RFC 39172004年10月。
[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月。
[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月。
[RFC5472] Zseby, T., Boschi, E., Brownlee, N., and B. Claise, "IP Flow Information Export (IPFIX) Applicability", RFC 5472, March 2009.
[RFC5472]Zseby，T.，Boschi，E.，Brownlee，N.，和B.Claise，“IP流信息导出（IPFIX）适用性”，RFC 54722009年3月。
Authors' Addresses
作者地址
Carsten Schmoll Fraunhofer FOKUS Kaiserin-Augusta-Allee 31 Berlin D-10589 Germany
Carsten Schmoll Fraunhofer FOKUS Kaiserin Augusta Allee 31柏林D-10589德国
Phone: +49 30 3463 7136
EMail: carsten.schmoll@fokus.fraunhofer.de
URI: http://www.fokus.fraunhofer.de
Phone: +49 30 3463 7136
EMail: carsten.schmoll@fokus.fraunhofer.de
URI: http://www.fokus.fraunhofer.de
Paul Aitken Cisco Systems, Inc. 96 Commercial Quay Edinburgh EH6 6LX Scotland
Paul Aitken Cisco Systems，Inc.96爱丁堡商业码头EH6 6LX苏格兰
Phone: +44 131 561 3616
EMail: paitken@cisco.com
URI: http://www.cisco.com
Phone: +44 131 561 3616
EMail: paitken@cisco.com
URI: http://www.cisco.com
Benoit Claise Cisco Systems, Inc. De Kleetlaan 6a b1 1831 Diegem Belgium
Benoit Claise Cisco Systems，Inc.De Kleetlaan 6a b1 1831 Diegem比利时
Phone: +32 2 704 5622
EMail: bclaise@cisco.com
URI: http://www.cisco.com
Phone: +32 2 704 5622
EMail: bclaise@cisco.com
URI: http://www.cisco.com