60 likes | 222 Views
IPFIX Configuration Data Model draft-muenz-ipfix-configuration-00.txt. Gerhard Münz. Motivation. IPFIX devices offer various configuration possibilities A common device-independent configuration data model facilitates network management and configuration
E N D
IPFIX Configuration Data Modeldraft-muenz-ipfix-configuration-00.txt Gerhard Münz
Motivation • IPFIX devices offer various configuration possibilities • A common device-independent configuration data model facilitates network management and configuration • draft-muenz-ipfix-configuration-00.txt: • Overview on common configuration parameters • separately for Observation Point, Collecting Process, Metering Process, and Exporting Process • forming a data path through the IPFIX device • Specification of an XML-based configuration data model for IPFIX devices • device-independent • extensible • can be used with Netconf protocol or SOAP (or others) 66th IETF Meeting, Montreal, 2006
Possible Data Paths (without bifurcations) +-------------+ +----------+ +----------+ +-----------+ | Observation |-->| Metering |-...->| Metering |-->| Exporting | | Point | | Process | | Process | | Process | +-------------+ +----------+ +----------+ +-----------+ \______________________________/ 1..n Figure 2: Data Path starting with an Observation Point +------------+ +----------+ +----------+ +-----------+ | Collecting |-->| Metering |-...->| Metering |-->| Exporting | | Process | | Process | | Process | | Process | +------------+ +----------+ +----------+ +-----------+ \______________________________/ 0..n Figure 3: Data Path starting with a Collecting Process 66th IETF Meeting, Montreal, 2006
Overview to Configurable Parameters 66th IETF Meeting, Montreal, 2006
Feedback requested • Will IPFIX configuration become a WG item? • Use of SNMP/MIB or XML for configuration? • If XML: • Shall we commit ourselves to the Netconf Protocol? • Or leave the decision on the protocol to the user and specify the data model only? • Agreement on the common set of configurable parameters has to be found 66th IETF Meeting, Montreal, 2006