1 / 6

Gerhard Münz, Benoit Claise 70th IETF Meeting, Vancouver, 2007

Configuration Data Model for IPFIX and PSAMP Review of draft-muenz-ipfix-configuration-02.txt and changes in draft-muenz-ipfix-configuration-03.txt http://www.history-project.net/ipfix-configuration/draft-muenz-ipfix-configuration-03.txt. Gerhard Münz, Benoit Claise

sheffieldm
Télécharger la présentation

Gerhard Münz, Benoit Claise 70th IETF Meeting, Vancouver, 2007

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. Configuration Data Model forIPFIX and PSAMP Review of draft-muenz-ipfix-configuration-02.txtandchanges in draft-muenz-ipfix-configuration-03.txthttp://www.history-project.net/ipfix-configuration/draft-muenz-ipfix-configuration-03.txt Gerhard Münz, Benoit Claise 70th IETF Meeting, Vancouver, 2007

  2. Reviews received for -02 • We received three thorough reviews. Thank you very much!!! • Comments about how to improve the text: • add note of caution concerning configuration of Template IDs • done in -03 • problems to understand configuration of a Metering Process as combination of Selection Process instance(s) and one cache instance • hopefully better explained and motivated in -03 • configuration data model is also useful for storage of configuration data • mentioned in the introduction of -03 70th IETF Meeting, Vancouver, 2007

  3. Reviews received for -02 • Comments concerning the XML Schema: • request for “direction” parameter for ObservationPoint->Lincard/Interface • added in -03 • request for “description” attribute which can be used for annotations • added in -03 • request for integration of file input/output • started with FileExport as new export option in -03, solutions for configuring file input is subject to ongoing work • request for ACL-like filters (OR filter is missing) • consensus is required as only AND is specified in [PSAMP-TECH] • request for configurable packet size and delay caused by Exporting Process • propose to use device-specific extension of the model if such configuration parameters exist • request for observationPointId parameter • added in -03, as well as exportingProcessId, meteringProcessId, selectorId (all optional, configuration does not have to be supported by device) 70th IETF Meeting, Vancouver, 2007

  4. Additional changes in -03 • Text: • many small changes aiming at increasing the comprehensibility • Configuration data model: • configuration of Exporting Process restructured • Reporting class is now called Option class • UML: • removed “id” attributes from diagrams which are needed for references in XML  class diagrams now only show configuration parameters 70th IETF Meeting, Vancouver, 2007

  5. To be done/open issues • File export: • configuration of a collector writing received data into a file • Add the possibility to directly link the collecting process to an exporting process with FileExport? • File import: • raw packets: add a file-based Observation Point (e.g. pcap file) • IPFIX/PSAMP records: add a file-based Collecting Process • Do we need this second option? Is anybody deploying such a configuration? • Selection Process: • check if current configuration corresponds to PSAMP view • SCTP: • add PR-SCTP related parameters 70th IETF Meeting, Vancouver, 2007

  6. Relationship to Netconf • Comments received: • recommend but do not mandate • protocol-independence is an advantage • no-one requested to force the usage of Netconf • Suggestion: • keep the configuration data model protocol-independent 70th IETF Meeting, Vancouver, 2007

More Related