draft-ietf-psamp-protocol-09.txt   rfc5476.txt 
PSAMP working group
Internet Draft EDITOR: B. Claise
draft-ietf-psamp-protocol-09.txt Cisco Systems, Inc.
Intended status: Proposed Standard December 10th 2007
Packet Sampling (PSAMP) Protocol Specifications
Status of this Memo
By submitting this Internet-Draft, each author represents that Network Working Group B. Claise, Ed.
any applicable patent or other IPR claims of which he or she is Request for Comments: 5476 A. Johnson
aware have been or will be disclosed, and any of which he or Category: Standards Track Cisco Systems, Inc.
she becomes aware will be disclosed, in accordance with Section J. Quittek
6 of BCP 79. NEC Europe Ltd.
Internet-Drafts are working documents of the Internet Packet Sampling (PSAMP) Protocol Specifications
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 Status of This Memo
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 This document specifies an Internet standards track protocol for the
http://www.ietf.org/ietf/1id-abstracts.txt. Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
The list of Internet-Draft Shadow Directories can be accessed Copyright Notice
at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on June, 2008. Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
Copyright Notice This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
Copyright (C) The IETF Trust (2007). This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Abstract Abstract
This document specifies the export of packet information from a This document specifies the export of packet information from a
PSAMP Exporting Process to a PSAMP Collecting Process. For export Packet SAMPling (PSAMP) Exporting Process to a PSAMP Collecting
of packet information the IP Flow Information eXport (IPFIX) Process. For export of packet information, the IP Flow Information
protocol is used, as both the IPFIX and PSAMP architecture match eXport (IPFIX) protocol is used, as both the IPFIX and PSAMP
very well and the means provided by the IPFIX protocol are architecture match very well, and the means provided by the IPFIX
sufficient. The document specifies in detail how the IPFIX protocol protocol are sufficient. The document specifies in detail how the
is used for PSAMP export of packet information. 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 [RFC2119].
Table of Contents Table of Contents
1. Introduction.................................................3 1. Introduction ....................................................3
2. PSAMP Documents Overview.....................................3 1.1. Conventions Used in This Document ..........................3
3. Terminology..................................................4 2. PSAMP Documents Overview ........................................4
3.1 IPFIX Terminology..........................................4 3. Terminology .....................................................4
3.2 PSAMP Terminology..........................................5 3.1. IPFIX Terminology ..........................................4
3.2.1 Packet Streams and Packet Content.......................5 3.2. PSAMP Terminology ..........................................5
3.2.2 Selection Process.......................................6 3.2.1. Packet Streams and Packet Content ...................5
3.2.3 Reporting...............................................7 3.2.2. Selection Process ...................................6
3.2.4 Metering Process........................................8 3.2.3. Reporting ...........................................7
3.2.5 Exporting Process.......................................8 3.2.4. Metering Process ....................................8
3.2.6 PSAMP Device............................................8 3.2.5. Exporting Process ...................................8
3.2.7 Collector...............................................8 3.2.6. PSAMP Device ........................................8
3.2.8 Selection Methods.......................................8 3.2.7. Collector ...........................................8
3.3 IPFIX and PSAMP Terminology Comparison....................11 3.2.8. Selection Methods ...................................9
3.3.1 IPFIX and PSAMP Processes..............................11 3.3. IPFIX and PSAMP Terminology Comparison ....................11
3.3.2 Packet Report, Packet Interpretation, and Data Record..11 3.3.1. IPFIX and PSAMP Processes ..........................11
4. Differences between PSAMP and IPFIX.........................12 3.3.2. Packet Report, Packet Interpretation, and
4.1 Architecture Point of View................................12 Data Record ........................................12
4.2 Protocol Point of View....................................13 4. Differences between PSAMP and IPFIX ............................12
4.3 Information Model Point of View...........................14 4.1. Architecture Point of View ................................12
5. PSAMP Requirements versus the IPFIX Solution................14 4.2. Protocol Point of View ....................................14
5.1 High Level View of the Integration........................15 4.3. Information Model Point of View ...........................14
6. Using the IPFIX Protocol for PSAMP..........................16 5. PSAMP Requirements versus the IPFIX Solution ...................14
6.1 Selector ID...............................................16 5.1. High-Level View of the Integration ........................15
6.2 The Selection Sequence ID.................................16 6. Using the IPFIX Protocol for PSAMP .............................16
6.3 The Exporting Process.....................................17 6.1. Selector ID ...............................................17
6.4 Packet Report.............................................17 6.2. The Selection Sequence ID .................................17
6.4.1 Basic Packet Report....................................17 6.3. The Exporting Process .....................................17
6.4.2 Extended Packet Report.................................20 6.4. Packet Report .............................................17
6.5 Report Interpretation.....................................21 6.4.1. Basic Packet Report ................................17
6.5.1 Selection Sequence Report Interpretation...............21 6.4.2. Extended Packet Report .............................21
6.5.2 Selector Report Interpretation.........................23 6.5. Report Interpretation .....................................22
6.5.2.1 Systematic Count-Based Sampling.......................24 6.5.1. Selection Sequence Report Interpretation ...........23
6.5.2.2 Systematic Time-Based Sampling........................25 6.5.2. Selector Report Interpretation .....................25
6.5.2.3 Random n-out-of-N Sampling............................26 6.5.2.1. Systematic Count-Based Sampling ...........25
6.5.2.4 Uniform Probabilistic Sampling........................27 6.5.2.2. Systematic Time-Based Sampling ............27
6.5.2.5 Property Match Filtering..............................29 6.5.2.3. Random n-out-of-N Sampling ................28
6.5.2.6 Hash-Based Filtering..................................30 6.5.2.4. Uniform Probabilistic Sampling ............29
6.5.2.7 Other Selection Methods...............................34 6.5.2.5. Property Match Filtering ..................31
6.5.3 Selection Sequence Statistics Report Interpretation....34 6.5.2.6. Hash-Based Filtering ......................33
6.5.4 Accuracy Report Interpretation.........................36 6.5.2.7. Other Selection Methods ...................36
7. Security Considerations.....................................39 6.5.3. Selection Sequence Statistics Report
8. IANA Considerations.........................................40 Interpretation .....................................37
8.1 IPFIX Related Considerations..............................40 6.5.4. Accuracy Report Interpretation .....................39
8.2 PSAMP Related Considerations..............................40 7. Security Considerations ........................................43
9. References..................................................40 8. IANA Considerations ............................................43
9.1 Normative References......................................40 8.1. IPFIX-Related Considerations ..............................43
9.2 Informative References....................................41 8.2. PSAMP-Related Considerations ..............................43
10. Acknowledgments............................................41 9. References .....................................................44
11. Intellectual Property Statement............................42 9.1. Normative References ......................................44
12. Copyright Statement........................................42 9.2. Informative References ....................................44
13. Disclaimer.................................................43 10. Acknowledgments ...............................................45
1. Introduction 1. Introduction
The name PSAMP is a contraction of the phrase Packet SAMPling. The The name PSAMP is a contraction of the phrase "Packet Sampling". The
word "sampling" captures the idea that only a subset of all packets word "Sampling" captures the idea that only a subset of all packets
passing a network element will be selected for reporting. PSAMP passing a network element will be selected for reporting. PSAMP
selection operations include random selection, deterministic selection operations include random selection, deterministic
selection, and deterministic approximations to random selection selection, and deterministic approximations to random selection
(hash-based selection). (Hash-based Selection).
The IP Flow information export (IPFIX) protocol specified in [IPFIX- The IP Flow Information eXport (IPFIX) protocol specified in
PROTO] exports IP traffic information [IPFIX-INFO] observed at [RFC5101] exports IP traffic information [RFC5102] observed at
network devices. This matches the general protocol requirements network devices. This matches the general protocol requirements
outlined in the PSAMP framework [PSAMP-FMWK]. However, there are outlined in the PSAMP framework [RFC5474]. However, there are some
some architectural differences between IPFIX and PSAMP in the architectural differences between IPFIX and PSAMP in the requirements
requirements for an export protocol. While the IPFIX architecture for an export protocol. While the IPFIX architecture [RFC5470] is
[IPFIX-ARCH] is focused on gathering and exporting IP traffic flow focused on gathering and exporting IP traffic flow information, the
information, the focus of the PSAMP framework [PSAMP-FMWK] is on focus of the PSAMP framework [RFC5474] is on exporting information on
exporting information on individual packets. This basic difference individual packets. This basic difference and a set of derived
and a set of derived differences in protocol requirements are differences in protocol requirements are outlined in Section 4.
outlined in Section 4. Despite these differences, the IPFIX protocol Despite these differences, the IPFIX protocol is well suited for the
is well suited as PSAMP protocol. Section 5 specifies how the IPFIX PSAMP protocol. Section 5 specifies how the IPFIX protocol is used
protocol is used for the export of packet samples. Required for the export of packet samples. Required extensions of the IPFIX
extensions of the IPFIX information model are specified in the PSAMP information model are specified in the PSAMP information model
information model [PSAMP-INFO]. [RFC5477].
1.1. Conventions Used in This Document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
2. PSAMP Documents Overview 2. PSAMP Documents Overview
[PSAMP-FMWK]: "A Framework for Packet Selection and Reporting", This document is one out of a series of documents from the PSAMP
describes the PSAMP framework for network elements to select subsets group.
of packets by statistical and other methods, and to export a stream
of reports on the selected packets to a collector.
[PSAMP-TECH]: "Sampling and Filtering Techniques for IP Packet [RFC5474]: "A Framework for Packet Selection and Reporting" describes
Selection", describes the set of packet selection techniques the PSAMP framework for network elements to select subsets of packets
supported by PSAMP. by statistical and other methods, and to export a stream of reports
on the selected packets to a Collector.
This document: "Packet Sampling (PSAMP) Protocol Specifications" [RFC5475]: "Sampling and Filtering Techniques for IP Packet
specifies the export of packet information from a PSAMP Exporting Selection" describes the set of packet selection techniques supported
Process to a PSAMP Collecting Process. by PSAMP.
[PSAMP-INFO]: "Information Model for Packet Sampling Exports" defines RFC 5476 (this document): "Packet Sampling (PSAMP) Protocol
an information and data model for PSAMP. Specifications" specifies the export of packet information from a
PSAMP Exporting Process to a PSAMP Collecting Process.
[RFC5477]: "Information Model for Packet Sampling Exports" defines an
information and data model for PSAMP.
3. Terminology 3. Terminology
As the IPFIX export protocol is used to export the PSAMP information, As the IPFIX export protocol is used to export the PSAMP information,
the relevant IPFIX terminology from [IPFIX-PROTO] is copied over in the relevant IPFIX terminology from [RFC5101] is copied over in this
this document. All terms defined in this section have their first document. All terms defined in this section have their first letter
letter capitalized when used in this document. The terminology capitalized when used in this document. The terminology summary
summary table in section 3.1 gives a quick overview of the table in Section 3.1 gives a quick overview of the relationships
relationships between the different IPFIX terms. The PSAMP between the different IPFIX terms. The PSAMP terminology defined
terminology defined here is fully consistent with all terms listed in here is fully consistent with all terms listed in [RFC5475] and
[PSAMP-TECH] and [PSAMP-FMWK] but only definitions that are relevant [RFC5474], but only definitions that are relevant to the PSAMP
to the PSAMP protocol appear here. Section 5.4 applies the PSAMP protocol appear here. Section 3.3 applies the PSAMP terminology to
terminology to the IPFIX protocol terminology. the IPFIX protocol terminology.
3.1 IPFIX Terminology 3.1. IPFIX Terminology
IPFIX-specific terminology used in this document is defined in IPFIX-specific terminology used in this document is defined in
section 2 of [IPFIX-PROTO]. The only exceptions are the Metering Section 2 of [RFC5101]. The only exceptions are the Metering
Process, Exporting Process, and the Collector terms, which are Process, Exporting Process, and the Collector terms, which are
defined more precisely in the PSAMP terminology section. As in defined more precisely in the PSAMP terminology section. In this
[IPFIX-PROTO], these IPFIX-specific terms have the first letter of a document, as in [RFC5101], the first letter of each IPFIX-specific
word capitalized when used in this document. term is capitalized.
+------------------+---------------------------------------------+ +------------------+---------------------------------------------+
| | contents | | | contents |
| +--------------------+------------------------+ | +--------------------+------------------------+
| Set | Template | record | | Set | Template | record |
+------------------+--------------------+------------------------+ +------------------+--------------------+------------------------+
| Data Set | / | Data Record(s) | | Data Set | / | Data Record(s) |
+------------------+--------------------+------------------------+ +------------------+--------------------+------------------------+
| Template Set | Template Record(s) | / | | Template Set | Template Record(s) | / |
+------------------+--------------------+------------------------+ +------------------+--------------------+------------------------+
skipping to change at page 5, line 17 skipping to change at page 5, line 17
| +--------------------+------------------------+ | +--------------------+------------------------+
| Set | Template | record | | Set | Template | record |
+------------------+--------------------+------------------------+ +------------------+--------------------+------------------------+
| Data Set | / | Data Record(s) | | Data Set | / | Data Record(s) |
+------------------+--------------------+------------------------+ +------------------+--------------------+------------------------+
| Template Set | Template Record(s) | / | | Template Set | Template Record(s) | / |
+------------------+--------------------+------------------------+ +------------------+--------------------+------------------------+
| Options Template | Options Template | / | | Options Template | Options Template | / |
| Set | Record(s) | | | Set | Record(s) | |
+------------------+--------------------+------------------------+ +------------------+--------------------+------------------------+
Figure A: Terminology Summary Table Figure A: Terminology Summary Table
3.2 PSAMP Terminology 3.2. PSAMP Terminology
The PSAMP terminology section has been copied over from [PSAMP-TECH]. The PSAMP terminology section has been copied from [RFC5475].
3.2.1 Packet Streams and Packet Content 3.2.1. Packet Streams and Packet Content
Observed Packet Stream * Observed Packet Stream
The Observed Packet Stream is the set of all packets observed at the The Observed Packet Stream is the set of all packets observed at
Observation Point. the Observation Point.
Packet Stream * Packet Stream
A Packet Stream denotes a subset of the Observed Packet Stream that A Packet Stream denotes a set of packets from the Observed Packet
flows past some specified point within the Selection Process. Stream that flows past some specified point within the Metering
An example of a Packet Stream is the output of the Selection Process. Process. An example of a Packet Stream is the output of the
Note that packets selected from a stream, e.g. by Sampling, do not Selection Process. Note that packets selected from a stream,
necessarily possess a property by which they can be distinguished e.g., by Sampling, do not necessarily possess a property by which
from packets that have not been selected. For this reason the term they can be distinguished from packets that have not been
"stream" is favored over "flow", which is defined as set of packets selected. For this reason, the term "stream" is favored over
with common properties [RFC3917]. "flow", which is defined as a set of packets with common
properties [RFC3917].
Packet Content * Packet Content
The Packet Content denotes the union of the packet header (which The Packet Content denotes the union of the packet header (which
includes link layer, network layer and other encapsulation headers) includes link layer, network layer, and other encapsulation
and the packet payload. Note that, depending on the Observation headers) and the packet payload. Note that, depending on the
Point, the link layer information might not be available. Observation Point, the link layer information might not be
available.
3.2.2 Selection Process 3.2.2. Selection Process
Selection Process * Selection Process
A Selection Process takes the Observed Packet Stream as its input and A Selection Process takes the Observed Packet Stream as its input
selects a subset of that stream as its output. and selects a subset of that stream as its output.
Selection State * Selection State
A Selection Process may maintain state information for use by the A Selection Process may maintain state information for use by the
Selection Process. At a given time, the Selection State may depend Selection Process. At a given time, the Selection State may
on packets observed at and before that time, and other variables. depend on packets observed at and before that time, and other
Examples include: variables. Examples include:
(i) sequence numbers of packets at the input of Selectors; (i) sequence numbers of packets at the input of Selectors;
(ii) a timestamp of observation of the packet at the (ii) a timestamp of observation of the packet at the Observation
Observation Point; Point;
(iii) iterators for pseudorandom number generators; (iii) iterators for pseudorandom number generators;
(iv) hash values calculated during selection; (iv) hash values calculated during selection;
(v) indicators of whether the packet was selected by a (v) indicators of whether the packet was selected by a given
given Selector. Selector.
Selection Processes may change portions of the Selection State as a Selection Processes may change portions of the Selection State as
result of processing a packet. Selection state for a packet is to a result of processing a packet. Selection state for a packet is
reflect the state after processing the packet. to reflect the state after processing the packet.
Selector * Selector
A Selector defines the action of a Selection Process on a single A Selector defines the action of a Selection Process on a single
packet of its input. If selected, the packet becomes an element of packet of its input. If selected, the packet becomes an element
the output Packet Stream. of the output Packet Stream.
The Selector can make use of the following information in determining The Selector can make use of the following information in
whether a packet is selected: determining whether a packet is selected:
(i) the Packet Content; (i) the Packet Content;
(ii) information derived from the packet's treatment at the (ii) information derived from the packet's treatment at the
Observation Point; Observation Point;
(iii) any selection state that may be maintained by the (iii) any selection state that may be maintained by the Selection
Selection Process. Process.
Composite Selector * Composite Selector
A Composite Selector is an ordered composition of Selectors, in which
the output Packet Stream issuing from one Selector forms the input
Packet Stream to the succeeding Selector.
Primitive Selector A Composite Selector is an ordered composition of Selectors, in
which the output Packet Stream issuing from one Selector forms the
input Packet Stream to the succeeding Selector.
* Primitive Selector
A Selector is primitive if it is not a Composite Selector. A Selector is primitive if it is not a Composite Selector.
Selector ID * Selector ID
The Selector ID is the unique ID identifying a Primitive Selector. The Selector ID is the unique ID identifying a Primitive Selector.
The ID is unique within the Observation Domain. The ID is unique within the Observation Domain.
Selection Sequence * Selection Sequence
From all the packets observed at an Observation Point, only a few From all the packets observed at an Observation Point, only a few
packets are selected by one or more Selectors. The Selection packets are selected by one or more Selectors. The Selection
Sequence is a unique value per Observation Domain describing the Sequence is a unique value per Observation Domain describing the
Observation Point and the Selector IDs through which the packets are Observation Point and the Selector IDs through which the packets
selected. are selected.
3.2.3 Reporting 3.2.3. Reporting
Packet Reports * Packet Reports
Packet Reports comprise a configurable subset of a packet's input to Packet Reports comprise a configurable subset of a packet's input
the Selection Process, including the Packet Content, information to the Selection Process, including the Packet Content,
relating to its treatment (for example, the output interface), and information relating to its treatment (for example, the output
its associated selection state (for example, a hash of the Packet interface), and its associated selection state (for example, a
Content). hash of the Packet Content).
Report Interpretation * Report Interpretation
Report Interpretation comprises subsidiary information, relating to Report Interpretation comprises subsidiary information, relating
one or more packets, that are used for interpretation of their Packet to one or more packets, that is used for interpretation of their
Reports. Examples include configuration parameters of the Selection Packet Reports. Examples include configuration parameters of the
Process. Selection Process.
Report Stream * Report Stream
The Report Stream is the output of a Metering Process, comprising two The Report Stream is the output of a Metering Process, comprising
distinguished types of information: Packet Reports, and Report two distinguished types of information: Packet Reports and Report
Interpretation. Interpretation.
3.2.4 Metering Process 3.2.4. Metering Process
Metering Process * Metering Process
A Metering Process selects packets from the Observed Packet Stream A Metering Process selects packets from the Observed Packet Stream
using a Selection Process, and produces as output a Report Stream using a Selection Process, and produces as output a Report Stream
concerning the selected packets. The PSAMP Metering Process can be concerning the selected packets.
viewed as analogous to the IPFIX metering process [IPFIX-PROTO],
which produces flow records as its output.
3.2.5 Exporting Process The PSAMP Metering Process can be viewed as analogous to the IPFIX
Metering Process [RFC5101], which produces Flow Records as its
output, with the difference that the PSAMP Metering Process always
contains a Selection Process. The relationship between PSAMP and
IPFIX is further described in [RFC5477] and [RFC5474].
Exporting Process 3.2.5. Exporting Process
An Exporting Process sends, in the form of Export Packets, the output * Exporting Process
of one or more Metering Processes to one or more Collectors.
Export Packet An Exporting Process sends, in the form of Export Packets, the
output of one or more Metering Processes to one or more
Collectors.
An Export Packet is a combination of Report Interpretation(s) and/or * Export Packet
one or more Packet Reports that are bundled by the Exporting Process
into a Export Packet for exporting to a Collector.
3.2.6 PSAMP Device An Export Packet is a combination of Report Interpretation(s)
and/or one or more Packet Reports that are bundled by the
Exporting Process into an Export Packet for exporting to a
Collector.
PSAMP Device 3.2.6. PSAMP Device
A PSAMP Device is a device hosting at least an Observation Point, a * PSAMP Device
Selection Process and an Exporting Process. Typically, corresponding
Observation Point(s), Selection Process(es) and Exporting Process(es)
are co-located at this device, for example at a router.
3.2.7 Collector A PSAMP Device is a device hosting at least an Observation Point,
a Selection Process, and an Exporting Process. Typically,
corresponding Observation Point(s), Selection Process(es), and
Exporting Process(es) are co-located at this device, for example,
at a router.
Collector 3.2.7. Collector
* Collector
A Collector receives a Report Stream exported by one or more A Collector receives a Report Stream exported by one or more
Exporting Processes. In some cases, the host of the Metering and/or Exporting Processes. In some cases, the host of the Metering
Exporting Processes may also serve as the Collector. and/or Exporting Processes may also serve as the Collector.
3.2.8 Selection Methods 3.2.8. Selection Methods
Filtering
A filter is a Selector that selects a packet deterministically based * Filtering
on the Packet Content, or its treatment, or functions of these
occurring in the Selection State. Examples include property match
Filtering, and Hash-based Selection.
Sampling A filter is a Selector that selects a packet deterministically
based on the Packet Content, or its treatment, or functions of
these occurring in the Selection State. Two examples are:
A Selector that is not a filter is called a Sampling operation. This (i) Property Match Filtering: A packet is selected if a
reflects the intuitive notion that if the selection of a packet specific field in the packet equals a predefined value.
cannot be determined from its content alone, there must be some type
of Sampling taking place.
Content-independent Sampling (ii) Hash-based Selection: A Hash Function is applied to the
Packet Content, and the packet is selected if the result
falls in a specified range.
A Sampling operation that does not use Packet Content (or quantities * Sampling
derived from it) as the basis for selection is called a Content-
independent Sampling operation. Examples include systematic A Selector that is not a filter is called a Sampling
Sampling, and uniform pseudorandom Sampling driven by a pseudorandom operation. This reflects the intuitive notion that if the
number whose generation is independent of Packet Content. Note that selection of a packet cannot be determined from its content
in Content-independent Sampling it is not necessary to access the alone, there must be some type of Sampling taking place.
* Content-Independent Sampling
A Sampling operation that does not use Packet Content (or
quantities derived from it) as the basis for selection is
called a Content-independent Sampling operation. Examples
include systematic Sampling, and uniform pseudorandom
Sampling driven by a pseudorandom number whose generation
is independent of Packet Content. Note that in Content-
independent Sampling, it is not necessary to access the
Packet Content in order to make the selection decision. Packet Content in order to make the selection decision.
Content-dependent Sampling * Content-Dependent Sampling
A Sampling operation where selection is dependent on Packet Content A Sampling operation where selection is dependent on Packet
is called a Content-dependent Sampling operation. Examples include Content is called a Content-dependent Sampling operation.
pseudorandom selection according to a probability that depends on the An example is pseudorandom selection according to a
contents of a packet field. Note that this is not a filter, because probability that depends on the contents of a packet field.
the selection is not deterministic. Note that this is not a filter, because the selection is
not deterministic.
Hash Domain * Hash Domain
A subset of the Packet Content and the packet treatment, viewed as an A Hash Domain is a subset of the Packet Content and the
N-bit string for some positive integer N. packet treatment, viewed as an N-bit string for some
positive integer N.
Hash Range * Hash Range
A set of M-bit strings for some positive integer M that define the A Hash Range is a set of M-bit strings for some positive
range of values the result of the hash operation can take. integer M that define the range of values the result of the
hash operation can take.
Hash Function * Hash Function
A deterministic map from the Hash Domain into the Hash Range. A Hash Function defines a deterministic map from the Hash
Domain into the Hash Range.
Hash Selection Range * Hash Selection Range
A subset of the Hash Range. The packet is selected if the action of
the Hash Function on the Hash Domain for the packet yields a result
in the Hash Selection Range.
Hash-based Selection A Hash Selection Range is a subset of the Hash Range. The
packet is selected if the action of the Hash Function on
the Hash Domain for the packet yields a result in the Hash
Selection Range.
Filtering specified by a Hash Domain, a Hash Function, a Hash Range * Hash-based Selection
and a Hash Selection Range.
Approximative Selection A Hash-based Selection is Filtering specified by a Hash
Domain, a Hash Function, a Hash Range, and a Hash Selection
Range.
Selectors in any of the above categories may be approximated by * Approximative Selection
operations in the same or another category for the purposes of
implementation. For example, uniform pseudorandom Sampling may be
approximated by Hash-based Selection, using a suitable Hash Function
and Hash Domain. In this case, the closeness of the approximation
depends on the choice of Hash Function and Hash Domain.
Population Selectors in any of the above categories may be
approximated by operations in the same or another category
for the purposes of implementation. For example, uniform
pseudorandom Sampling may be approximated by Hash-based
Selection, using a suitable Hash Function and Hash Domain.
In this case, the closeness of the approximation depends on
the choice of Hash Function and Hash Domain.
A Population is a Packet Stream, or a subset of a Packet Stream. A * Population
Population can be considered as a base set from which packets are
selected. An example is all packets in the Observed Packet Stream
that are observed within some specified time interval.
Population Size A Population is a Packet Stream, or a subset of a Packet
Stream. A Population can be considered as a base set from
which packets are selected. An example is all packets in
the Observed Packet Stream that are observed within some
specified time interval.
The Population Size is the number of all packets in the Population. * Population Size
Sample Size The Population Size is the number of all packets in the
Population.
The number of packets selected from the Population by a Selector. * Sample Size
Configured Selection Fraction The Sample Size is the number of packets selected from the
Population by a Selector.
The Configured Selection Fraction is the ratio of the number of * Configured Selection Fraction
packets selected by a Selector from an input Population, to the
Population Size, as based on the configured selection parameters.
Attained Selection Fraction The Configured Selection Fraction is the expected ratio of
the Sample Size to the Population Size, as based on the
configured selection parameters.
The Attained Selection Fraction is the actual ratio of the * Attained Selection Fraction
number of packets selected by a Selector from an input
Population, to the Population Size. For some Sampling methods the
Attained Selection Fraction can differ from the Configured Selection
Fraction due to, for example, the 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 Fraction usually
approaches the Configured Selection Fraction.
3.3 IPFIX and PSAMP Terminology Comparison The Attained Selection Fraction is the ratio of the actual
Sample Size to the Population Size. For some Sampling
methods, the Attained Selection Fraction can differ from
the Configured Selection Fraction due to, for example, the
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 Fraction
usually approaches the Configured Selection Fraction.
3.3. IPFIX and PSAMP Terminology Comparison
The PSAMP terminology has been specified with an IPFIX background, as The PSAMP terminology has been specified with an IPFIX background, as
PSAMP and IPFIX have similar terms. However, this section clarifies PSAMP and IPFIX have similar terms. However, this section clarifies
the terms between the IPFIX and PSAMP terminology. the terms between the IPFIX and PSAMP terminology.
3.3.1 IPFIX and PSAMP Processes 3.3.1. IPFIX and PSAMP Processes
The figure B indicates the sequence of the processes (Metering and Figure B indicates the sequence of the IPFIX processes (Metering and
Exporting) within the PSAMP Device. Exporting) within the PSAMP Device.
+------------------+ +------------------+
| Metering Process | | Metering Process |
| +-----------+ | +-----------+ | +-----------+ | +-----------+
Observed | | Selection | | | Exporting | Observed | | Selection | | | Exporting |
Packet--->| | Process |--------->| Process |--->Collector Packet--->| | Process |--------->| Process |--->Collector
Stream | +-----------+ | +-----------+ Stream | +-----------+ | +-----------+
+------------------+ +------------------+
Figure B: PSAMP Processes Figure B: PSAMP Processes
The Selection Process, which takes an Observed Packet Stream as its The Selection Process, which takes an Observed Packet Stream as its
input, is an integral part of the Metering Process. The Selection input, is an integral part of the Metering Process. The Selection
Process chooses which packets from its input packet stream will be Process chooses which packets from its input Packet Stream will be
reported on by the rest of the Metering Process. Note that a reported on by the rest of the Metering Process. Note that a
"Process" is not necessarily implemented as a separate CPU thread. "Process" is not necessarily implemented as a separate CPU thread.
3.3.2 Packet Report, Packet Interpretation, and Data Record 3.3.2. Packet Report, Packet Interpretation, and Data Record
The PSAMP terminology speaks of Packet Report and Packet The PSAMP terminology speaks of Packet Report and Packet
Interpretation, while the IPFIX terminology speaks of Data Record and Interpretation, while the IPFIX terminology speaks of Data Record and
(Option) Template Record. The PSAMP Packet Report, which comprises (Options) Template Record. The PSAMP Packet Report, which comprises
information about the observed packet, can be viewed as analogous to information about the observed packet, can be viewed as analogous to
the IPFIX Data Record defined by a Template Record. The PSAMP Packet the IPFIX Data Record defined by a Template Record. The PSAMP Report
Interpretation, which comprises subsidiary information used for the Interpretation, which comprises subsidiary information used for the
interpretation of the Packet Reports, can be viewed as analogous to interpretation of the Packet Reports, can be viewed as analogous to
the IPFIX Data Record defined by an Option Template Record. the IPFIX Data Record defined by an Options Template Record. This
Options Template Record contains subsidiary information, applicable
to the observed packet sent into the PSAMP Packet Report.
4. Differences between PSAMP and IPFIX 4. Differences between PSAMP and IPFIX
The output of the IPFIX working group relevant for this draft is The output of the IPFIX working group relevant for this document is
structured into three documents: structured into three documents:
- IP Flow information architecture [IPFIX-ARCH]
- IPFIX protocol specifications [IPFIX-PROTO]
- IP Flow information export information model [IPFIX-INFO]
In the following sections we investigate the differences between - IP Flow information architecture [RFC5470]
- IPFIX protocol specifications [RFC5101]
- IP Flow information export information model [RFC5102]
In the following sections, we investigate the differences between
IPFIX and PSAMP for each of those aspects. IPFIX and PSAMP for each of those aspects.
4.1 Architecture Point of View 4.1. Architecture Point of View
Traffic Flow measurement as described in the IPFIX requirements Traffic Flow measurement as described in the IPFIX requirements
[RFC3917] and the IPFIX architecture [IPFIX-ARCH] can be separated [RFC3917] and the IPFIX architecture [RFC5470] can be separated into
into two stages: packet processing and Flow processing. two stages: packet processing and Flow processing. Figure C
Figure C illustrates these stages. illustrates these stages.
In stage 1, all processing steps act on packets. Packets are In stage 1, all processing steps act on packets. Packets are
captured, time stamped, selected by one or more selection steps and captured, timestamped, selected by one or more selection steps, and
finally forwarded to packet classification that maps packets to finally forwarded to packet classification that maps packets to
Flows. The packets selection steps may include Filtering and Flows. The packets' selection steps may include Filtering and
Sampling functions. Sampling functions.
In stage 2, all processing steps act on Flows. After packets are In stage 2, all processing steps act on Flows. After packets are
classified (mapped to Flows), Flows are generated (or updated if they classified (mapped to Flows), Flows are generated (or updated if they
exist already). Flow generation and update steps may be performed exist already). Flow generation and update steps may be performed
repeatedly for aggregating Flows. Finally, Flows are exported. repeatedly for aggregating Flows. Finally, Flows are exported.
Packet Sampling as described in the PSAMP framework [PSAMP-FMWK] Packet Sampling as described in the PSAMP framework [RFC5474] covers
covers only stage 1 of the IPFIX architecture with the packet only stage 1 of the IPFIX architecture with the packet classification
classification replaced by packet record export. replaced by Packet Report export, while IPFIX covers stage 2 also, as
it generates Flow Records out of the selected packets.
IPFIX architecture PSAMP framework IPFIX architecture PSAMP framework
packet header packet header packet header packet header
capturing \ capturing capturing \ capturing
| | | | | |
timestamping | timestamping timestamping | timestamping
| | | | | |
v | v v | v
+------>+ | stage 1: +------>+ +------>+ | stage 1: +------>+
| | > packet | | | | > packet | |
| packet | processing | packet | packet | processing | packet
| selection | | selection | selection | | selection
| | | | | | | | | |
+-------+ | +-------+ +-------+ | +-------+
| | | | | |
v | v v | v
packet / packet record packet / Packet Report
classification \ export classification \ export
| | | |
v | v |
+------>+ | +------>+ |
| | | | | |
| Flow generation | | Flow generation |
| and update | stage 2: | and update | stage 2:
| | > Flow | | > Flow
| v | processing | v | processing
| Flow | | Flow |
| selection | | selection |
| | | | | |
+-------+ | +-------+ |
| | | |
v | v |
Flow Record / Flow Record /
export export
Figure C: Comparison of IPFIX architecture and PSAMP framework Figure C: Comparison of IPFIX Architecture and PSAMP Framework
4.2 Protocol Point of View 4.2. Protocol Point of View
Concerning the protocol, the major difference between IPFIX and PSAMP Concerning the protocol, the major difference between IPFIX and PSAMP
is that the IPFIX protocol exports Flow Records while the PSAMP is that the IPFIX protocol exports Flow Records while the PSAMP
protocol exports Packet Records. From a pure export point of view, protocol exports Packet Reports. From a pure export point of view,
IPFIX will not distinguish a Flow Record composed of several packets IPFIX will not distinguish a Flow Record composed of several packets
aggregated together, from a Flow Record composed of a single packet. aggregated together from a Flow Record composed of a single packet.
So the PSAMP export can be seen as special IPFIX Flow Record So the PSAMP export can be seen as a special IPFIX Flow Record
containing information about a single packet. containing information about a single packet.
All extensions of the IPFIX protocol that are required to satisfy the All extensions of the IPFIX protocol that are required to satisfy the
PSAMP requirements have already been incorporated in the IPFIX PSAMP requirements have already been incorporated in the IPFIX
protocol [IPFIX-PROTO], which was developed in parallel with the protocol [RFC5101], which was developed in parallel with the PSAMP
PSAMP protocol. An example is the need for a data type for protocol protocol. An example is the need for a data type for protocol fields
fields that have flexible length, such as an octet array. This was that have flexible length, such as an octet array. This was added to
added to the IPFIX protocol specification in order to meet the the IPFIX protocol specification in order to meet the requirement of
requirement of the PSAMP protocol to report content of captured the PSAMP protocol to report content of captured packets, for
packets, for example the first octets of a packet. example, the first octets of a packet.
4.3 Information Model Point of View 4.3. Information Model Point of View
From the information model point of view, the overlap between both From the information model point of view, the overlap between both
the IPFIX and PSAMP protocols is quite large. Most of the the IPFIX and PSAMP protocols is quite large. Most of the
Information Elements in the IPFIX protocol are also relevant for Information Elements in the IPFIX protocol are also relevant for
exporting packet information, for example all fields reporting packet exporting packet information, for example, all fields reporting
header properties. Only a few Information Elements, such as packet header properties. Only a few Information Elements, such as
observedFlowTotalCount (whose value will always be 1 for PSAMP) etc., observedFlowTotalCount (whose value will always be 1 for PSAMP),
cannot be used in a meaningful way by the PSAMP protocol. Also, etc., cannot be used in a meaningful way by the PSAMP protocol.
IPFIX protocol requirements concerning stage 2 of figure C do not Also, IPFIX protocol requirements concerning stage 2 of Figure C do
apply to the PSAMP metering process. not apply to the PSAMP Metering Process.
Further required extensions apply to the information model. Even if Further required extensions apply to the information model. Even if
the IPFIX charter speaks of Sampling, no Sampling related Information the IPFIX charter speaks of Sampling, no Sampling-related Information
Elements are specified in [IPFIX-INFO]. The task of specifying them Elements are specified in [RFC5102]. The task of specifying them was
was intentionally left for the PSAMP information model [PSAMP-INFO]. intentionally left for the PSAMP information model [RFC5477]. A set
A set of several additional fields is required for satisfying the of several additional fields is required for satisfying the
requirements for the PSAMP information model [PSAMP-TECH]. requirements for the PSAMP information model [RFC5475].
Exploiting the extensibility of the IPFIX information model, the Exploiting the extensibility of the IPFIX information model, the
required extension is covered by the PSAMP information model required extension is covered by the PSAMP information model
specified in [PSAMP-INFO]. specified in [RFC5477].
5. PSAMP Requirements versus the IPFIX Solution 5. PSAMP Requirements versus the IPFIX Solution
In the "Generic Requirements for PSAMP" section, [PSAMP-FMWK] The [RFC5474] contains PSAMP protocol requirements throughout the
describes some requirements that affect directly the PSAMP export document, with a special focus in Section 4, "Generic Requirements
protocol. for PSAMP", and its subsections.
In the "Generic Selection Process Requirements" section, [PSAMP-FMWK] Section 4 of [RFC5474] describes one requirement that, if not
describes one requirement that, if not directly related to the export directly related to the export protocol, will put some constraints on
protocol, will put some constraints on it. Parallel Measurements: it. Parallel Measurements: multiple independent Selection Processes
multiple independent selection processes at the same entity. at the same entity.
Finally, [PSAMP-FMWK] describes a series of requirements specifying [RFC5474] also describes a series of requirements specifying the
the different Information Elements that MUST and SHOULD be reported different Information Elements that MUST and SHOULD be reported to
to the Collector. Nevertheless IPFIX, being a generic export the Collector. Nevertheless, IPFIX, being a generic export protocol,
protocol, can export any Information Elements as long as they are can export any Information Elements as long as they are described in
described in the information model. So these requirements are mainly the information model. So these requirements are mainly targeted for
targeted for the [PSAMP-INFO] document. [RFC5477].
The PSAMP protocol specifications meets almost all the protocol The PSAMP protocol specification meets almost all the protocol
requirements stated in the PSAMP framework document [PSAMP-FMWK]: requirements stated in the PSAMP framework document [RFC5474]:
* Extensibility * Extensibility
* Parallel selection processes * Parallel selection processes
* Encrypted packets * Encrypted packets
* Indication of information loss * Indication of information loss
* Accuracy * Accuracy
* Privacy * Privacy
* Timeliness * Timeliness
* Congestion avoidance * Congestion avoidance
* Secure export * Secure export
* Export rate limit * Export rate limit
* Microsecond timestamp resolution * Microsecond timestamp resolution
The only requirement that is not met is Export Packet compression. The only requirement that is not met is Export Packet compression.
With the choice of IPFIX as PSAMP export protocol, the export packet With the choice of IPFIX as the PSAMP export protocol, the Export
compression option mentioned in the section 8.5 of the framework Packet compression option mentioned in the Section 8.5 of the
document [PSAMP-FMWK] is not addressed. framework document [RFC5474] is not addressed.
5.1 High Level View of the Integration 5.1. High-Level View of the Integration
The Template Record in the Template Set is used to describe the The Template Record in the Template Set is used to describe the
different PSAMP Information Elements that will be exported to the different PSAMP Information Elements that will be exported to the
Collector. The Collector decodes the Template Record in the Template Collector. The Collector decodes the Template Record in the Template
Set and knows which Information Elements to expect when it receives Set and knows which Information Elements to expect when it receives
the Data Records in the PSAMP Packet Report Data Set. Typically, in the Data Records in the PSAMP Packet Report Data Set. Typically, in
the base level of the PSAMP functionality, the Template Set will the base level of the PSAMP functionality, the Template Set will
contain the input sequence number, the packet fragment (some number contain the input sequence number, the packet fragment (some number
of contiguous bytes from the start of the packet or from the start of of contiguous bytes from the start of the packet or from the start of
the payload) and the Selection Sequence. the payload), and the Selection Sequence.
The Options Template Record in the Options Template Set is used to The Options Template Record in the Options Template Set is used to
describe the different PSAMP Information Elements that concern the describe the different PSAMP Information Elements that concern the
Metering Process itself: Sampling and/or Filtering functions, and the Metering Process itself: Sampling and/or Filtering functions, and the
associated parameters. The Collector decodes the Options Template associated parameters. The Collector decodes the Options Template
Records in the Option Template Set and knows which Information Records in the Options Template Set and knows which Information
Elements to expect when it receives the Data Records in the PSAMP Elements to expect when it receives the Data Records in the PSAMP
Report Interpretation Data Set. Typically, the Options Template Report Interpretation Data Set. Typically, the Options Template
would contain the Selection Sequence, the Sampling or Filtering would contain the Selection Sequence, the Sampling or Filtering
functions, and the Sampling or Filtering associated parameters. functions, and the Sampling or Filtering associated parameters.
PSAMP requires all the different possibilities of the IPFIX protocol PSAMP requires all the different possibilities of the IPFIX protocol
specifications [IPFIX-PROTO]. That is the 3 types of Set (Data Set, specifications [RFC5101], that is, the three types of Sets (Data Set,
Template Set and Options Templates Set) with the 2 types of Templates Template Set, and Options Templates Set) with the two types of
Records (Template Record and Options Template Record), as described Template Records (Template Record and Options Template Record), as
in the figure A. As a consequence, PSAMP can't rely on a subset of described in Figure A. As a consequence, PSAMP can't rely on a
the IPFIX protocol specifications described in [IPFIX-PROTO]. The subset of the IPFIX protocol specifications described in [RFC5101].
entire IPFIX protocol specifications [IPFIX-PROTO] MUST be The entire IPFIX protocol specifications [RFC5101] MUST be
implemented for the PSAMP protocol. implemented for the PSAMP protocol.
6. Using the IPFIX Protocol for PSAMP 6. Using the IPFIX Protocol for PSAMP
In this section, we describe the usage of the IPFIX protocol for In this section, we describe the usage of the IPFIX protocol for
PSAMP. We describe the record formats and the additional PSAMP. We describe the record formats and the additional
requirements that must be met. PSAMP uses two different types of requirements that must be met. PSAMP uses two different types of
messages: messages:
- Packet Reports - Packet Reports
- Report Interpretation - Report Interpretation
The format of Packet Reports is defined in IPFIX Template Records. The format of Packet Reports is defined in IPFIX Template Records.
The PSAMP data is transferred as Information Elements in IPFIX Data The PSAMP data is transferred as Information Elements in IPFIX Data
Records as described by the Template Record. There are two different Records as described by the Template Record. There are two different
types of Packet Reports. Basic Packet Reports contain only the basic types of Packet Reports. Basic Packet Reports contain only the basic
Information Elements required for PSAMP reporting. Extended Packet Information Elements required for PSAMP reporting. Extended Packet
Reports MAY contain further Information Elements. Reports MAY contain other Information Elements, and do not
The format of Report Interpretations is defined in IPFIX Option necessarily include Packet Content (See section 6.4.2).
The format of Report Interpretations is defined in the IPFIX Options
Template Record. The Information Elements are transferred in IPFIX Template Record. The Information Elements are transferred in IPFIX
Data Records as described by the Option Template Record. There are Data Records as described by the Options Template Record. There are
four different types of Report Interpretation messages: four different types of Report Interpretation messages:
- Selection Sequence Report Interpretation - Selection Sequence Report Interpretation
- Selector Report Interpretation - Selector Report Interpretation
- Selection Sequence Statistics Report Interpretation - Selection Sequence Statistics Report Interpretation
- Accuracy Report Interpretation - Accuracy Report Interpretation
A description and examples about the usage of those reports is given
A description and examples about the usage of those reports are given
below. below.
6.1 Selector ID 6.1. Selector ID
The Selector ID is the unique ID identifying a Primitive Selector. The Selector ID is the unique ID identifying a Primitive Selector.
Each Primitive Selector MUST have a unique ID within the Observation Each Primitive Selector MUST have a unique ID within the Observation
Domain. The Selector ID is represented by the selectorId Information Domain. The Selector ID is represented by the selectorId Information
Element [PSAMP-INFO]. Element [RFC5477].
6.2 The Selection Sequence ID 6.2. The Selection Sequence ID
From all the packets observed at an Observation Point, a subset of From all the packets observed at an Observation Point, a subset of
packets is selected by one or more Selectors. The Selection Sequence packets is selected by one or more Selectors. The Selection Sequence
is the combination of an Observation Point and one or more is the combination of an Observation Point and one or more
Selector(s) through which the packets are selected. The Selection Selector(s) through which the packets are selected. The Selection
Sequence ID is a unique value representing that combination. The Sequence ID is a unique value representing that combination. The
Selection Sequence ID is represented by the selectionSequenceId Selection Sequence ID is represented by the selectionSequenceId
Information Element [PSAMP-INFO]. Information Element [RFC5477].
6.3 The Exporting Process 6.3. The Exporting Process
An Exporting Process MUST be able to limit the export rate according An Exporting Process MUST be able to limit the export rate according
to a configurable value. The Exporting Process MAY limit the export to a configurable value. The Exporting Process MAY limit the export
rate on a per Collecting Process basis. rate on a per Collecting Process basis.
6.4 Packet Report 6.4. Packet Report
For each Selection Sequence, for each selected packet, a Packet For each Selection Sequence, for each selected packet, a Packet
Report MUST be created. The format of the Packet Report is specified Report MUST be created. The format of the Packet Report is specified
in a Template Record contained in a Template Set. in a Template Record contained in a Template Set.
There are two types of Packet Report, as described in [PSAMP-FMWK]: There are two types of Packet Report, as described in [RFC5474]: the
the basic Packet Report and the extended Packet Report. basic Packet Report and the extended Packet Report.
6.4.1 Basic Packet Report 6.4.1. Basic Packet Report
For each selected packet, the Packet Report MUST contain the For each selected packet, the Packet Report MUST contain the
following information: following information:
- The selectionSequenceId Information Element - The selectionSequenceId Information Element
If there is a digest function in the selection sequence, the Packet If there is a digest function in the Selection Sequence, the Packet
report MUST contain the hash value (digestHashValue Information Report MUST contain the hash value (digestHashValue Information
Element) generated by the digest hash function for each selected Element) generated by the digest Hash Function for each selected
packet. If there is more than one digest function then each hash packet. If there is more than one digest function, then each hash
value MUST be included in the same order as they appear in the value MUST be included in the same order as they appear in the
selection sequence. If there are no digest functions in the Selection Sequence. If there are no digest functions in the
selection sequence no element for the digest needs to be sent. Selection Sequence, no element for the digest needs to be sent.
- Some number of contiguous bytes from the start of the packet, - Some number of contiguous bytes from the start of the packet,
including the packet header (which includes link layer, network layer including the packet header (which includes link layer, network
and other encapsulation headers) and some subsequent bytes of the layer, and other encapsulation headers) and some subsequent bytes
packet payload. Alternatively, the number of contiguous bytes may of the packet payload. Alternatively, the number of contiguous
start at the beginning of the payload. The dataLinkFrameSection, bytes may start at the beginning of the payload. The
mplsLabelStackSection, mplsPayloadPacketSection, ipPacketSection, and dataLinkFrameSection, mplsLabelStackSection,
mplsPayloadPacketSection, ipPacketSection, and
ipPayloadPacketSection PSAMP Information Elements are available for ipPayloadPacketSection PSAMP Information Elements are available for
this use. If one of those Information Elements that contain some this use.
number of contiguous bytes has got a content with an insufficient
number of octets compared to its length specified in the Template,
then this Information Element MUST be sent with a new Template using
either a fixed length Information Element of the necessary size or a
variable length Information Element.
For each selected packet, the Packet Report SHOULD contain the For each selected packet, the Packet Report SHOULD contain a time-
following information: related Information Element that matches the Metering Process time
- the observationTimeMicroseconds Information Element accuracy. Typically, the observationTimeMicroseconds Information
In the Packet Report, the PSAMP device MUST be capable of exporting Element. Other possible Information Elements are the
observationTimeSeconds, the observationTimeMilliseconds, or the
observationTimeNanoseconds.
In the Packet Report, the PSAMP Device MUST be capable of exporting
the number of observed packets and the number of packets selected by the number of observed packets and the number of packets selected by
each instance of its Primitive Selectors (as described by the non each instance of its Primitive Selectors (as described by the
scope Information Elements of the Selection Sequence Statistics non-scope Information Elements of the Selection Sequence Statistics
Report Interpretation) although it MAY be a configurable option not Report Interpretation), although it MAY be a configurable option not
to include them. If exported, the Attained Selection Fraction may to include them. If exported, the Attained Selection Fraction may be
be calculated precisely for the Observed Packet Stream. The Packet calculated precisely for the Observed Packet Stream. The Packet
Report MAY include only the final selector packetSelected, to act as Report MAY include only the final selector packetSelected, to act as
an index for that selection sequence in the Selection Sequence an index for that Selection Sequence in the Selection Sequence
Statistics Report Interpretation, which also allows the calculation Statistics Report Interpretation, which also allows the calculation
of the Attained Selection Fraction. of the Attained Selection Fraction.
The contiguous Information Elements (dataLinkFrameSection, The contiguous Information Elements (dataLinkFrameSection,
mplsLabelStackSection, mplsPayloadPacketSection, ipPacketSection, mplsLabelStackSection, mplsPayloadPacketSection, ipPacketSection, and
and ipPayloadPacketSection) MAY be encoded with a fixed length field ipPayloadPacketSection) MAY be encoded with a fixed-length field or
or with a variable sized field. If one of these Information with a variable-sized field. If one of these Information Elements is
Elements is encoded with a fixed length field whose length is too encoded with a fixed-length field whose length is too long for the
long for the number of contiguous bytes in the selected packet, number of contiguous bytes in the selected packet, padding MUST NOT
padding MUST NOT be used. In this case, the Exporting Process MUST be used. In this case, the Exporting Process MUST export the
export the information either in a new Template Record with the information either in a new Template Record with the correct fixed-
correct fixed length field, or either in a new Template Record with length field or in a new Template Record with a variable-length
a variable length field. field.
Here is an example of a basic Packet Report, with a Here is an example of a basic Packet Report, with a
SelectionSequenceId value of 9 and dataLinkFrameSection SelectionSequenceId value of 9 and dataLinkFrameSection Information
Information Element of 12 bytes, 0x4500 005B A174 0000 FF11 832E, Element of 12 bytes, 0x4500 005B A174 0000 FF11 832E, encoded with a
encoded with a fixed length field. fixed-length field.
IPFIX Template Record: IPFIX Template Record:
0 1 2 3 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 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 | | Set ID = 2 | Length = 24 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 260 | Field Count = 4 | | Template ID = 260 | Field Count = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 19, line 8 skipping to change at page 19, line 33
| dataLinkFrameSection = 315 | Field Length = 12 | | dataLinkFrameSection = 315 | Field Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|observationTimeMicroseconds=324| Field Length = 4 | |observationTimeMicroseconds=324| Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The associated IPFIX Data Record: The associated IPFIX Data Record:
0 1 2 3 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 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 | | Set ID = 260 | Length = 32 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 9 | | 9 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0x9123 0613 | | 0x9123 0613 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0x4500 005B | | 0x4500 005B |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0xA174 0000 | | 0xA174 0000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0xFF11 832E | | 0xFF11 832E |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| observation time encoded as dateTimeSeconds [IPFIX-PROTO] | | observation time ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... encoded as dateTimeMicroSeconds [RFC5101] |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure D: Example of a Basic Packet Report Figure D: Example of a Basic Packet Report
Here is an example of a basic Packet Report, with a Here is an example of a basic Packet Report, with a
SelectionSequenceId value of 9 and ipHeaderPacketSection Information SelectionSequenceId value of 9 and ipHeaderPacketSection Information
Element of 12 bytes, 0x4500 005B A174 0000 FF11 832E, encoded with a Element of 12 bytes, 0x4500 005B A174 0000 FF11 832E, encoded with a
variable sized field. variable-sized field.
IPFIX Template Record: IPFIX Template Record:
0 1 2 3 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 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 = 16 | | Set ID = 2 | Length = 16 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 261 | Field Count = 2 | | Template ID = 261 | Field Count = 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 20, line 13 skipping to change at page 20, line 41
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length = 12 | 0x4500 ... | | Length = 12 | 0x4500 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... 005B | 0xA174 ... | | ... 005B | 0xA174 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... 0000 | 0xFF11 ... | | ... 0000 | 0xFF11 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... 832E | | ... 832E |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
Figure E: Example of a Basic Packet Report, Figure E: Example of a Basic Packet Report
with a variable sized field with a Variable-Sized Field
6.4.2 Extended Packet Report 6.4.2. Extended Packet Report
Alternatively to the basic Packet Report, the extended Packet Report Alternatively to the basic Packet Report, the extended Packet Report
MAY contain other Information Elements related to the protocols used MAY contain other Information Elements related to the protocols used
in the packet (such as source and destination IP addresses), related in the packet (such as source and destination IP addresses), related
to the packet treatment (such as output interface, destination BGP to the packet treatment (such as output interface, destination BGP
autonomous system [RFC4271]), or related to the Selection State autonomous system [RFC4271]), or related to the Selection State
associated with the packet (such as timestamp, hash value). associated with the packet (such as timestamp, hash value).
It is envisaged that selection of fields for extended Packet Reports It is envisaged that selection of fields for extended Packet Reports
may be used to reduce reporting bandwidth, in which case the option may be used to reduce reporting bandwidth, in which case the option
skipping to change at page 20, line 47 skipping to change at page 21, line 36
0 1 2 3 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 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 = 32 | | Set ID = 2 | Length = 32 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 261 | Field Count = 6 | | Template ID = 261 | Field Count = 6 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| selectionSequenceId = 301 | Field Length = 4 | |0| selectionSequenceId = 301 | Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| sourceIPv4Address = 44 | Field Length = 4 | |0| sourceIPv4Address = 8 | Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| destinationIPv4Address = 45 | Field Length = 4 | |0| destinationIPv4Address = 12 | Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| totalLengthIPv4 = 190 | Field Length = 2 | |0| totalLengthIPv4 = 190 | Field Length = 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| tcpSourcePort = 182 | Field Length = 2 | |0| tcpSourcePort = 182 | Field Length = 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| tcpDestinationPort = 183 | Field Length = 2 | |0| tcpDestinationPort = 183 | Field Length = 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The associated IPFIX Data Record: The associated IPFIX Data Record:
0 1 2 3 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 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 | | Set ID = 261 | Length = 20 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 9 | | 9 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 192.0.2.1 | | 192.0.2.1 |
skipping to change at page 21, line 31 skipping to change at page 22, line 24
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 192.0.2.106 | | 192.0.2.106 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 72 | 1372 | | 72 | 1372 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 80 | | 80 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure F: Example of an Extended Packet Report Figure F: Example of an Extended Packet Report
6.5 Report Interpretation 6.5. Report Interpretation
To make full sense of the Packet Reports there are a number of To make full sense of the Packet Reports, there are a number of
additional pieces of information that must be communicated to the additional pieces of information that must be communicated to the
Collector: Collector:
- The details about which Selectors and Observation Points are being - The details about which Selectors and Observation Points are being
used within a Selection Sequences MUST be provided using the used within a Selection Sequence MUST be provided using the
Selection Sequence Report Interpretation. Selection Sequence Report Interpretation.
- The configuration details of each Selector MUST be provided using - The configuration details of each Selector MUST be provided using
the Selector Report Interpretation. the Selector Report Interpretation.
- The Selector ID statistics MUST be provided using the Selection - The Selector ID statistics MUST be provided using the Selection
Sequence Statistics Report Interpretation. Sequence Statistics Report Interpretation.
- The accuracies of the reported fields MUST be provided using the - The accuracies of the reported fields MUST be provided using the
Accuracy Report Interpretation. Accuracy Report Interpretation.
6.5.1 Selection Sequence Report Interpretation 6.5.1. Selection Sequence Report Interpretation
Each Packet Report contains a selectionSequenceId Information Element Each Packet Report contains a selectionSequenceId Information Element
that identifies the particular combination of Observation Point and that identifies the particular combination of Observation Point and
Selector(s) used for its selection. For every selectionSequenceId Selector(s) used for its selection. For every selectionSequenceId
Information Element in use, the PSAMP Device MUST export a Selection Information Element in use, the PSAMP Device MUST export a Selection
Sequence Report Interpretation using an Options Template with the Sequence Report Interpretation using an Options Template with the
following Information Elements: following Information Elements:
Scope: selectionSequenceId Scope: selectionSequenceId
Non-Scope: one Information Element representing Non-Scope: one Information Element mapping the Observation Point
the Observation Point
selectorId (one or more) selectorId (one or more)
An Information Element representing the Observation Point would An Information Element representing the Observation Point would
typically be taken from the ingressInterface, egressInterface, typically be taken from the ingressInterface, egressInterface,
lineCardId, exporterIPv4Address, exporterIPv6Address Information lineCardId, exporterIPv4Address, or exporterIPv6Address Information
Elements (specified in [IPFIX-INFO]), but not limited to those: any Elements (specified in [RFC5102]), but is not limited to those: any
Information Element specified in [IPFIX-INFO] or [PSAMP-INFO] can Information Element specified in [RFC5102] or [RFC5477] can
potentially be used. In case of more complex Observation Points potentially be used. In case of more complex Observation Points
(such as a list of interfaces, a bus, etc..), a new Information (such as a list of interfaces, a bus, etc.), a new Information
Element describing the new type of Observation Point must be Element describing the new type of Observation Point must be
specified, along with an option template record describing it in more specified, along with an Options Template Record describing it in
details (if necessary). more detail (if necessary).
If the packets are selected by a Composite Selector, the Selection If the packets are selected by a Composite Selector, the Selection
Sequence is composed of several Primitive Selectors. In such a case, Sequence is composed of several Primitive Selectors. In such a case,
the Selection Sequence Report Interpretation MUST contain the list of the Selection Sequence Report Interpretation MUST contain the list of
all the Primitive Selector IDs in the Selection Sequence. If all the Primitive Selector IDs in the Selection Sequence. If
multiple Selectors are contained in the Selection Sequence Report multiple Selectors are contained in the Selection Sequence Report
Interpretation, the selectorId's MUST be identified in the order they Interpretation, the selectorId's MUST be identified in the order they
are used. are used.
Example of two Selection Sequences: Example of two Selection Sequences:
skipping to change at page 23, line 9 skipping to change at page 24, line 17
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 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 | | Set ID = 3 | Length = 26 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 262 | Field Count = 4 | | Template ID = 262 | Field Count = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope Field Count = 1 |0| selectionSequenceId = 301 | | Scope Field Count = 1 |0| selectionSequenceId = 301 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope 1 Length = 4 |0| ingressInterface = 10 | | Scope 1 Length = 4 |0| ingressInterface = 10 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |0| selectorId = 300 | | Field Length = 4 |0| selectorId = 302 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |0| selectorId = 300 | | Field Length = 4 |0| selectorId = 302 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 | | Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The associated IPFIX Data Record: The associated IPFIX Data Record:
0 1 2 3 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 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 | Length = 36 | | Set ID = 262 | Length = 36 |
skipping to change at page 23, line 41 skipping to change at page 25, line 4
| 9 | | 9 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 5 | | 5 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 10 | | 10 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 5 | | 5 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure G: Example of a Selection Sequence Report Interpretation Figure G: Example of a Selection Sequence Report Interpretation
Notes: Notes:
* There are two Records here in the same Data Set. Each record * There are two Records here in the same Data Set. Each record
defines a different Selection Sequence. defines a different Selection Sequence.
* If, for example, a different Selection Sequence is composed of * If, for example, a different Selection Sequence is composed of
three Selectors then a different Options Template with three three Selectors, then a different Options Template with three
selectorId Information Elements (instead of two) must be used. selectorId Information Elements (instead of two) must be used.
6.5.2 Selector Report Interpretation 6.5.2. Selector Report Interpretation
An IPFIX Data Record, defined by an Option Template Record, MUST be An IPFIX Data Record, defined by an Options Template Record, MUST be
used to send the configuration details of every Selector in use. The used to send the configuration details of every Selector in use. The
Option Template Record MUST contain the selectorId Information Options Template Record MUST contain the selectorId Information
Element as the Scope field and the SelectorAlgorithm Information Element as the Scope field and the SelectorAlgorithm Information
Element followed by some specific configuration parameters: Element followed by some specific configuration parameters:
Scope: selectorId Scope: selectorId
Non-scope: selectorAlgorithm Non-scope: selectorAlgorithm
algorithm specific Information Elements algorithm-specific Information Elements
The algorithm specific Information Elements are specified in the The algorithm-specific Information Elements are specified in the
following subsections, depending on the selection method represented following subsections, depending on the selection method represented
by the value of the selectorAlgorithm [PSAMP-INFO]. by the value of the selectorAlgorithm [RFC5477].
6.5.2.1 Systematic Count-Based Sampling 6.5.2.1. Systematic Count-Based Sampling
In systematic count-based Sampling, the start and stop triggers for In systematic count-based Sampling, the start and stop triggers for
the Sampling interval are defined in accordance with the spatial the Sampling interval are defined in accordance with the spatial
packet position (packet count) [PSAMP-TECH]. packet position (packet count) [RFC5475].
The REQUIRED algorithm specific Information Elements in the case of The REQUIRED algorithm-specific Information Elements in the case of
systematic count-based Sampling are: systematic count-based Sampling are:
samplingPacketInterval: number of packets selected in a row samplingPacketInterval: number of packets selected in a row
samplingPacketSpace: number of packets between selections samplingPacketSpace: number of packets between selections
Example of a simple 1 out-of 10 systematic count-based Selector Example of a simple 1 out-of 10 systematic count-based Selector
definition, where the samplingPacketInterval is 1 and the definition, where the samplingPacketInterval is 1 and the
samplingPacketSpace is 9. samplingPacketSpace is 9.
IPFIX Options Template Record: IPFIX Options Template Record:
skipping to change at page 25, line 19 skipping to change at page 26, line 37
0 1 2 3 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 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 | Length = 11 | | Set ID = 263 | Length = 11 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 15 | | 15 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 1 | 1 | 9 | | 1 | 1 | 9 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure H: Example of the Selector Report Interpretation, Figure H: Example of the Selector Report Interpretation
For Systematic Count-Based Sampling for Systematic Count-Based Sampling
Notes: Notes:
* A selectorAlgorithm value of 1 represents systematic count-based * A selectorAlgorithm value of 1 represents systematic count-based
Sampling. Sampling.
* samplingPacketInterval and samplingPacketSpace are of type * samplingPacketInterval and samplingPacketSpace are of type
unsigned32 but are compressed down to one octet here, as allowed by unsigned32 but are compressed down to one octet here, as allowed by
the IPFIX protocol specifications [IPFIX-PROTO]. the IPFIX protocol specifications [RFC5101].
6.5.2.2 Systematic Time-Based Sampling 6.5.2.2. Systematic Time-Based Sampling
In systematic time-based Sampling, the start and stop triggers are In systematic time-based Sampling, the start and stop triggers are
used to define the Sampling intervals [PSAMP-TECH]. The REQUIRED used to define the Sampling intervals [RFC5475]. The REQUIRED
algorithm specific Information Elements in the case of systematic algorithm-specific Information Elements in the case of systematic
time-based Sampling are: time-based Sampling are:
samplingTimeInterval: time (in us) when packets are selected samplingTimeInterval: time (in microseconds) when packets are
samplingTimeSpace: time (in us) between selections selected
samplingTimeSpace: time (in microseconds) between selections
Example of a 100 us out-of 1000 us systematic time-based Selector Example of a 100 microsecond out-of 1000 microsecond systematic
definition, where the samplingTimeInterval is 100 and the time-based Selector definition, where the samplingTimeInterval is 100
samplingTimeSpace is 900 and the samplingTimeSpace is 900.
IPFIX Options Template Record: IPFIX Options Template Record:
0 1 2 3 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 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 | | Set ID = 3 | Length = 26 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 264 | Field Count = 4 | | Template ID = 264 | Field Count = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 26, line 28 skipping to change at page 27, line 52
0 1 2 3 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 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 | Length = 12 | | Set ID = 264 | Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 16 | | 16 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 2 | 100 | 900 | | 2 | 100 | 900 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure I: Example of the Selector Report Interpretation, Figure I: Example of the Selector Report Interpretation
For Systematic Time-Based Sampling for Systematic Time-Based Sampling
Notes: Notes:
* A selectorAlgorithm value of 2 represents systematic time-based * A selectorAlgorithm value of 2 represents systematic time-based
Sampling. Sampling.
* samplingTimeInterval and samplingTimeSpace are of type unsigned32 * samplingTimeInterval and samplingTimeSpace are of type unsigned32
but are compressed down here. but are compressed down here.
6.5.2.3 Random n-out-of-N Sampling 6.5.2.3. Random n-out-of-N Sampling
In random n-out-of-N Sampling, n elements are selected out of the In random n-out-of-N Sampling, n elements are selected out of the
parent population that consists of N elements [PSAMP-TECH]. The parent Population that consists of N elements [RFC5475]. The
REQUIRED algorithm specific Information Elements in case of random n- REQUIRED algorithm-specific Information Elements in case of random
out-of-N Sampling are: n-out-of-N Sampling are:
samplingSize: number of packets selected samplingSize: number of packets selected
samplingPopulation: number of packets in selection population samplingPopulation: number of packets in selection Population
Example of a 1 out-of 10 random n-out-of-N Sampling Selector: Example of a 1 out-of 10 random n-out-of-N Sampling Selector:
IPFIX Options Template Record: IPFIX Options Template Record:
0 1 2 3 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 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 | | Set ID = 3 | Length = 26 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 27, line 35 skipping to change at page 29, line 16
0 1 2 3 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 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 | Length = 11 | | Set ID = 265 | Length = 11 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 17 | | 17 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 3 | 1 | 10 | | 3 | 1 | 10 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure J: Example of the Selector Report Interpretation, Figure J: Example of the Selector Report Interpretation
For Random n-out-of-N Sampling for Random n-out-of-N Sampling
Notes: Notes:
* A selectorAlgorithm value of 3 represents Random n-out-of-N * A selectorAlgorithm value of 3 represents Random n-out-of-N
Sampling. Sampling.
* samplingSize and samplingPopulation are of type unsigned32 but are * samplingSize and samplingPopulation are of type unsigned32 but are
compressed down to one octet here. compressed down to one octet here.
6.5.2.4 Uniform Probabilistic Sampling 6.5.2.4. Uniform Probabilistic Sampling
In uniform probabilistic Sampling, each element has the same In uniform probabilistic Sampling, each element has the same
probability p of being selected from the parent population [PSAMP- probability p of being selected from the parent Population [RFC5475].
TECH]. The algorithm specific Information Element in case of uniform The algorithm-specific Information Element in case of uniform
probabilistic Sampling is: probabilistic Sampling is:
samplingProbablility: a floating point number for the Sampling samplingProbability: a floating point number for the Sampling
probability. probability.
Example of a 15% uniform probability Sampling Selector: Example of a 15% uniform probability Sampling Selector:
IPFIX Options Template Record: IPFIX Options Template Record:
0 1 2 3 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 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 | | Set ID = 3 | Length = 22 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 271 | Field Count = 3 | | Template ID = 271 | Field Count = 3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope Field Count = 1 |0| selectorId = 302 | | Scope Field Count = 1 |0| selectorId = 302 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |0| selectorAlgorithm = 304 | | Field Length = 4 |0| selectorAlgorithm = 304 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 1 |0| samplingProbabilility = 311 | | Field Length = 1 |0| samplingProbability = 311 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 | | Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Associated IPFIX Data Record: Associated IPFIX Data Record:
0 1 2 3 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 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 | Length = 11 | | Set ID = 271 | Length = 11 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 20 | | 20 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 4 | 0.15 | | 4 | 0.15 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
Figure K: Example of the Selector Report Interpretation, Figure K: Example of the Selector Report Interpretation
For Uniform Probabilistic Sampling for Uniform Probabilistic Sampling
Notes: Notes:
* A selectorAlgorithm value of 4 represents Uniform Probabilistic * A selectorAlgorithm value of 4 represents Uniform Probabilistic
Sampling. Sampling.
* samplingProbablility is of type float64 but is compressed down to a
* samplingProbability is of type float64 but is compressed down to a
float32 here. float32 here.
6.5.2.5 Property Match Filtering 6.5.2.5. Property Match Filtering
This classification includes match(es) on field(s) within a packet This classification includes match(es) on field(s) within a packet
and/or on properties of the router state. With this method, a packet and/or on properties of the router state. With this method, a packet
is selected if a specific field in the packet equals a predefined is selected if a specific field in the packet equals a predefined
value. value.
The algorithm specific Information Elements defining configuration The algorithm-specific Information Elements defining configuration
parameters for property match filtering are taken from the full range parameters for Property Match Filtering are taken from the full range
of available Information Elements. of available Information Elements.
When multiple different Information Elements are defined, the filter When multiple different Information Elements are defined, the filter
acts as a logical AND. Note that the logical OR is not covered by acts as a logical AND. Note that the logical OR is not covered by
these PSAMP specifications. The property match Filtering Options these PSAMP specifications. The Property Match Filtering Options
Template Record MUST NOT have multiple identical Information Template Record MUST NOT have multiple identical Information
Elements. The result of the filter is independent from the order of Elements. The result of the filter is independent from the order of
the Information Elements in the Option Template Record, but the order the Information Elements in the Options Template Record, but the
may be important for implementation purposes, as the first filter order may be important for implementation purposes, as the first
will have to work at a higher rate. In any case, an implementation filter will have to work at a higher rate. In any case, an
is not constrained to respect the filter ordering as long as the implementation is not constrained to respect the filter ordering as
result is the same, and it may even implement the composite Filtering long as the result is the same, and it may even implement the
in Filtering in one single step. composite Filtering in one single step.
Since encryption alters the meaning of encrypted fields, when the Since encryption alters the meaning of encrypted fields, when the
Property Match Filtering classification is based on the encrypted Property Match Filtering classification is based on the encrypted
field(s) in the packet, it MUST be able to recognize that the field(s) in the packet, it MUST be able to recognize that the
field(s) are not available and MUST NOT select those packets unless field(s) are not available and MUST NOT select those packets unless
specifically directed by the Information Element description. specifically directed by the Information Element description. Even
Even if they are ignored, the encrypted packets MUST be accounted for if they are ignored, the encrypted packets MUST be accounted for in
in the Selector packetsObserved Information Element [PSAMP-INFO], the Selector packetsObserved Information Element [RFC5477], part of
part of the Selection Sequence Statistics Report Interpretation. the Selection Sequence Statistics Report Interpretation.
Example of a match based filter Selector, whose rules are: Example of a match-based filter Selector, whose rules are:
IPv4 Source Address = 192.0.2.1 IPv4 Source Address = 192.0.2.1
IPv4 Next-Hop Address = 192.0.2.129 IPv4 Next-Hop Address = 192.0.2.129
IPFIX Options Template Record: IPFIX Options Template Record:
0 1 2 3 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 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 | | Set ID = 3 | Length = 26 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 266 | Field Count = 4 | | Template ID = 266 | Field Count = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope Field Count = 1 |0| selectorId = 302 | | Scope Field Count = 1 |0| selectorId = 302 |
skipping to change at page 30, line 28 skipping to change at page 32, line 40
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 21 | | 21 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 5 | 192.0.2 ... | | 5 | 192.0.2 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... .1 | 192.0.2 ... | | ... .1 | 192.0.2 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... .129 | | ... .129 |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
Figure L: Example of the Selector Report Interpretation, Figure L: Example of the Selector Report Interpretation
For match based and router state Filtering for Match-Based and Router State Filtering
Notes: Notes:
* A selectorAlgorithm value of 5 represents property match Filtering.
* In this filter there is a mix of information from the packet and * 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. information from the router.
6.5.2.6 Hash-Based Filtering 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:
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 - IP identification field
- Flags field - Flags field
- Fragment offset - Fragment offset
- Source IP address - Source IP address
- Destination IP address - Destination IP address
- A number of bytes from the IP payload. The number of bytes and - A number of bytes from the IP payload. The number of bytes and
starting offset MUST be configurable if the hash function supports starting offset MUST be configurable if the Hash Function
it. supports it.
For the bytes taken from the IP payload, IPSX has a fixed offset For the bytes taken from the IP payload, IPSX has a fixed offset of 0
of 0 bytes and a fixed size of 8 bytes. The number and offset of bytes and a fixed size of 8 bytes. The number and offset of payload
payload bytes in the BOB function MUST be configurable. bytes in the BOB function MUST be configurable.
The minimum configuration ranges MUST be as follows: The minimum configuration ranges MUST be as follows:
Number of bytes: from 8 to 32 Number of bytes: from 8 to 32
Offset: from 0 to 64 Offset: from 0 to 64
If the selected payload bytes are not available and the hash function 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 can take a variable-sized input, then the Hash Function MUST be run
with the information which is available and a shorter size. Passing with the information that is available and a shorter size. Passing 0
0 as a substitute for missing payload bytes is only acceptable if as a substitute for missing payload bytes is only acceptable if the
the hash function takes a fixed size as is the case with IPSX. Hash Function takes a fixed size as is the case with IPSX.
If the hash function can take an initialization value then this If the Hash Function can take an initialization value, then this
value MUST be configurable. value MUST be configurable.
A hash-based selection function MAY be configurable as a digest A Hash-based Selection function MAY be configurable as a digest
function. Any selection process which is configured as a digest function. Any Selection Process that is configured as a digest
function MUST have the output value included in the basic packet function MUST have the output value included in the basic Packet
report for any selected packet. Report for any selected packet.
Each hash function used as a hash-based selector requires its own Each Hash Function used as a Hash-based Selection Selector requires
value for the selectorAlgorithm. Currently we have BOB (6), IPSX (7) its own value for the selectorAlgorithm. Currently, we have BOB (6),
and CRC (8) defined and any MAY be used for either Filtering IPSX (7), and CRC (8) defined and any MAY be used for either
or creating a Packet Digest. Only BOB is recommended though and Filtering or creating a Packet Digest. Only BOB is recommended
SHOULD be used. though and SHOULD be used.
The REQUIRED algorithm specific Information Elements in case of hash The REQUIRED algorithm-specific Information Elements in case of
based selection are: Hash-based Selection are:
hashIPPayloadOffset - The payload offset used by a Hash-based
Selection Selector
hashIPPayloadSize - The payload size used by a Hash-based
Selection Selector
hashOutputRangeMin - One or more values for the beginning of each
potential output range.
hashIPPayloadOffset - The payload offset used by a hash based
Selector
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 hashOutputRangeMax - One or more values for the end of each
potential output range. potential output range.
hashSelectedRangeMin - One or more values for the beginning of
each selected range. hashSelectedRangeMin - One or more values for the beginning of each
selected range.
hashSelectedRangeMax - One or more values for the end of each hashSelectedRangeMax - One or more values for the end of each
selected range. selected range.
hashDigestOutput - A 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 hashDigestOutput - A 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. then the minimum and maximum elements may be repeated as needed.
These MUST make one or more non-overlapping ranges. The elements These MUST make one or more non-overlapping ranges. The elements
SHOULD be sent as pairs of minimum and maximum in ascending order, SHOULD be sent as pairs of minimum and maximum in ascending order;
however if they are sent out of order then there will only be one however, if they are sent out of order, then there will only be one
way to interpret the ranges to produce a non-overlapping range and way to interpret the ranges to produce a non-overlapping range and
the Collecting Process MUST be prepared to accept and decode this. the Collecting Process MUST be prepared to accept and decode this.
The following algorithm specific Information Element MAY be sent, The following algorithm-specific Information Element MAY be sent, but
but is optional for security considerations: is optional for security considerations:
hashInitialiserValue - The initialiser value to the hash function.
hashInitialiserValue - The initialiser value to the Hash Function.
Since encryption alters the meaning of encrypted fields, when the Since encryption alters the meaning of encrypted fields, when the
Hash-Based Filtering classification is based on the encrypted Hash-based Filtering classification is based on the encrypted
field(s) in the packet, it MUST be able to recognize that the 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 field(s) are not available and MUST NOT select those packets. Even
if they are ignored, the encrypted packets MUST be accounted in the if they are ignored, the encrypted packets MUST be accounted for in
Selector packetsObserved Information Element [PSAMP-INFO], part of the Selector packetsObserved Information Element [RFC5477], which is
the Selection Sequence Statistics Report Interpretation. part of the Selection Sequence Statistics Report Interpretation.
Example of a hash based filter Selector, whose configuration is: Example of a Hash-based Filter Selector, whose configuration is:
Hash Function = BOB Hash Function = BOB
Hash IP Payload Offset = 0 Hash IP Payload Offset = 0
Hash IP Payload Size = 16 Hash IP Payload Size = 16
Hash Initialiser Value = 0x9A3F9A3F Hash Initialiser Value = 0x9A3F9A3F
Hash Output Range = 0 to 0xFFFFFFFF Hash Output Range = 0 to 0xFFFFFFFF
Hash Selected Range = 100 to 200 and 400 to 500 Hash Selected Range = 100 to 200 and 400 to 500
IPFIX Options Template Record: IPFIX Options Template Record:
0 1 2 3 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 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 = 50 | | Set ID = 3 | Length = 50 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 269 | Field Count = 8 | | Template ID = 269 | Field Count = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope Field Count = 1 |0| selectorId = 300 | | Scope Field Count = 1 |0| selectorId = 302 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope 1 Length = 4 |0| selectorAlgorithm = 302 | | Scope 1 Length = 4 |0| selectorAlgorithm = 302 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 1 |0| hashIPpayloadOffset = 327 | | Field Length = 1 |0| hashIPpayloadOffset = 327 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |0| hashIPpayloadSize = 328 | | Field Length = 4 |0| hashIPpayloadSize = 328 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |0| hashInitialiserValue = 329 | | Field Length = 4 |0| hashInitialiserValue = 329 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 |0| hashOutputRangeMin = 330 | | Field Length = 4 |0| hashOutputRangeMin = 330 |
skipping to change at page 33, line 43 skipping to change at page 36, line 34
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... | ... 200 | | ... | ... 200 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... | ... 400 | | ... | ... 400 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... | ... 500 | | ... | ... 500 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... | | ... |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
Figure M: Example of the Selector Report Interpretation, Figure M: Example of the Selector Report Interpretation
for Hash Based Filtering for Hash-based Filtering
Notes: Notes:
* A selectorAlgorithm value of 6 represents hash-based Filtering
* A selectorAlgorithm value of 6 represents Hash-based Filtering
using the BOB algorithm. using the BOB algorithm.
6.5.2.7 Other Selection Methods 6.5.2.7. Other Selection Methods
Some potential new selection methods MAY be added. Some of the new Some potential new selection methods MAY be added. Some of the new
selection methods, such as non-uniform probabilistic Sampling and selection methods, such as non-uniform probabilistic Sampling and
flow state dependent Sampling, are described in [PSAMP-TECH], with flow-state-dependent Sampling, are described in [RFC5475], with
further references. further references.
Each new selection method MUST be assigned a unique value for the Each new selection method MUST be assigned a unique value for the
selectorAlgorithm Information Element. Its configuration selectorAlgorithm Information Element. Its configuration
parameter(s), along with the way to report it/them with an Options parameter(s), along with the way to report it/them with an Options
Template, MUST be clearly specified. Template, MUST be clearly specified.
6.5.3 Selection Sequence Statistics Report Interpretation 6.5.3. Selection Sequence Statistics Report Interpretation
A Selector MAY be used in multiple Selection Sequences. However, A Selector MAY be used in multiple Selection Sequences. However,
each use of a Selector must be independent, so each separate logical each use of a Selector must be independent, so each separate logical
instance of a Selector MUST maintain its own individual Selection instance of a Selector MUST maintain its own individual Selection
State and statistics. State and statistics.
The Selection Sequence Statistics Report Interpretation MUST include The Selection Sequence Statistics Report Interpretation MUST include
the number of observed packets (Population Size) and the number of the number of observed packets (Population Size) and the number of
packets selected (Sample Size) by each instance of its Primitive packets selected (Sample Size) by each instance of its Primitive
Selectors. Selectors.
skipping to change at page 34, line 42 skipping to change at page 37, line 35
Selectors in the Selection Sequence Statistics Report Interpretation Selectors in the Selection Sequence Statistics Report Interpretation
MUST match the order of the Selectors in the Selection Sequence. MUST match the order of the Selectors in the Selection Sequence.
If the full set of statistics is not sent as part of the Basic Packet If the full set of statistics is not sent as part of the Basic Packet
Reports, the PSAMP Device MUST export a Selection Sequence Statistics Reports, the PSAMP Device MUST export a Selection Sequence Statistics
Report Interpretation for every Selection Sequence, using an Options Report Interpretation for every Selection Sequence, using an Options
Template containing the following Information Elements: Template containing the following Information Elements:
Scope: selectionSequenceId Scope: selectionSequenceId
Non-scope: packetsObserved Non-scope: packetsObserved
packetsSelected (first) packetsSelected (first Selector)
... ...
packetsSelected (last) packetsSelected (last Selector)
The packetsObserved Information Element [PSAMP-INFO] MUST contain the The packetsObserved Information Element [RFC5477] MUST contain the
number of packets seen at the Observation Point, and as a consequence number of packets seen at the Observation Point, and as a consequence
passed to the first Selector in the Selection Sequence. The passed to the first Selector in the Selection Sequence. The
packetsSelected Information Element [PSAMP-INFO] contains the number packetsSelected Information Element [RFC5477] contains the number of
of packets selected by a Selector in the Selection Sequence. packets selected by a Selector in the Selection Sequence.
The Attained Selection Fraction for the Selection Sequence is The Attained Selection Fraction for the Selection Sequence is
calculated by dividing the number of selected packets calculated by dividing the number of selected packets
(packetsSelected Information Element) for the last Selector by the (packetsSelected Information Element) for the last Selector by the
number of observed packets (packetsObserved Information Element). number of observed packets (packetsObserved Information Element).
The Attained Selection Fraction can be calculated for each Selector The Attained Selection Fraction can be calculated for each Selector
by dividing the number of packets selected for that Selector by the by dividing the number of packets selected for that Selector by the
value for the previous Selector. value for the previous Selector.
The statistics for the whole sequence SHOULD be taken at a single The statistics for the whole sequence SHOULD be taken at a single
logical point in time; the input value for a Selector MUST equal the logical point in time; the input value for a Selector MUST equal the
output value of the previous selector. output value of the previous Selector.
The Selection Sequence Statistics Report Interpretation MUST be The Selection Sequence Statistics Report Interpretation MUST be
exported periodically. exported periodically.
Example of Selection Sequence Statistics Report Interpretation: Example of Selection Sequence Statistics Report Interpretation:
Selection Sequence 7 (Filter->Sampling): Selection Sequence 7 (Filter->Sampling):
Observed 100 (observationPointId 1, Interface 5) Observed 100 (observationPointId 1, Interface 5)
Selected 50 (selectorId 5, match IPV4SourceAddress 192.0.2.1) Selected 50 (selectorId 5, match IPV4SourceAddress 192.0.2.1)
skipping to change at page 36, line 28 skipping to change at page 39, line 28
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 9 | | 9 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 100 | | 100 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 10 | | 10 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 3 | | 3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure N: Example of the Selection Sequence Statistics Report Figure N: Example of the Selection Sequence Statistics
Interpretation Report Interpretation
Notes: Notes:
* The Attained Sampling Fractions for Selection Sequence 7 are:
* The Attained Selection Fractions for Selection Sequence 7 are:
Filter 10: 50/100 Filter 10: 50/100
Sampler 5: 6/50 Sampler 5: 6/50
Number of samples selected: 6 Number of samples selected: 6
* The Attained Sampling Fractions for Selection Sequence 9 are: * The Attained Selection Fractions for Selection Sequence 9 are:
Sampler 5: 10/100 Sampler 5: 10/100
Filter 10: 3/10 Filter 10: 3/10
Number of samples selected: 3 Number of samples selected: 3
6.5.4 Accuracy Report Interpretation 6.5.4. Accuracy Report Interpretation
In order for the Collecting Process to determine the inherent In order for the Collecting Process to determine the inherent
accuracy of the reported quantities (for example timestamps), the accuracy of the reported quantities (for example, timestamps), the
PSAMP Device SHOULD send an Accuracy Report Interpretation. PSAMP Device SHOULD send an Accuracy Report Interpretation.
The Accuracy Report Interpretation MUST be exported by an Option The Accuracy Report Interpretation MUST be exported by an Options
Template Record with a scope that contains the Information Element Template Record with a scope that contains the Information Element
for which the accuracy is required. In case the accuracy is specific for which the accuracy is required. In case the accuracy is specific
to a template, a second scope containing the templateId value MUST be to a template, a second scope containing the templateId value MUST be
added to the Option Template Record. The accuracy SHOULD be reported added to the Options Template Record. The accuracy SHOULD be
either with the fixedError Information Element [PSAMP-INFO], or with reported either with the absoluteError Information Element [RFC5477]
the relativeError Information Element [PSAMP-INFO]. or with the relativeError Information Element [RFC5477].
Accuracy Report Interpretation using the fixedError Information Accuracy Report Interpretation using the absoluteError Information
Element: Element:
Scope: informationElementId Scope: informationElementId
Non-scope: fixedError Non-scope: absoluteError
Accuracy Report Interpretation using the fixedError Information Accuracy Report Interpretation using the absoluteError Information
Element and a double scope: Element and a double scope:
Scope: templateId Scope: templateId
informationElementId informationElementId
Non-scope: fixedError Non-scope: absoluteError
Accuracy Report Interpretation using the relativeError Information Accuracy Report Interpretation using the relativeError Information
Element: Element:
Scope: informationElementId Scope: informationElementId
Non-scope: relativeError Non-scope: relativeError
Accuracy Report Interpretation using the relativeError Information Accuracy Report Interpretation using the relativeError Information
Element and a double scope: Element and a double scope:
Scope: templateId Scope: templateId
informationElementId informationElementId
Non-scope: relativeError Non-scope: relativeError
For example, the accuracy of an Information Element whose Abstract For example, the accuracy of an Information Element whose Abstract
Data Type is dateTimeMilliseconds [IPFIX-INFO], for which the unit is Data Type is dateTimeMilliseconds [RFC5102], for which the unit is
specified as milliseconds, can be specified with the fixedError specified as milliseconds, can be specified with the absoluteError
Information Element with the milliseconds units. In this case, the Information Element with the milliseconds units. In this case, the
error interval is the Information Element value +/- the value error interval is the Information Element value +/- the value
reported in the fixedError. reported in the absoluteError.
For example, the accuracy of an Information Element to estimate the For example, the accuracy of an Information Element to estimate the
accuracy of a sampled flow, for which the unit would be specified in accuracy of a sampled flow, for which the unit would be specified in
octets, can be specified with the relativeError Information Element octets, can be specified with the relativeError Information Element
with the octet units. In this case, the error interval is the with the octet units. In this case, the error interval is the
Information Element value +/- the value reported in the relativeError Information Element value +/- the value reported in the relativeError
times the reported Information Element value. times the reported Information Element value.
Alternatively to reporting either the fixedError Information Element An alternative to reporting either the absoluteError Information
or the relativeError Information Element in the Accuracy Report Element or the relativeError Information Element in the Accuracy
Interpretation, both Information Elements MAY be present. This Report Interpretation, is to report both. For this case whatever is
scenario could help in more complex situations where the system clock least accurate for the reported value should be used.
drifts, on the top of having its own accuracy, during the duration of
a measurement.
If the accuracy of a reported quantity changes on the Metering If the accuracy of a reported quantity changes on the Metering
Process, a new Accuracy Report Interpretation MUST be generated. The Process, a new Accuracy Report Interpretation MUST be generated. The
Collecting Process MUST keep the accuracy of the latest Accuracy Collecting Process MUST keep the accuracy of the latest Accuracy
Report Interpretation. Report Interpretation.
Example of an Accuracy Report Interpretation using the fixedError Example of an Accuracy Report Interpretation using the absoluteError
Information Element and a double scope: the timeMicroseconds Information Element and a double scope: the timeMicroseconds
contained in the Template 5 has an accuracy of +/- 2 ms, represented contained in the Template 5 has an accuracy of +/- 2 ms, represented
by the fixedError Information Element. by the absoluteError Information Element.
Scope: templateId = 6 Scope: templateId = 6
informationElementId = timeMicroseconds informationElementId = timeMicroseconds
Non-scope: fixedError = 2 ms Non-scope: absoluteError = 2 ms
IPFIX Options Template Record: IPFIX Options Template Record:
0 1 2 3 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 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 | | Set ID = 3 | Length = 22 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 267 | Field Count = 3 | | Template ID = 267 | Field Count = 3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope Field Count = 2 |0| templateId = 145 | | Scope Field Count = 2 |0| templateId = 145 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope 1 Length = 2 |0| InformationElementId = 303 | | Scope 1 Length = 2 |0| InformationElementId = 303 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope 2 Length = 2 |0| fixedError = 320 | | Scope 2 Length = 2 |0| absoluteError = 320 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Field Length = 4 | | Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The associated IPFIX Data Record: The associated IPFIX Data Record:
0 1 2 3 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 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 = 12 | | Set ID = 267 | Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 5 | 324 | | 5 | 324 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 2 (encoded as a float32) | | 2 (encoded as a float32) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure O: Example of the Selection Sequence Statistics Report Figure O: Example of the Selection Sequence
Interpretation Statistics Report Interpretation
Notes: Notes:
* fixedError is of type float64 but is compressed down to a float32
here. * absoluteError is of type float64 but is compressed down to a
float32 here.
The second example displays an Accuracy Report Interpretation using The second example displays an Accuracy Report Interpretation using
the relativeError Information Element and a single scope: the the relativeError Information Element and a single scope: the
timeMicroseconds has an error of 5 percents, represented by the timeMicroseconds has an error of 5%, represented by the
proportionalAccuracy Information Element. proportionalAccuracy Information Element.
Scope: informationElementId = timeMicroseconds Scope: informationElementId = timeMicroseconds
Non-scope: relativeError = 0.05 Non-scope: relativeError = 0.05
IPFIX Options Template Record: IPFIX Options Template Record:
0 1 2 3 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 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 | | Set ID = 3 | Length = 18 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 39, line 40 skipping to change at page 42, line 45
0 1 2 3 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 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 | | Set ID = 267 | Length = 10 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 324 | 0.05 ... | | 324 | 0.05 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ...(encoded as a float32) | | ...(encoded as a float32) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure P: Example of the Selection Sequence Statistics Report Figure P: Example of the Selection Sequence
Interpretation Statistics Report Interpretation
Notes: Notes:
* relativeError is of type float64 but is compressed down to a * relativeError is of type float64 but is compressed down to a
float32 here. float32 here.
7. Security Considerations 7. Security Considerations
As IPFIX has been selected as the PSAMP export protocol and as the As IPFIX has been selected as the PSAMP export protocol and as the
PSAMP security requirements are not stricter than the IPFIX security PSAMP security requirements are not stricter than the IPFIX security
requirements, refer to the IPFIX export protocol [IPFIX-PROTO] for requirements, refer to the IPFIX export protocol [RFC5101] for the
the security considerations. security considerations.
In the basic Packet Report, a PSAMP Device exports some number of In the basic Packet Report, a PSAMP Device exports some number of
contiguous bytes from the start of the packet, including the packet contiguous bytes from the start of the packet, including the packet
header (which includes link layer, network layer and other header (which includes link layer, network layer, and other
encapsulation headers) and some subsequent bytes of the packet encapsulation headers) and some subsequent bytes of the packet
payload. The PSAMP Device SHOULD NOT export the full payload of payload. The PSAMP Device SHOULD NOT export the full payload of
conversations, as this would mean wiretapping [RFC2804]. The PSAMP conversations, as this would mean wiretapping [RFC2804]. The PSAMP
Device MUST respect local privacy laws. Device MUST respect local privacy laws.
8. IANA Considerations 8. IANA Considerations
The PSAMP Protocol, as set out in this document, has two sets of The PSAMP protocol, as set out in this document, has two sets of
assigned numbers. Considerations for assigning them are discussed assigned numbers. Considerations for assigning them are discussed in
in this section, using the example policies as set out in the this section, using the example policies as set out in [RFC5226],
"Guidelines for IANA Considerations" document IANA-RFC [RFC2434]. "Guidelines for IANA Considerations".
8.1 IPFIX Related Considerations 8.1. IPFIX-Related Considerations
As the PSAMP protocol uses the IPFIX protocol, refer to the IANA As the PSAMP protocol uses the IPFIX protocol, refer to the IANA
considerations section in [IPFIX-PROTO] for the assignments of considerations section in [RFC5101] for the assignments of numbers
numbers used in the protocol and for the numbers used in the used in the protocol and for the numbers used in the information
information model. model.
8.2 PSAMP Related Considerations 8.2. PSAMP-Related Considerations
Each new selection method MUST be assigned a unique value for the Each new selection method MUST be assigned a unique value for the
selectorAlgorithm Information Element [PSAMP-INFO]. Initial selectorAlgorithm Information Element [RFC5477]. Initial contents of
contents of this registry are found section 8.2.4 in [PSAMP-INFO]. this registry are found in Section 8.2.1 in [RFC5477]. Its
Its configuration parameter(s), along with the way to report it/them configuration parameter(s), along with the way to report them with an
with an Options Template, MUST be clearly specified. Options Template, MUST be clearly specified.
New assignments for the PSAMP selection method will be administered New assignments for the PSAMP selection method will be administered
by IANA, on a First Come First Served basis [RFC2434], subject to by IANA, on a First Come First Served basis [RFC5226], subject to
Expert Review [RFC2434]. The group of experts must double check the Expert Review [RFC5226]. The group of experts must double check the
Information Elements definitions with already defined Information Information Elements definitions with already defined Information
Elements for completeness, accuracy and redundancy. Those experts Elements for completeness, accuracy, and redundancy. These experts
will initially be drawn from the Working Group Chairs and document will initially be drawn from the Working Group Chairs and document
editors of the IPFIX and PSAMP Working Groups. editors of the IPFIX and PSAMP Working Groups.
9. References 9. References
9.1 Normative References 9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
[RFC2434] H. Alvestrand, T. Narten, "Guidelines for Writing an IANA Requirement Levels", BCP 14, RFC 2119, March 1997.
Considerations Section in RFCs", RFC 2434, October 1998
[PSAMP-TECH] T. Zseby, M. Molina, N. Duffield, S. Niccolini, F. [RFC5101] Claise, B., Ed., "Specification of the IP Flow Information
Raspall, "Sampling and Filtering Techniques for IP Packet Selection" Export (IPFIX) Protocol for the Exchange of IP Traffic Flow
draft-ietf-psamp-sample-tech-10.txt Information", RFC 5101, January 2008.
[PSAMP-INFO] T. Dietz, F. Dressler, G. Carle, B. Claise, "Information [RFC5102] Quittek, J., Bryant, S., Claise, B., Aitken, P., and J.
Model for Packet Sampling Exports", draft-ietf-psamp-info-07.txt Meyer, "Information Model for IP Flow Information Export",
RFC 5102, January 2008.
[IPFIX-INFO] J. Quittek, S. Bryant, B. Claise, J. Meyer, "Information [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
Model for IP Flow Information Export" draft-ietf-ipfix-info-15.txt IANA Considerations Section in RFCs", BCP 26, RFC 5226, May
2008.
[IPFIX-PROTO] B. Claise (Editor) "Specification of the IPFIX Protocol [RFC5475] Zseby, T., Molina, M., Duffield, N., Niccolini, S., and F.
for the Exchange of IP Traffic Flow Information", draft-ietf-ipfix- Raspall, "Sampling and Filtering Techniques for IP Packet
protocol-26.txt Selection", RFC 5475, March 2009.
9.2 Informative References [RFC5477] Dietz, T., Claise, B., Aitken, P., Dressler, F., and G.
Carle, "Information Model for Packet Sampling Exports", RFC
5477, March 2009.
[IPFIX-ARCH] G. Sadasivan, N. Brownlee, B. Claise, J. Quittek, 9.2. Informative References
"Architecture Model for IP Flow Information Export" draft-ietf-ipfix-
architecture-12.txt"
[PSAMP-FMWK] D. Chiou, B. Claise, N. Duffield, A. Greenberg, M. [RFC2804] IAB and IESG, "IETF Policy on Wiretapping", RFC 2804, May
Grossglauser, P. Marimuthu, J. Rexford, G. Sadasivan, "A Framework 2000.
for Passive Packet Measurement" draft-ietf-psamp-framework-12.txt
[RFC4271] Y. Rekhter, T. Li, Hares, S. "A Border Gateway Protocol 4 [RFC3917] Quittek, J., Zseby, T., Claise, B., and S. Zander,
(BGP-4)", RFC 4271, January 2006 "Requirements for IP Flow Information Export (IPFIX)", RFC
[RFC3917] J. Quittek, T. Zseby, B. Claise, S. Zander, "Requirements 3917, October 2004.
for IP Flow Information Export", RFC 3917, October 2004
[RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A Border
Gateway Protocol 4 (BGP-4)", RFC 4271, January 2006.
[RFC5470] Sadasivan, G., Brownlee, N., Claise, B., and J. Quittek,
"Architecture for IP Flow Information Export" RFC 5470,
March 2009.
[RFC5474] Duffield, N., Ed., "A Framework for Packet Selection and
Reporting", RFC 5474, March 2009.
10. Acknowledgments 10. Acknowledgments
The authors would like to thank the PSAMP group, especially Paul The authors would like to thank the PSAMP group, especially Paul
Aitken for fruitful discussions and for proofreading the document Aitken for fruitful discussions and for proofreading the document
several times. several times.
Authors' Addresses Authors' Addresses
Benoit Claise Benoit Claise
skipping to change at page 42, line 4 skipping to change at page 45, line 18
Aitken for fruitful discussions and for proofreading the document Aitken for fruitful discussions and for proofreading the document
several times. several times.
Authors' Addresses Authors' Addresses
Benoit Claise Benoit Claise
Cisco Systems Cisco Systems
De Kleetlaan 6a b1 De Kleetlaan 6a b1
1831 Diegem 1831 Diegem
Belgium Belgium
Phone: +32 2 704 5622 Phone: +32 2 704 5622
E-mail: bclaise@cisco.com EMail: bclaise@cisco.com
Juergen Quittek Juergen Quittek
NEC Europe Ltd. NEC Europe Ltd.
Network Laboratories Network Laboratories
Kurfuersten-Anlage 36 Kurfuersten-Anlage 36
69115 Heidelberg 69115 Heidelberg
Germany Germany
Phone: +49 6221 90511-15 Phone: +49 6221 90511-15
Email: quittek@nw.neclab.eu EMail: quittek@nw.neclab.eu
Andrew Johnson Andrew Johnson
Cisco Systems Cisco Systems
96 Commercial Quay 96 Commercial Quay
Edinburgh EH6 6LX Edinburgh EH6 6LX
Scotland Scotland
Phone: +44 131 561 3641
Email: andrjohn@cisco.com
11. Intellectual Property Statement Phone: +44 131 561 3641
EMail: andrjohn@cisco.com
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.
12. Copyright Statement
Copyright (C) The IETF Trust (2007).
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.
13. Disclaimer
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,
THE IETF TRUST 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.
 End of changes. 326 change blocks. 
645 lines changed or deleted 747 lines changed or added

This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/