datatracker.ietf.org
Sign In
Version 4.51.p2, 2013-06-11
Report a bug

Exporting MIB Variables using the IPFIX Protocol
draft-ietf-ipfix-mib-variable-export-02

Active Internet-Draft (ipfix WG)
Document Stream: IETF
Last updated: 2013-02-25
Replaces: draft-johnson-ipfix-mib-variable-export
Intended RFC status: (None)
Other versions: plain text, pdf, html

IETF State: WG Document (ipfix)
Document shepherd:(None)
Shepherd writeup
Consensus:Unknown

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

IPFIX Working Group                                            B. Claise
Internet-Draft                                                 P. Aitken
Intended status: Standards Track                                  S. B S
Expires: August 29, 2013                             Cisco Systems, Inc.
                                                        J. Schoenwaelder
                                                Jacobs University Bremen
                                                       February 25, 2013

            Exporting MIB Variables using the IPFIX Protocol
                draft-ietf-ipfix-mib-variable-export-02

Abstract

   This document specifies a way to complement IPFIX Flow Records with
   Management Information Base (MIB) objects, avoiding the need to
   define new IPFIX Information Elements for existing Management
   Information Base objects that are already fully specified.

   This method requires an extension to the current IPFIX protocol.  New
   Template Set and Options Template Sets are specified to allow the
   export of Extended Field Specifiers, which may represent IPFIX
   Information Elements and Simple Network Management Protocol (SNMP)
   MIB Objects.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on August 29, 2013.

Copyright Notice

   Copyright (c) 2013 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal

Claise, et al.           Expires August 29, 2013                [Page 1]
Internet-Draft     Exporting MIB Variables with IPFIX      February 2013

   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Open Issues / To do list . . . . . . . . . . . . . . . . . . .  4
   2.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  5
   3.  Motivation and Architectural Model . . . . . . . . . . . . . .  6
   4.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  8
   5.  Extended Records . . . . . . . . . . . . . . . . . . . . . . .  8
     5.1.  Extended Template Record Format  . . . . . . . . . . . . .  8
     5.2.  Extended Options Template Record Format  . . . . . . . . . 10
     5.3.  Extended Field Specifiers  . . . . . . . . . . . . . . . . 11
       5.3.1.  Standard Field Specifier Format  . . . . . . . . . . . 11
       5.3.2.  Extended Field Specifier Format  . . . . . . . . . . . 12
       5.3.3.  Extended Field Specifier Format for IPFIX
               Information Elements . . . . . . . . . . . . . . . . . 15
       5.3.4.  Extended Field Specifier Format for a non-indexed
               MIB Object . . . . . . . . . . . . . . . . . . . . . . 16
       5.3.5.  Extended Field Specifier Format for an indexed MIB
               Object, with a MIB OID as index  . . . . . . . . . . . 17
       5.3.6.  Extended Field Specifier Format for an indexed MIB
               Object, with an IPFIX Information Element as index . . 20
       5.3.7.  Extended Field Specifier Format for an indexed MIB
               Object, with a previous IPFIX Information Element
               as index . . . . . . . . . . . . . . . . . . . . . . . 24
       5.3.8.  Extended Field Specifier Format for an Indexed MIB
               Object, with an IPFIX Information Element for the
               OID segment identifying the instance . . . . . . . . . 27
     5.4.  Identifying the SNMP Context . . . . . . . . . . . . . . . 30
     5.5.  Template Management  . . . . . . . . . . . . . . . . . . . 30
   6.  Example Use Cases  . . . . . . . . . . . . . . . . . . . . . . 31
     6.1.  Without Using the Specifications in this Document  . . . . 31
     6.2.  Non-indexed MIB Object: Established TCP Connections  . . . 32
     6.3.  Enterprise Specific MIB Object: Detailing CPU Load