Configuration Data Model for the IP Flow Information Export (IPFIX) and Packet Sampling (PSAMP) Protocols
RFC 6728

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 10
• 11

draft-ietf-ipfix-configuration-model-11.txt:
xym 0.4:
Extracting 'ietf-ipfix-psamp@2012-06-12.yang'
   Removed 0 empty lines
Extracting 'my-ipfix-psamp-deviation'
   Getting YANG file name from module name: my-ipfix-psamp-deviation.yang


ietf-ipfix-psamp@2012-06-12.yang:
pyang 1.7.3: pyang --verbose --ietf -p {libs} {model}:
ietf-ipfix-psamp@2012-06-12.yang:258: warning: the escape sequence "\S" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning
ietf-ipfix-psamp@2012-06-12.yang:278: warning: the escape sequence "\S" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning

yanglint 0.14.53: yanglint --verbose -p {rfclib} -p {draftlib} -p {tmplib} {model} -i:
err : Invalid keyword "\S+"".
err : Module "ietf-ipfix-psamp" parsing failed.

Internet Engineering Task Force (IETF)                          G. Muenz
Request for Comments: 6728                                   TU Muenchen
Category: Standards Track                                      B. Claise
ISSN: 2070-1721                                                P. Aitken
                                                     Cisco Systems, Inc.
                                                            October 2012

  Configuration Data Model for the IP Flow Information Export (IPFIX)
                 and Packet Sampling (PSAMP) Protocols

Abstract

   This document specifies a data model for the IP Flow Information
   Export (IPFIX) and Packet Sampling (PSAMP) protocols.  It is for
   configuring and monitoring Selection Processes, Caches, Exporting
   Processes, and Collecting Processes of IPFIX- and PSAMP-compliant
   Monitoring Devices using the Network Configuration Protocol
   (NETCONF).  The data model is defined using UML (Unified Modeling
   Language) class diagrams and formally specified using YANG.  The
   configuration data is encoded in Extensible Markup Language (XML).

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc6728.

Copyright Notice

   Copyright (c) 2012 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.  Code Components extracted from this document must

Muenz, et al.                Standards Track                    [Page 1]
RFC 6728          IPFIX/PSAMP Configuration Data Model      October 2012

   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.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  IPFIX Documents Overview  . . . . . . . . . . . . . . . .   4
     1.2.  PSAMP Documents Overview  . . . . . . . . . . . . . . . .   5
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Structure of the Configuration Data Model . . . . . . . . . .   7
     3.1.  Metering Process Decomposition in Selection Process
           and Cache . . . . . . . . . . . . . . . . . . . . . . . .   8
     3.2.  UML Representation  . . . . . . . . . . . . . . . . . . .  10
     3.3.  Exporter Configuration  . . . . . . . . . . . . . . . . .  15
     3.4.  Collector Configuration . . . . . . . . . . . . . . . . .  17
   4.  Configuration Parameters  . . . . . . . . . . . . . . . . . .  18
     4.1.  ObservationPoint Class  . . . . . . . . . . . . . . . . .  18
     4.2.  SelectionProcess Class  . . . . . . . . . . . . . . . . .  20
       4.2.1.  Selector Class  . . . . . . . . . . . . . . . . . . .  21
       4.2.2.  Sampler Classes . . . . . . . . . . . . . . . . . . .  22
       4.2.3.  Filter Classes  . . . . . . . . . . . . . . . . . . .  23
     4.3.  Cache Class . . . . . . . . . . . . . . . . . . . . . . .  25
       4.3.1.  ImmediateCache Class  . . . . . . . . . . . . . . . .  26
       4.3.2.  TimeoutCache, NaturalCache, and PermanentCache
               Class . . . . . . . . . . . . . . . . . . . . . . . .  27
       4.3.3.  CacheLayout Class . . . . . . . . . . . . . . . . . .  29
     4.4.  ExportingProcess Class  . . . . . . . . . . . . . . . . .  32
       4.4.1.  SctpExporter Class  . . . . . . . . . . . . . . . . .  34
       4.4.2.  UdpExporter Class . . . . . . . . . . . . . . . . . .  36