1 / 7

IPFIX Testing Draft draft-ietf-ipfix-testing-00.txt ( was draft-schmoll-ipfix-testing-00.txt )

This draft discusses the importance of testing and identifying potential errors in IPFIX implementations. It covers various tests including connectivity, data transmission, error handling, and more to improve reliability. Future directions include formal test specifications and an IPFIX test suite.

ljoel
Télécharger la présentation

IPFIX Testing Draft draft-ietf-ipfix-testing-00.txt ( was draft-schmoll-ipfix-testing-00.txt )

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 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 )

  2. 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

  3. 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”

  4. Recent Changes • Corrected terminology • Added Template Withdrawal Message • Added figures to illustrate incorrect Templates

  5. 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/

  6. Possible Future Direction • More formal test specification (TTCN) • Out-of-the-box IPFIX test suite for everyone • “library” of defective packets • Suggestions?

  7. The End • For the draft see: • draft-ietf-ipfix-testing-00.txt • Comments?

More Related