40 likes | 59 Views
This document provides updates and enhancements to the IPFIX protocol, addressing limitations, and open issues. It includes an accounting example, IPFIX and RMON comparison, IPv6 compatibility, and more. The text has been improved with additional sections for better clarity and utility. Reliability requirements for usage-based accounting systems are emphasized, aligning with RFC guidelines. Enhancements to the IPFIX Information Model and further potential issues are discussed, aiming to optimize IPFIX usability and address any remaining concerns.
E N D
IPFIX Applicability Updatedraft-ietf-ipfix-as-04.txt Tanja Zseby, FhG FOKUS Elisa Boschi, FhG FOKUS Nevil Brownlee, CAIDA Benoit Claise, Cisco Systems
Changes • Added Accounting Example • As requested last time: “rather show a common example not an exotic one” • Added some sections • IPFIX Limitations (was: “Where not to use IPFIX”) • IPFIX and RMON • IPFIX and IPv6 • Shortened some sections • IPFIX and RTFM • IPFIX and PSAMP • Removed section "IPFIX and TEWG“ • no volunteers • considered not so relevant • Improved introduction • Some small corrections and a bit of rewriting IPFIX Applicability
Open Issues • IPFIX Limitations (comment Tal Givoli on list) • RFC 3917 (Requirement Draft): “Requirements defined in sections 5.1 and 6.3.2. are not sufficient to guarantee the level of reliability that is needed for many usage-based accounting systems. Particular reliability requirements for accounting systems are discussed in [RFC2975].” • add some text on this in IPFIX limitations • IPFIX and PSAMP • Explicitly mention usability of IPFIX by extending IPIFX Info Model • Further issues ? IPFIX Applicability
Thank you for your attention ! Questions ?