PSAMP working group
   Internet Draft                                EDITOR:     B. Claise
   draft-ietf-psamp-protocol-03.txt
   draft-ietf-psamp-protocol-04.txt                       Cisco Systems
   Expires: April September 2006                                   March 2006                                     October 2005

              Packet Sampling (PSAMP) Protocol Specifications

 Status of this Memo
   By submitting this Internet-Draft, each author represents that any
   applicable patent or other IPR claims of which he or she is aware
   have been or will be disclosed, and any of which he or she becomes
   aware will be disclosed, in accordance with Section 6 of 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 on April 23, September 30, 2006.

  Copyright Notice

    Copyright (C) The Internet Society (2005). (2006).

 Abstract

   This document specifies the export of packet information from a
   PSAMP Exporting Process to a PSAMP Colleting Collecting Process.  For export
   of packet information the IP Flow Information eXport (IPFIX)
   protocol is used, as both the IPFIX and PSAMP architecture match
   very well and the means provided by the IPFIX protocol are
   sufficient.  The document specifies in detail how the IPFIX protocol
   is used for PSAMP export of packet information.

  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. 2119 [RFC2119].

  Table of Contents
     1. Points of Discussion.........................................3
      1.1 Open Issues................................................3
      1.2 Action Items...............................................4 Introduction................................................3
     2. Introduction.................................................4
     3. PSAMP Documents Overview.....................................5
     4. Terminology..................................................5
      4.1 Overview....................................3
     3. Terminology.................................................4
      3.1 IPFIX Terminology..........................................6
      4.2 Terminology..........................................4
      3.2 PSAMP Terminology.........................................10
     4.2.1 Terminology..........................................8
     3.2.1   Packet Streams and Packet Content......................10
     4.2.2 Content.....................8
     3.2.2   Selection Process......................................11
     4.2.3   Reporting..............................................12
     4.2.4 Process.....................................9
     3.2.3   Reporting............................................10
     3.2.4   Exporting Process......................................13
     4.2.5 Process....................................11
     3.2.5   PSAMP Device...........................................13
     4.2.6 Device.........................................11
     3.2.6   Selection Methods......................................13
      4.3 Methods....................................11
      3.3 IPFIX and PSMAP Terminology Comparison....................15
     4.3.1 Comparison....................13
     3.3.1   PSAMP and IPFIX Processes..............................16
     4.3.2 Processes............................13
     3.3.2   Packet Report, Packet Interpretation, and Data Record..16
     5. Record14
     4. Differences between PSAMP and IPFIX.........................16
      5.1 IPFIX........................14
      4.1 Architecture Point of View................................16
      5.2 View................................14
      4.2 Protocol Point of View....................................18
      5.3 View....................................16
      4.3 Information Model Point of View...........................18
     6. View...........................16
     5. PSAMP Requirements versus the IPFIX Solution................19
      6.1 IPFIX Solution for the PSAMP Requirements.................19
      6.2 Solution...............16
      5.1 High Level View of the Integration........................21
     7. Integration........................17
     6. Using the IPFIX Protocol for PSAMP..........................22
      7.1 PSAMP.........................18
      6.1 Selector ID...............................................22
      7.2 ID...............................................18
      6.2 The Associations..........................................22
      7.3 Selection Sequence....................................18
      6.3 The Exporting Process.....................................18
      6.4 Packet Reports............................................22
     7.3.1 Report.............................................18
     6.4.1   Basic Packet Reports...................................22
     7.3.2 Report..................................19
     6.4.2   Extended Packet Reports................................24
      7.4 Report...............................21
      6.5 Report Interpretation.....................................25
     7.4.1   Associations Interpretation.....................................23
     6.5.1   Selection Sequence Report Interpretation.....................25
     7.4.2 Interpretation.............23
     6.5.2   Selector Report Interpretation.........................27
     7.4.2.1 Interpretation.......................25
     6.5.2.1  Systematic Count-Based Sampling.......................28
     7.4.2.2 Sampling......................25
     6.5.2.2  Systematic Time-Based Sampling........................29
     7.4.2.3 Sampling.......................27
     6.5.2.3  Random n-out-of-N Sampling............................30
     7.4.2.4 Sampling...........................28
     6.5.2.4  Uniform Probabilistic Sampling........................31
     7.4.2.5 Sampling.......................29
     6.5.2.5  Property Match Filtering..............................32
     7.4.2.6 Filtering.............................30
     6.5.2.6  Hash-Based Filtering..................................34
     7.4.2.7 Filtering.................................32
     6.5.2.7  Other Selection Methods...............................34
     7.4.3   Associations Methods..............................35
     6.5.3   Selection Sequence Statistics Report Interpretation..........34
     7.4.4 Interpretation..35
     6.5.4   Accuracy Report Interpretation.........................37
     7.4.5   Observation Point Report Interpretation................37
     8. Interpretation.......................38
     7. Security Considerations.....................................37
     9. Considerations....................................41
     8. IANA Considerations.........................................37
      9.1 Considerations........................................41
      8.1 IPFIX Related Considerations..............................37
      9.2 Considerations..............................41
      8.2 PSAMP Related Considerations..............................37
     10. References.................................................38
      10.1 Considerations..............................41
     9. References.................................................42
      9.1 Normative References.....................................38
      10.2 References......................................42
      9.2 Informative References...................................38
     11. Acknowledgments............................................39 References....................................42
     10. Acknowledgments...........................................43

 1.     Points
   Introduction

   The name PSAMP is a contraction of Discussion

 1.1      Open Issues

   This section covers the open issues, still to be resolved/updated in
   this draft:

   PROTO-04 Should probably have phrase Packet SAMPling.  The
   word "sampling" captures the idea that only a separate section subset of all packets
   passing a network element will be selected for reporting.  PSAMP
   selection operations include random selection, deterministic
   selection (filtering), and deterministic approximations to random
   selection (hash-based selection).

   The IP Flow information export (IPFIX) protocol specified in [IPFIX-
   PROTO] exports IP traffic information [IPFIX-INFO] observed at
   network devices.  This matches the examples?

   PROTO-08 Instead of sending general protocol requirements
   outlined in the input sequence number PSAMP framework [PSAMP-FMWK].  However, there are
   some architectural differences between IPFIX and PSAMP in the
   requirements for each
   selector ID, a counter64 value, associated with every packet, an export protocol.  While the
   working group should discuss IPFIX architecture
   [IPFIX-ARCH] is focused on gathering and exporting IP traffic flow
   information, the possibility to send focus of the PSAMP framework [PSAMP-FMWK] is on
   exporting information on regular basis with an option template record. Specifically in the
   case of Composite Selector, we would send multiple times individual packets.  This basic difference
   and a 64-bit
   counter set of derived differences in each packet.

   PROTO-11 Discuss how to implement protocol requirements are
   outlined in Section 4.  Despite these differences, the accuracy report interpretation

   PROTO-12 Discuss IPFIX protocol
   is well suited as PSAMP protocol.  Section 5 specifies how to implement the observation point report
   interpretation (if we need one)

   PROTO-16 IANA considerations section to be completed.
   Two questions:
   1. I'm not too sure whether we should mandate a new IETF RFC IPFIX
   protocol is used for the
   new selection method description?
   2. I'm not too sure whether we should mandate new IANA-registered export of packet samples.  Required
   extensions of the IPFIX information elements model are specified in the PSAMP
   information model [PSAMP-INFO].

 2.
   PSAMP Documents Overview

   [PSAMP-FMWK]: "A Framework for Packet Selection and Reporting",
   describes the new selection method?
       In PSAMP framework for network elements to select subsets
   of packets by statistical and other words, can we have proprietary selection method in methods, and to export a stream
   of reports on the
   selectorAlgorithm Information Element?

   PROTO-17 "Encrypted Packets: Selectors that interpret packet fields
   must be configurable selected packets to ignore (i.e. not select) encrypted packets,
   when they are detected". "Since a collector.

   [PSAMP-TECH]: "Sampling and Filtering Techniques for IP Packet
   Selection", describes the set of packet encryption alters selection techniques
   supported by PSAMP.

   [PSAMP-PROTO]: "Packet Sampling (PSAMP) Protocol Specifications"
   (this document), specifies the meaning export of encrypted fields, field match filtering must be configurable packet information from a
   PSAMP Exporting Process to
   ignore encrypted packets, when detected." I guess we will need extra
   text a PSAMP Collecting Process.

   [PSAMP-INFO]: "Information Model for this.

   PROTO-18 "The exporting process must have Packet Sampling Exports" defines
   an export rate limit,
   configurable per Exporting Process". I guess we need extra text information and data model for
   this.

   PROTO-19 "the timestamp of observation PSAMP.

   [PSAMP-MIB]: "Definitions of Managed Objects for Packet Sampling"
   describes the packet at PSAMP Management Information Base.

 3.
   Terminology

   As the
   Observation Point. The timestamp should be reported IPFIX export protocol is used to microsecond
   resolution." Nothing export the PSAMP information,
   the relevant IPFIX terminology from [IPFIX-PROTO] is mentioned copied over in
   this draft regarding this issue.

   PROTO-20 Hash based filtering to be completed.

 1.2      Action Items

   PROTO-101 See EDITOR'S NOTE

   PROTO-104 Fix the document.  The terminology sections, as summary table in section 4.1 gives a last step before
   publication

   PROTO-106 Extend security considerations by a discussion on exported
   Payload. Consider whether [PSAMP-INFO] or [PSAMP-PROTO] or both
   is/are
   quick overview of the place(s).

   PROTO-107 Provide relationships between the equivalent for variable length I.E.
   Here different IPFIX
   terms.  The PSAMP terminology defined here is an example of a basic Packet Report, with a SelectionPath
   value of 9 (will be explained later on) and ipPacketSection
   Information Element of 12 bytes, encoded fully consistent with a fixed length.
   This is an example of PROTO-15, to be put
   all terms listed in section 7.3.1

   PROTO-108 Have a statement [PSAMP-TECH] and [PSAMP-FMWK] but only
   definitions that this are only relevant to the PSAMP protocol specification
   meets all requirements for appear here.
   Section 5.4 applies the PSAMP terminology to the IPFIX protocol stated
   terminology.

 3.1
    IPFIX Terminology

   The IPFIX terminology section has been entirely copied over from
   [IPFIX-PROTO], except for the IPFIX Exporting Process term, which is
   defined more precisely in the framework
   except ... PSAMP terminology section.

   Observation Point

   An then have Observation Point is a list of bullets, location in the network where at minimum there IP packets
   can be observed.  Examples include: a line to which a probe is
   stated "not yet covered"
   attached, a shared medium, such as an Ethernet-based LAN, a single
   port of a router, or a longer explanation why it set of interfaces (physical or logical) of a
   router.

   Note that every Observation Point is not
   covered. This associated with an Observation
   Domain (defined below), and that one Observation Point may be a
   superset of several other Observation Points.  For example one
   Observation Point can be an entire line card.  That would be replacement for the long list of requirements
   in section 6.1

 2.    Introduction

   The name PSAMP is a contraction
   superset of the phrase Packet SAMPling.  The
   word "sampling" captures individual Observation Points at the idea that only a subset of all packets
   passing a network element will be selected line card's
   interfaces.

   Observation Domain

   An Observation Domain is the largest set of Observation Points for reporting.  PSAMP
   selection operations include random selection, deterministic
   selection (filtering), and deterministic approximations to random
   selection (hash-based selection).

   The IP
   which Flow information export (IPFIX) protocol specified in [IPFIX-
   PROTO] exports IP traffic information [IPFIX-INFO] observed at
   network devices.  This matches can be aggregated by a Metering Process.

   Each Observation Domain presents itself using a unique ID to the general protocol requirements
   outlined in
   Collecting Process to identify the PSAMP framework [PSAMP-FMWK].  However, there are
   some architectural differences between IPFIX and PSAMP in the
   requirements for Messages it generates.  For
   example, a router line card may be an export protocol.  While the IPFIX architecture
   [IPFIX-ARCH] observation domain if it is focused on gathering and exporting
   composed of several interfaces, each of which is an Observation
   Point.  Every Observation Point is associated with an Observation
   Domain.

   IP traffic flow
   information, Traffic Flow or Flow

   There are several definitions of the focus term 'flow' being used by the
   Internet community.  Within the context of IPFIX we use the PSAMP framework [PSAMP-FMWK] following
   definition:

   A Flow is on
   exporting information on individual packets.  This basic difference
   and defined as a set of derived differences in protocol requirements are
   outlined IP packets passing an Observation Point
   in Section 5.  Despite these differences, the IPFIX protocol network during a certain time interval.  All packets belonging
   to a particular Flow have a set of common properties.  Each property
   is well suited defined as PSAMP protocol.  Section 5 specifies how the IPFIX
   protocol is used for the export of packet samples.  Required
   extensions result of applying a function to the IPFIX information model are specified in the PSAMP
   information model [PSAMP-INFO]. values of:

      1. one or more packet header field (e.g. destination IP address),
      transport header field (e.g. destination port number), or
      application header field (e.g. RTP header fields [RFC1889])

      2. one or more characteristics of the packet itself (e.g. number
      of MPLS labels, etc...)

      3.    PSAMP Documents Overview

   [PSAMP-FMWK]: "A Framework for Packet Selection and Reporting",
   describes one or more of fields derived from packet treatment (e.g. next
      hop IP address, the PSAMP framework for network elements output interface, etc...)

   A packet is defined to select subsets
   of packets by statistical and other methods, and belong to export a stream Flow if it completely satisfies
   all the defined properties of reports on the selected Flow.

   This definition covers the range from a Flow containing all packets
   observed at a network interface to a collector.

   [PSAMP-TECH]: "Sampling and Filtering Techniques for IP Packet
   Selection", describes the set Flow consisting of just a single
   packet selection techniques
   supported between two applications.  It includes packets selected by PSAMP.

   [PSAMP-PROTO]: "Packet Sampling (PSAMP) Protocol Specifications"
   (this document), specifies a
   sampling mechanism.

   Flow Key

   Each of the export fields which
   1.  Belong to the packet header (e.g. destination IP address)
   2.  Are a property of the packet information itself (e.g. packet length)
   3.  Are derived from a
   PSAMP Exporting Process packet treatment (e.g. AS number)
   and which are used to define a PSAMP Colleting Process

   [PSAMP-INFO]: "Information Model for Packet Sampling Exports" defines
   an Flow are termed Flow Keys.

   Flow Record

   A Flow Record contains information and data model for PSAMP.

   [PSAMP-MIB]: "Definitions of Managed Objects for Packet Sampling"
   describes the PSAMP Management Information Base

 4.    Terminology

   As the IPFIX export protocol is used to export the PSAMP information,
   the relevant IPFIX terminology from [IPFIX-PROTO] is copied over in
   this document.  The terminology summary table in section 4.1 gives about a
   quick overview specific Flow that was
   observed at an Observation Point.  A Flow Record contains measured
   properties of the relationships between Flow (e.g. the different IPFIX
   terms.  The PSAMP terminology defined here is fully consistent with total number of bytes for all terms listed in [PSAMP-TECH] and [PSAMP-FMWK] but only
   definitions that are only relevant to the PSAMP protocol appear here.
   The section 5.4 applies the PSAMP terminology to
   Flow's packets) and usually characteristic properties of the IPFIX protocol
   terminology.

 4.1     IPFIX Terminology

   EDITOR'S NOTE: The terminology has been entirely copied over from
   [IPFIX-PROTO].  Before publication, we should evaluate which terms
   should be kept, if not all.  The ones required for sure so far are: Flow Record, Flow, Information Element,
   (e.g. source IP address).

   Metering Process, Collector,
   Scope, Set, Template Record, Data Record, Data Set, Template Set,
   Template Record(s), Options Template Set, Options Template Record.
   Note: the IPFIX Exporting Process was not used, as the PSAMP
   Exporting

   The Metering Process is more specific. generates Flow Records.  Inputs to the process
   are packet headers and characteristics observed at an Observation Point

   An
   Point, and packet treatment at the Observation Point is a location in (for example the network where IP packets
   can be observed.  Examples include: a line to which a probe is
   attached, a shared medium, such as an Ethernet-based LAN, a single
   port
   selected output interface).

   The Metering Process consists of a router, or a set of interfaces (physical or logical) of a
   router.

   Note functions that every Observation Point is associated with an Observation
   Domain (defined below), includes
   packet header capturing, timestamping, sampling, classifying, and that
   maintaining Flow Records.

   The maintenance of Flow Records may include creating new records,
   updating existing ones, computing Flow statistics, deriving further
   Flow properties, detecting Flow expiration, passing Flow Records to
   the Exporting Process, and deleting Flow Records.

   Exporter

   A device which hosts one or more Exporting Processes is termed an
   Exporter.

   IPFIX Device

   An IPFIX Device hosts at least one Observation Point may be Point, a
   superset Metering
   Process and an Exporting Process.

   Collecting Process

   A Collecting Process receives Flow Records from one or more
   Exporting Processes.  The Collecting Process might process or store
   received Flow Records, but such actions are out of several other Observation Points.  For example scope for this
   document.

   Collector

   A device which hosts one
   Observation Point can be or more Collecting Processes is termed a
   Collector.

   Template

   Template is an entire line card.  That would be the
   superset ordered sequence of <type, length> pairs, used to
   completely specify the individual Observation Points at the line card's
   interfaces.

   Observation Domain

   An Observation Domain is the largest structure and semantics of a particular set of Observation Points for
   which Flow
   information can that needs to be aggregated by communicated from an IPFIX Device to a Metering Process.
   Collector.  Each Observation Domain presents itself using Template is uniquely identifiable by means of a unique ID to
   Template ID.

   IPFIX Message

   An IPFIX Message is a message originating at the
   Collecting Exporting Process to identify
   that carries the IPFIX Messages it generates.  For
   example, a router line card may be an observation domain if it is
   composed records of several interfaces, each of which this Exporting Process and whose
   destination is an Observation
   Point.  Every Observation Point a Collecting Process.  An IPFIX Message is associated with an Observation
   Domain.

   IP Traffic Flow or Flow

   There are several definitions of the term 'flow' being used by
   encapsulated at the
   Internet community.  Within transport layer.

   Message Header

   The Message Header is the context first part of an IPFIX we use Message, which
   provides basic information about the following
   definition: message such as the IPFIX
   version, length of the message, message sequence number, etc.

   Template Record

   A Flow Template Record defines the structure and interpretation of fields
   in a Data Record.

   Data Record

   A Data Record is defined as a set record that contains values of IP packets passing an Observation Point
   in the network during a certain time interval.  All packets belonging parameters
   corresponding to a particular Flow have a set of common properties.  Each property Template Record.

   Options Template Record

   An Options Template Record is defined as a Template Record that defines the result
   structure and interpretation of applying fields in a function Data Record, including
   defining how to scope the values of:

      1. one or more packet header field (e.g. destination IP address),
      transport header field (e.g. destination port number), or
      application header field (e.g. RTP header fields [RFC1889])

      2. one or more characteristics applicability of the packet itself (e.g. number Data Record.

   Set

   Set is a generic term for a collection of MPLS labels, etc...)

      3. records that have a similar
   structure.  In an IPFIX Message, one or more of fields derived from packet treatment (e.g. next
      hop IP address, Sets follow the output interface, etc...)

   A packet is defined to belong to a Flow if it completely satisfies
   all the defined properties Message
   Header.

   There are three different types of the Flow.

   This definition covers the range from a Flow containing all packets
   observed at a network interface to Sets: Template Set, Options
   Template Set, and Data Set.

   Template Set

   A Template Set is a Flow consisting collection of just a single
   packet between two applications.  It includes packets selected by one or more Template Records that
   have been grouped together in an IPFIX Message.

   Options Template Set

   An Options Template Set is a
   sampling mechanism.

   Flow Key

   Each collection of the fields which
   1.  Belong to the packet header (e.g. destination IP address)
   2.  Are a property one or more Options
   Template Records that have been grouped together in an IPFIX Message.

   Data Set
   A Data Set is one or more Data Records, of the packet itself (e.g. packet length)
   3.  Are derived from packet treatment (e.g. AS number)
   and which are used to define a Flow same type, that are termed Flow Keys.

   Flow Record

   A Flow
   grouped together in an IPFIX Message.  Each Data Record contains information about is previously
   defined by a specific Flow that was
   observed at an Observation Point.  A Flow Template Record contains measured
   properties or an Options Template Record.

   Information Element

   An Information Element is a protocol and encoding independent
   description of an attribute which may appear in an IPFIX Record.  The
   IPFIX information model [IPFIX-INFO] defines the Flow (e.g. the total number base set of bytes
   Information Elements for all the
   Flow's packets) and usually characteristic properties of the Flow
   (e.g. source IP address).

   Metering Process IPFIX.  The Metering Process generates Flow Records.  Inputs to type associated with an
   Information Element indicates constraints on what it may contain and
   also determines the process
   are packet headers valid encoding mechanisms for use in IPFIX.

    +------------------+---------------------------------------------+
    |                  |                 Contents                    |
    |                  +--------------------+------------------------+
    |       Set        |      Template      |         Record         |
    +------------------+--------------------+------------------------+
    |   Data Set       |          /         |     Data Record(s)     |
    +------------------+--------------------+------------------------+
    |   Template Set   | Template Record(s) |           /            |
    +------------------+--------------------+------------------------+
    | Options Template | Options Template   |           /            |
    |       Set        | Record(s)          |                        |
    +------------------+--------------------+------------------------+
               Figure A: Terminology Summary Table

 3.2
     PSAMP Terminology

   The PSAMP terminology section has been copied over from [PSAMP-TECH].

 3.2.1    Packet Streams and characteristics Packet Content

   Observed Packet Stream

   The Observed Packet Stream is the set of all packets observed at an the
   Observation
   Point, and Point.

   Packet Stream

   A packet treatment at stream denotes a set of packets that flows past some
   specified point within the Observation Point (for Selection Process.  An example of a Packet
   Stream is the
   selected output interface).

   The Metering Process consists of the Selection Process.  Note that packets
   selected from a stream, e.g. by Sampling, do not necessarily possess
   a property by which they can be distinguished from packets that have
   not been selected.  For this reason the term "stream" is favored over
   "flow", which is defined as set of functions that includes packets with common properties
   [IPFIX-REQ].

   Packet Content

   The packet content denotes the union of the packet header capturing, timestamping, sampling, classifying, (which
   includes link layer, network layer and
   maintaining Flow Records.

   The maintenance of Flow Records may include creating new records,
   updating existing ones, computing Flow statistics, deriving further
   Flow properties, detecting Flow expiration, passing Flow Records to
   the Exporting Process, other encapsulation headers)
   and deleting Flow Records.

   Exporter

   A device which hosts one or more Exporting Processes is termed an
   Exporter.

   IPFIX Device

   An IPFIX Device hosts at least one Observation Point, a Metering the packet payload.

 3.2.2   Selection Process and an Exporting Process.

   Collecting

   Selection Process

   A Collecting Process receives Flow Records from one or more
   Exporting Processes.  The Collecting Selection Process might process or store
   received Flow Records, but such actions are out of scope for this
   document.

   Collector

   A device which hosts one or more Collecting Processes is termed a
   Collector.

   Template

   Template is an ordered sequence of <type, length> pairs, used to
   completely specify takes the structure Observed Packet Stream as its input and semantics of
   selects a particular set subset of
   information that needs to be communicated from an IPFIX Device to a
   Collector.  Each Template is uniquely identifiable stream as its output.

   Selection State

   A Selection Process may maintain state information for use by means of a
   Template ID.

   IPFIX Message

   An IPFIX Message is the
   Selection Process.  At a message originating at given time, the Exporting Process Selection State may depend
   on packets observed at and before that carries the IPFIX records of this Exporting Process time, and whose
   destination is a Collecting Process.  An IPFIX Message is
   encapsulated other variables.
   Examples include:

       (i)   sequence numbers of packets at the transport layer.

   Message Header

   The Message Header is the first part input of Selectors;

       (ii)  a timestamp of observation of an IPFIX Message, which
   provides basic information about the message such as packet at the IPFIX
   version, length
             Observation Point;

       (iii) iterators for pseudorandom number generators;

       (iv)  hash values calculated during selection;

       (v)   indicators of whether the message, message sequence number, etc.

   Template Record packet was selected by a
             given Selector.

   Selection Processes may change portions of the Selection State as a
   result of processing a packet.  Selection state for a packet is to
   reflect the state after processing the packet.

   Selector

   A Template Record Selector defines the structure and interpretation action of fields
   in a Data Record.

   Data Record

   A Data Record is Selection Process on a record that contains values single
   packet of its input.  If selected, the parameters
   corresponding to a Template Record.

   Options Template Record

   An Options Template Record is a Template Record that defines packet becomes an element of
   the
   structure and interpretation output Packet Stream.

   The Selector can make use of fields the following information in determining
   whether a Data Record, including
   defining how to scope packet is selected:

       (i)  the applicability of Packet Content;

       (ii) information derived from the Data Record.

   Set

   Set is a generic term for a collection of records packet's treatment at the
            Observation Point;

       (iii) any selection state that have a similar
   structure.  In may be maintained by the
             Selection Process.

   Composite Selector

   A Composite Selector is an IPFIX Message, ordered composition of Selectors, in which
   the output Packet Stream issuing from one or more Sets follow Selector forms the Message
   Header.

   There are three different types of Sets: Template Set, Options
   Template Set, and Data Set.

   Template Set input
   Packet Stream to the succeeding Selector.

   Primitive Selector

   A Template Set Selector is primitive if it is not a collection of one or more Template Records that
   have been grouped together in an IPFIX Message.

   Options Template Set

   An Options Template Set Composite Selector.

   Selector ID

   The Selector ID is the unique ID identifying a collection of Primitive Selector.
   The ID is unique within the Observation Domain.

   Selection Sequence

   From all the packets observed at an Observation Point, only a few
   packets are selected by one or more Options
   Template Records that have been grouped together in an IPFIX Message.

   Data Set

   A Data Set Selectors.  The Selection
   Sequence is a unique value per Observation Domain describing the
   Observation Point and the Selector IDs through which the packets are
   selected.

 3.2.3   Reporting

   Packet Reports

   Packet Reports comprise a configurable subset of a packet's input to
   the Selection Process, including the Packet Content, information
   relating to its treatment (for example, the output interface), and
   its associated selection state (for example, a hash of the Packet
   Content)

   Report Interpretation
   Report Interpretation comprises subsidiary information, relating to
   one or more Data Records, of the same type, packets, that are
   grouped together in an IPFIX Message.  Each Data Record used for interpretation of their Packet
   Reports.  Examples include configuration parameters of the Selection
   Process.

   Report Stream

   The Report Stream is previously
   defined by the output of a Template Record Selection Process, comprising
   two distinguished types of information: Packet Reports, and Report
   Interpretation.

 3.2.4   Exporting Process

   Exporting Process

   An Exporting Process sends, in the form of Export Packets, the output
   of one or an Options Template Record.

   Information Element more Selection Processes to one or more Collectors.

   Export Packet

   An Information Element Export Packet is a protocol and encoding independent
   description combination of an attribute which may appear in an IPFIX Record.  The
   IPFIX information model [IPFIX-INFO] defines the base set of
   Information Elements for IPFIX.  The type associated with an
   Information Element indicates constraints on what it may contain and
   also determines the valid encoding mechanisms for use in IPFIX.

    +------------------+---------------------------------------------+
    |                  |                 Contents                    |
    |                  +--------------------+------------------------+
    |       Set        |      Template      |         Record         |
    +------------------+--------------------+------------------------+
    |   Data Set       |          /         |     Data Record(s)     |
    +------------------+--------------------+------------------------+
    |   Template Set   | Template Record(s) |           /            |
    +------------------+--------------------+------------------------+
    | Options Template | Options Template   |           /            |
    |       Set        | Record(s)          |                        |
    +------------------+--------------------+------------------------+

               Figure A: Terminology Summary Table

 4.2      PSAMP Terminology

   EDITOR'S NOTE: The terminology has been entirely copied over from
   [PSAMP-TECH], except for some (almost) similar terms where only the
   IPFIX terms were kept (for example, observation point).  Before
   publication, we should evaluate which terms should be kept.  The ones
   required for sure so far are: Selector, Composite Selector, Packet
   Reports, Report Interpretation(s) and/or
   one or more Packet Interpretation, PSAMP device, Collector, Filtering,
   Sampling.  Note Reports that are bundled by the terms Selector ID and Association ID, coming
   from [PSAMP-FMWK], has been added in the Selection Exporting Process section.

 4.2.1    Packet Streams and Packet Content

   Observed Packet Stream

   The Observed
   into a Export Packet Stream for exporting to a Collector.

 3.2.5   PSAMP Device

   PSAMP Device

   A PSAMP Device is the set of all packets observed a device hosting at the least an Observation Point.

   Packet Stream

   A packet stream denotes Point, a set of packets that flows past some
   specified point within the
   Selection Process and an Exporting Process.  An  Typically, corresponding
   Observation Point(s), Selection Process(es) and Exporting Process(es)
   are co-located at this device, for example of at a Packet
   Stream router.

 3.2.6   Selection Methods

   Filtering

   A filter is the output a Selector that selects a packet deterministically based
   on the Packet Content, or its treatment, or functions of these
   occurring in the selection process.  Note Selection State.  Examples include field match
   Filtering, and Hash-based Selection.

   Sampling

   A Selector that packets
   selected from a stream, e.g. by Sampling, do is not necessarily possess a property by which they can filter is called a Sampling operation.  This
   reflects the intuitive notion that if the selection of a packet
   cannot be distinguished determined from packets its content alone, there must be some type
   of Sampling taking place.

   Content-independent Sampling

   A Sampling operation that have does not been selected.  For this reason use Packet Content (or quantities
   derived from it) as the term "stream" basis for selection is favored over
   "flow", which called a Content-
   independent Sampling operation.  Examples include systematic
   Sampling, and uniform pseudorandom Sampling driven by a pseudorandom
   number whose generation is defined as set independent of packets with common properties
   [IPFIX-REQ]. Packet Content.  Note that
   in Content-independent Sampling it is not necessary to access the
   Packet Content
   The packet content denotes in order to make the union of selection decision.

   Content-dependent Sampling

   A Sampling operation where selection is dependent on Packet Content
   is called a Content-dependent Sampling operation.  Examples include
   pseudorandom selection according to a probability that depends on the
   contents of a packet header (which
   includes link layer, network layer and other encapsulation headers)
   and field.  Note that this is not a filter, because
   the packet payload.

 4.2.2   Selection Process

   Selection Process selection is not deterministic.

   Hash Domain

   A Selection Process takes subset of the Observed Packet Stream as its input Content and
   selects a subset of that stream as its output.

   Selection State the packet treatment, viewed as an
   N-bit string for some positive integer N.

   Hash Range

   A Selection Process may maintain state information set of M-bit strings for use by the
   Selection Process.  At a given time, the Selection State may depend
   on packets observed at and before some positive integer M that time, and other variables.
   Examples include:

       (i)   sequence numbers of packets at define the input
   range of Selectors;

       (ii)  a timestamp values the result of observation the hash operation can take.

   Hash Function

   A deterministic map from the Hash Domain into the Hash Range.

   Hash Selection Range

   A subset of the Hash Range.  The packet at is selected if the
             Observation Point;

       (iii) iterators for pseudorandom number generators;

       (iv)  hash values calculated during selection;

       (v)   indicators action of whether
   the Hash Function on the Hash Domain for the packet was selected by yields a
             given Selector;

   Selection Processes may change portions of result
   in the Hash Selection State as Range.

   Hash-based Selection

   Filtering specified by a
   result of processing Hash Domain, a packet.  Selection state for Hash Function, a packet is to
   reflect Hash Range
   and a Hash Selection Range.

   Approximative Selection
   Selectors in any of the state after processing above categories may be approximated by
   operations in the packet.

   Selector

   A Selector defines same or another category for the action purposes of
   implementation.  For example, uniform pseudorandom Sampling may be
   approximated by Hash-based Selection, using a Selection Process on a single
   packet of its input.  If selected, suitable Hash Function
   and Hash Domain.  In this case, the packet becomes an element closeness of the output Packet Stream.

   The Selector can make use of approximation
   depends on the following information in determining
   whether a packet choice of Hash Function and Hash Domain.

   Population

   A Population is selected:

       (i)  the a Packet Content;

       (ii) information derived from the packet's treatment at the
            Observation Point;

       (iii) any selection state that may be maintained by the
             Selection Process.

   Composite Selector Stream, or a subset of a Packet Stream.  A Composite Selector
   Population can be considered as a base set from which packets are
   selected.  An example is an ordered composition of Selectors, all packets in which the output Observed Packet Stream issuing from one Selector forms
   that are observed within some specified time interval.

   Population Size

   The Population Size is the input
   Packet Stream to number of all packets in the succeeding Selector.

   Primitive Selector

   A Selector is primitive if it is not a Composite Selector.

   Selector ID Population.

   Sample Size

   The Selector ID is number of packets selected from the unique ID identifying Population by a Primitive Selector.

   Configured Selection Fraction

   The ID Configured Selection Fraction is unique within the Observation Domain.

   Selection Path

   From all ratio of the number of
   packets observed at an Observation Point, only a few
   packets are selected by one or more Selectors.  The Selection Path is a unique value describing the Observation Point and the Selector IDs
   through which from an input Population, to the packets are selected.  The
   Population Size, as based on the configured selection parameters.

   Attained Selection Path is unique
   per Observation Domain. Fraction

   The Attained Selection Path Fraction is represented by the
   selectionPath Information Element [PSAMP-INFO].

 4.2.3   Reporting

   Packet Reports

   Packet Reports comprise a configurable subset actual ratio of the
   number of packets selected by a packet's Selector from an input
   Population, to the Selection Process, including Population Size.  For some Sampling methods the Packet Content, information
   relating to its treatment (for example,
   Attained Selection Fraction can differ from the output interface), and
   its associated selection state (for Configured Selection
   Fraction due to, for example, a hash of the Packet
   Content)

   Report Interpretation:

   Report Interpretation comprises subsidiary information, relating to
   one or more packets, that are used for interpretation of their Packet
   Reports.  Examples include configuration parameters inherent statistical variability in
   Sampling decisions of probabilistic Sampling and Hash-based
   Selection.  Nevertheless, for large Population Sizes and properly
   configured Selectors, the Attained Selection
   Process.

   Report Stream:

   The Report Stream is Fraction usually
   approaches the output of a Configured Selection Process, comprising
   two distinguished types Fraction.

 3.3
     IPFIX and PSMAP Terminology Comparison

   The PSAMP terminology has been specified with an IPFIX background, as
   PSAMP and IPFIX have similar terms.  However, this section explains
   the non compatible terms between IPFIX and PSAMP.

 3.3.1   PSAMP and IPFIX Processes
   The figure B indicates the sequence of information: Packet Reports, the processes (selection and Report
   Interpretation.

 4.2.4
   exporting) within the PSAMP Device.

                  +----------+      +-----------+
        Observed  | Metering |      | Exporting |
        Packet--->| Process

   Exporting Process:

   An Exporting  |----->| Process sends, in the form of Export Packet, the output
   of one or more Selection   |--->Collector
        Stream    +----------+      +-----------+

       Figure B: PSAMP Processes to one or more Collectors.

   Export Packet:

   An Export

   The Selection Process, which takes an Observed Packet Stream as its
   input and produces Packet Reports as its output, is a combination an integral part
   of the Metering Process, which by its definition produces Flow
   Records as its output.

 3.3.2   Packet Report, Packet Interpretation, and Data Record

   The PSAMP terminology speaks of Packet Report Interpretation and/or one
   or more and Packet Reports are bundled by
   Interpretation, while the Exporting Process into a
   Export IPFIX terminology speaks of Data Record and
   (Option) Template Record.  The PSAMP Packet for exporting Report, which comprises
   information about the observed packet, can be viewed as analogous to
   the IPFIX Data Record defined by a Collector.

 4.2.5   PSAMP Device

   PSAMP Device

   A Template Record.  The PSAMP Device is a device hosting at least an Observation Point, a
   Selection Process and Packet
   Interpretation, which comprises subsidiary information used for the
   interpretation of the Packet Reports, can be viewed as analogous to
   the IPFIX Data Record defined by an Exporting Process.  Typically, corresponding
   Observation Point(s), Selection Process(es) Option Template Record.

 4.
   Differences between PSAMP and Exporting Process(es)
   are co-located at this device, IPFIX

   The output of the IPFIX working group relevant for example at a router.

 4.2.6   Selection Methods

   Filtering

   A filter this draft is a Selector that selects a packet deterministically based
   on the Packet Content, or its treatment, or functions
   structured into three documents:
      - IP Flow information architecture [IPFIX-ARCH]
      - IPFIX protocol specifications [IPFIX-PROTO]
      - IP Flow information export information model [IPFIX-INFO]

 4.1
     Architecture Point of these
   occurring View

   Traffic Flow measurement as described in the Selection State.  Examples include field match
   Filtering, IPFIX requirements
   [RFC3917] and Hash-based Selection.

   Sampling

   A Selector that is not a filter is called a Sampling operation.  This
   reflects the intuitive notion that if the IPFIX architecture [IPFIX-ARCH] can be separated
   into two stages: packet processing and Flow processing.
   Figure C illustrates these stages.

   In stage 1, all processing steps act on packets.  Packets are
   captured, time stamped, selected by one or more selection of a steps and
   finally forwarded to packet
   cannot be determined from its content alone, there must be some type
   of Sampling taking place.

   Content-independent Sampling

   A Sampling operation classification that does not use Packet Content (or quantities
   derived from it) as the basis for maps packets to
   Flows.  The packets selection is called a Content-
   independent Sampling operation.  Examples steps may include systematic
   Sampling, Filtering and uniform pseudorandom
   Sampling driven by a pseudorandom
   number whose functions.

   In stage 2, all processing steps act on Flows.  After packets are
   classified (mapped to Flows), Flows are generated or updated if they
   exist already.  Flow generation is independent of and update steps may be performed
   repeatedly for aggregating Flows.  Finally, Flows are exported.

   Packet Content.  Note that
   in Content-independent Sampling it is not necessary to access the
   Packet Content as described in order to make the selection decision.

   Content-dependent Sampling

   A Sampling operation where selection is dependent on Packet Content
   is called a Content-dependent Sampling operation.  Examples include
   pseudorandom selection according to a probability that depends on the
   contents of a packet field.  Note that this is not a filter, because the selection is not deterministic.

   Hash Domain

   A subset PSAMP framework [PSAMP-FMWK]
   covers only stage 1 of the Packet Content and IPFIX architecture with the packet treatment, viewed as an
   N-bit string for some positive integer N.

   Hash Range

   A set of M-bit strings for some positive integer M that define the
   range of values the result of the hash operation can take.

   Hash Function

   A deterministic map from the Hash Domain into the Hash Range.

   Hash Selection Range

   A subset of the Hash Range.  The
   classification replaced by packet is selected if the action of
   the Hash Function on the Hash Domain for the record export.

      IPFIX architecture                       PSAMP framework

        packet yields a result
   in the Hash Selection Range.

   Hash-based Selection

   Filtering specified by a Hash Domain, a Hash Function, and Hash Range header                           packet header
          capturing     \                         capturing
              |          |                            |
         timestamping    |                       timestamping
              |          |                            |
              v          |                            v
      +------>+          |  stage 1:          +------>+
      |       |           > packet            |       |
      |    packet        |  processing        |    packet
      |   selection      |                    |   selection
      |       |          |                    |       |
      +-------+          |                    +-------+
              |          |                            |
              v          |                            v
           packet       /                       packet record
        classification  \                          export
              |          |
              v          |
      +------>+          |
      |       |          |
      | Flow generation  |
      |   and a Hash Selection Range.

   Approximative Selection

   Selectors in any of the above categories may be approximated by
   operations in the same or another category for the purposes update     |  stage 2:
      |       |           > Flow
      |       v          |  processing
      |     Flow         |
      |   selection      |
      |       |          |
      +-------+          |
              |          |
              v          |
         Flow Record    /
           export

       Figure C: Comparison of
   implementation.  For example, uniform pseudorandom Sampling may be
   approximated by Hash-based Selection, using a suitable Hash Function IPFIX architecture and Hash Domain.  In this case, the closeness PSAMP framework
 4.2
     Protocol Point of View

   Concerning the approximation
   depends on protocol, the choice of Hash Function major difference between IPFIX and Hash Domain.

   Population
   A Population PSAMP
   is a that the IPFIX protocol exports Flow Records while the PSAMP
   protocol exports Packet Stream, or Records.  From a subset pure export point of view,
   IPFIX will not distinguish a Packet Stream.  A
   Population Flow Record composed of several packets
   aggregated together from a Flow Record composed of a single packet.
   So the PSAMP export can be considered seen as special IPFIX Flow Record
   containing information about a base set from which packets are
   selected.  An example is all packets in single packet.

   All extensions of the Observed Packet Stream IPFIX protocol that are observed within some specified time interval.

   Population Size

   The Population Size is required to satisfy the number of all packets
   PSAMP requirements have already been incorporated in the Population.

   Sample Size

   The number of packets selected from IPFIX
   protocol [IPFIX-PROTO], which was developed in parallel with the Population by a Selector.

   Configured Selection Fraction

   The Configured Selection Fraction
   PSAMP protocol.  An example is the ratio of the number of
   packets selected by need for a Selector from data type for protocol
   fields that have flexible length, such as an input Population, octet array.  This was
   added to the
   Population Size, as based on IPFIX protocol specification in order to meet the configured selection parameters.

   Attained Selection Fraction

   The Attained Selection Fraction is
   requirement of the actual ratio PSAMP protocol to report content of captured
   packets, for example the
   number first octets of packets selected by a Selector from an input
   Population, to packet.

 4.3
     Information Model Point of View

   From the Population Size.  For some Sampling methods information model point of view, the
   Attained Selection Fraction can differ from overlap between both
   the Configured Selection
   Fraction due to, for example, IPFIX and PSAMP protocols is quite large.  Most of the inherent statistical variability
   Information Elements in
   Sampling decisions of probabilistic Sampling and Hash-based
   Selection.  Nevertheless, the IPFIX protocol are also relevant for large Population Sizes and properly
   configured Selectors, the Attained Selection Fraction usually
   approaches
   exporting packet information, for example all fields reporting packet
   header properties.  Only a few Information Elements, such as
   flowCount, packetCount (whose value will always be 1 for PSAMP) etc.,
   cannot be used in a meaningful way by the Configured Selection Fraction.

 4.3      IPFIX and PSMAP Terminology Comparison

   EDITOR'S NOTE:
     Some terms between IPFIX and PSAMP were almost similar but protocol.  Also,
   IPFIX protocol requirements concerning stage 2 of figure C do not
     quite:
     - observation point.  I kept the one from IPFIX.  However, if
   apply to the
     PSAMP/IPFIX definitons would be aligned, it would better.
     - exporting PSAMP metering process.  I kept the one from PSAMP.
     - Collector: I kept

   Further required extensions apply to the one from IPFIX, which implies that I used information model.  Even if
   the Collecting Process defined in IPFIX (it charter speaks about flows, but
     there is of Sampling, no PSAMP Collecting Process definition)

   The PSAMP terminology has been Sampling related Information
   Elements are specified with an IPFIX background, as in [IPFIX-INFO].  The task of specifying them
   was intentionally left for the PSAMP and IPFIX have similar terms.  However, this section explains a
   couple information model [PSAMP-INFO].
   A set of non compatible terms between IPFIX and PSAMP.

 4.3.1 several additional fields is required for satisfying the
   requirements for the PSAMP and IPFIX Processes

   The figure B indicates information model [PSAMP-TECH].

   Exploiting the sequence extensibility of the processes (selection and
   exporting) within IPFIX information model, the
   required extension is covered by the PSAMP Device.

                  +----------+      +-----------+
        Observed  | Metering |      | Exporting |
        Packet--->| Process  |----->| Process   |--->Collector
        Stream    +----------+      +-----------+

       Figure B: information model
   specified in [PSAMP-INFO].

 5.
   PSAMP Processes

   The Selection Process, which takes an Observed Packet Stream as its
   input, and produces Packet Reports as its output, is an integral part
   of the Metering Process, which by its definition, produces Flow
   Records as its output.

 4.3.2   Packet Report, Packet Interpretation, and Data Record

   The PSAMP terminology speaks of Packet Report and Packet
   Interpretation, while Requirements versus the IPFIX terminology speaks of Data Record and
   (Option) Template Record.  The Packet Report, which comprises
   information about Solution

   In the observed packet, can be viewed as analogous "Generic Requirements for PSAMP" section, [PSAMP-FMWK]
   describes some requirements that affect directly the PSAMP export
   protocol.

   In the "Generic Selection Process Requirements" section, [PSAMP-FMWK]
   describes one requirement that, if not directly related to the Data Record defined by a Template Record.  The Packet
   Interpretation, which comprises subsidiary information used for export
   protocol, will put some constraints on it.  Parallel Measurements:
   multiple independent selection processes at the
   interpretation same entity.

   Finally, [PSAMP-FMWK] describes a series of requirements specifying
   the Packet Reports, can different Information Elements that MUST and SHOULD be viewed as analogous reported
   to the Data Record defined by an Option Template Record.

 5.
   Differences between PSAMP and IPFIX

   The output of the IPFIX working group relevant for this draft is
   structured into three documents:
      - IP Flow information architecture [IPFIX-ARCH]
      - IPFIX protocol specifications [IPFIX-PROTO]
      - IP Flow information Collector.  Nevertheless IPFIX, being a generic export information model [IPFIX-INFO]

 5.1
     Architecture Point of View

   Traffic Flow measurement
   protocol, can export any Information Elements as long as there are
   described in the IPFIX information model.  So these requirements
   [RFC3917] and are mainly
   targeted for the IPFIX architecture [IPFIX-ARCH] can be separated
   into two stages: packet processing and Flow processing. [PSAMP-INFO] document.

   The figure C illustrates these stages.

   On stage 1, PSAMP protocol specifications meets almost all processing steps act on packets.  Packets are
   captured, time stamped, selected by one or more selection steps and
   finally forwarded to the protocol
   requirements stated in the PSAMP framework document [PSAMP-FMWK]:

       * Extensibility
       * Parallel measurement processes
       * Encrypted packets
       * Indication of information loss
       * Accuracy
       * Privacy
       * Timeliness
       * Congestion avoidance
       * Secure export
       * Export rate limit
       * Microsecond timestamp resolution

   The only requirement that is not met is Export Packet compression.
   With the choice of IPFIX as PSAMP export protocol, the export packet classification
   compression option mentioned in the section 8.5 of the framework
   document [PSAMP-FMWK] is not addressed.

 5.1
    High Level View of the Integration

   The Template Record in the Template Set is used to describe the
   different PSAMP Information Elements that maps packets will be exported to
   Flows. the
   Collector.  The packets selection steps may include Filtering Collector decodes the Template Record in the Template
   Set and
   Sampling functions.

   On stage 2, all processing steps act on Flows.  After packets are
   classified (mapped knows which Information Elements to Flows), Flows are generated, or updated if they
   exist already.  Flow generation and update steps may be performed
   repeatedly for aggregating Flows.  Finally, Flows are exported.

   Packet Sampling as described expect when it receives
   the Data Records in the Data Set, i.e. the PSAMP framework [PSAMP-FMWK]
   covers only stage 1 Packet Reports.
   Typically, in the base level of the IPFIX architecture with PSAMP functionality, the Template
   Set will contain the input sequence number, the packet
   classification replaced by fragment (some
   number of contiguous bytes from the start of the packet record export.

      IPFIX architecture                       PSAMP framework

        packet header                           packet header
           capturing     \                         capturing
              |          |                            |
         timestamping    |                       timestamping
              |          |                            |
              v          |                            v
      +------>+          |  stage 1:          +------>+
      |       |           > packet            |       |
      |    packet        |  processing        |    packet
      |   selection      |                    |   selection
      |       |          |                    |       |
      +-------+          |                    +-------+
              |          |                            |
              v          |                            v
           packet       /                       packet record
        classification  \                          export
              |          |
              v          |
      +------>+          |
      |       |          |
      | Flow generation  |
      |   and update     |  stage 2:
      |       |           > Flow
      |       v          |  processing
      |     Flow         |
      |   selection      |
      |       |          |
      +-------+          |
              |          |
              v          |
         Flow Record    /
           export

       Figure C: Comparison or from the
   start of IPFIX architecture the payload) and PSAMP framework
 5.2      Protocol Point of View

   Concerning the protocol, Selection Sequence.

   The Options Template Record in the major difference between IPFIX and PSAMP Options Template Set is used to
   describe the different PSAMP Information Elements that concern the IPFIX protocol exports Flow Records while
   Metering Process itself: Sampling and/or Filtering functions, and the PSAMP
   protocol exports Packet Records.  From a pure export point of view,
   IPFIX will not distinguish a Flow Record composed of several packets
   aggregated together, from a Flow Record composed of a single packet.
   So
   associated parameters.  The Collector decodes the PSAMP export can be seen as special IPFIX Flow Record
   containing information about a single packet.

   All extensions of Options Template
   Records in the IPFIX protocol that are required Option Template Set and knows which Information
   Elements to satisfy expect when it receives the
   PSAMP requirements, have already been incorporated Data Records in the IPFIX
   protocol [IPFIX-PROTO], which was developed in parallel with Data Set,
   i.e. the PSAMP protocol.  An example is Report Interpretation.  Typically, the need of a data type for protocol
   fields that have flexible length, such as an octet array.  This was
   added to Options
   Template would contain the IPFIX protocol specification in order to meet Selection Sequence, the
   requirement of Sampling or
   Filtering functions, and the Sampling or Filtering associated
   parameters.

   PSAMP protocol to report content of captured
   packets, for example the first octets of a packet.

 5.3      Information Model Point of View

   From requires all the information model point different possibilities of view, the overlap between both the IPFIX and PSAMP protocols protocol
   specifications [IPFIX-PROTO].  That is quite large.  Most the 3 types of Set (Data Set,
   Template Set and Options Templates Set) with the
   Information Elements 2 types of Templates
   Records (Template Record and Options Template Record), as described
   in the figure A.  As a consequence, PSAMP can't rely on a subset of
   the IPFIX protocol specifications are also relevant for
   exporting packet information, for example all fields reporting packet
   header properties.  Only a few Information Elements, such as
   flowCount, packetCount (whose value will always be 1 for PSAMP) etc.,
   cannot be used described in a meaningful way by the PSAMP protocol.  Also, [IPFIX-PROTO].
   The entire IPFIX protocol requirements concerning stage 2 of figure C do not
   apply to specifications [IPFIX-PROTO] MUST be
   implemented for the PSAMP metering process.

   Further required extensions apply to the information model.  Even if protocol.

 6.
   Using the IPFIX charter speaks of sampling, no Sampling related Information
   Elements are specified in [IPFIX-INFO].  The task of specifying them
   was intentionally left Protocol for the PSAMP information model [PSAMP-INFO].
   A set of several additional fields

 6.1
    Selector ID

   The Selector ID is required for satisfying the
   requirements for unique ID identifying a Primitive Selector.
   Each Primitive Selector MUST have a unique ID within the PSAMP information model [PSAMP-TECH].

   Additional required extensions of Observation
   Domain.  The Selector ID is represented by the information model concern
   packet filtering, and selectorId Information
   Element [PSAMP-INFO].

 6.2
    The Selection Sequence ID

   From all the field reporting content of packets observed at an Observation Point, a packet using
   the flexible length data type mentioned above.

   Exploiting the extensibility subset of
   packets is selected by one or more Selectors.  The Selection Sequence
   is the IPFIX information model, combination of an Observation Point and one or more
   Selector(s) through which the
   required extension packets are selected. The Selection
   Sequence ID is covered a unique value representing that combination.  The
   Selection Sequence ID is represented by the PSAMP information model
   specified in selectionSequenceId
   Information Element [PSAMP-INFO].

 6.    PSAMP Requirements versus the IPFIX Solution

   In the "Generic Requirements for PSAMP" section, [PSAMP-FMWK]
   describes some requirements that affect directly

 6.3
    The Exporting Process

   An Exporting Process MUST be able to limit the PSAMP export
   protocol.

   In the "Generic Selection Process Requirements" section, [PSAMP-FMWK]
   describes one requirement that, if not directly related rate according
   to a configurable value.  The Exporting Process MAY limit the export
   protocol, will put some constraints
   rate on it. Parallel Measurements:
   multiple independent selection processes at the same entity.

   In the "Reporting Process" section, [PSAMP-FMWK] finally describes a
   series of requirements specifying the different Information Elements
   that per Collecting Process basis.

 6.4
    Packet Report

   For each Selection Sequences, for each selected packet, a Packet
   Report MUST and SHOULD reported to be created.  The format of the Collector.  Nevertheless IPFIX,
   being a generic export protocol, can export any Information Elements
   as long as there Packet Report is specified
   in a Template Record contained in a Template Set.

   There are two types of Packet Report, as described in [PSAMP-FWMK]:
   the information model.  So these
   requirements are mainly targeted for basic Packet Report and the [PSAMP-INFO] document.

 6.1     IPFIX Solution for extended Packet Report.

 6.4.1   Basic Packet Report

   For each selected packet, the PSAMP Requirements

   Let's address Packet Report MUST contain the PSAMP requirements that influence
   following information:
   - The selectionSequenceId Information Element
   - The hash value (digestHashValue) generated by the export
   protocol.

   * Extensibility: digest hash
    function.  If there are no digest functions in the protocol must be able selection
    sequence then no element needs to accommodate additional
   packet selectors not currently defined.

   This requirement is addressed by the IPFIX information model, which be sent.  If there is extensible.

   * Parallel Measurement Processes: the protocol more than
    one digest function then each hash value must support
   simultaneous operation of multiple independent Measurement Processes
   at be included in
    the same host.

   This requirement is addressed by exporting the selectionPath
   Information Element order as they appear in every Packet Report.  Note that without this
   requirement, exporting the Selector ID in a Scope part selection sequence.
   - Some number of every
   single Packet Report could have been sufficient.

   * Encrypted Packets: Selectors that interpret packet fields must be
   configurable to ignore (i.e. not select) encrypted packets, when they
   are detected.

   EDITOR'S NOTE: I guess we will need extra text for this.

   * Indication contiguous bytes from the start of Information Loss: the Report Stream must include
   sufficient information to indicate or allow packet,
   including the detection packet header (which includes link layer, network layer
   and other encapsulation headers) and some subsequent bytes of loss
   occurring within the Selection, Reporting or Exporting Processes, or
   in transport. This
   packet payload.  Alternatively, the number of contiguous bytes may be achieved by
   start at the use beginning of sequence numbers.

   An Options Template, with updated statistics, MUST be sent on regular
   basis.  This Options Template contains the payload.  The dataLinkFrameSection,
   mplsLabelStackSection, mplsPayloadPacketSection, ipPacketSection, and
   ipPayloadPacketSection PSAMP Information Elements are available for example
   this use.

   For each selected packet, the total number
   of Packet Report exported from SHOULD contain the
   following information:
   - the observationTimeMicroSeconds Information Element

   In the Packet Report, the PSAMP device, device MUST be capable of exporting
   the total number of
   packet observed, etc...  Thus the Collector can compare observed packets and the number of
   Packet Report received per selector ID with packets selected by
   each instance of its Primitive Selectors (as described by the number actually
   metered and/or sent.  In case non
   scope Information Elements of discrepancy, the Selection Sequence Statistics
   Report Interpretation) although it MAY be a new Sampling rate
   could configurable option not
   to include them.  If exported, the Attained Selection Fraction may
   be computed.

   * Accuracy: calculated precisely for the Observed Packet Stream.  The Packet
   Report Stream must MAY include information only the final selector packetSelected, to act as
   an index for that enables selection sequence in the accuracy Selection Sequence
   Statistics Report Interpretation, which also allows the calculation
   of measurements to the Attained Selection Fraction.

   The contiguous Information Elements (dataLinkFrameSection,
   mplsLabelStackSection, mplsPayloadPacketSection, ipPacketSection,
   and ipPayloadPacketSection) MAY be determined.

   This requirement encoded with a fixed length field
   or with a variable sized field.  If one of these Information
   Elements is address encoded with a fixed length field whose length is too
   long for the accuracy report interpretation,
   that sends the accuracy number of contiguous bytes in the measurements.

   EDITOR'S NOTE: is selected packet,
   padding MUST NOT be used.  In this case, the accuracy or Exporting Process MUST
   export the precision?

   * Privacy: selection of information either in a new Template Record with the content
   correct fixed length field, or either in a new Template Record with
   a variable length field.

   Here is an example of a basic Packet Reports will be
   cognizant Report, with a
   SelectionSequenceId value of privacy 9 and anonymity issues while being responsive to
   the needs ipHeaderPacketSection Information
   Element of measurement applications, and in accordance 12 bytes, 0x4500 005B A174 0000 FF11 832E, encoded with RFC
   2804.  Full packet capture of arbitrary packet streams is explicitly
   out of scope.

   This requirement doesn't concern the export protocol itself.

   * Timeliness: configuration must allow for limiting of buffering
   delays for the formation and transmission for Export Packets. a
   fixed length field.

    IPFIX Template Record:

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |           Set ID = 2          |         Length = 24           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |        Template ID = 260      |        Field Count = 4        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |   selectionSequenceId = 301   |        Field Length = 4       |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      digestHashValue = 326    |        Field Length = 4       |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  ipHeaderPacketSection = 313  |        Field Length = 12      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |observationTimeMicroSeconds=324|        Field Length = 4       |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

    The associated IPFIX protocol specifications Data Record:

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |           Set ID = 260        |           Length = 28         |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                               9                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                         0x9123 0613                           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                         0x4500 005B                           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                         0xA174 0000                           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                         0xFF11 832E                           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |   observation time encoded as dateTimeSeconds [IPFIX-PROTO] describe an
   inactivity timeout for the Flow expiration.  This inactivity timeout   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

            Figure D: Example of a Basic Packet Report

   Here is configurable, an example of a basic Packet Report, with a minimum value of 0 for immediate expiration.
   Note that this minimum
   SelectionSequenceId value of 0 will force every single Data Record
   to contain information about a single packet 9 and not an aggregation
   of packets.

   * Congestion Avoidance: export ipHeaderPacketSection Information
   Element of a report stream across a network
   MUST be congestion avoiding in compliance 12 bytes, 0x4500 005B A174 0000 FF11 832E, encoded with RFC 2914.

   IPFIX, by its charter, MUST also respect this requirement.

   * Secure Export:
   - confidentiality: the option to encrypt exported data must be
   provided.
   - integrity: alterations in transit to exported data must be
   detectable at the Collector
   - authenticity: authenticity of exported data must be verifiable by
   the Collector in order to detect forged data.

   The motivation here is the same as for security in IPFIX export.

   * Compression: to conserve network bandwidth and resources at the
   Collector, the Export Packets may be compressed before export.

   With the choice of a
   variable sized field.

    IPFIX as PSAMP export protocol, the compression
   option mentioned in the framework is not addressed.

   * The exporting process must have an export rate limit, configurable
   per Exporting Process.

   EDITOR'S NOTE: this is an open issue.

   * The timestamp of observation of the packet at the Observation
   Point. The timestamp should be reported to microsecond resolution.

   EDITOR'S NOTE: this is an open issue.

 6.2     High Level View of the Integration

   The Template Record in the Template Record:

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |           Set is used to describe the
   different PSAMP Information Elements that will be exported to the
   Collector.  The Collector decodes the Template Record in the ID = 2          |         Length = 16           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |        Template ID = 261      |        Field Count = 2        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |    selectionSequenceId = 301  |        Field Length = 4       |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  ipHeaderPacketSection = 313  |      Field Length = 65535     |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

    The associated IPFIX Data Record:

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |           Set and knows which Information Elements ID = 261        |           Length = 21         |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                               9                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Length = 12  |                  0x4500 ...                   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |   ...  005B   |                  0xA174 ...                   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |   ...  0000   |                  0xFF11 ...                   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |   ...  832E   |
   +-+-+-+-+-+-+-+-+

            Figure E: Example of a Basic Packet Report,
                      with a variable sized field

 6.4.2   Extended Packet Report

   Alternatively to expect when it receives
   the Data Records in the Data Set, i.e. basic Packet Report, the PSAMP extended Packet Reports.
   Typically, in Report
   MAY contain other Information Elements related to the base level of protocols used
   in the PSAMP functionality, packet (such as source and destination IP addresses), related
   to the Template
   Set will contain packet treatment (such as output interface, destination BGP
   autonomous system), or related to the input sequence number, Selection State associated with
   the packet fragment (some (such as timestamp, hash value).

   It is envisaged that selection of fields for extended Packet Reports
   may be used to reduce reporting bandwidth, in which case the option
   to report some number of contiguous bytes from the start of the packet or from the
   start of the payload) and
   packet, mandatory in the Selection Path.

   The Options Template Record in basic Packet Report, may not be exercised.
   In this case, the Options Template Set Packet Content MAY be omitted.  Note this
   configuration is used quite similar to
   describe the different PSAMP Information Elements that concern the
   Metering Process itself: Sampling and/or Filtering functions, plus
   the associated parameters.  The Collector decodes the Options
   Template Records in the Option Template Set and knows an IPFIX device for which
   Information Elements to expect when it receives the Data Records in
   the Data Set, i.e. the PSAMP Report Interpretation.  Typically, the
   Options a
   Template would contain the Selection Path, the Sampling or
   Filtering functions, and the Sampling or Filtering associated
   parameters.

   PSAMP requires all the different possibilities of the IPFIX protocol
   specifications [IPFIX-PROTO].  That Record containing information about a single packet is the 3 types
   reported.

   Example of Set (Data Set, a detailed Extended Packet Report:

    IPFIX Template Record:

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |            Set and Options Templates Set) with the ID =  2 types of Templates
   Records (Template Record and Options        |           Length = 32         |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |       Template Record), as described
   in the figure A.  As a consequence, PSAMP can't rely on a subset of
   the IPFIX protocol specifications are described in [IPFIX-PROTO].
   The entire IPFIX protocol specifications [IPFIX-PROTO] MUST be
   implemented for the PSAMP export.

 7.    Using the IPFIX Protocol for PSAMP

 7.1     Selector ID

   The Selector ID is the unique ID identifying a Primitive Selector.
   Each Primitive Selector MUST have a unique ID within the Observation
   Domain.

 7.2 = 261       |         Field Count = 6       |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |0|  selectionSequenceId = 301  |         Field Length = 4      |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |0|  sourceIPv4Address = 44     |         Field Length = 4      |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |0| destinationIPv4Address = 45 |         Field Length = 4      |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |0|    totalLengthIPv4 = 190    |         Field Length = 2      |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |0|     tcpSourcePort = 182     |         Field Length = 2      |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |0|  tcpDestinationPort = 183   |         Field Length = 2      |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

    The Associations

   From all the packets observed at associated IPFIX Data Record:

     0                   1                   2                   3
     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |           Set ID = 261        |            Length = 20        |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                               9                               |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                           10.0.0.1                            |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                          10.0.1.106                           |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                72             |                1372           |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |               80              |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       Figure F: Example of an Observation Point, a subset Extended Packet Report

  6.5
     Report Interpretation

   To make full sense of
   packets is selected by one or more Selectors.  The Selection Path is
   a unique value describing the Observation Point and Packet Reports there are a number of
   additional pieces of information that must be communicated to the Selector
   ID(s) through
   Collector:
   - The details about which the packets Selectors and Observation Points are selected.  The Selection Path is
   represented by the selectionPath Information Element [PSAMP-INFO].

 7.3     Packet Reports

   For each Associations, for each selected packet, being
   used within a Packet Report Selection Sequences MUST be created. provided using the
   Selection Sequence Report Interpretation.
   - The format configuration details of each Selector MUST be provided using
   the Packet Selector Report is specified in a
   Template Record contained in a Template Set.

   There are two types Interpretation.
   - The Selector ID statistics MUST be provided using the Selection
   Sequence Statistics Report Interpretation.
   - The accuracies of Packet Report, as described in [PSAMP-FWMK]: the basic reported fields MUST be provided using the
   Accuracy Report Interpretation.

 6.5.1   Selection Sequence Report Interpretation

   Each Packet Report and contains a selectionSequenceId Information Element
   that identifies the extended Packet Report.

 7.3.1   Basic Packet Reports particular combination of Observation Point and
   Selector(s) used for its selection.  For each selected packet, every selectionSequenceId
   Information Element in use, the Packet Report PSAMP Device MUST contain export a Selection
   Sequence Report Interpretation using an Options Template with the
   following information:
   - The selectionPath Information Elements:

    Scope:     selectionSequenceId
    Non-Scope: one Information Element
   - Some number of contiguous bytes representing
                   the Observation Point
               selectorId (one or more)

   An Information Element representing the Observation Point would
   typically be taken from the start ingressInterface, egressInterface,
   lineCardId, exporterIPv4Address, exporterIPv6Address Information
   Elements (specified in [IPFIX-INFO]), but not limited to those: any
   Information Element specified in [IFPIX-INFO] or [PSAMP-INFO] can
   potentially be used.  In case of more complex Observation Points
   (such as a list of interfaces, a bus, etc..), a new Information
   Element describing the packet,
   including the packet header (which includes link layer, network layer
   and other encapsulation headers) and some subsequent bytes new type of Observation Point must be
   specified, along with an option template record describing it in more
   details (if necessary).

   If the
   packet payload.  Alternatively, packets are selected by a Composite Selector, the number Selection
   Sequence is composed of contiguous bytes may
   start at several Primitive Selectors.  In such a case,
   the beginning Selection Sequence Report Interpretation MUST contain the list of
   all the payload. The Layer2PacketSection,
   l2PayloadPacketSection, mplsLabelStackSection,
   mplsPayloadPacketSection, ipPacketSection, and ipPayloadPacketSection
   PSAMP Information Elements are available for this use.
   - The input sequence number(s) of any Selectors that acted on the
   packet, represented by Primitive Selector IDs in the selectorInputSequenceNumber Information
   Element.

   The contiguous Information Elements (Layer2PacketSection,
   l2PayloadPacketSection, mplsLabelStackSection,
   mplsPayloadPacketSection, ipPacketSection, and
   ipPayloadPacketSection) MAY be encoded with a fixed length field or
   with a variable sized field. Selection Sequence.  If one of these Information Elements is
   encoded with a fixed length field whose length is too long for the
   number of contiguous bytes
   multiple Selectors are contained in the selected packet, padding MUST NOT
   be used. In this case, Selection Sequence Report
   Interpretation, the Exporting Process selectorId's MUST export the
   information either in a new Template Record with the correct fixed
   length field, or either in a new Template Record with a variable
   length field.

   EDITOR'S NOTE: instead of sending the input sequence number for each
   selector ID, a counter64 value, associated with every packet, the
   working group should discuss the possibility to send the information
   on regular basis with an option template record.  Specifically in the
   case of Composite Selector, we would send multiple times a 64-bit
   counter be identified in each packet.  The example below doesn't contain the input
   sequence number.

   Here is an example of a basic Packet Report, with a SelectionPath
   value order they
   are used.

   Example of two Selection Sequences:

    Selection Sequence 7 (Filter->Sampling):
      ingressInterface    5
      selectorId          5 (Filter, match IPV4SourceAddress 10.0.0.1)
      selectorId         10 (Sampler, Random 1 out-of ten)

    Selection Sequence 9 and ipHeaderPacketSection Information Element of 12 bytes,
   0x4500 005B A174 0000 FF11 832E, encoded with a fixed length field. (Sampling->Filtering):
      ingressInterface    5
      selectorId         10 (Sampler, Random 1 out-of ten)
      selectorId          5 (Filter, match IPV4SourceAddress 10.0.0.1)

   IPFIX Options Template Record:

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |          Set ID = 2 3           |          Length = 16 26          |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |        Template ID = 260 262      |         Field Count = 2 4       |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       selectionPath = 321     |     Scope Field Count =  1    |0|  selectionSequenceId = 301  |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       Scope 1 Length = 4      |0|     ingressInterface = 10   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  ipHeaderPacketSection        Field Length = 313 4       |0|      selectorId = 300       |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |        Field Length = 12 4       |0|      selectorId = 300       |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |        Field Length = 4       |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   The associated IPFIX Data Record:

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |          Set ID = 260 262         |           Length = 20 36         |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                               7                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                               5                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                               5                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                              10                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                               9                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                         0x4500 005B                               5                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                         0xA174 0000                              10                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                         0xFF11 832E                               5                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

       Figure D: G: Example of a Basic Packet Selection Sequence Report

   Here Interpretation

   Notes:
   * There are two Records here in the same Data Set.  Each record
   defines a different Selection Sequence.
   * If, for example, a different Selection Sequence is an example composed of
   three Selectors then a basic Packet Report, different Options Template with a SelectionPath
   value of 9 (will be explained later on) and ipPacketSection three
   selectorId Information Element Elements (instead of 12 bytes, encoded with a variable length.

   EDITOR'S NOTE: to two) must be added

 7.3.2   Extended Packet Reports

   Alternatively to the basic Packet Report, the extended Packet used.

 6.5.2   Selector Report
   MAY contain extra Information Elements related Interpretation

   An IPFIX Data Record, defined by an Option Template Record, MUST be
   used to send the protocols used configuration details of every Selector in use.  The
   Option Template Record MUST contain the packet (such selectorId Information
   Element as source the Scope field and destination IP addresses), related
   to the packet treatment (such as output interface, destination BGP
   autonomous system), related to SelectorAlgorithm Information
   Element followed by some specific configuration parameters:

    Scope:     selectorId
    Non-scope: selectorAlgorithm
               algorithm specific Information Elements

   The algorithm specific Information Elements are specified in the Selection State associated with
   following subsections, depending on the packet (such as timestamp, hash value).

   It is envisaged that selection method represented
   by the value of fields for extended Packet Reports
   may be used to reduce reporting bandwidth, in which case the option
   to report some number of contiguous bytes from selectorAlgorithm.

 6.5.2.1 Systematic Count-Based Sampling

   In systematic count-based Sampling, the start of and stop triggers for
   the
   packet, mandatory Sampling interval are defined in accordance with the basic Packet Report, may not be exercised.
   In this case, spatial
   packet position (packet count) [PSAMP-TECH].

   The REQUIRED algorithm specific Information Elements in the Packet Content MAY be omitted.  Note this
   configuration is quite similar to an IPFIX device for which a
   Template Record containing information about case of
   systematic count-based Sampling are:

      samplingPacketInterval: number of packets selected in a single packet is
   reported. row
      samplingPacketSpace:    number of packets between selections
   Example of a detailed Extended Packet Report: simple 1 out-of 10 systematic count-based Selector
   definition, where the samplingPacketInterval is 1 and the
   samplingPacketSpace is 9.

   IPFIX Options Template Record:

   0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |          Set ID =  2 3           |          Length = 32 26          |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |        Template ID = 261  263     |         Field Count = 6 4       |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |0|      selectionPath = 321
   |    Scope Field Length Count = 4      |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+  1     |0|  sourceIPv4Address = 44     |         Field Length       selectorId = 4 302      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |0| destinationIPv4Address = 45
   |         Field      Scope 1 Length = 4      |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+       |0|    totalLengthIPv4   selectorAlgorithm = 190 304   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       Field Length = 2 1        |0|samplingPacketInterval = 305 |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |0|     tcpSourcePort = 182
   |       Field Length = 2      |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1        |0|  tcpDestinationPort  samplingPacketSpace = 183 306  |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       Field Length = 2 1        |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

    The associated
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Associated IPFIX Data Record:

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |            Set ID = 261 263       |          Length = 20        |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                               9                               |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                           10.0.0.1 11          |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                          10.0.1.106                              15                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                72             |                1372       1       |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+      1        |               80      9        |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

       Figure E: H: Example of an Extended Packet Report

  7.4 the Selector Report Interpretation

   To make full sense Interpretation,
                 For Systematic Count-Based Sampling

   Notes:
   * A selectorAlgorithm value of the Packet Reports there are a number of
   additional pieces of information that must be communicated to the
   Collector:
   - The details about which Selectors 1 represents systematic count-based
   Sampling.
   * samplingPacketInterval and Observation Points samplingPacketSpace are being
   used within an Associations MUST be provided using the Associations
   Report Interpretation.
   - The configuration details of each Selector MUST be provided using
   the Selector Report Interpretation.
   - The Selector ID statistics MUST be provided using the
   AssociationsStatistics Report Interpretation.
   - The accuracies of the reported fields MUST be provided using the
   Accuracy Report Interpretation.
   - Further information about each Observation Point MAY be provided
   using the Observation Point Report Interpretation.
   EDITOR'S NOTE: type
   unsigned32 but are compressed down to be discussed on one octet here, as allowed by
   the mailing list.

 7.4.1   Associations Report Interpretation

   Each Packet Report contains a selectionPath Information Element that
   identifies IPFIX protocol specifications [IPFIX-PROTO].

 6.5.2.2 Systematic Time-Based Sampling

   In systematic time-based Sampling, the particular combination of Observation Point start and
   Selector(s) stop triggers are
   used for its selection.  For every selectionPath
   Information Element in use, the PSAMP Device MUST export an
   Associations Report Interpretation using an Options Template with to define the
   following Sampling intervals [PSAMP-TECH].  The REQUIRED
   algorithm specific Information Element:

    Scope:     selectionPath
    Non-Scope: observationPointId
               selectorId (one or more)

   If Elements in the case of systematic
   time-based Sampling are:

      samplingTimeInterval: time (in us) when packets are selected by a Composite Selector, the Selection
   Path field is composed
      samplingTimeSpace:    time (in us) between selections

   Example of several Primitive Selectors.  In such a
   case, the Associations Report Interpretation MUST contain the list of
   all the Primitive 100 us out-of 1000 us systematic time-based Selector IDs in the Selection Path.  If multiple
   Selectors are contained in
   definition, where the Associations Report Interpretation, samplingTimeInterval is 100 and the Selectors ID MUST be identified in the order they are used.

   The observationPointID SHOULD be first Information Element and the
   optional processes SHOULD be last ones so that the path of the
   selected Packet
   samplingTimeSpace is provided in the logical order.

   Example of a Two Selection Path:

    Selection Path 7 (Filter->Sampling):
      observationPointID  1 (Interface 5),
      selectorId          5 (Filter, match IPV4SourceAddress 10.0.0.1),
      selectorId         10 (Sampler, Random 1 out-of ten),
      meteringProcessID    15 (IPFIX Metering Process)

    Selection Path 9 (Sampling->Filtering):
      observationPointID  1 (Interface 5),
      selectorId         10 (Sampler, Random 1 out-of ten),
      selectorId          5 (Filter, match IPV4SourceAddress 10.0.0.1),
      meteringProcessID    15 (IPFIX Metering Process) 900

   IPFIX Options Template Record:

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |           Set ID = 3          |          Length = 26          |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      Template ID = 262 264        |        Field Count = 5 4        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |    Scope Field Count =  4 1      |0|      selectionPath      selectorId = 321 302       |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Scope 1 Length = 4        |0|   observationPointId     selectorAlgorithm = 320 304 |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      Field Length = 4 1         |0|      selectorId  samplingTimeInterval = 300 307 |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      Field Length = 4 1         |0|      selectorId   samplingTimeSpace = 300 308   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      Field Length = 4 2         |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   EDITOR'S NOTE: check the observationPointId

   The associated

   Associated IPFIX Data Record:

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |           Set ID = 262 264        |          Length = 36         |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                               7                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                               1                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                               5                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                              10                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                               9 12          |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                               1                              16                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                              10        2      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+       100     |                               5             900               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

       Figure F: I: Example of an Associations the Selector Report Interpretation Interpretation,
                 For Systematic Time-Based Sampling
   Notes:
   * There are two Records here in the same Data Set.  Each record
   defines a different Selection Path. A selectorAlgorithm value of 2 represents systematic time-based
   Sampling.
   * If a different Selection Path used three Selectors then a different
   Options Template would have to be used.

 7.4.2   Selector Report Interpretation

   An IPFIX Data Record, defined by an Option Template Record, MUST be
   used to send samplingTimeInterval and samplingTimeSpace are of type unsigned32
   but are compressed down here.

 6.5.2.3 Random n-out-of-N Sampling

   In random n-out-of-N Sampling, n elements are selected out of the configuration details
   parent population that consists of every Selector in use. N elements [PSAMP-TECH].  The
   Option Template Record MUST contain the selectorId Information
   Element as the Scope field and the SelectorAlgorithm Information
   Element followed by some specific configuration parameters:

    Scope:     selectorId
    Non-scope: selectorAlgorithm
               algorithm specific Information Elements
   The algorithm specific Information Elements are specified in the
   following subsections, depending on the selection method represented
   by the value of the selectorAlgorithm.

   The Associations statistics MUST be exported periodically.

 7.4.2.1 Systematic Count-Based Sampling

   In systematic count-based Sampling, the start and stop triggers for
   the Sampling interval are defined in accordance to the spatial packet
   position (packet count) [PSAMP-TECH].
   The REQUIRED algorithm specific
   REQUIRED algorithm specific Information Elements in case of
   systematic count-based random n-
   out-of-N Sampling are:

      samplingPacketInterval:

      samplingSize:       number of packets selected in a row
      samplingPacketSpace:
      samplingPopulation: number of packets between selections in selection population

   Example of a simple 1 out-of 10 systematic count-based Selector
   definition, where the samplingPacketInterval is 1 and the
   samplingPacketSpace is 9. random n-out-of-N Sampling Selector:

   IPFIX Options Template Record:

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |           Set ID = 3          |          Length = 26          |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      Template ID =  263 265        |        Field Count = 4        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Scope Field Count = 1     |0|      selectorId = 300 302       |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Scope 1 Length = 4        |0|  selectorAlgorithm = 302 304    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      Field Length = 1        |0|samplingPacketInterval         |0|      samplingSize = 304 309     |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      Field Length = 1         |0|  samplingPacketSpace  samplingPopulation = 305 310   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      Field Length = 1         |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Associated IPFIX Data Record:

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |         Set ID = 263 265          |          Length = 11          |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                              15                              17                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       1       3       |       1       |      9        10     |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

       Figure G: J: Example of the Selector Report Interpretation,
                 For Systematic Count-Based Random n-out-of-N Sampling

   Notes:
   * A selectorAlgorithm value of 1 3 represents systematic count-based Random n-out-of-N
   Sampling.
   * samplingPacketInterval samplingSize and samplingPacketSpace samplingPopulation are of type unsigned32 but are
   compressed down to one octet here, as allowed by
   the IPFIX protocol specifications [IPFIX-PROTO].

 7.4.2.2 Systematic Time-Based here.

 6.5.2.4 Uniform Probabilistic Sampling

   In systematic time-based uniform probabilistic Sampling, each element has the start and stop triggers are
   used to define same
   probability p of being selected from the Sampling intervals [PSAMP-TECH]. parent population [PSAMP-
   TECH].  The REQUIRED algorithm specific Information Elements Element in case of systematic time-
   based uniform
   probabilistic Sampling are:

      samplingTimeInterval: time (in ms) when packets are selected
      samplingTimeSpace:    time (in ms) between selections is:

     samplingProbablility: a floating point number for the Sampling
                           probability.

   Example of a 100 ms out-of 1000 ms systematic time-based Selector
   definition, where the samplingTimeInterval is 100 and the
   samplingTimeSpace is 900 15% uniform probability Sampling Selector:

   IPFIX Options Template Record:

   0                   1                   2                   3
   0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |          Set ID = 3           |             Length = 26 22       |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       Template ID = 264 271       |         Field Count = 4 3       |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Scope Field Count = 1     |0|      selectorId = 300       |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Scope 1 Length = 4        |0|     selectorAlgorithm = 302       |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      Field Length = 1 4         |0|  samplingTimeInterval   selectorAlgorithm = 306 304   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      Field Length = 1         |0|   samplingTimeSpace samplingProbabilility = 307 311 |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      Field Length = 2 4         |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Associated IPFIX Data Record:

   0                   1                   2                   3
   0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |           Set ID = 264 271        |          Length = 16 11          |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                              16                              20                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |        2      |       100      4        |             900                          0.15                 |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |               |
   +-+-+-+-+-+-+-+-+

      Figure H: K: Example of the Selector Report Interpretation,
                For Systematic Time-Based Uniform Probabilistic Sampling

   Notes:
   * A selectorAlgorithm value of 2 4 represents systematic time-based Uniform Probabilistic
   Sampling.
   * samplingTimeInterval and samplingTimeSpace are samplingProbablility is of type unsigned32 float64 but are is compressed down to a
   float32 here.

 7.4.2.3 Random n-out-of-N Sampling

   In random n-out-of-N Sampling, n elements are selected out

 6.5.2.5 Property Match Filtering

   This classification includes match(es) on field(s) within a packet
   and/or on properties of the
   parent population that consists of N elements [PSAMP-TECH]. router state.  With this method, a packet
   is selected if a specific field in the packet equals a predefined
   value.

   The
   REQUIRED algorithm specific Information Elements in case defining configuration
   parameters for property match filtering are taken from the full range
   of random n-
   out-of-N Sampling are:

      samplingSize:       number available Information Elements.

   When multiple different Information Elements are defined, the filter
   acts as a logical AND.  Note that the logical OR is not covered by
   these PSAMP specifications.  The property match Filtering Options
   Template Record MUST NOT have multiple identical Information
   Elements.  The result of packets selected
      samplingPopulation: number the filter is independent from the order of packets
   the Information Elements in selection population

   Example of a 1 out-of 10 random n-out-of-N Sampling Selector:

   IPFIX Options the Option Template Record:

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Record, but the order
   may be important for implementation purposes, as the first filter
   will have to work at a higher rate.  In any case, an implementation
   is not constrained to respect the filter ordering as long as the
   result is the same, and it may even implement the composite Filtering
   in Filtering in one single step.

   Since encryption alters the meaning of encrypted fields, when the
   Property Match Filtering classification is based on the encrypted
   field(s) in the packet, it MUST be able to recognize that the
   field(s) are not available and MUST NOT select those packets.
   Even if they are ignored, the encrypted packets MUST be accounted for
   in the Selector packetsObserved Information Element [PSAMP-INFO],
   part of the Selection Sequence Statistics Report Interpretation.

   Example of a match based filter Selector, whose rules are:
      IPv4 Source Address   = 10.0.0.1
      IPv4 Next-Hop Address = 10.0.1.1

   IPFIX Options Template Record:

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |             Set ID =  3       |          Length = 26          |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |        Template ID = 265 266      |       Field Count = 4         |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Scope Field Count = 1     |0|     selectorId = 300 302        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      Scope 1 Length = 4       |0|   selectorAlgorithm = 302 304   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       Field Length = 1        |0|      samplingSize    sourceIPv4Address = 309 8    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       Field Length = 1 4        |0|  samplingPopulation   ipNextHopIPv4Address = 308 15 |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       Field Length = 1 4        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

    Associated IPFIX Data Record:

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |           Set ID = 265 266        |        Length = 11            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                              17                              21                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       3       5       |       1                         10.0.0 ...            |        10
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ... .1        |                         10.0.1 ...            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | ... .1        |
   +-+-+-+-+-+-+-+-+

       Figure I: L: Example of the the Selector Report Interpretation,
                 For match based and router state Filtering

   Notes:
   * A selectorAlgorithm value of 5 represents property match Filtering.

   * In this filter there is a mix of information from the packet and
   information from the router.

 6.5.2.6 Hash-Based Filtering

   In hash based selection a hash function is run on IPv4 traffic
   the following fields MUST be used as input to that hash function:
    - IP identification field
    - Flags field
    - Fragment offset
    - Source IP address
    - Destination IP address
    - A number of bytes from the IP payload.  The number of bytes and
   starting offset MUST be configurable if the hash function supports
   it.

   For the bytes taken from the IP payload, IPSX has a fixed offset
   of 0 bytes and a fixed size of 8 bytes.  The number and offset of
   payload bytes in the BOB function MUST be configurable.  If any
   of the configured set of bytes from the IP payload are unavailable
   then 0 MUST be used, which may result in a different value than
   if the hash function is run on a subset of the input.

   The minimum configuration ranges MUST be as follows:
    Number of bytes:  from 8 to 32
    Offset:           from 0 to 64

   If the selected payload bytes are not available and the hash function
   can take a variable sized input then the hash function MUST be run
   with the information which is available and a shorter size.  Passing
   0 as a substitute for missing payload bytes is only acceptable if
   the hash function takes a fixed size as is the case with IPSX.

   If the hash function can take an initialization value then this
   value MUST be configurable.

   A hash-based selection function MAY be configurable as a digest
   function.  Any selection process which is configured as a digest
   function MUST have the output value included in the basic packet
   report for any selected packet.

   Each hash function used as a hash-based selector requires its own
   value for the selectorAlgorithm. Currently we have BOB (6), IPSX (7)
   and CRC (8) defined and any MAY be used for either Filtering
   or creating a Packet Digest.  Only BOB is recommended though and
   SHOULD be used.

   The REQUIRED algorithm specific Information Elements in case of hash
   based selection are:

   hashIPPayloadOffset   - The payload offset used by a hash based
                          Selector Report Interpretation,
                 For Random n-out-of-N Sampling

   Notes:
   *
   hashIPPayloadSize     - The payload size used by a hash based
                          Selector
   hashOutputRangeMin    - One or more values for the beginning of
                          each potential output range.
   hashOutputRangeMax    - One or more values for the end of each
                          potential output range.
   hashSelectedRangeMin  - One or more values for the beginning of
                          each selected range.
   hashSelectedRangeMax  - One or more values for the end of each
                          selected range.
   hashDigestOutput      - A selectorAlgorithm value boolean value, TRUE if the output from
                          this selector has been configured to be
                          included in the packet report as a packet
                          digest.

   NOTE: If more than one selection or output range needs to be sent
   then the minimum and maximum elements may be repeated as needed.
   These MUST make one or more non-overlapping ranges.  The elements
   SHOULD be sent as pairs of 3 represents Random n-out-of-N
   sampling.
   * samplingSize minimum and samplingPopulation maximum in ascending order,
   however if they are sent out of type unsigned32 order then there will only be one
   way to interpret the ranges to produce a non-overlapping range and
   the Collecting Process MUST be prepared to accept and decode this.

   The following algorithm specific Information Element MAY be sent,
   but are
   compressed down is optional for security considerations:
   hashInitialiserValue  - The initialiser value to one octet here.

 7.4.2.4 Uniform Probabilistic Sampling

   In uniform probabilistic Sampling, each element has the same
   probability p hash function.

   Since encryption alters the meaning of beings encrypted fields, when the
   Hash-Based Filtering classification is based on the encrypted
   field(s) in the packet, it MUST be able to recognize that the
   field(s) are not available and MUST NOT select those packets select
   those packets.  Even if they are selected from ignored, the parent population
   [PSAMP-TECH].  The algorithm specific encrypted packets MUST
   be accounted in the Selector packetsObserved Information Element in case
   [PSAMP-INFO], part of
   uniform probabilistic Sampling is:

     samplingProbablility: a floating point number for the Sampling
                           probability. Selection Sequence Statistics Report
   Interpretation.

   Example of a 15% uniform probability Sampling Selector: hash based filter Selector, whose configuration is:
   Hash Function           = BOB
   Hash IP Payload Offset  = 0
   Hash IP Payload Size    = 16
   Hash Initialiser Value  = 0x9A3F9A3F
   Hash Output Range       = 0 to 0xFFFFFFFF
   Hash Selected Range     = 100 to 200 and 400 to 500

   IPFIX Options Template Record:

   0                   1                   2                   3
   0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |             Set ID =  3       |          Length = 22 50          |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |        Template ID = 271 269      |       Field Count = 3 8         |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Scope Field Count = 1     |0|     selectorId = 300        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      Field      Scope 1 Length = 4       |0|   selectorAlgorithm = 302   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       Field Length = 1        |0|  samplingProbablility  hashIPpayloadOffset = X 327  |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       Field Length = 1 4        |0|   hashIPpayloadSize = 328   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       Field Length = 4        |0|  hashInitialiserValue = 329 |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       Field Length = 4        |0|   hashOutputRangeMin = 330  |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       Field Length = 4        |0|   hashOutputRangeMax = 331  |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       Field Length = 4        |0|  hashSeletionRangeMin = 332 |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       Field Length = 4        |0|  hashSeletionRangeMax = 333 |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       Field Length = 4        |0|  hashSeletionRangeMin = 332 |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       Field Length = 4        |0|  hashSeletionRangeMax = 333 |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       Field Length = 4        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   EDITOR'S NOTE: check the value of samplingProbablility in [PSAMP-
   INFO]

   Associated IPFIX Data Record:

   0                   1                   2                   3
   0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |           Set ID = 271 266        |        Length = 11 45            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                              20                              22                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      4       6       |                          0.15                            ...                |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | ...   0       |                            ...                |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | ...  16       |                      0x9A3F9A ...             |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | ...  3F       |                            ...                |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | ...   0       |                      0xFFFFFF ...             |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | ...  FF       |                        ... 100                |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      ...      |                        ... 200                |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      ...      |                        ... 400                |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      ...      |                        ... 500                |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      ...      |
   +-+-+-+-+-+-+-+-+

       Figure I: M: Example of the Selector Report Interpretation,
                For Uniform Probabilistic Selector Report Interpretation,
                 for Hash Based Filtering

   Notes:
   * A selectorAlgorithm value of 6 represents hash-based Filtering
   using the BOB algorithm.

 6.5.2.7 Other Selection Methods

   Some potential new selection methods MAY be added.  Some of the new
   selection methods, such as non-uniform probabilistic Sampling

   Notes:
   * A selectorAlgorithm and
   flow state dependent Sampling, are described in [PSAMP-TECH], with
   further references.

   Each new selection method MUST be assigned a unique value for the
   selectorAlgorithm Information Element.  Its configuration
   parameter(s), along with the way to report it/them with an Options
   Template, MUST be clearly specified.

 6.5.3   Selection Sequence Statistics Report Interpretation

   A Selector MAY be used in multiple Selection Sequences.  However,
   each use of 4 represents Uniform Probabilistic
   Sampling.

 7.4.2.5 Property Match Filtering

   This classification includes match(es) on field(s) within a packet
   and/or on properties Selector must be independent, so each separate logical
   instance of the router state.  With this method, a packet
   is Selector MUST maintain its own individual Selection
   State and statistics.

   The Selection Sequence Statistics Report Interpretation MUST include
   the number of observed packets (Population Size) and the number of
   packets selected if (Sample Size) by each instance of its Primitive
   Selectors.

   Within a specific field in Selection Sequence composed of several Primitive Selectors,
   the packet equals a predefined
   value.

   The algorithm specific Information Elements, defining configuration
   parameters number of packets selected for property one Selector is equal to the
   number of packets seen by the next Selector.  The order of the
   Selectors in the Selection Sequence Statistics Report Interpretation
   MUST match filtering, are taken from the order of the Selectors in the Selection Sequence.

   If the full
   range set of available statistics is not sent part of the Basic Packet
   Reports, the PSAMP Device MUST export a Selection Sequence Statistics
   Report Interpretation for every Selection Sequence, using an Options
   Template containing the following Information Elements.

   When multiple different Elements:

    Scope:         selectionSequenceId
    Non-scope:     packetsObserved
                   packetsSelected (first)
                   ...
                   packetsSelected (last)

   The packetsObserved Information Elements are defined, Element [PSAMP-INFO] MUST contain the filter
   acts
   number of packets seen at the Observation Point, and as a logical AND.  Note that consequence
   passed to the logical OR is not covered by
   these PSAMP specifications. first Selector in the Selection Sequence.  The property match Filtering Options
   Template Record MUST NOT have multiple identical
   packetsSelected Information
   Elements.  The result Element [PSAMP-INFO] contains the number
   of packets selected by a Selector in the filter Selection Sequence.

   The Attained Selection Fraction for the Selection Sequence is independent from
   calculated by dividing the order number of
   the observed packets
   (packetsObserved Information Elements in Element) by the Option Template Record, but value of selected
   packets (packetsSelected Information Element) for the order
   may last Selector.
   The Attained Selection Fraction can be important calculated for implementation purposes, as each Selector
   by dividing the first filter
   will have to work number of packets selected for that Selector by the
   value for the previous Selector.

   The statistics for the whole sequence SHOULD be taken at a higher rate.  In any case, an implementation
   is not constrained to respect the filter ordering, as long as single
   logical point in time; the
   result is input value for a Selector MUST equal the same, and it may even implement
   output value of the composite Filtering
   in Filtering in previous selector.

   The Selection Sequence Statistics Report Interpretation MUST be
   exported periodically.

   Example of Selection Sequence Statistics Report Interpretation:

    Selection Sequence 7 (Filter->Sampling):

      Observed   100  (observationPointId  1, Interface 5)
      Selected    50  (selectorId  5, match IPV4SourceAddress 10.0.0.1)
      Selected     6  (selectorId 10, Sampler: Random one out-of ten)

    Selection Sequence 9 (Sampling->Filtering):

      Observed   100  (observationPointId  1, Interface 5)
      Selected    10  (selectorId 10, Sampler: Random one single step.

   Example of a out-of ten)
      Selected     3  (selectorId  5, match based filter Selector, whose rules are:
      IPv4 Source Address   = 10.0.0.1
      IPv4 Next-Hop Address = 10.0.1.1 IPV4SourceAddress 10.0.0.1)
   IPFIX Options Template Record:

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |            Set ID = 3         |           Length = 26         |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       Template ID = 266 267       |        Field Count = 4        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Scope Field Count = 1     |0|     selectorId  selectionSequenceId = 300 301  |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      Scope 1 Length = 4       |0|   selectorAlgorithm    packetsObserved = 302 318    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       Field Length = 1 4        |0|    sourceIPv4Address    packetsSelected = 8 319    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       Field Length = 4        |0|   ipNextHopIPv4Address    packetsSelected = 15 319    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       Field Length = 4        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

    Associated

   The associated IPFIX Data Record:

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |           Set ID = 266  267       |          Length = 11 36          |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                              21                               7                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       5                              100                              |                         10.0.0 ...
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                              50                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | ... .1                               6                               |                         10.0.1 ...
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                               9                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | ... .1                              100                              |
   +-+-+-+-+-+-+-+-+
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                              10                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                               3                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

       Figure J: N: Example of the Selector Selection Sequence Statistics Report Interpretation,
                 For match based and router state Filtering

   Notes:
   * A selectorAlgorithm value of 5 represents property match Filtering.
   * In this filter there is a mix of information from the packet and
   information from the router.

 7.4.2.6 Hash-Based Filtering

   EDITOR'S NOTE: to be completed
                 Interpretation
   Notes:
   * A selectorAlgorithm value of 6 represents hash-based Filtering.

 7.4.2.7 Other The Attained Sampling Fractions for Selection Methods

   Some potential new selection methods MAY be added.  Some Sequence 7 are:
            Filter 10: 50/100
            Sampler 5: 6/50
            Number of the new
   selection methods, such as non-uniform probabilistic samples selected: 6

   * The Attained Sampling and
   flow state dependent Sampling, are described in [PSAMP-TECH], with
   further references.

   Each new selection method MUST be assigned a unique value Fractions for the
   selectorAlgorithm Information Element.  Its configuration
   parameter(s), along with the way to report it/them with an Options
   Template, MUST be clearly specified.

 7.4.3   Associations Statistics Report Interpretation

   A Selector MAY be used in multiple Associations.  However, each use
   of a Selector must be independent, so each separate logical instances
   of a Selector MUST maintain its separate Selection State and
   statistics.

   The Associations Statistics Sequence 9 are:
            Sampler 5: 10/100
            Filter 10: 3/10
            Number of samples selected: 3

 6.5.4   Accuracy Report Interpretation MUST include
   In order for the
   number of packets seen (Population Size) and Collecting Process to determine the number inherent
   accuracy of packets
   selected (Sample Size) the reported quantities (for example timestamps), the
   PSAMP Device SHOULD send an Accuracy Report Interpretation.

   The Accuracy Report Interpretation MUST be exported by each instance of its Primitive Selector.
   Within an Association composed of several Primitive Selectors, Option
   Template Record with a scope that contains the
   number of packets selected Information Element
   for one Selector which the accuracy is equal required.  In case the accuracy is specific
   to a template, a second scope containing the number of
   packets seen by templateId value MUST be
   added to the next Selector. Option Template Record.  The order of accuracy SHOULD be reported
   either with the Selectors in fixedError Information Element [PSAMP-INFO], or with
   the
   Associations Statistics relativeError Information Element [PSAMP-INFO].

   Accuracy Report Interpretation MUST match the order of
   the Selectors in using the Association, as defined in fixedError Information
   Element:
    Scope:     informationElementId
    Non-scope: fixedError

   Accuracy Report Interpretation using the Associations fixedError Information
   Element and a double scope:
    Scope:     templateId
               informationElementId
    Non-scope: fixedError

   Accuracy Report Interpretation.

   The Associations Statistics Interpretation using the relativeError Information
   Element:
    Scope:     informationElementId
    Non-scope: relativeError

   Accuracy Report Interpretation MUST also contain using the number relativeError Information
   Element and a double scope:
    Scope:     templateId
               informationElementId
    Non-scope: relativeError

   For example, the accuracy of packets observed at an Information Element whose Abstract
   Data Type is dateTimeMilliSeconds [IPFIX-INFO], for which the unit is
   specified as milliseconds, can be specified with the fixedError
   Information Element with the milliseconds units.  In this case, the
   error interval is the Information Element value +/- the Observation. value
   reported in the fixedError.

   For every Selection Path, example, the PSAMP Device MUST export an
   Associations statistics Report Interpretation using accuracy of an Options
   Template Information Element to estimate the
   accuracy of a sampled flow, for which the unit would be specified in
   octets, can be specified with the following Information Element:

    Scope:     SelectionPath
    Non-scope: packetsObserved
               packetsSelected (one or more)

   The packetsObserved relativeError Information Element contains
   with the number of
   packets seen at octet units.  In this case, the Observation Point, and as a consequence passed to error interval is the first Selector
   Information Element value +/- the value reported in the Association.  The packetsSelected relativeError
   time the reported Information Element contains value.

   Alternatively to reporting either the number of packets selected by fixedError Information Element
   or the
   various Selectors relativeError Information Element in the Associations.

   The Attained Selection Fraction can Accuracy Report
   Interpretation, both Information Elements MAY be calculated for each Selector
   by dividing present.  This
   scenario could help in more complex situations where the number system clock
   drifts, on the top of packets selected for that Selector by having its own accuracy, during the
   previous value.

   The statistics for duration of
   a measurement.

   If the whole sequence SHOULD be taken at accuracy of a single
   logical point in time, reported quantity changes on the input value for Metering
   Process, a Selector new Accuracy Report Interpretation MUST equal be generated.  The
   Collecting Process MUST keep the
   output value accuracy of the previous selector. latest Accuracy
   Report Interpretation.

   Example of Associations Statistics an Accuracy Report Interpretation:

    Associations set 7 (Filter->Sampling):

      Observed   100  (observationPointID  1, Interface 5)
      Selected    50  (selectorId  5, match IPV4SourceAddress 10.0.0.1)
      Selected Interpretation using the fixedError
   Information Element and a double scope: the timeMicroSeconds
   contained in the Template 5 has an accuracy of +/- 2 ms, represented
   by the fixedError Information Element.
    Scope:     templateId = 6  (selectorId 10, Sampler: Random one out-of ten)

    Associations set 9 (Sampling->Filtering):

      Observed   100  (observationPointID  1, Interface 5)
      Selected    10  (selectorId 10, Sampler: Random one out-of ten)
      Selected     3  (selectorId  5, match IPV4SourceAddress 10.0.0.1)
               informationElementId = timeMicroSeconds
    Non-scope: fixedError = 2 ms

   IPFIX Options Template Record:

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |            Set ID = 3         |           Length = 30 22         |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       Template ID = 267       |        Field Count = 5        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Scope Field Count = 1     |0|      selectionPath = 321    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      Scope 1 Length = 4       |0|    packetsObserved Count = 324 3        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Scope Field Length Count = 4 2     |0|    packetsSelected       templateId = 325 145      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       Field      Scope 1 Length = 4 2       |0|    packetsSelected InformationElementId = 325 303  |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       Field      Scope 2 Length = 4 2       |0|    packetsSelected      fixedError = 325 320       |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       Field Length = 4        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   The associate associated IPFIX Data Record:

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |           Set ID =  267       |          Length = 24          |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                               7                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                              100                              |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                              50                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                               6                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                               9 12          |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                              100                              |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+              5                |                              10             324               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                               3                    2  (encoded as a float32)                  |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

       Figure K: O: Example of the Association Selection Sequence Statistics Report
                 Interpretation

   Notes:
   * The Attained Packet Fractions for the first set of Associations
   are:
            Filter 10: 50/100
            Sampler 5: 6/50
            Number fixedError is of samples sent type float64 but is compressed down to Metering Process: 6
   * a float32
   here.

   The Attained Packet Fractions for the second set of Associations
   are:
            Sampler 5: 10/100
            Filter 10: 3/10
            Number of samples sent to Metering Process: 3

 7.4.4 example displays an Accuracy Report Interpretation

   The inherent accuracy of using
   the relativeError Information Elements in the Packet
   Report MUST be reported in order to enable Element and a single scope: the Collector to determine
   timeMicroSeconds has an error of 5 percents, represented by the accuracy
   proportionalAccuracy Information Element.
    Scope:     informationElementId = timeMicroSeconds
    Non-scope: relativeError = 0.05

   IPFIX Options Template Record:

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |            Set ID = 3         |           Length = 18         |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       Template ID = 268       |        Field Count = 2        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Scope Field Count = 1     |0| InformationElementId = 303  |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      Scope 1 Length = 2       |0|      relativeError= 321     |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       Field Length = 4        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   The associated IPFIX Data Record:

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |           Set ID =  267       |          Length = 10          |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |             324               |                     0.05 ...  |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | ...(encoded as a float32)     |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

       Figure P: Example of the measurements.

   EDITOR'S NOTE: to be completed

 7.4.5   Observation Point Report Interpretation

   For each Observation Point, an Observation Option Selection Sequence Statistics Report
                 Interpretation MAY be sent.

   EDITOR'S NOTE:

   Notes:
   * relativeError is of type float64 but is compressed down to be completed

 8. a
   float32 here.

 7.
   Security Considerations

   As IPFIX has been selected as the PSAMP export protocol and as the
   PSAMP security requirements are not stricter than the IPFIX security
   requirements, refer to the IPFIX export protocol [IPFIX-PROTO] for
   the security considerations.

 9.

   In the basic Packet Report, a PSAMP Device exports some number of
   contiguous bytes from the start of the packet, including the packet
   header (which includes link layer, network layer and other
   encapsulation headers) and some subsequent bytes of the packet
   payload. The PSAMP Device SHOULD NOT export the full payload of
   conversations, as this would mean wiretapping [RFC2804].

 8.
   IANA Considerations

   The PSAMP Protocol, as set out in this document, has two sets of
   assigned numbers.  Considerations for assigning them are discussed in
   this section, using the example policies as set out in the
   "Guidelines for IANA Considerations" document IANA-RFC [RFC2434].

 9.1

 8.1
     IPFIX Related Considerations

   As the PSAMP protocol uses the IPFIX protocol, refer to the IANA
   considerations section in [IPFIX-PROTO] for the assignments of
   numbers used in the protocol and for the numbers used in the
   information model.

 9.2

 8.2
     PSAMP Related Considerations

   Each new selection method MUST be assigned a unique value for the
   selectorAlgorithm Information Element.  Its configuration
   parameter(s), along with the way to report it/them with an Options
   Template, MUST be clearly specified.

   Each new selection method MUST be assigned a unique value for the
   selectorAlgorithm Information Element.

   New assignments for the PSAMP selection method will be administered
   by IANA, on a First Come First Served basis [RFC 2434], subject to
   Expert Review [RFC 2434], i.e. review by one of a group of experts
   designated by an IETF Operations and Management Area Director.  The
   group of experts must double check the Information Elements
   definitions with already defined Information Elements for
   completeness, accuracy and redundancy.  Those experts will initially
   be drawn from the Working Group Chairs and document editors of the
   IPFIX and PSAMP Working Groups.

 10.

 9.
   References

 10.1

 9.1
     Normative References

   [RFC1771] Y. Rekhter, T. Li, "A Border Gateway Protocol 4 (BGP-4)",
   RFC 1771, March 1995

   [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
   Requirement Levels", BCP 14, RFC 2119, March 1997

   [RFC2434] H. Alvestrand, T. Narten, "Guidelines for Writing an IANA
   Considerations Section in RFCs", RFC 2434, October 1998

   [PSAMP-TECH] T. Zseby, M. Molina, N. Duffield, S. Niccolini, F.
   Raspall, "Sampling and Filtering Techniques for IP Packet Selection"
   draft-ietf-psamp-sample-tech-07.txt

   [PSAMP-MIB] T. Dietz, B. Claise "Definitions of Managed Objects for
   Packet Sampling" draft-ietf-psamp-mib-05.txt

   [PSAMP-INFO] T. Dietz, F. Dressler, G. Carle, B. Claise, "Information
   Model for Packet Sampling Exports", draft-ietf-psamp-info-03.txt

   [IPFIX-ARCH] G. Sadasivan, N. Brownlee, B. Claise, J. Quittek,
   "Architecture Model for IP Flow Information Export" draft-ietf-ipfix-
   arch-09.txt"

   [IPFIX-INFO] J. Quittek, S. Bryant, B. Claise, J. Meyer, "Information
   Model for IP Flow Information Export" draft-ietf-ipfix-info-11.txt

   [IPFIX-PROTO] B. Claise (Editor) "IPFIX Protocol Specifications",
   draft-ietf-ipfix-protocol-19.txt

   [RFC1771] Y. Rekhter, T. Li, "A Border Gateway Protocol 4 (BGP-4)",
   RFC 1771, March 1995.

   [RFC2434] H. Alvestrand, T. Narten, "Guidelines for Writing an IANA
   Considerations Section in RFCs", RFC 2434, October 1998.

 10.2

 9.2
    Informative References

   [PSAMP-MIB] T. Dietz, B. Claise "Definitions of Managed Objects for
   Packet Sampling" draft-ietf-psamp-mib-05.txt
   [PSAMP-FMWK] D. Chiou, B. Claise, N. Duffield, A. Greenberg, M.
   Grossglauser, P. Marimuthu, J. Rexford, G. Sadasivan,  "A Framework
   for Passive Packet Measurement" draft-ietf-psamp-framework-10.txt

   [RFC3917] J. Quittek, T. Zseby, B. Claise, S. Zander, "Requirements
   for IP Flow Information Export", RFC 3917, October 2004

 11.

 10.
    Acknowledgments

   The authors would like to thank the PSAMP group, especially Paul
   Aitken for fruitful discussions and for proofreading the document. document
   several times.

   Authors' Addresses

   Benoit Claise
   Cisco Systems
   De Kleetlaan 6a b1
   1831 Diegem
   Belgium
   Phone: +32 2 704 5622
   E-mail: bclaise@cisco.com

   Juergen Quittek
   NEC Europe Ltd.
   Network Laboratories
   Kurfuersten-Anlage 36
   69115 Heidelberg
   Germany
   Phone: +49 6221 90511-15
   Email: quittek@ccrle.nec.de

   Andrew Johnson
   Cisco Systems
   96 Commercial Quay
   Edinburgh EH6 6LX
   Scotland
   Phone: +44 131 561 3641
   Email: andrjohn@cisco.com

   Intellectual Property Statement

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at ietf-
   ipr@ietf.org.

   The IETF has been notified of intellectual property rights claimed in
   regard to some or all of the specification contained in this
   document.  For more information consult the online list of claimed
   rights.

   Disclaimer of Validity

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
   ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
   INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
   INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

   Copyright Statement

   Copyright (C) The Internet Society (2005). (2006).  This document is subject
   to the rights, licenses and restrictions contained in BCP 78, and
   except as set forth therein, the authors retain all their rights.

   Acknowledgment

   Funding for the RFC Editor function is currently provided by the
   Internet Society