draft-ietf-psamp-protocol-05.txt   draft-ietf-psamp-protocol-06.txt 
PSAMP working group PSAMP working group
Internet Draft EDITOR: B. Claise Internet Draft EDITOR: B. Claise
draft-ietf-psamp-protocol-05.txt Cisco Systems draft-ietf-psamp-protocol-06.txt Cisco Systems
Packet Sampling (PSAMP) Protocol Specifications Packet Sampling (PSAMP) Protocol Specifications
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 29 skipping to change at page 1, line 29
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress". reference material or to cite them other than as "work in progress".
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on September 30, 2006. This Internet-Draft will expire on December 26, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2006).
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 PSAMP Exporting Process to a PSAMP Collecting Process. For export
of packet information the IP Flow Information eXport (IPFIX) of packet information the IP Flow Information eXport (IPFIX)
skipping to change at page 2, line 36 skipping to change at page 2, line 36
3.3.1 PSAMP and IPFIX Processes..............................13 3.3.1 PSAMP and IPFIX Processes..............................13
3.3.2 Packet Report, Packet Interpretation, and Data Record..14 3.3.2 Packet Report, Packet Interpretation, and Data Record..14
4. Differences between PSAMP and IPFIX.........................14 4. Differences between PSAMP and IPFIX.........................14
4.1 Architecture Point of View................................14 4.1 Architecture Point of View................................14
4.2 Protocol Point of View....................................16 4.2 Protocol Point of View....................................16
4.3 Information Model Point of View...........................16 4.3 Information Model Point of View...........................16
5. PSAMP Requirements versus the IPFIX Solution................16 5. PSAMP Requirements versus the IPFIX Solution................16
5.1 High Level View of the Integration........................17 5.1 High Level View of the Integration........................17
6. Using the IPFIX Protocol for PSAMP..........................18 6. Using the IPFIX Protocol for PSAMP..........................18
6.1 Selector ID...............................................18 6.1 Selector ID...............................................18
6.2 The Selection Sequence....................................18 6.2 The Selection Sequence ID.................................18
6.3 The Exporting Process.....................................18 6.3 The Exporting Process.....................................18
6.4 Packet Report.............................................18 6.4 Packet Report.............................................18
6.4.1 Basic Packet Report....................................19 6.4.1 Basic Packet Report....................................19
6.4.2 Extended Packet Report.................................21 6.4.2 Extended Packet Report.................................21
6.5 Report Interpretation.....................................23 6.5 Report Interpretation.....................................23
6.5.1 Selection Sequence Report Interpretation...............23 6.5.1 Selection Sequence Report Interpretation...............23
6.5.2 Selector Report Interpretation.........................25 6.5.2 Selector Report Interpretation.........................25
6.5.2.1 Systematic Count-Based Sampling.......................25 6.5.2.1 Systematic Count-Based Sampling.......................25
6.5.2.2 Systematic Time-Based Sampling........................27 6.5.2.2 Systematic Time-Based Sampling........................27
6.5.2.3 Random n-out-of-N Sampling............................28 6.5.2.3 Random n-out-of-N Sampling............................28
skipping to change at page 4, line 5 skipping to change at page 4, line 5
[PSAMP-FMWK]: "A Framework for Packet Selection and Reporting", [PSAMP-FMWK]: "A Framework for Packet Selection and Reporting",
describes the PSAMP framework for network elements to select subsets describes the PSAMP framework for network elements to select subsets
of packets by statistical and other methods, and to export a stream of packets by statistical and other methods, and to export a stream
of reports on the selected packets to a collector. of reports on the selected packets to a collector.
[PSAMP-TECH]: "Sampling and Filtering Techniques for IP Packet [PSAMP-TECH]: "Sampling and Filtering Techniques for IP Packet
Selection", describes the set of packet selection techniques Selection", describes the set of packet selection techniques
supported by PSAMP. supported by PSAMP.
[PSAMP-PROTO]: "Packet Sampling (PSAMP) Protocol Specifications" This document: "Packet Sampling (PSAMP) Protocol Specifications"
(this document), specifies the export of packet information from a specifies the export of packet information from a PSAMP Exporting
PSAMP Exporting Process to a PSAMP Collecting Process. Process to a PSAMP Collecting Process.
[PSAMP-INFO]: "Information Model for Packet Sampling Exports" defines [PSAMP-INFO]: "Information Model for Packet Sampling Exports" defines
an information and data model for PSAMP. an information and data model for PSAMP.
[PSAMP-MIB]: "Definitions of Managed Objects for Packet Sampling" [PSAMP-MIB]: "Definitions of Managed Objects for Packet Sampling"
describes the PSAMP Management Information Base. describes the PSAMP Management Information Base.
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,
skipping to change at page 8, line 18 skipping to change at page 8, line 18
Information Element Information Element
An Information Element is a protocol and encoding independent An Information Element is a protocol and encoding independent
description of an attribute which may appear in an IPFIX Record. The description of an attribute which may appear in an IPFIX Record. The
IPFIX information model [IPFIX-INFO] defines the base set of IPFIX information model [IPFIX-INFO] defines the base set of
Information Elements for IPFIX. The type associated with an Information Elements for IPFIX. The type associated with an
Information Element indicates constraints on what it may contain and Information Element indicates constraints on what it may contain and
also determines the valid encoding mechanisms for use in IPFIX. also determines the valid encoding mechanisms for use in IPFIX.
+------------------+---------------------------------------------+ +------------------+---------------------------------------------+
| | 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) | / |
+------------------+--------------------+------------------------+ +------------------+--------------------+------------------------+
| Options Template | Options Template | / | | Options Template | Options Template | / |
| Set | Record(s) | | | Set | Record(s) | |
+------------------+--------------------+------------------------+ +------------------+--------------------+------------------------+
Figure A: Terminology Summary Table Figure A: Terminology Summary Table
skipping to change at page 9, line 6 skipping to change at page 9, line 6
Packet Stream Packet Stream
A packet stream denotes a set of packets that flows past some A packet stream denotes a set of packets that flows past some
specified point within the Selection Process. An example of a Packet specified point within the Selection Process. An example of a Packet
Stream is the output of the Selection Process. Note that packets Stream is the output of the Selection Process. Note that packets
selected from a stream, e.g. by Sampling, do not necessarily possess selected from a stream, e.g. by Sampling, do not necessarily possess
a property by which they can be distinguished from packets that have a property by which they can be distinguished from packets that have
not been selected. For this reason the term "stream" is favored over not been selected. For this reason the term "stream" is favored over
"flow", which is defined as set of packets with common properties "flow", which is defined as set of packets with common properties
[IPFIX-REQ]. [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 headers)
and the packet payload. and the packet payload.
3.2.2 Selection Process 3.2.2 Selection Process
Selection Process Selection Process
skipping to change at page 18, line 51 skipping to change at page 18, line 51
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 Sequences, for each selected packet, a Packet For each Selection Sequences, 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-FWMK]: There are two types of Packet Report, as described in [PSAMP-FMWK]:
the basic Packet Report and the extended Packet Report. the 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
- The hash value (digestHashValue) generated by the digest hash - The hash value (digestHashValue) generated by the digest hash
function. If there are no digest functions in the selection function. If there are no digest functions in the selection
sequence then no element needs to be sent. If there is more than sequence then no element needs to be sent. If there is more than
skipping to change at page 19, line 26 skipping to change at page 19, line 26
including the packet header (which includes link layer, network layer including the packet header (which includes link layer, network layer
and other encapsulation headers) and some subsequent bytes of the and other encapsulation headers) and some subsequent bytes of the
packet payload. Alternatively, the number of contiguous bytes may packet payload. Alternatively, the number of contiguous bytes may
start at the beginning of the payload. The dataLinkFrameSection, start at the beginning of the payload. The dataLinkFrameSection,
mplsLabelStackSection, mplsPayloadPacketSection, ipPacketSection, and mplsLabelStackSection, mplsPayloadPacketSection, ipPacketSection, and
ipPayloadPacketSection PSAMP Information Elements are available for ipPayloadPacketSection PSAMP Information Elements are available for
this use. this use.
For each selected packet, the Packet Report SHOULD contain the For each selected packet, the Packet Report SHOULD contain the
following information: following information:
- the observationTimeMicroSeconds Information Element - the observationTimeMicroseconds Information Element
In the Packet Report, the PSAMP device MUST be capable of exporting 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 non
scope Information Elements of the Selection Sequence Statistics 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 calculated precisely for the Observed Packet Stream. The Packet be 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
skipping to change at page 20, line 22 skipping to change at page 20, line 22
| Set ID = 2 | Length = 24 | | Set ID = 2 | Length = 24 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 260 | Field Count = 4 | | Template ID = 260 | Field Count = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| selectionSequenceId = 301 | Field Length = 4 | | selectionSequenceId = 301 | Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| digestHashValue = 326 | Field Length = 4 | | digestHashValue = 326 | Field Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ipHeaderPacketSection = 313 | Field Length = 12 | | ipHeaderPacketSection = 313 | 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 = 28 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 9 | | 9 |
skipping to change at page 21, line 46 skipping to change at page 21, line 46
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), or related to the Selection State associated with autonomous system [RFC1771]), or related to the Selection State
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
to report some number of contiguous bytes from the start of the to report some number of contiguous bytes from the start of the
packet, mandatory in the basic Packet Report, may not be exercised. packet, mandatory in the basic Packet Report, may not be exercised.
In this case, the Packet Content MAY be omitted. Note this In this case, the Packet Content MAY be omitted. Note this
configuration is quite similar to an IPFIX device for which a configuration is quite similar to an IPFIX device for which a
Template Record containing information about a single packet is Template Record containing information about a single packet is
reported. reported.
skipping to change at page 23, line 39 skipping to change at page 23, line 39
Scope: selectionSequenceId Scope: selectionSequenceId
Non-Scope: one Information Element representing Non-Scope: one Information Element representing
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, exporterIPv6Address Information
Elements (specified in [IPFIX-INFO]), but not limited to those: any Elements (specified in [IPFIX-INFO]), but not limited to those: any
Information Element specified in [IFPIX-INFO] or [PSAMP-INFO] can Information Element specified in [IPFIX-INFO] or [PSAMP-INFO] 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 option template record describing it in more
details (if necessary). details (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
skipping to change at page 30, line 49 skipping to change at page 30, line 49
the Information Elements in the Option Template Record, but the order the Information Elements in the Option Template Record, but the order
may be important for implementation purposes, as the first filter may be important for implementation purposes, as the first filter
will have to work at a higher rate. In any case, an implementation will have to work at a higher rate. In any case, an implementation
is not constrained to respect the filter ordering as long as the is not constrained to respect the filter ordering as long as the
result is the same, and it may even implement the composite Filtering result is the same, and it may even implement the composite Filtering
in Filtering in one single step. in 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. field(s) are not available and MUST NOT select those packets unless
specifically directed by the Information Element description.
Even if they are ignored, the encrypted packets MUST be accounted for Even if they are ignored, the encrypted packets MUST be accounted for
in the Selector packetsObserved Information Element [PSAMP-INFO], in the Selector packetsObserved Information Element [PSAMP-INFO],
part of the Selection Sequence Statistics Report Interpretation. part of 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 = 10.0.0.1 IPv4 Source Address = 10.0.0.1
IPv4 Next-Hop Address = 10.0.1.1 IPv4 Next-Hop Address = 10.0.1.1
IPFIX Options Template Record: IPFIX Options Template Record:
skipping to change at page 32, line 23 skipping to change at page 32, line 23
- 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 supports
it. 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 bytes and a fixed size of 8 bytes. The number and offset of of 0 bytes and a fixed size of 8 bytes. The number and offset of
payload bytes in the BOB function MUST be configurable. If any payload bytes in the BOB function MUST be configurable.
of the configured set of bytes from the IP payload are unavailable
then 0 MUST be used, which may result in a different value than
if the hash function is run on a subset of the input.
The minimum configuration ranges MUST be as follows: 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 which is available and a shorter size. Passing
0 as a substitute for missing payload bytes is only acceptable if 0 as a substitute for missing payload bytes is only acceptable if
the hash function takes a fixed size as is the case with IPSX. the hash function takes a fixed size as is the case with IPSX.
skipping to change at page 39, line 4 skipping to change at page 38, line 48
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 [IPFIX-INFO], for which the unit is
specified as milliseconds, can be specified with the fixedError specified as milliseconds, can be specified with the fixedError
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 fixedError.
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
skipping to change at page 39, line 30 skipping to change at page 39, line 27
scenario could help in more complex situations where the system clock scenario could help in more complex situations where the system clock
drifts, on the top of having its own accuracy, during the duration of drifts, on the top of having its own accuracy, during the duration of
a measurement. 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 fixedError
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 fixedError Information Element.
Scope: templateId = 6 Scope: templateId = 6
informationElementId = timeMicroSeconds informationElementId = timeMicroseconds
Non-scope: fixedError = 2 ms Non-scope: fixedError = 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 |
skipping to change at page 40, line 27 skipping to change at page 40, line 25
Figure O: Example of the Selection Sequence Statistics Report Figure O: Example of the Selection Sequence Statistics Report
Interpretation Interpretation
Notes: Notes:
* fixedError is of type float64 but is compressed down to a float32 * fixedError is of type float64 but is compressed down to a float32
here. 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 percents, 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Template ID = 268 | Field Count = 2 | | Template ID = 268 | Field Count = 2 |
skipping to change at page 42, line 21 skipping to change at page 42, line 19
group of experts must double check the Information Elements group of experts must double check the Information Elements
definitions with already defined Information Elements for definitions with already defined Information Elements for
completeness, accuracy and redundancy. Those experts will initially completeness, accuracy and redundancy. Those experts will initially
be drawn from the Working Group Chairs and document editors of the be drawn from the Working Group Chairs and document editors of the
IPFIX and PSAMP Working Groups. IPFIX and PSAMP Working Groups.
9. References 9. References
9.1 Normative References 9.1 Normative References
[RFC1771] Y. Rekhter, T. Li, "A Border Gateway Protocol 4 (BGP-4)",
[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 [RFC2434] H. Alvestrand, T. Narten, "Guidelines for Writing an IANA
Considerations Section in RFCs", RFC 2434, October 1998 Considerations Section in RFCs", RFC 2434, October 1998
[PSAMP-TECH] T. Zseby, M. Molina, N. Duffield, S. Niccolini, F. [PSAMP-TECH] T. Zseby, M. Molina, N. Duffield, S. Niccolini, F.
Raspall, "Sampling and Filtering Techniques for IP Packet Selection" Raspall, "Sampling and Filtering Techniques for IP Packet Selection"
draft-ietf-psamp-sample-tech-07.txt draft-ietf-psamp-sample-tech-07.txt
[PSAMP-INFO] T. Dietz, F. Dressler, G. Carle, B. Claise, "Information [PSAMP-INFO] T. Dietz, F. Dressler, G. Carle, B. Claise, "Information
Model for Packet Sampling Exports", draft-ietf-psamp-info-03.txt Model for Packet Sampling Exports", draft-ietf-psamp-info-03.txt
skipping to change at page 43, line 4 skipping to change at page 42, line 44
[IPFIX-INFO] J. Quittek, S. Bryant, B. Claise, J. Meyer, "Information [IPFIX-INFO] J. Quittek, S. Bryant, B. Claise, J. Meyer, "Information
Model for IP Flow Information Export" draft-ietf-ipfix-info-11.txt Model for IP Flow Information Export" draft-ietf-ipfix-info-11.txt
[IPFIX-PROTO] B. Claise (Editor) "IPFIX Protocol Specifications", [IPFIX-PROTO] B. Claise (Editor) "IPFIX Protocol Specifications",
draft-ietf-ipfix-protocol-19.txt draft-ietf-ipfix-protocol-19.txt
9.2 Informative References 9.2 Informative References
[PSAMP-MIB] T. Dietz, B. Claise "Definitions of Managed Objects for [PSAMP-MIB] T. Dietz, B. Claise "Definitions of Managed Objects for
Packet Sampling" draft-ietf-psamp-mib-05.txt Packet Sampling" draft-ietf-psamp-mib-05.txt
[PSAMP-FMWK] D. Chiou, B. Claise, N. Duffield, A. Greenberg, M. [PSAMP-FMWK] D. Chiou, B. Claise, N. Duffield, A. Greenberg, M.
Grossglauser, P. Marimuthu, J. Rexford, G. Sadasivan, "A Framework Grossglauser, P. Marimuthu, J. Rexford, G. Sadasivan, "A Framework
for Passive Packet Measurement" draft-ietf-psamp-framework-10.txt for Passive Packet Measurement" draft-ietf-psamp-framework-10.txt
[RFC1771] Y. Rekhter, T. Li, "A Border Gateway Protocol 4 (BGP-4)",
[RFC1889] Schulzrinne, H., Casner, S., Frederick, R., Jacobson, V.,
"RTP: A Transport Protocol for Real-Time Applications", RFC 1889,
January 1996
[RFC3917] J. Quittek, T. Zseby, B. Claise, S. Zander, "Requirements [RFC3917] J. Quittek, T. Zseby, B. Claise, S. Zander, "Requirements
for IP Flow Information Export", RFC 3917, October 2004 for IP Flow Information Export", RFC 3917, October 2004
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
 End of changes. 22 change blocks. 
26 lines changed or deleted 29 lines changed or added

This html diff was produced by rfcdiff 1.32. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/