Debian Codegraph @

rfc5471.html

raw
1 <pre>Network Working Group C. Schmoll
2 Request for Comments: 5471 Fraunhofer FOKUS
3 Category: Informational P. Aitken
4 B. Claise
5 Cisco Systems, Inc.
6 March 2009
7
8
9 <span class="h1">Guidelines for IP Flow Information Export (IPFIX) Testing</span>
10
11 Status of This Memo
12
13 This memo provides information for the Internet community. It does
14 not specify an Internet standard of any kind. Distribution of this
15 memo is unlimited.
16
17 Copyright Notice
18
19 Copyright (c) 2009 IETF Trust and the persons identified as the
20 document authors. All rights reserved.
21
22 This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
23 Provisions Relating to IETF Documents in effect on the date of
24 publication of this document (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>).
25 Please review these documents carefully, as they describe your rights
26 and restrictions with respect to this document.
27
28 This document may contain material from IETF Documents or IETF
29 Contributions published or made publicly available before November
30 10, 2008. The person(s) controlling the copyright in some of this
31 material may not have granted the IETF Trust the right to allow
32 modifications of such material outside the IETF Standards Process.
33 Without obtaining an adequate license from the person(s) controlling
34 the copyright in such materials, this document may not be modified
35 outside the IETF Standards Process, and derivative works of it may
36 not be created outside the IETF Standards Process, except to format
37 it for publication as an RFC or to translate it into languages other
38 than English.
39
40
41
42
43
44
45
46
47
48
49
50
51
52 <span class="grey">Schmoll, et al. Informational [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc5471">RFC 5471</a> Guidelines for IPFIX Testing March 2009</span>
55
56
57 Abstract
58
59 This document presents a list of tests for implementers of IP Flow
60 Information eXport (IPFIX) compliant Exporting Processes and
61 Collecting Processes. This document specifies guidelines for a
62 series of tests that can be run on the IPFIX Exporting Process and
63 Collecting Process in order to probe the conformity and robustness of
64 the IPFIX protocol implementations. These tests cover all important
65 functions, in order to gain a level of confidence in the IPFIX
66 implementation. Therefore, they allow the implementer to perform
67 interoperability or plug tests with other IPFIX Exporting Processes
68 and Collecting Processes.
69
70 Table of Contents
71
72 <a href="#section-1">1</a>. Introduction ....................................................<a href="#page-4">4</a>
73 <a href="#section-1.1">1.1</a>. Document Scope .............................................<a href="#page-4">4</a>
74 <a href="#section-1.2">1.2</a>. IPFIX Documents Overview ...................................<a href="#page-5">5</a>
75 <a href="#section-2">2</a>. Terminology .....................................................<a href="#page-5">5</a>
76 <a href="#section-2.1">2.1</a>. Conventions Used in This Document ..........................<a href="#page-5">5</a>
77 <a href="#section-3">3</a>. Test Specifications .............................................<a href="#page-5">5</a>
78 <a href="#section-3.1">3.1</a>. Exporting Process/Collecting Process Connectivity Tests ....<a href="#page-6">6</a>
79 3.1.1. Connectivity Tests between the Exporting
80 Process and Collecting ..............................<a href="#page-6">6</a>
81 <a href="#section-3.2">3.2</a>. Template and Data Record Tests .............................<a href="#page-6">6</a>
82 3.2.1. Transmission of Template with Fixed-Size
83 Information Elements ................................<a href="#page-7">7</a>
84 3.2.2. Transmission of Template with
85 Variable-Length Information Elements ................<a href="#page-7">7</a>
86 <a href="#section-3.2.3">3.2.3</a>. Set Padding .........................................<a href="#page-7">7</a>
87 <a href="#section-3.2.4">3.2.4</a>. Record Padding ......................................<a href="#page-8">8</a>
88 <a href="#section-3.2.5">3.2.5</a>. Template Withdrawal Message .........................<a href="#page-9">9</a>
89 <a href="#section-3.3">3.3</a>. Information Element Tests .................................<a href="#page-11">11</a>
90 <a href="#section-3.3.1">3.3.1</a>. Enterprise-Specific Information Elements ...........<a href="#page-11">11</a>
91 <a href="#section-3.3.2">3.3.2</a>. Reduced Size Encoding of Information Elements ......<a href="#page-11">11</a>
92 3.3.3. Multiple Instances of the Same Information
93 Element in One Template.............................<a href="#page-12">12</a>
94 <a href="#section-3.4">3.4</a>. Options Template Tests ....................................<a href="#page-12">12</a>
95 <a href="#section-3.4.1">3.4.1</a>. Using Any Information Elements as Scope ............<a href="#page-12">12</a>
96 <a href="#section-3.4.2">3.4.2</a>. Using Multiple Scopes ..............................<a href="#page-13">13</a>
97 <a href="#section-3.4.3">3.4.3</a>. Metering Process Statistics Option Template ........<a href="#page-13">13</a>
98 3.4.4. Metering Process Reliability Statistics
99 Option Template ....................................<a href="#page-14">14</a>
100 3.4.5. Exporting Process Reliability Statistics
101 Option Template ....................................<a href="#page-14">14</a>
102 <a href="#section-3.4.6">3.4.6</a>. Flow Keys Option Template ..........................<a href="#page-14">14</a>
103
104
105
106
107
108 <span class="grey">Schmoll, et al. Informational [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc5471">RFC 5471</a> Guidelines for IPFIX Testing March 2009</span>
111
112
113 <a href="#section-3.5">3.5</a>. Stress/Load Tests .........................................<a href="#page-15">15</a>
114 <a href="#section-3.5.1">3.5.1</a>. Large Number of Records for One Template ...........<a href="#page-15">15</a>
115 <a href="#section-3.5.2">3.5.2</a>. Excessive Rate of Incoming Data Records ............<a href="#page-15">15</a>
116 <a href="#section-3.5.3">3.5.3</a>. Large Templates ....................................<a href="#page-16">16</a>
117 3.5.4. Many New Templates within the Data Template
118 Timeout Interval ...................................<a href="#page-16">16</a>
119 3.5.5. Multiple Exporting Processes Exporting to
120 One Collecting Process .............................<a href="#page-17">17</a>
121 3.5.6. Export from One Exporting Process to
122 Multiple Collecting Processes ......................<a href="#page-17">17</a>
123 <a href="#section-3.6">3.6</a>. Error Handling ............................................<a href="#page-17">17</a>
124 <a href="#section-3.6.1">3.6.1</a>. Temporary Network Disconnect .......................<a href="#page-17">17</a>
125 3.6.2. Exporting Process Termination and Restart
126 during Data Transmission ...........................<a href="#page-18">18</a>
127 3.6.3. Collecting Process Termination and Restart
128 during Data Transmission ...........................<a href="#page-18">18</a>
129 3.6.4. Incorrect Template Records and Options
130 Template Records ...................................<a href="#page-19">19</a>
131 <a href="#section-3.6.5">3.6.5</a>. Incorrect Data Record ..............................<a href="#page-22">22</a>
132 <a href="#section-3.6.6">3.6.6</a>. Export of Non-Matching Template and Data Records ...<a href="#page-23">23</a>
133 <a href="#section-3.6.7">3.6.7</a>. Unknown Set IDs ....................................<a href="#page-23">23</a>
134 <a href="#section-3.6.8">3.6.8</a>. Re-Using Template IDs ..............................<a href="#page-24">24</a>
135 <a href="#section-3.7">3.7</a>. TLS Connectivity and Policy Selection .....................<a href="#page-28">28</a>
136 <a href="#section-3.7.1">3.7.1</a>. TLS Test Setup .....................................<a href="#page-28">28</a>
137 <a href="#section-3.7.2">3.7.2</a>. TLS over TCP Connectivity Test .....................<a href="#page-29">29</a>
138 <a href="#section-3.7.3">3.7.3</a>. DTLS over UDP Connectivity Test ....................<a href="#page-29">29</a>
139 <a href="#section-3.7.4">3.7.4</a>. DTLS over PR-SCTP Connectivity Test ................<a href="#page-29">29</a>
140 <a href="#section-3.7.5">3.7.5</a>. TLS Bidirectional Authentication Policy Test .......<a href="#page-30">30</a>
141 3.7.6. Exporting Process Identity Mismatch TLS
142 Policy Test ........................................<a href="#page-30">30</a>
143 3.7.7. Collecting Process Identity Mismatch TLS
144 Policy Test ........................................<a href="#page-30">30</a>
145 <a href="#section-4">4</a>. Security Considerations ........................................<a href="#page-30">30</a>
146 <a href="#section-5">5</a>. Acknowledgments ................................................<a href="#page-31">31</a>
147 <a href="#section-6">6</a>. Normative References ...........................................<a href="#page-31">31</a>
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164 <span class="grey">Schmoll, et al. Informational [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc5471">RFC 5471</a> Guidelines for IPFIX Testing March 2009</span>
167
168
169 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
170
171 An IPFIX implementation, whether in software, firmware, or hardware,
172 needs to be tested thoroughly in order to check its robustness and
173 gain confidence in the conformity to the IPFIX documents on which it
174 is based.
175
176 For a testable IPFIX software tool kit, one needs at least one IPFIX
177 Exporting Process and one IPFIX Collecting Process. However, when
178 one has, for example, only implemented a Collector, then it can be
179 complemented with a third-party Exporter for these tests.
180
181 This document specifies guidelines for a series of tests that can be
182 run on the IPFIX Exporting Process and Collecting Process in order to
183 probe the conformity and robustness of the IPFIX protocol
184 implementations.
185
186 The tests listed here can form a valuable common basis for
187 implementers involved in interoperability testing when all of them
188 use these tests to check their own Exporting Process and Collecting
189 Process implementation first.
190
191 The tests can be executed in a testbed environment or on a live
192 network.
193
194 However, care should be taken regarding the "stress/load test" and
195 the "temporary network disconnect", as they might impact other
196 systems in the network. We recommend that these specific tests
197 should be executed only in a testbed environment.
198
199 <span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Document Scope</span>
200
201 This document lists tests intended to be performed between an
202 implementation of an IPFIX Exporting Process and an IPFIX Collecting
203 Process. For some tests, multiple instances of each of those
204 components (Observation Points, Metering Process, Exporting Process,
205 Collecting Process) are involved. The testing of those different
206 IPFIX components complicates the testing as usually one tests his
207 software against an existing implementation, which is proven to be
208 compliant. In some cases, two unproven implementations of the
209 Exporting Process and Collecting Process must be tested against each
210 other. The tests range from basic transport connectivity to export
211 of Template and associated Data Records, high load on the Collecting
212 Process, and error condition situations. This document is not
213 intended as a replacement for formal testing software procedures
214 based on, e.g., TTCN3 (<a href="http://www.ttcn-3.org/">http://www.ttcn-3.org/</a>) but as a best-
215 practices approach to an informal testing of a developer's IPFIX
216 implementation.
217
218
219
220 <span class="grey">Schmoll, et al. Informational [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc5471">RFC 5471</a> Guidelines for IPFIX Testing March 2009</span>
223
224
225 <span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a>. IPFIX Documents Overview</span>
226
227 The IPFIX protocol [<a href="./rfc5101" title="&quot;Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of IP Traffic Flow Information&quot;">RFC5101</a>] provides network administrators with
228 access to IP Flow information. The architecture for the export of
229 measured IP Flow information out of an IPFIX Exporting Process to a
230 Collecting Process is defined in [<a href="./rfc5470" title="&quot;Architecture for IP Flow Information Export&quot;">RFC5470</a>], per the requirements
231 specified in [<a href="./rfc3917" title="&quot;Requirements for IP Flow Information Export (IPFIX)&quot;">RFC3917</a>].
232
233 [<a id="ref-RFC5470">RFC5470</a>] specifies how IPFIX Data Records and Templates are carried
234 via a congestion-aware transport protocol from IPFIX Exporting
235 Processes to IPFIX Collecting Processes. IPFIX has a formal
236 description of IPFIX Information Elements, their name, type, and
237 additional semantic information, as specified in [<a href="./rfc5102" title="&quot;Information Model for IP Flow Information Export&quot;">RFC5102</a>]. Finally,
238 [<a href="./rfc5472" title="&quot;IP Flow Information Export (IPFIX) Applicability&quot;">RFC5472</a>] describes what type of applications can use the IPFIX
239 protocol and how they can use the information provided. It
240 furthermore shows how the IPFIX framework relates to other
241 architectures and frameworks.
242
243 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span>
244
245 IPFIX-specific terminology used in this document is defined in
246 <a href="./rfc5101#section-2">Section&nbsp;2 of [RFC5101]</a>. In this document, as in [<a href="./rfc5101" title="&quot;Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of IP Traffic Flow Information&quot;">RFC5101</a>], the first
247 letter of each IPFIX-specific term is capitalized.
248
249 <span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Conventions Used in This Document</span>
250
251 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
252 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
253 document are to be interpreted as described in [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>].
254
255 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Test Specifications</span>
256
257 The tests described in this section MAY be performed using an IPFIX
258 Exporting Process on one host and an IPFIX Collecting Process on a
259 different host. The configuration of the Observation Point, Metering
260 Process, Exporting Process, and Collection Process SHOULD be recorded
261 for every test along with the test results.
262
263 The successful execution of all tests described in this section will
264 give the tester a high confidence that the tested implementation is
265 conformant with the IPFIX architecture and protocol. It does however
266 not provide a 100% comprehensive coverage or formal proof of
267 conformance.
268
269
270
271
272
273
274
275
276 <span class="grey">Schmoll, et al. Informational [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc5471">RFC 5471</a> Guidelines for IPFIX Testing March 2009</span>
279
280
281 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Exporting Process/Collecting Process Connectivity Tests</span>
282
283 This section lists the basic tests that are preconditions for the
284 more complex tests specified in later sections of this document.
285
286 <span class="h4"><a class="selflink" id="section-3.1.1" href="#section-3.1.1">3.1.1</a>. Connectivity Tests between the Exporting Process and Collecting</span>
287 <span class="h4"> Process</span>
288
289 The tester must create one Exporting Process and one Collecting
290 Process, must configure the Exporting Process to export at least one
291 Template Set and associated Data Records to the Collecting Process,
292 and must cause the Exporting Process to initiate the export.
293
294 When the Exporting Process and Collecting Process are to be connected
295 by a Stream Control Transmission Protocol (SCTP) transport, the
296 tester must ensure that an SCTP association is established.
297
298 When the Exporting Process and Collecting Process are to be connected
299 by a TCP transport, the tester must ensure that a TCP connection is
300 established.
301
302 The tester must ensure that the Transport Session parameters (IP
303 addresses and ports) are correct.
304
305 Note that specifying instructions and tools on how to ensure that a
306 Transport Session is correctly established and that the parameters
307 are correct is out of the scope of this document.
308
309 The tester must ensure that the Data Records are actually exported.
310 The transmitted data might be observed online with an appropriate
311 packet sniffing tool. Such a tool is also a viable help to check if
312 the initial connection (SCTP, TCP) has been successfully established.
313
314 The tester must record which combinations of IPv4 and IPv6
315 transports, and UDP, SCTP, and TCP transmission protocols are
316 supported, and should perform the test for all the supported
317 combinations.
318
319 <span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Template and Data Record Tests</span>
320
321 This section lists tests for checking the correct transmission of
322 IPFIX Template Sets and associated Data Sets.
323
324
325
326
327
328
329
330
331
332 <span class="grey">Schmoll, et al. Informational [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc5471">RFC 5471</a> Guidelines for IPFIX Testing March 2009</span>
335
336
337 <span class="h4"><a class="selflink" id="section-3.2.1" href="#section-3.2.1">3.2.1</a>. Transmission of Template with Fixed-Size Information Elements</span>
338
339 The tester must create a Template with a few fixed-size Information
340 Elements where each data type specified in <a href="./rfc5101#section-6.1">Section&nbsp;6.1 of [RFC5101]</a>
341 (octet, unsigned16, unsigned32 ...) is used at least once, and cause
342 the Template and associated Data Records to be exported over all
343 applicable combinations of transports and protocols in <a href="#section-3.1">Section 3.1</a>.
344
345 The tester must ensure that the Template and associated Data Records
346 were correctly received and decoded by the Collecting Process. For
347 this process, the use of verbose debugging output is suggested in
348 order to allow a detailed comparison with the sent (and therefore
349 expected) data.
350
351 <span class="h4"><a class="selflink" id="section-3.2.2" href="#section-3.2.2">3.2.2</a>. Transmission of Template with Variable-Length Information</span>
352 <span class="h4"> Elements</span>
353
354 The tester must create a Template with a mixture of fixed-sized and
355 variable-length Information Elements, as specified in <a href="./rfc5101#section-7">Section&nbsp;7 of
356 [RFC5101]</a>, and cause the Template and associated Data Records to be
357 exported over all applicable combinations of transports and protocols
358 in <a href="#section-3.1">Section 3.1</a>.
359
360 The tester must ensure that the Template contains at least:
361
362 o a single variable-length Information Element.
363
364 o a single variable-length Information Element followed by a
365 fixed-length Information Element.
366
367 o a fixed-length Information Element followed by a variable-
368 length Information Element.
369
370 o multiple variable-length Information Elements.
371
372 The tester must ensure that the Template and associated Data Records
373 were correctly received and decoded by the Collecting Process.
374
375 <span class="h4"><a class="selflink" id="section-3.2.3" href="#section-3.2.3">3.2.3</a>. Set Padding</span>
376
377 <a href="./rfc5101#section-3.3.1">Section&nbsp;3.3.1 of [RFC5101]</a> specifies IPFIX Set alignment using
378 padding.
379
380 The tester must configure a packet generator to generate two Data
381 Sets with padding in between consisting of zero valued octets, as
382 shown in Figure 1. They must be exported to the Collecting Process,
383 which must correctly decode the Data Sets and all the Data Records.
384
385
386
387
388 <span class="grey">Schmoll, et al. Informational [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc5471">RFC 5471</a> Guidelines for IPFIX Testing March 2009</span>
391
392
393 +--------------------------------------------------+
394 | Set Header #1 |
395 +--------------------------------------------------+
396 | Data Record |
397 +--------------------------------------------------+
398 | Data Record |
399 +--------------------------------------------------+
400 ...
401 +--------------------------------------------------+
402 | Data Record |
403 +--------------------------------------------------+
404 | Padding with 0 valued octets |
405 +--------------------------------------------------+
406 | Set Header #2 |
407 +--------------------------------------------------+
408 | Data Record |
409 +--------------------------------------------------+
410
411 Figure 1
412
413 <span class="h4"><a class="selflink" id="section-3.2.4" href="#section-3.2.4">3.2.4</a>. Record Padding</span>
414
415 The tester must configure a packet generator to generate a Template
416 that contains the padding Information Element (i.e., paddingOctets).
417 The Template and associated Data Records must be exported to the
418 Collecting Process, over all applicable combinations of transports
419 and protocols in <a href="#section-3.1">Section 3.1</a>.
420
421 The tester must repeat the test with various padding sizes, including
422 padding to boundaries other than 4 or 8 octets.
423
424 The tester must ensure the Collecting Process correctly interprets
425 cases where the Data Records are so short that the padding is equal
426 to or longer than the length of the record, so the padding might
427 otherwise be interpreted as another record (e.g., 1 byte TOS plus 3
428 bytes of padding). Refer to the specifications in <a href="./rfc5101#section-3.3.1">Section&nbsp;3.3.1 of
429 [RFC5101]</a>. Figure 2 depicts such a Template, while Figure 3 depicts
430 a Data Record conforming to that Template.
431
432
433
434
435
436
437
438
439
440
441
442
443
444 <span class="grey">Schmoll, et al. Informational [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc5471">RFC 5471</a> Guidelines for IPFIX Testing March 2009</span>
447
448
449 0 1 2 3
450 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
451 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
452 | Set ID = 2 | Length = 16 octets |
453 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
454 | Template ID 256 | Field Count = 2 |
455 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
456 |0| ipDiffServCodePoint = 195 | Field Length = 1 |
457 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
458 |0| paddingOctets = 210 | Field Length = 3 |
459 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
460
461 Figure 2
462
463 0 1 2 3
464 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
465 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
466 | Set ID = 256 | Length = 64 |
467 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
468 | 1 | 0 |
469 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
470
471 Figure 3
472
473 The tester must test fixed-size padding (e.g., 12 bytes of data plus
474 2 bytes of padding) and variable-length padding (e.g., export a
475 string and a variable number of padding bytes afterwards to align the
476 next Information Element to a 4 byte boundary).
477
478 <span class="h4"><a class="selflink" id="section-3.2.5" href="#section-3.2.5">3.2.5</a>. Template Withdrawal Message</span>
479
480 IPFIX Template management and Template Withdrawal are specified in
481 <a href="./rfc5101#section-8">Section&nbsp;8 of [RFC5101]</a>.
482
483 <span class="h5"><a class="selflink" id="section-3.2.5.1" href="#section-3.2.5.1">3.2.5.1</a>. Withdrawal of a Previously Sent Template</span>
484
485 The tester must create an IPFIX Template and cause that Template to
486 be exported to an IPFIX Collector over a reliable transport.
487
488 The tester must check that the Template will be correctly received
489 and decoded by the Collecting Process.
490
491 The tester must cause the Exporting Process to send an IPFIX Template
492 Withdrawal Message to the Collector in respect of the Template. The
493 Template Withdrawal Message must be sent over the same Transport
494 Session as the Template.
495
496
497
498
499
500 <span class="grey">Schmoll, et al. Informational [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc5471">RFC 5471</a> Guidelines for IPFIX Testing March 2009</span>
503
504
505 The tester must ensure that the Template Withdrawal Message was
506 correctly received and decoded by the Collecting Process, and that
507 the previously sent Template was discarded by the Collecting Process.
508
509 <span class="h5"><a class="selflink" id="section-3.2.5.2" href="#section-3.2.5.2">3.2.5.2</a>. Withdrawal of a Previously Withdrawn Template</span>
510
511 The tester must create, export, and withdraw an IPFIX Template as
512 described in <a href="#section-3.2.5.1">Section 3.2.5.1</a>.
513
514 The tester must cause the Exporting Process to send a second IPFIX
515 Template Withdrawal Message to the Collector in respect of the same
516 Template. The Template Withdrawal Message must be sent over the same
517 Transport Session as the Template.
518
519 The tester must ensure that the Collecting Process discards the IPFIX
520 Message and shuts down the SCTP association or closes the TCP
521 connection. The tester must check that the Collecting Process logged
522 the error.
523
524 <span class="h5"><a class="selflink" id="section-3.2.5.3" href="#section-3.2.5.3">3.2.5.3</a>. Withdrawal of a Previously Unsent Template</span>
525
526 The tester must cause the Exporting Process to send an IPFIX Template
527 Withdrawal Message to the Collector in respect of a Template that has
528 not yet been exported. The Template Withdrawal Message must be sent
529 over a reliable transport.
530
531 The tester must ensure that the Collecting Process discards the IPFIX
532 Message and shuts down the SCTP association or closes the TCP
533 connection. The tester must check that the Collecting Process logged
534 the error.
535
536 <span class="h5"><a class="selflink" id="section-3.2.5.4" href="#section-3.2.5.4">3.2.5.4</a>. Withdrawing All Data Templates</span>
537
538 The tester must create several IPFIX Templates and cause them to be
539 exported to an IPFIX Collector over a reliable transport.
540
541 The tester must ensure that the Templates were correctly received and
542 decoded by the Collecting Process.
543
544 The tester must cause the Exporting Process to send an IPFIX All Data
545 Templates Withdrawal Message to the Collector over the same Transport
546 Session as the Templates.
547
548 The tester must ensure that the All Data Templates Withdrawal Message
549 was correctly received and decoded by the Collecting Process, and
550 that all the previously sent Templates were discarded by the
551 Collecting Process.
552
553
554
555
556 <span class="grey">Schmoll, et al. Informational [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc5471">RFC 5471</a> Guidelines for IPFIX Testing March 2009</span>
559
560
561 <span class="h5"><a class="selflink" id="section-3.2.5.5" href="#section-3.2.5.5">3.2.5.5</a>. Withdrawing All Option Templates</span>
562
563 The tester must create several IPFIX Option Templates and cause them
564 to be exported to an IPFIX Collector over a reliable transport.
565
566 The tester must ensure that the Option Templates were correctly
567 received and decoded by the Collecting Process.
568
569 The tester must cause the Exporting Process to send an IPFIX All
570 Option Templates Withdrawal Message to the Collector over the same
571 Transport Session as the Templates.
572
573 The tester must ensure that the All Option Templates Withdrawal
574 Message was correctly received and decoded by the Collecting Process,
575 and that all the previously sent Option Templates were discarded by
576 the Collecting Process.
577
578 <span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Information Element Tests</span>
579
580 This section lists the tests that cover the use of Information
581 Elements.
582
583 <span class="h4"><a class="selflink" id="section-3.3.1" href="#section-3.3.1">3.3.1</a>. Enterprise-Specific Information Elements</span>
584
585 The tester must cause the export of a Template and associated Data
586 Record that makes use of Enterprise-specific Information Elements as
587 specified in <a href="./rfc5101#section-3.2">Section&nbsp;3.2 of [RFC5101]</a>.
588
589 The tester must ensure that the Template and associated Data Record
590 are correctly received and decoded by the Collecting Process, and it
591 must ensure that Information Elements that are unknown to the
592 Collecting Process are not silently discarded.
593
594 <span class="h4"><a class="selflink" id="section-3.3.2" href="#section-3.3.2">3.3.2</a>. Reduced Size Encoding of Information Elements</span>
595
596 The tester must cause the export of a Template and associated Data
597 Record containing Information Elements using reduced size encoding as
598 specified in <a href="./rfc5101#section-6.2">Section&nbsp;6.2 of [RFC5101]</a>.
599
600 The tester must ensure that in the case of Information Elements
601 transmitted using reduced size encoding, the Collecting Process is
602 aware of the real size of each Information Element and not only the
603 reduced size used for its transmission.
604
605
606
607
608
609
610
611
612 <span class="grey">Schmoll, et al. Informational [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc5471">RFC 5471</a> Guidelines for IPFIX Testing March 2009</span>
615
616
617 <span class="h4"><a class="selflink" id="section-3.3.3" href="#section-3.3.3">3.3.3</a>. Multiple Instances of the Same Information Element in One</span>
618 <span class="h4"> Template</span>
619
620 The tester must cause the export of a Template and associated Data
621 Record containing multiple instances of the same Information Element
622 consecutively.
623
624 The tester must ensure that the Collecting Process is able to parse
625 the IPFIX Message, and that it stores all values received for all the
626 Information Elements that appeared multiple times in the Template
627 definition.
628
629 The tester must ensure that the Collecting Process reports the
630 Information Elements in the same order as they were specified in the
631 Template Record, as specified in <a href="./rfc5101#section-8">Section&nbsp;8 of [RFC5101]</a>.
632
633 The tester must cause the export of another Template and associated
634 Data Record containing multiple instances of the same Information
635 Element with other Information Elements in between.
636
637 The tester must ensure that the Collecting Process is able to parse
638 the IPFIX Message, and that it stores all values received for all the
639 Information Elements that appeared multiple times in the Template
640 definition.
641
642 The tester must ensure that the Collecting Process reports the
643 Information Elements in the same order as they were specified in the
644 Template Record, as specified in <a href="./rfc5101#section-8">Section&nbsp;8 of [RFC5101]</a>.
645
646 <span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. Options Template Tests</span>
647
648 This section lists the tests that cover the correct transfer of IPFIX
649 Options Templates.
650
651 <span class="h4"><a class="selflink" id="section-3.4.1" href="#section-3.4.1">3.4.1</a>. Using Any Information Elements as Scope</span>
652
653 Options Templates contain scope fields that give the context of the
654 reported Information Elements in the corresponding Data Records.
655 Scope fields are an Information Element specified in [<a href="./rfc5102" title="&quot;Information Model for IP Flow Information Export&quot;">RFC5102</a>].
656
657 The tester SHOULD perform the export of Options Template Records
658 containing various different Information Elements of each of the
659 abstract data types specified in <a href="./rfc5101#section-6.1">Section&nbsp;6.1 of [RFC5101]</a> (octet,
660 unsigned16, unsigned32 ...) in their scope fields, and must export a
661 Data Record using each Template.
662
663 The tester must check that the Templates and the associated Data
664 Records are correctly received and decoded by the Collecting Process.
665
666
667
668 <span class="grey">Schmoll, et al. Informational [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc5471">RFC 5471</a> Guidelines for IPFIX Testing March 2009</span>
671
672
673 The tester must ensure that the Collecting Process accepts
674 Information Elements in the scope field other than IPFIX Information
675 Elements that have been recorded by IANA.
676
677 The tester must ensure that the Collecting Process accepts an
678 Enterprise-specific Information Element in the scope field.
679
680 As specified in <a href="./rfc5101#section-3.4.2.1">Section&nbsp;3.4.2.1 of [RFC5101]</a>, the Scope Field Count
681 must NOT be zero. The tester must cause the export of an Options
682 Template Record containing a Scope Field Count of zero.
683
684 The tester must ensure that the Collecting Process shuts down the
685 SCTP association and discards the IPFIX Message. The tester should
686 check that the Collecting Process logged the error.
687
688 <span class="h4"><a class="selflink" id="section-3.4.2" href="#section-3.4.2">3.4.2</a>. Using Multiple Scopes</span>
689
690 The tester must cause the export of an Options Template Record
691 containing multiple scope fields, and a Data Record conforming to
692 that Template.
693
694 The tester must ensure that the Collecting Process reports the
695 Information Elements in the same order as they were specified in the
696 Options Template Record, as specified in <a href="./rfc5101#section-3.4.2.1">Section&nbsp;3.4.2.1 of
697 [RFC5101]</a>.
698
699 <span class="h4"><a class="selflink" id="section-3.4.3" href="#section-3.4.3">3.4.3</a>. Metering Process Statistics Option Template</span>
700
701 The tester must create a Metering Process Statistics Option Template,
702 as specified in <a href="./rfc5101#section-4.1">Section&nbsp;4.1 of [RFC5101]</a>, and cause the Option
703 Template and an associated Data Record to be exported.
704
705 The tester must ensure that the Collecting Process correctly receives
706 and decodes the Option Template and associated Data Record.
707
708 The tester must also check that the optional meteringProcessId Scope
709 Field is supported by the Collecting Process implementation.
710
711 If several Metering Processes are available on the Exporter
712 Observation Domain, the tester must create a Metering Process
713 Statistics Option Template containing multiple scopes and an
714 associated Data Record, must cause the Option Template and associated
715 Data Record to be exported, and must ensure that the Collecting
716 Process correctly receives and decodes the Option Template and
717 associated Data Record.
718
719
720
721
722
723
724 <span class="grey">Schmoll, et al. Informational [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc5471">RFC 5471</a> Guidelines for IPFIX Testing March 2009</span>
727
728
729 <span class="h4"><a class="selflink" id="section-3.4.4" href="#section-3.4.4">3.4.4</a>. Metering Process Reliability Statistics Option Template</span>
730
731 The tester must create a Metering Process Reliability Statistics
732 Option Template, as specified in <a href="./rfc5101#section-4.2">Section&nbsp;4.2 of [RFC5101]</a>, and must
733 cause the Option Template and an associated Data Record to be
734 exported.
735
736 The tester must ensure that the Collecting Process correctly receives
737 and decodes the Option Template and associated Data Record.
738
739 The tester must also check that the optional meteringProcessId Scope
740 Field is supported by the Collecting Process implementation.
741
742 <span class="h4"><a class="selflink" id="section-3.4.5" href="#section-3.4.5">3.4.5</a>. Exporting Process Reliability Statistics Option Template</span>
743
744 The tester must create an Exporting Process Reliability Statistics
745 Option Template, as specified in <a href="./rfc5101#section-4.3">Section&nbsp;4.3 of [RFC5101]</a>, and must
746 cause the Option Template and an associated Data Record to be
747 exported.
748
749 The tester must ensure that the Collecting Process correctly receives
750 and decodes the Option Template and associated Data Record.
751
752 <span class="h4"><a class="selflink" id="section-3.4.6" href="#section-3.4.6">3.4.6</a>. Flow Keys Option Template</span>
753
754 The tester must create a Flow Keys Option Template, as specified in
755 <a href="./rfc5101#section-4.4">Section&nbsp;4.4 of [RFC5101]</a>, where the templateId refers to an existing
756 Template, and must cause the Option Template and an associated Data
757 Record to be exported.
758
759 The tester must ensure that the Collecting Process correctly receives
760 and decodes the Option Template and associated Data Record, and it
761 must ensure that the Collecting Process associates the Flow Keys with
762 the right Data Record Information Elements.
763
764 The tester must create another Flow Keys Data Record to be exported
765 where the associated templateId has insufficient fields to satisfy
766 the flowKeyIndicator.
767
768 The tester must ensure that the Collecting Process discards the IPFIX
769 Message and shuts down the SCTP association or closes the TCP
770 connection. The tester must check that the Collecting Process logged
771 the error.
772
773 The tester must create another Flow Keys Option Template, where the
774 templateId refers to a non-existing Template, and must cause the
775 Option Template and an associated Data Record to be exported.
776
777
778
779
780 <span class="grey">Schmoll, et al. Informational [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc5471">RFC 5471</a> Guidelines for IPFIX Testing March 2009</span>
783
784
785 The tester must ensure that the Collecting Process shuts down the
786 SCTP association and discards the IPFIX Message. The tester should
787 check that the Collecting Process logged the error.
788
789 <span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a>. Stress/Load Tests</span>
790
791 Stress tests are used to check correct behavior and robustness of an
792 IPFIX Collecting Process implementation when a number of Data Records
793 arrive very quickly. This is especially important when IPFIX over
794 UDP is used, since in that case a slow Collecting Process cannot
795 block the IPFIX Exporting Processes from exporting because UDP is not
796 congestion aware.
797
798 The tests may be dependent upon the hardware and transport technology
799 in use. Therefore, the tests may need to be scaled up or down to
800 meet the needs of the particular implementation. However, the
801 implementer must ensure that the implementation is stable under
802 excessive traffic conditions, for whatever definition of "excessive"
803 applies at their intended installation.
804
805 The implementer must ensure the correct operation of the Exporting
806 Process and/or Collecting Process when the Collecting Process is
807 incapable of processing records at the rate that they are received.
808
809 <span class="h4"><a class="selflink" id="section-3.5.1" href="#section-3.5.1">3.5.1</a>. Large Number of Records for One Template</span>
810
811 The tester should export many Data Records to the Collecting Process,
812 all conforming to the same Template, in order to put the Collecting
813 Process under stress.
814
815 Depending on what the Collecting Process does (save to file, store to
816 database, analyze the data) the Collecting Process may use up a lot
817 of memory.
818
819 The tester must ensure that, if the Collecting Process runs out of
820 memory, it shuts down the specific SCTP association or closes the TCP
821 connection but remains available to receive data on other open
822 Transport Sessions and also stays available for future Transport
823 Sessions.
824
825 <span class="h4"><a class="selflink" id="section-3.5.2" href="#section-3.5.2">3.5.2</a>. Excessive Rate of Incoming Data Records</span>
826
827 The tester should perform a test where Data Records are exported to
828 the Collecting Process with an increasing export rate.
829
830 For TCP or SCTP in reliable mode, the tester must ensure that the
831 export stalls the Exporting Process once the Collecting Process
832 becomes fully loaded.
833
834
835
836 <span class="grey">Schmoll, et al. Informational [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc5471">RFC 5471</a> Guidelines for IPFIX Testing March 2009</span>
839
840
841 For UDP export, the tester must ensure that the Collecting Process
842 drops records as it becomes overloaded, and must check that the
843 Collecting Process logged a warning.
844
845 <span class="h4"><a class="selflink" id="section-3.5.3" href="#section-3.5.3">3.5.3</a>. Large Templates</span>
846
847 The tester must create Templates with the maximum possible number of
848 Information Elements and cause these to be exported to the Collecting
849 Process.
850
851 The total length field in the IP header is 16 bits, allowing a length
852 up to 65535 octets in one application-level datagram. This limits
853 the number of Information Elements one can specify in an IPFIX
854 Template when using UDP export. SCTP and TCP are streaming
855 protocols, so they do not impose much restriction on the packet
856 level. UDP requires 20 octets for a minimal IPv4 header, 8 octets
857 for the UDP header, 16 octets for the IPFIX header, 4 octets for the
858 Set header, and 4 octets for the Template header, so the Template
859 definition may be up to (65535 - 20 - 8 - 16 - 4 - 4) = 65483 octets
860 long. The minimum IPFIX Information Element specification requires 4
861 octets: two for the Information Element ID and two for the field
862 length. Therefore, the maximum number of IPFIX Information Elements
863 in a single Template is 65483 / 4 = 16370. With this many
864 Information Elements, the Template will be 65480 octets long, while
865 the entire packet will be 65532 octets long.
866
867 The tester must create Data Records conforming to this Template, and
868 cause them to be exported. Note that, for the implementation, the
869 associated Data Records might be smaller or larger than the Template
870 Records depending on the length of the Information Elements defined
871 by the Template and on the presence of variable-length Information
872 Elements.
873
874 The tester must ensure that the Collecting Process correctly receives
875 and decodes the Template and associated Data Records.
876
877 <span class="h4"><a class="selflink" id="section-3.5.4" href="#section-3.5.4">3.5.4</a>. Many New Templates within the Data Template Timeout Interval</span>
878
879 The tester should create a large number of different Templates and
880 cause them to be exported to the Collecting Process to stress test
881 the Collecting Process's memory consumption.
882
883 The tester must ensure that the Collecting Process gracefully
884 discards Templates if it's running out of memory resources, and it
885 should check that warnings are logged.
886
887
888
889
890
891
892 <span class="grey">Schmoll, et al. Informational [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc5471">RFC 5471</a> Guidelines for IPFIX Testing March 2009</span>
895
896
897 <span class="h4"><a class="selflink" id="section-3.5.5" href="#section-3.5.5">3.5.5</a>. Multiple Exporting Processes Exporting to One Collecting Process</span>
898
899 The tester must configure multiple Exporting Processes to export
900 Templates and associated Data Records to the same Collecting Process
901 at the same time.
902
903 The tester must ensure that all the Templates and associated Data
904 Records are correctly received and decoded at the Collecting Process,
905 and that no Exporting Process stalls or disconnects completely unless
906 the Collecting Process runs out of memory.
907
908 <span class="h4"><a class="selflink" id="section-3.5.6" href="#section-3.5.6">3.5.6</a>. Export from One Exporting Process to Multiple Collecting</span>
909 <span class="h4"> Processes</span>
910
911 If the Exporting Process supports multiple simultaneous export
912 destinations, the tester must configure the Exporting Process to
913 export Data Records in parallel to different Collecting Processes.
914
915 The tester must configure the use of a mixture of simple and complex
916 Templates and ensure they are all correctly received and decoded by
917 all the Collecting Processes.
918
919 <span class="h3"><a class="selflink" id="section-3.6" href="#section-3.6">3.6</a>. Error Handling</span>
920
921 This section lists and describes a number of problems that might
922 occur in either the network or data transmission or related to wrong
923 information encoding, and that the IPFIX Exporting Process and
924 Collecting Process must be capable of handling in a graceful way. It
925 is intended to test the robustness and fault tolerance of the IPFIX
926 Processes.
927
928 <span class="h4"><a class="selflink" id="section-3.6.1" href="#section-3.6.1">3.6.1</a>. Temporary Network Disconnect</span>
929
930 The IPFIX Exporting Process and Collecting Process behavior must be
931 checked upon interruptions of data transmission due to network
932 failures (whether physical or logical, e.g., defective routing).
933
934 The tester must configure continuous export over all applicable
935 combinations of transports and protocols in <a href="#section-3.1">Section 3.1</a>, in turn.
936
937 For SCTP-based associations and TCP-based connections, the tester
938 should create a short disconnect between the Exporting Process and
939 the Collecting Process (e.g., by momentarily interrupting the network
940 connection) and must ensure that export continues after the
941 connection is repaired. The tester must then create a longer
942 disconnection between the Exporting Process and Collecting Process,
943 and it must ensure that export continues after the connection is
944 repaired.
945
946
947
948 <span class="grey">Schmoll, et al. Informational [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc5471">RFC 5471</a> Guidelines for IPFIX Testing March 2009</span>
951
952
953 For UDP-based data export, there is no noticeable connection loss,
954 but data received with non-consecutive sequence numbers indicates
955 data loss. Refer to the sequence number specifications in <a href="./rfc5101#section-3.1">Section</a>
956 <a href="./rfc5101#section-3.1">3.1 of [RFC5101]</a>. The tester should create a short disconnect
957 between the Exporting Process and Collecting Process, and it must
958 ensure that this is recognized and reported by the Collecting Process
959 per <a href="./rfc5101#section-3.1">Section&nbsp;3.1 of [RFC5101]</a>.
960
961 <span class="h4"><a class="selflink" id="section-3.6.2" href="#section-3.6.2">3.6.2</a>. Exporting Process Termination and Restart during Data</span>
962 <span class="h4"> Transmission</span>
963
964 An IPFIX Collecting Process might be confronted with a faulty
965 Exporting Process implementation that suddenly crashes, dropping any
966 open connections. The Exporting Process may be restarted again soon
967 after the crash.
968
969 Such an event will only be visible to the Collecting Process when the
970 IPFIX Messages (Templates and associated Data Records) are carried
971 over TCP or SCTP. For export via UDP, no such test is available due
972 to the connection-less nature of the transport.
973
974 The tester must configure continuous export over all applicable
975 combinations of SCTP and TCP transports and protocols in <a href="#section-3.1">Section 3.1</a>,
976 in turn. For each combination, the tester must establish export,
977 then kill the active Exporting Process.
978
979 The tester must ensure that the associated Collecting Process shuts
980 down SCTP associations and closes TCP connections associated with
981 that export after a suitable timeout period.
982
983 The tester must Ensure that the Collecting Process discards the
984 Template(s) received on the killed transport session.
985
986 The tester must restart the Exporting Process again, and it must
987 ensure that the Exporting Process exports the Templates again.
988
989 The tester must ensure that the Collecting Process receives and
990 accepts both Templates and associated Data Records from the new
991 Exporting Process running at the same source host.
992
993 <span class="h4"><a class="selflink" id="section-3.6.3" href="#section-3.6.3">3.6.3</a>. Collecting Process Termination and Restart during Data</span>
994 <span class="h4"> Transmission</span>
995
996 An IPFIX Exporting Process might be confronted with a faulty
997 Collecting Process implementation that suddenly crashes, dropping any
998 open Transport Sessions. The Collecting Process may be restarted
999 again soon after the crash.
1000
1001
1002
1003
1004 <span class="grey">Schmoll, et al. Informational [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc5471">RFC 5471</a> Guidelines for IPFIX Testing March 2009</span>
1007
1008
1009 The tester must set up an Exporting Process and Collecting Process
1010 and cause IPFIX Templates and associated Data Records to be exported
1011 over all applicable combinations of SCTP and TCP transports and
1012 protocols in <a href="#section-3.1">Section 3.1</a>, in turn. Via UDP, the restart of the
1013 Collecting Process will be invisible to the Exporting Process and
1014 have no effect.
1015
1016 The tester must terminate the Collecting Process while the export is
1017 in progress, and must ensure that the Exporting Process shuts down
1018 SCTP associations and closes TCP connections associated with that
1019 Collecting Process.
1020
1021 The tester must restart the Collecting Process and ensure that the
1022 Exporting Process connects to the Collecting Process again and that
1023 it exports the IPFIX Templates again.
1024
1025 The tester must ensure that the new Collecting Process correctly
1026 receives and decodes the IPFIX Data Records again.
1027
1028 <span class="h4"><a class="selflink" id="section-3.6.4" href="#section-3.6.4">3.6.4</a>. Incorrect Template Records and Options Template Records</span>
1029
1030 These tests verify the Collecting Process's operation when it
1031 receives a Template Record or Options Template Record with an invalid
1032 message length. Refer to the specifications in <a href="#section-3.4.1">Section 3.4.1</a> and
1033 3.4.2 of [<a href="./rfc5101" title="&quot;Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of IP Traffic Flow Information&quot;">RFC5101</a>], respectively.
1034
1035 Consider the example Template Record shown in Figure 4. This
1036 Template record is missing one Information Element ID and one
1037 Information Element length field. There is insufficient data in the
1038 Set for the specified Set length, and the overall record is four
1039 octets too short for the specified total length.
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060 <span class="grey">Schmoll, et al. Informational [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc5471">RFC 5471</a> Guidelines for IPFIX Testing March 2009</span>
1063
1064
1065 0 1 2 3
1066 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
1067 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1068 | Version = 10 | Total Length = 32 |
1069 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1070 | Export Time = 1155202151 |
1071 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1072 | Sequence Number = 0x12345678 |
1073 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1074 | Observation Domain ID = 0x33334444 |
1075 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1076 | Set ID = 2 | Set Length = 12 |
1077 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1078 | Template ID = 257 | Field Count = 2 |
1079 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1080 |0| Info Element Identifier = 8 | Field Length = 4 |
1081 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1082
1083 Figure 4
1084
1085 The tester must create and cause the Exporting Process to export the
1086 following IPFIX Templates, and must ensure the correct Collecting
1087 Process behavior for each of the transports and protocols in <a href="#section-3.1">Section</a>
1088 <a href="#section-3.1">3.1</a>.
1089
1090 The tester must do the following:
1091
1092 o For SCTP transport, ensure that the Collecting Process discards
1093 the IPFIX Message, shuts down the SCTP association, and logs the
1094 error.
1095
1096 o For TCP transport, ensure that the Collecting Process discards the
1097 IPFIX Message, closes the TCP connection, and logs the error.
1098 Note that since TCP is a streaming (rather than record-based)
1099 protocol, template length errors cannot be detected and may cause
1100 framing to be lost, potentially rendering the remainder of the
1101 IPFIX stream unintelligible. Therefore, some of these tests are
1102 not applicable for TCP transport, as indicated.
1103
1104 o For UDP transport, ensure that the Collecting Process discards the
1105 IPFIX Message and logs the error.
1106
1107 (a) The tester must create the IPFIX Template shown in Figure 4 and
1108 cause the Exporting Process to export it. The tester must ensure
1109 that the Collecting Process's behavior is as specified above for
1110 each transport type except for TCP, for which this test is not
1111 applicable.
1112
1113
1114
1115
1116 <span class="grey">Schmoll, et al. Informational [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc5471">RFC 5471</a> Guidelines for IPFIX Testing March 2009</span>
1119
1120
1121 (b) Consider the IPFIX Template shown in Figure 4, modified with
1122 total length = 28. In this case, the IPFIX Message has to be
1123 rejected because the field count = 2 and there is no second
1124 Information Element record present in the Set. The available
1125 data is exhausted after reading the first Information Element
1126 record.
1127
1128 The tester must create the modified Template and cause the
1129 Exporting Process to export it. The tester must ensure that the
1130 Collecting Process's behavior is as specified above for each
1131 transport type.
1132
1133 (c) Consider the IPFIX Template shown in Figure 4, modified with
1134 total length = 26. In this case, the IPFIX Message has to be
1135 rejected because the IPFIX Message length is too short. After
1136 the first Information Element, the IPFIX Message data is
1137 exhausted according to the total length information.
1138
1139 The tester must create the modified Template and cause the
1140 Exporting Process to export it. The tester must ensure that the
1141 Collecting Process's behavior is as specified above for each
1142 transport type. The TCP connection used for this test must be
1143 manually reset after the test.
1144
1145 (d) Consider the IPFIX Template shown in Figure 4, modified with
1146 field count = 1. In this case, the IPFIX Message must be
1147 rejected because the total length is too large and does not match
1148 the amount of data available.
1149
1150 The tester must create the modified Template and cause the
1151 Exporting Process to export it. The tester must ensure that the
1152 Collecting Process's behavior is as specified above for each
1153 transport type. This test is not applicable for TCP transport.
1154
1155 (e) Finally, when the IPFIX Template shown in Figure 4 is extended
1156 with the data shown in Figure 5, it becomes a correct IPFIX
1157 Template.
1158
1159 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1160 |0| Info Element Identifier = 12| Field Length = 4 |
1161 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1162
1163 Figure 5
1164
1165 The tester must create the modified Template and cause the
1166 Exporting Process to export it. The tester must ensure that the
1167 Template is accepted by the Collecting Process for each transport
1168 type.
1169
1170
1171
1172 <span class="grey">Schmoll, et al. Informational [Page 21]</span></pre>
1173 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
1174 <span class="grey"><a href="./rfc5471">RFC 5471</a> Guidelines for IPFIX Testing March 2009</span>
1175
1176
1177 The example Template record shown in Figure 6 must be dropped because
1178 the scope field count = 0.
1179
1180 0 1 2 3
1181 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
1182 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1183 | Version = 10 | Total Length = 30 |
1184 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1185 | Export Time = 1155202151 |
1186 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1187 | Sequence Number = 0x12345678 |
1188 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1189 | Observation Domain ID = 0x33334444 |
1190 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1191 | Set ID = 3 | Set Length = 14 |
1192 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1193 | Template ID = 257 | Field Count = 1 |
1194 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1195 | Scope Field Count = 0 |0| Info Element Identifier = 8 |
1196 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1197 | Field Length = 4 |
1198 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1199
1200 Figure 6
1201
1202 The tester must create the Template shown in Figure 6 and cause the
1203 Exporting Process to export it. The tester must ensure that the
1204 IPFIX Message is discarded by the Collecting Process for each
1205 transport type, and must check that the Collecting Process logs an
1206 error. The tester must ensure that the Collecting Process also shuts
1207 down the SCTP association or closes the TCP connection.
1208
1209 The tester must create an IPFIX Options Template where the field
1210 count is less than the scope field count, and cause the Exporting
1211 Process to export it. Use the above IPFIX Options Template with
1212 scope field count = 2. The tester must ensure that the Template is
1213 discarded by the Collecting Process for each transport type, and must
1214 check that the Collecting Process logs an error. The tester must
1215 ensure that the Collecting Process shuts down the SCTP association or
1216 closes the TCP connection.
1217
1218 <span class="h4"><a class="selflink" id="section-3.6.5" href="#section-3.6.5">3.6.5</a>. Incorrect Data Record</span>
1219
1220 The tester must create the following invalid Data Records and cause
1221 them to be exported to the Collecting Process over all applicable
1222 combinations of transports and protocols in <a href="#section-3.1">Section 3.1</a>.
1223
1224
1225
1226
1227
1228 <span class="grey">Schmoll, et al. Informational [Page 22]</span></pre>
1229 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
1230 <span class="grey"><a href="./rfc5471">RFC 5471</a> Guidelines for IPFIX Testing March 2009</span>
1231
1232
1233 o IPFIX Message too short.
1234
1235 o Illegal use of reduced size encoding.
1236
1237 o Invalid length specification in case of variable-length
1238 Information Elements.
1239
1240 The tester must ensure that the Collecting Process discards the IPFIX
1241 Message and shuts down the SCTP association or closes the TCP
1242 connection.
1243
1244 <span class="h4"><a class="selflink" id="section-3.6.6" href="#section-3.6.6">3.6.6</a>. Export of Non-Matching Template and Data Records</span>
1245
1246 The tester must create Templates and associated Data Records that
1247 fail to conform to those Templates in the following ways:
1248
1249 o too few Information Elements in Data Record
1250
1251 o too many Information Elements in Data Record
1252
1253 The tester must cause the Templates and associated Data Records to be
1254 exported to the Collecting Process over all applicable combinations
1255 of transports and protocols in <a href="#section-3.1">Section 3.1</a>.
1256
1257 The tester must ensure that the Collecting Process discards the IPFIX
1258 Message and shuts down the SCTP association or closes the TCP
1259 connection.
1260
1261 <span class="h4"><a class="selflink" id="section-3.6.7" href="#section-3.6.7">3.6.7</a>. Unknown Set IDs</span>
1262
1263 The tester must create Template Sets, Option Template Sets, and
1264 associated Data Sets using Set IDs which are unknown to the
1265 Collecting Process, and cause these to be exported to the Collecting
1266 Process over all applicable combinations of transports and protocols
1267 in <a href="#section-3.1">Section 3.1</a>.
1268
1269 Per <a href="./rfc5101#section-3.3.2">Section&nbsp;3.3.2 of [RFC5101]</a>, only the Set ID values 2 and 3 denote
1270 valid Sets.
1271
1272 The tester must ensure that the Collecting Process ignores the
1273 unknown Sets, logs a warning, and processes the remainder of the
1274 IPFIX Message.
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284 <span class="grey">Schmoll, et al. Informational [Page 23]</span></pre>
1285 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
1286 <span class="grey"><a href="./rfc5471">RFC 5471</a> Guidelines for IPFIX Testing March 2009</span>
1287
1288
1289 <span class="h4"><a class="selflink" id="section-3.6.8" href="#section-3.6.8">3.6.8</a>. Re-Using Template IDs</span>
1290
1291 <span class="h5"><a class="selflink" id="section-3.6.8.1" href="#section-3.6.8.1">3.6.8.1</a>. Using SCTP Transport</span>
1292
1293 Refer to <a href="./rfc5101#section-9">Section&nbsp;9 of [RFC5101]</a> for the Collecting Process's SCTP
1294 Template management specifications.
1295
1296 The tester must create an IPFIX Template and cause it to be exported
1297 to a Collecting Process over SCTP transport.
1298
1299 The tester must ensure that the Template was correctly received and
1300 decoded by the Collecting Process.
1301
1302 The tester must cause the same Template to be exported to the same
1303 Collecting Process over the same SCTP association, and must ensure
1304 that the Collecting Process resets the SCTP association and discards
1305 the IPFIX Message.
1306
1307 The tester must create another IPFIX template and cause it to be
1308 exported to the Collecting Process over SCTP transport.
1309
1310 The tester must ensure that the Template was correctly received and
1311 decoded by the Collecting Process.
1312
1313 The tester must modify the Template contents while retaining the same
1314 Template ID.
1315
1316 The tester must cause the modified Template to be exported to the
1317 same Collecting Process over the SCTP same association, and must
1318 ensure that the Collecting Process resets the SCTP association and
1319 discards the IPFIX Message.
1320
1321 The tester must check that an error was logged.
1322
1323 The tester must create another IPFIX Template and cause it to be
1324 exported to the Collecting Process over SCTP transport.
1325
1326 The tester must ensure that the Template was correctly received and
1327 decoded by the Collecting Process.
1328
1329 The tester must cause a Template Withdrawal Message for the Template
1330 to be sent to the Collecting Process over the same SCTP association,
1331 and must ensure that the Template has been discarded by the
1332 Collecting Process.
1333
1334 The tester must create Data Records conforming to the Template and
1335 cause them to be exported to the Collecting Process over the same
1336 SCTP association.
1337
1338
1339
1340 <span class="grey">Schmoll, et al. Informational [Page 24]</span></pre>
1341 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
1342 <span class="grey"><a href="./rfc5471">RFC 5471</a> Guidelines for IPFIX Testing March 2009</span>
1343
1344
1345 The tester must ensure that the Collecting Process discards the Data
1346 Records and logs a warning.
1347
1348 The tester must cause the same Template to be exported to the same
1349 Collecting Process over the same SCTP association.
1350
1351 The tester must ensure that the Template was correctly received and
1352 decoded by the Collecting Process.
1353
1354 The tester must create Data Records conforming to the Template and
1355 cause them to be exported to the Collecting Process over the same
1356 SCTP association.
1357
1358 The tester must ensure that the Collecting Process correctly receives
1359 and decodes the Data Records.
1360
1361 <span class="h5"><a class="selflink" id="section-3.6.8.2" href="#section-3.6.8.2">3.6.8.2</a>. Using TCP Transport</span>
1362
1363 Refer to <a href="./rfc5101#section-10.4.3">Section&nbsp;10.4.3 of [RFC5101]</a> for the Collecting Process's TCP
1364 Template management specifications.
1365
1366 The tester must create an IPFIX Template and cause it to be exported
1367 to a Collecting Process over TCP transport.
1368
1369 The tester must ensure that the Template was correctly received and
1370 decoded by the Collecting Process.
1371
1372 The tester must cause the same Template to be exported to the same
1373 Collecting Process over the same TCP connection, and must ensure that
1374 the Collecting Process resets the TCP connection and discards the
1375 IPFIX Message.
1376
1377 The tester must create an IPFIX Template and cause it to be exported
1378 to the Collecting Process over TCP transport.
1379
1380 The tester must ensure that the Template was correctly received and
1381 decoded by the Collecting Process.
1382
1383 The tester must modify the Template contents while retaining the same
1384 Template ID.
1385
1386 The tester must cause the modified Template to be exported to the
1387 same Collecting Process over the same TCP connection, and must ensure
1388 that the Collecting Process resets the TCP connection and discards
1389 the IPFIX Message.
1390
1391 The tester must check that an error was logged.
1392
1393
1394
1395
1396 <span class="grey">Schmoll, et al. Informational [Page 25]</span></pre>
1397 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
1398 <span class="grey"><a href="./rfc5471">RFC 5471</a> Guidelines for IPFIX Testing March 2009</span>
1399
1400
1401 The tester must create another IPFIX Template and cause it to be
1402 exported to the Collecting Process over TCP transport.
1403
1404 The tester must ensure that the Template was correctly received and
1405 decoded by the Collecting Process.
1406
1407 The tester must cause a Template Withdrawal Message for the Template
1408 to be sent to the Collecting Process over the same TCP connection,
1409 and must ensure that the Template has been discarded by the
1410 Collecting Process.
1411
1412 The tester must create Data Records conforming to the same Template
1413 and cause them to be exported to the same Collecting Process over the
1414 same TCP connection.
1415
1416 The tester must ensure that the Collecting Process discards the Data
1417 Records and logs a warning.
1418
1419 The tester must cause the same Template to be exported to the same
1420 Collecting Process over the same TCP connection.
1421
1422 The tester must ensure that the Template was correctly received and
1423 decoded by the Collecting Process.
1424
1425 The tester must create Data Records conforming to the Template and
1426 cause them to be exported to the same Collecting Process over the
1427 same TCP connection.
1428
1429 The tester must ensure that the Collecting Process correctly receives
1430 and decodes the Data Records.
1431
1432 <span class="h5"><a class="selflink" id="section-3.6.8.3" href="#section-3.6.8.3">3.6.8.3</a>. Using UDP Transport</span>
1433
1434 Refer to Sections <a href="#section-10.3.6">10.3.6</a> and <a href="#section-10.3.7">10.3.7</a> of [<a href="./rfc5101" title="&quot;Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of IP Traffic Flow Information&quot;">RFC5101</a>] for the UDP Template
1435 management specifications.
1436
1437 <span class="h6"><a class="selflink" id="section-3.6.8.3.1" href="#section-3.6.8.3.1">3.6.8.3.1</a>. Re-Using the Same Template ID inside the Template Lifetime</span>
1438
1439 The tester must create an IPFIX Template and cause it to be exported
1440 to a Collecting Process over UDP transport.
1441
1442 The tester must ensure that the Template was correctly received and
1443 decoded by the Collecting Process.
1444
1445 Before the Template lifetime expires on the Collecting Process, the
1446 tester must cause the same Template to be exported over the same UDP
1447 connection to the same Collecting Process and must ensure that the
1448 Collecting Process accepts the Template.
1449
1450
1451
1452 <span class="grey">Schmoll, et al. Informational [Page 26]</span></pre>
1453 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span>
1454 <span class="grey"><a href="./rfc5471">RFC 5471</a> Guidelines for IPFIX Testing March 2009</span>
1455
1456
1457 The tester must create a different Template with the same ID and must
1458 cause this to be exported to the same Collecting Process over the
1459 same UDP connection before the original Template lifetime expires.
1460
1461 The tester must ensure that the Collecting Process does not reject
1462 the new Template.
1463
1464 The tester must create Data Records conforming to the new Template
1465 and cause them to be exported to the same Collecting Process over the
1466 same UDP connection.
1467
1468 The tester must ensure that the Collecting Process correctly receives
1469 and decodes the Data Records.
1470
1471 <span class="h6"><a class="selflink" id="section-3.6.8.3.2" href="#section-3.6.8.3.2">3.6.8.3.2</a>. Re-Using the Same Template ID after the Template Lifetime</span>
1472
1473 The tester must create an IPFIX Template and cause it to be exported
1474 to a Collecting Process over UDP transport.
1475
1476 The tester must ensure that the Template was correctly received and
1477 decoded by the Collecting Process.
1478
1479 The tester must allow the received Template lifetime to expire on the
1480 Collecting Process.
1481
1482 The tester must create Data Records conforming to the Template and
1483 cause them to be exported to the same Collecting Process over the
1484 same UDP connection.
1485
1486 The tester must ensure that the Collecting Process discards the Data
1487 Records.
1488
1489 The tester must check that the Collecting Process logs a warning.
1490
1491 The tester must cause the same Template to be exported to the same
1492 Collecting Process over the same UDP connection.
1493
1494 The tester must ensure that the Template was correctly received and
1495 decoded by the Collecting Process.
1496
1497 The tester must create Data Records conforming to the Template and
1498 cause them to be exported to the same Collecting Process over the
1499 same UDP connection.
1500
1501 The tester must ensure that the Collecting Process correctly receives
1502 and decodes the Data Records.
1503
1504
1505
1506
1507
1508 <span class="grey">Schmoll, et al. Informational [Page 27]</span></pre>
1509 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span>
1510 <span class="grey"><a href="./rfc5471">RFC 5471</a> Guidelines for IPFIX Testing March 2009</span>
1511
1512
1513 <span class="h3"><a class="selflink" id="section-3.7" href="#section-3.7">3.7</a>. TLS Connectivity and Policy Selection</span>
1514
1515 This section lists tests that verify connectivity over TLS and
1516 Datagram Transport Layer Security (DTLS) and proper selection of TLS
1517 policies as specified in the IPFIX Protocol. It specifically does
1518 NOT purport to test the security of IPFIX Message transport over TLS
1519 or DTLS, as evaluating the security of a transport session is really
1520 a test of the TLS or DTLS implementation over which a given IPFIX
1521 implementation runs, and as such is out of scope for this document.
1522
1523 Refer to <a href="./rfc5101#section-11">Section&nbsp;11 of [RFC5101]</a> for the security specifications.
1524
1525 <span class="h4"><a class="selflink" id="section-3.7.1" href="#section-3.7.1">3.7.1</a>. TLS Test Setup</span>
1526
1527 Setting up for TLS connectivity and policy testing requires the
1528 creation of appropriate X.509 certificates and private keys for a
1529 test environment and the configuration of a DNS server to answer with
1530 consistent information for the hosts used in the test.
1531
1532 The tester must configure the following certificates:
1533
1534 1. A Certificate Authority (CA) certificate and associated
1535 private key for signing the following certificates.
1536
1537 2. One certificate and associated private key, with a CN (Common
1538 Name) or subjectAltName extension of type dNSName containing
1539 the fully qualified domain name of the host, signed by the CA
1540 certificate in 1, for each IPFIX Exporting Process in the
1541 test.
1542
1543 3. One certificate and associated private key, with a CN (common
1544 name) or subjectAltName extension of type dNSName containing
1545 the fully qualified domain name of the host, signed by the CA
1546 certificate in 1, for each IPFIX Collecting Process in the
1547 test.
1548
1549 The tester must configure consistent forward (A, AAAA) DNS records
1550 for each host in the test on a DNS server used by the hosts for name
1551 resolution. Note that there is no need to configure reverse (PTR)
1552 DNS records for the hosts, as no part of the protocol uses reverse
1553 lookups.
1554
1555 The tester must ensure that the Exporting Process and Collecting
1556 Process are on different hosts.
1557
1558
1559
1560
1561
1562
1563
1564 <span class="grey">Schmoll, et al. Informational [Page 28]</span></pre>
1565 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span>
1566 <span class="grey"><a href="./rfc5471">RFC 5471</a> Guidelines for IPFIX Testing March 2009</span>
1567
1568
1569 <span class="h4"><a class="selflink" id="section-3.7.2" href="#section-3.7.2">3.7.2</a>. TLS over TCP Connectivity Test</span>
1570
1571 The tester must set up certificates and DNS as in <a href="#section-3.7.1">Section 3.7.1</a>.
1572
1573 The tester must configure one Exporting Process and one Collecting
1574 Process with their appropriate certificates to transfer IPFIX
1575 Messages over TLS over TCP.
1576
1577 The tester must create an IPFIX Template and associated Data Record,
1578 and cause them to be exported over the TCP connection.
1579
1580 The tester must ensure that a TCP connection and a TLS connection
1581 were established, must ensure that data was exchanged, and must
1582 ensure that the data received at the Collecting Process is correct.
1583
1584 <span class="h4"><a class="selflink" id="section-3.7.3" href="#section-3.7.3">3.7.3</a>. DTLS over UDP Connectivity Test</span>
1585
1586 The tester must set up certificates and DNS as in <a href="#section-3.7.1">Section 3.7.1</a>.
1587
1588 The tester must configure one Exporting Process and one Collecting
1589 Process with their appropriate certificates to transfer IPFIX
1590 Messages over DTLS over UDP.
1591
1592 The tester must create an IPFIX Template and associated Data Record,
1593 and cause them to be exported over the UDP connection.
1594
1595 The tester must ensure that UDP packets were sent and a DTLS
1596 connection was established, must ensure that data was exchanged, and
1597 must ensure that the data received at the Collecting Process is
1598 correct.
1599
1600 <span class="h4"><a class="selflink" id="section-3.7.4" href="#section-3.7.4">3.7.4</a>. DTLS over PR-SCTP Connectivity Test</span>
1601
1602 The tester must set up certificates and DNS as in <a href="#section-3.7.1">Section 3.7.1</a>.
1603
1604 The tester must configure one Exporting Process and one Collecting
1605 Process with their appropriate certificates to transfer IPFIX
1606 Messages over DTLS over the Partially Reliable-Stream Control
1607 Transmission Protocol (PR-SCTP).
1608
1609 The tester must create an IPFIX Template and associated Data Record,
1610 and cause them to be exported over the SCTP association.
1611
1612 The tester must ensure that an SCTP association and a DTLS connection
1613 were established, must ensure that data was exchanged, and must
1614 ensure that the data received at the Collecting Process is correct.
1615
1616
1617
1618
1619
1620 <span class="grey">Schmoll, et al. Informational [Page 29]</span></pre>
1621 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span>
1622 <span class="grey"><a href="./rfc5471">RFC 5471</a> Guidelines for IPFIX Testing March 2009</span>
1623
1624
1625 <span class="h4"><a class="selflink" id="section-3.7.5" href="#section-3.7.5">3.7.5</a>. TLS Bidirectional Authentication Policy Test</span>
1626
1627 This is an optional test for Collecting Processes only; it requires
1628 the modification of an Exporting Process to NOT present a
1629 certificate.
1630
1631 The tester must modify an Exporting Process to NOT present a
1632 certificate.
1633
1634 The tester must perform the connectivity tests in Sections <a href="#section-3.7.2">3.7.2</a>,
1635 3.7.3, and 3.7.4.
1636
1637 The tester must ensure that the Collecting Process rejects the TLS or
1638 DTLS connection establishment.
1639
1640 <span class="h4"><a class="selflink" id="section-3.7.6" href="#section-3.7.6">3.7.6</a>. Exporting Process Identity Mismatch TLS Policy Test</span>
1641
1642 The tester must set up certificates and DNS as in <a href="#section-3.7.1">Section 3.7.1</a>.
1643
1644 The tester must use a certificate for the Exporting Process that does
1645 NOT match the fully qualified domain name of the host on which the
1646 Exporting Process runs.
1647
1648 The tester must Perform the connectivity tests in Sections <a href="#section-3.7.2">3.7.2</a>,
1649 3.7.3, and 3.7.4.
1650
1651 The tester must ensure that the Collecting Process rejects the TLS or
1652 DTLS connection establishment.
1653
1654 <span class="h4"><a class="selflink" id="section-3.7.7" href="#section-3.7.7">3.7.7</a>. Collecting Process Identity Mismatch TLS Policy Test</span>
1655
1656 The tester must set up certificates and DNS as in <a href="#section-3.7.1">Section 3.7.1</a>.
1657
1658 The tester must use a certificate for the Collecting Process that
1659 does NOT match the fully qualified domain name of the host on which
1660 the Collecting Process runs.
1661
1662 The tester must perform the connectivity tests in Sections <a href="#section-3.7.2">3.7.2</a>,
1663 3.7.3, and 3.7.4.
1664
1665 The tester must ensure that the Exporting Process rejects the TLS or
1666 DTLS connection establishment.
1667
1668 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
1669
1670 This memo raises no security issues.
1671
1672
1673
1674
1675
1676 <span class="grey">Schmoll, et al. Informational [Page 30]</span></pre>
1677 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span>
1678 <span class="grey"><a href="./rfc5471">RFC 5471</a> Guidelines for IPFIX Testing March 2009</span>
1679
1680
1681 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Acknowledgments</span>
1682
1683 The authors wish to thank Brian Trammell for contributing the initial
1684 text for <a href="#section-3.7">Section 3.7</a>.
1685
1686 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Normative References</span>
1687
1688 [<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
1689 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
1690
1691 [<a id="ref-RFC3917">RFC3917</a>] Quittek, J., Zseby, T., Claise, B., and S. Zander,
1692 "Requirements for IP Flow Information Export (IPFIX)", <a href="./rfc3917">RFC</a>
1693 <a href="./rfc3917">3917</a>, October 2004.
1694
1695 [<a id="ref-RFC5101">RFC5101</a>] Claise, B., Ed., "Specification of the IP Flow Information
1696 Export (IPFIX) Protocol for the Exchange of IP Traffic
1697 Flow Information", <a href="./rfc5101">RFC 5101</a>, January 2008.
1698
1699 [<a id="ref-RFC5102">RFC5102</a>] Quittek, J., Bryant, S., Claise, B., Aitken, P., and J.
1700 Meyer, "Information Model for IP Flow Information Export",
1701 <a href="./rfc5102">RFC 5102</a>, January 2008.
1702
1703 [<a id="ref-RFC5470">RFC5470</a>] Sadasivan, G., Brownlee, N., Claise, B., and J. Quittek,
1704 "Architecture for IP Flow Information Export", <a href="./rfc5470">RFC 5470</a>,
1705 March 2009.
1706
1707 [<a id="ref-RFC5472">RFC5472</a>] Zseby, T., Boschi, E., Brownlee, N., and B. Claise, "IP
1708 Flow Information Export (IPFIX) Applicability", <a href="./rfc5472">RFC 5472</a>,
1709 March 2009.
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732 <span class="grey">Schmoll, et al. Informational [Page 31]</span></pre>
1733 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span>
1734 <span class="grey"><a href="./rfc5471">RFC 5471</a> Guidelines for IPFIX Testing March 2009</span>
1735
1736
1737 Authors' Addresses
1738
1739 Carsten Schmoll
1740 Fraunhofer FOKUS
1741 Kaiserin-Augusta-Allee 31
1742 Berlin D-10589
1743 Germany
1744
1745 Phone: +49 30 3463 7136
1746 EMail: [email protected]
1747 URI: <a href="http://www.fokus.fraunhofer.de">http://www.fokus.fraunhofer.de</a>
1748
1749
1750 Paul Aitken
1751 Cisco Systems, Inc.
1752 96 Commercial Quay
1753 Edinburgh EH6 6LX
1754 Scotland
1755
1756 Phone: +44 131 561 3616
1757 EMail: [email protected]
1758 URI: <a href="http://www.cisco.com">http://www.cisco.com</a>
1759
1760
1761 Benoit Claise
1762 Cisco Systems, Inc.
1763 De Kleetlaan 6a b1
1764 1831 Diegem
1765 Belgium
1766
1767 Phone: +32 2 704 5622
1768 EMail: [email protected]
1769 URI: <a href="http://www.cisco.com">http://www.cisco.com</a>
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788 Schmoll, et al. Informational [Page 32]
1789 </pre>