70 likes | 75 Vues
Paul Aitken ( paitken@cisco.com ) Carsten Schmoll ( schmoll@fokus.fraunhofer.de ) 67th IETF - San Diego, CA, USA IPFIX Working Group. IPFIX Testing Draft draft-ietf-ipfix-testing-00.txt ( was draft-schmoll-ipfix-testing-00.txt ). Introduction. IPFIX is very versatile – good!
E N D
Paul Aitken (paitken@cisco.com) Carsten Schmoll (schmoll@fokus.fraunhofer.de) 67th IETF - San Diego, CA, USA IPFIX Working Group IPFIX Testing Draftdraft-ietf-ipfix-testing-00.txt( was draft-schmoll-ipfix-testing-00.txt )
Introduction • IPFIX is very versatile – good! • It’s a binary – non-human readable – data transport protocol Lots of things can be broken in an implementation • Programmers tend to implement the “good” cases first, and overlook some error cases Time to list what can go wrong and test it
Overview • Tests: • Exporter and Collector Connectivity (IPv4/6, TCP/UDP/SCTP) • Data Template and Data Transmission Tests • Information Element Tests • Option Template Tests • Stress/Load Tests • Error Handling • Goal: do your homework then go to interop tests, into “unknown territory”
Recent Changes • Corrected terminology • Added Template Withdrawal Message • Added figures to illustrate incorrect Templates
To Do • Update with recent feedback • Include testing of SCTP and TLS from the next interop Berlin, November 29/30, 2006 http://ants.fokus.fraunhofer.de/ipfix/interop06/
Possible Future Direction • More formal test specification (TTCN) • Out-of-the-box IPFIX test suite for everyone • “library” of defective packets • Suggestions?
The End • For the draft see: • draft-ietf-ipfix-testing-00.txt • Comments?