datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

Reporting Unobserved Fields in IPFIX
draft-aitken-ipfix-unobserved-fields-02

Document type: Active Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2013-12-31
Intended RFC status: Unknown
Other versions: plain text, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

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

IPFIX Working Group                                      P. Aitken
     Internet-Draft                                 Cisco Systems, Inc.
     Intended Status: Standards Track                       31 Dec 2013
     Expires: July, 2014

                    Reporting Unobserved Fields in IPFIX
                  draft-aitken-ipfix-unobserved-fields-02

     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), its areas, and its working
        groups.  Note that other groups may also distribute working
        documents as Internet-Drafts.

        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."

        The list of current Internet-Drafts can be accessed at
        http://www.ietf.org/ietf/1id-abstracts.txt

        The list of Internet-Draft Shadow Directories can be accessed at
        http://www.ietf.org/shadow.html

        This Internet-Draft will expire in July 2014.

     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
        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.

      


     Internet-Draft <Reporting Unobserved Fields in IPFIX>      Dec 2013

     Abstract

        The IPFIX protocol is designed to export information about
        observations, and lacks a method for reporting that observations
        are unavailable. This document discusses several methods for
        reporting when fields are unavailable, reviews the advantages
        and disadvantage of each, and recommends methods which should be
        used.

     Conventions used in this document

        The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
        NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
        "OPTIONAL" in this document are to be interpreted as described
        in RFC 2119 [RFC2119].

     Table of Contents

       1. Introduction ............................................  3
       2. Terminology .............................................  4
       2.1 New Terminology ........................................  4
       3. Potential Methods .......................................  4
       3.1 Zero-valued counters ...................................  4
       3.2 Multiple Templates .....................................  5
       3.3 CommonProperties .......................................  6
       3.4 Default Values .........................................  7
       3.4.1 Default of Zero ......................................  7
       3.4.2  Default of all-ones .................................  7
       3.4.3  General default value ...............................  8
       3.4.4  Field-specific default values........................  8
       3.5 "observedFieldsIndicator" bitfield .....................  9
       3.6 Length of Zero ......................................... 10
       3.7 Size field ............................................. 10
       3.8 Structure data lists ................................... 11
       3.8.1  Status list ......................................... 11
       3.8.2  Observed field list ................................. 11
       3.8.3  Combined field and status list ...................... 12
       4. Conclusion .............................................. 12
       5. New Information Elements ................................ 13
       6. Security Considerations ................................. 13
       7. IANA Considerations ..................................... 13
       8. References .............................................. 14
       8.1 Normative References ................................... 14
       8.2 Informative References ................................. 14
       9. Acknowledgements ........................................ 14
       10. Author's Address ....................................... 14

        TODO: would it be useful to define two new fields for reporting
        the start and end time of a period during which no observations
        were made?

        TODO: how do these methods work with structured data and MIBs?

     <Aitken>                Expires July 2014                 [Page 2]

[include full document text]