Skip to main content

PCEP Extensions for BIER
draft-chen-bier-pce-bier-04

Revision differences

Document history

Date Rev. By Action
2018-08-10
04 (System) Document has expired
2018-02-06
04 Ran Chen New version available: draft-chen-bier-pce-bier-04.txt
2018-02-06
04 (System) New version approved
2018-02-06
04 (System) Request for posting confirmation emailed to previous authors: Zheng Zhang , Ran Chen
2018-02-06
04 Ran Chen Uploaded new revision
2017-07-16
03 Ran Chen New version available: draft-chen-bier-pce-bier-03.txt
2017-07-16
03 (System) New version approved
2017-07-16
03 (System) Request for posting confirmation emailed to previous authors: Ran Chen , Zheng Zhang
2017-07-16
03 Ran Chen Uploaded new revision
2017-01-03
02 Ran Chen New version available: draft-chen-bier-pce-bier-02.txt
2017-01-03
02 (System) New version approved
2017-01-03
02 (System) Request for posting confirmation emailed to previous authors: "Ran Chen" , "Zheng Zhang"
2017-01-03
02 Ran Chen
Muenz, et al.                Standards Track                  [Page 52]
RFC 6728  …
Muenz, et al.                Standards Track                  [Page 52]
RFC 6728          IPFIX/PSAMP Configuration Data Model      October 2012

  Each object of the TransportSession class includes a list of objects
  of the Template class with information and statistics about the
  Templates transmitted or received on the given Transport Session.
  The Template class is specified in Section 4.8.

4.8.  Template Class

    +--------------------------------------+
    | Template                            |
    +--------------------------------------+
    | observationDomainId {readOnly}      |<>---+ 0..*
    | templateId {readOnly}                |    |
    | setId {readOnly}                    |    |
    | accessTime {readOnly}                |    |
    | templateDataRecords {readOnly}      |    |
    | templateDiscontinuityTime {readOnly} |    |
    +--------------------------------------+    |
                                                  |
                              +--------------------------------------+
                              | Field                                |
                              +--------------------------------------+
                              | ieId {readOnly}                      |
                              | ieLength {readOnly}                  |
                              | ieEnterpriseNumber {readOnly}        |
                              | isFlowKey {readOnly} {non-Options    |
                              |  Template only}                    |
                              | isScope {readOnly} {Options Template |
                              |  only}                              |
                              +--------------------------------------+

                        Figure 29: Template class

  The Template class contains state data about Templates used by an
  Exporting Process or received by a Collecting Process in a specific
  Transport Session.  The Field class defines one field of the
  Template.  The names and semantics of the state parameters correspond
  to the managed objects in the ipfixTemplateTable,
  ipfixTemplateDefinitionTable, and ipfixTemplateStatsTable of the
  IPFIX MIB module [RFC6615]:

  observationDomainId:  The ID of the Observation Domain for which this
      Template is defined.

  templateId:  This number indicates the Template ID in the IPFIX
      Message.

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

  setId:  This number indicates the Set ID of the Template.
      Currently, there are two values defined [RFC5101].  The value 2 is
      used for Sets containing Template definitions.  The value 3 is
      used for Sets containing Options Template definitions.

  accessTime:  Used for Exporting Processes, this parameter contains
      the time when this (Options) Template was last sent to the
      Collector or written to the file.
      Used for Collecting Processes, this parameter contains the time
      when this (Options) Template was last received from the Exporter
      or read from the file.

  templateDataRecords:  The number of transmitted or received Data
      Records defined by this (Options) Template since the point in time
      indicated by templateDefinitionTime.

  templateDiscontinuityTime:  Timestamp of the most recent occasion at
      which the counter templateDataRecords suffered a discontinuity.
      In contrast to ipfixTemplateDiscontinuityTime, the time is
      absolute and not relative to sysUpTime.

  ieId, ieLength, ieEnterpriseNumber:  Information Element identifier,
      length, and enterprise number of a field in the Template.  If this
      is not an enterprise-specific Information Element,
      ieEnterpriseNumber is zero.
      These state parameters are identical to
      ipfixTemplateDefinitionIeId, ipfixTemplateDefinitionIeLength, and
      ipfixTemplateDefinitionIeEnterpriseNumber in the IPFIX MIB module
      [RFC6615].

  isFlowKey:  If this state parameter is present, this is a Flow Key
      field.
      This parameter is only available for non-Options Templates (i.e.,
      if setId is 2).

  isFlowKey:  If this state parameter is present, this is a scope
      field.
      This parameter is only available for Options Templates (i.e., if
      setId is 3).

5.  Adaptation to Device Capabilities

  The configuration data model standardizes a superset of common IPFIX
  and PSAMP configuration parameters.  A typical Monitoring Device
  implementation will not support the entire range of possible
  configurations.  Certain functions may not be supported, such as the
  Collecting Process that does not exist on a Monitoring Device that is
  conceived as Exporter only.  The configuration of other functions may

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

  be subject to resource limitations or functional restrictions.  For
  example, the Cache size is typically limited according to the
  available memory on the device.  It is also possible that a
  Monitoring Device implementation requires the configuration of
  additional parameters that are not part of the configuration data
  model in order to function properly.

  YANG [RFC6020] offers several possibilities to restrict and adapt a
  configuration data model.  The current version of YANG defines the
  concepts of features, deviations, and extensions.

  The feature concept allows the author of a configuration data model
  to make proportions of the model conditional in a manner that is
  controlled by the device.  Devices do not have to support these
  conditional parts to conform to the model.  If the NETCONF protocol
  is used, features which are supported by the device are announced in
  the <hello> message [RFC6241].

  The configuration data model for IPFIX and PSAMP covers the
  configuration of Exporters, Collectors, and devices that may act as
  both.  As Exporters and Collectors implement different functions, the
  corresponding proportions of the model are conditional on the
  following features:

  exporter:  If this feature is supported, Exporting Processes can be
      configured.

  collector:  If this feature is supported, Collecting Processes can be
      configured.

  Exporters do not necessarily implement any Selection Processes,
  Caches, or even Observation Points in particular cases.  Therefore,
  the corresponding proportions of the model are conditional on the
  following feature:

  meter:  If this feature is supported, Observation Points, Selection
      Processes, and Caches can be configured.

  Additional features refer to different PSAMP Sampling and Filtering
  methods as well as to the supported types of Caches:

  psampSampCountBased:  If this feature is supported, Sampling method
      sampCountBased can be configured.

  psampSampTimeBased:  If this feature is supported, Sampling method
      sampTimeBased can be configured.

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

  psampSampRandOutOfN:  If this feature is supported, Sampling method
      sampRandOutOfN can be configured.

  psampSampUniProb:  If this feature is supported, Sampling method
      sampUniProb can be configured.

  psampFilterMatch:  If this feature is supported, Filtering method
      filterMatch can be configured.

  psampFilterHash:  If this feature is supported, Filtering method
      filterHash can be configured.

  immediateCache:  If this feature is supported, a Cache generating
      PSAMP Packet Reports can be configured using the ImmediateCache
      class.

  timeoutCache:  If this feature is supported, a Cache generating IPFIX
      Flow Records can be configured using the TimeoutCache class.

  naturalCache:  If this feature is supported, a Cache generating IPFIX
      Flow Records can be configured using the NaturalCache class.

  permanentCache:  If this feature is supported, a Cache generating
      IPFIX Flow Records can be configured using the PermanentCache
      class.

  The following features concern the support of UDP and TCP as
  transport protocols and the support of File Readers and File Writers:

  udpTransport:  If this feature is supported, UDP can be used as
      transport protocol by Exporting Processes and Collecting
      Processes.

  tcpTransport:  If this feature is supported, TCP can be used as
      transport protocol by Exporting Processes and Collecting
      Processes.

  fileReader:  If this feature is supported, File Readers can be
      configured as part of Collecting Processes.

  fileWriter:  If this feature is supported, File Writers can be
      configured as part of Exporting Processes.

  The deviation concept enables a device to announce deviations from
  the standard model using the "deviation" statement.  For example, it
  is possible to restrict the value range of a specific parameter or to
  define that the configuration of a certain parameter is not supported
  at all.  Hence, deviations are typically used to specify limitations

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

  due to resource constraints or functional restrictions.  Deviations
  concern existing parameters of the original configuration data model
  and must not be confused with model extensions.  Model extensions are
  specified with the "augment" statement and allow adding new
  parameters to the original configuration data model.

  If certain device-specific constraints cannot be formally specified
  with YANG, they MUST be expressed with human-readable text using the
  "description" statement.  The provided information MUST enable the
  user to define a configuration that is entirely supported by the
  Monitoring Device.  On the other hand, if a Monitoring Device is
  configured, it MUST notify the user about any part of the
  configuration that is not supported.  The Monitoring Device MUST NOT
  silently accept configuration data that cannot be completely
  enforced.  If the NETCONF protocol is used to send configuration data
  to the Monitoring Device, the error handling is specified in the
  NETCONF protocol specification [RFC6241].

  Just like features, deviations and model extensions are announced in
  NETCONF's <hello> message.  A usage example of deviations is given in
  Section 7.5.

6.  YANG Module of the IPFIX/PSAMP Configuration Data Model

  The YANG module specification of the configuration data model is
  listed below.  It makes use of the common YANG types defined in the
  modules urn:ietf:params:xml:ns:yang:ietf-yang-types and
  urn:ietf:params:xml:ns:yang:ietf-inet-types [RFC6021].

  <CODE BEGINS> file "ietf-ipfix-psamp@2012-09-05.yang"
  module ietf-ipfix-psamp {
    namespace Uploaded new revision
2016-07-06
01 Ran Chen New version available: draft-chen-bier-pce-bier-01.txt
2015-12-25
00 Ran Chen New version available: draft-chen-bier-pce-bier-00.txt