1 / 13

Enhancements and Issues in the IPFIX MIB Status Report: Proposed Changes and Solutions

This report discusses the current structure and issues of the IPFIX MIB related to flow export status management. It highlights proposed changes to enhance collector and exporter functionalities, defines writeability categories, and addresses missing elements like transport sessions and observation domains. The report suggests alignments with other drafts and proposes improvements to ensure clarity and functionality. Key changes include the introduction of transport session tables, adjustments to templates, and simplifications for observation domains, with an overall aim to enhance IPFIX data reporting.

tress
Télécharger la présentation

Enhancements and Issues in the IPFIX MIB Status Report: Proposed Changes and Solutions

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. IPFIX MIB Status Managed Object for IP Flow Export A Status ReportThomas Dietz dietz@netlab.nec.de Atsushi Kobayashi akoba@nttv6.net Benoit Claise bclaise@cisco.com

  2. Overview • Current Structure of the MIB Modules • Issues • Proposed Changes • Categorization of Writeability • Writeability by Structure IETF 67

  3. Current Structure – Collector • Exporters • Exporters where reports are received from • Session • Currently active Export Sessions • Templates • Received Templates IETF 67

  4. 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 IETF 67

  5. Issues • Transport Session is missing • Scope and Flow Key is missing • Observation Domain is not really defined • Writeability of the MIB IETF 67

  6. 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 IETF 67

  7. 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) IETF 67

  8. 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 IETF 67

  9. 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? IETF 67

  10. Categorization of Writeability • We propose 3 categories • Read Only • Conformance Dependent • Read Only by default, but may be implemented Read Write • Read Write IETF 67

  11. Writeability – Collector • Read Only IETF 67

  12. 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 IETF 67

  13. The End Thank you for your attention IETF 67

More Related