IPFIX MIB Status Managed Object for IP Flow Export A Status Report Thomas Dietz Atsushi Kobayashi Benoit Claise

09/11/2006IETF 672 Overview Current Structure of the MIB Modules Issues Proposed Changes Categorization of Writeability Writeability by Structure

09/11/2006IETF 673 Current Structure – Collector Exporters Exporters where reports are received from Session Currently active Export Sessions Templates Received Templates

09/11/2006IETF 674 Current Structure – Exporter Reporting Collectors and Groups of Collectors Templates Templates with Fields Instances Definition of Observation Domain Structure to bind Reporting and Templates together Methods Used as a placeholder for PSAMP usage

09/11/2006IETF 675 Issues Transport Session is missing Scope and Flow Key is missing Observation Domain is not really defined Writeability of the MIB

09/11/2006IETF 676 Proposed Changes – Collector Do minor alignments with the Exporter parts Align statistics with Exporter parts Thoroughly review alignment with other drafts Check Documentation of Objects

09/11/2006IETF 677 Proposed Changes – Exporter Introduce the transport session table Source and Destination IP Source and Destination Port Protocol Type (udp/tcp/sctp) Address Type (v4/v6) Index (text or integer) Refresh Timer for Templates and Option Templates (time or packets)

09/11/2006IETF 678 Proposed Changes – Exporter cont. 1 Reporting Substitute Collectors by Transport Sessions Keep Collector Groups but add attributes Backup Transport Session, Parallel Exporting etc. Templates Add flags for scope and flow key Add object for expressing variable length Methods Link to Transport Session and/or Template

09/11/2006IETF 679 Proposed Changes – Exporter cont. 2 Instance Remove Instance since the function is taken by the Transport Session Observation Domain Table could become very huge if listing all Domains with all Observation Points (ifIndex) We propose to simplify the MIB by assigning the ENTITY-MIB index to the Observation Domain Id  If yes is it a MIB only issue or should it also be added to the protocol draft?

09/11/2006IETF 6710 Categorization of Writeability We propose 3 categories Read Only Conformance Dependent Read Only by default, but may be implemented Read Write Read Write

09/11/2006IETF 6711 Writeability – Collector Read Only

09/11/2006IETF 6712 Writeability – Exporter Reporting Session– Read Write Collector Group – Read Write Templates Read Only Conformance Dependent if there is a good business case Methods Read Only or Conformance Dependent if there is a good business case

09/11/2006IETF 6713 The End Thank you for your attention