RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

RFC 5153, "IP Flow Information Export (IPFIX) Implementation Guidelines", April 2008

Source of RFC: ipfix (ops)
See Also: RFC 5153 w/ inline errata

Errata ID: 2900
Status: Verified
Type: Editorial
Publication Format(s) : TEXT

Reported By: Paul Aitken
Date Reported: 2011-08-01
Verifier Name: Dan Romascanu
Date Verified: 2011-08-02

Section 7.2 says:

   Consequently, an Exporting Process reporting traffic Flows measured
   at a device that hosts one or more middleboxes should clearly
   indicate to Collecting Processes the location of the used Observation
   Point(s) with respect to the middlebox(es).  This can be done by
   using Options with Observation Point as scope and elements like, for
   instance, lineCardID or samplerID.  Otherwise, processing the
   measured Flow data could lead to wrong results.

It should say:

   Consequently, an Exporting Process reporting traffic Flows measured
   at a device that hosts one or more middleboxes should clearly
   indicate to Collecting Processes the location of the used Observation
   Point(s) with respect to the middlebox(es).  This can be done by
   using Options with Observation Point as scope and elements like, for
   instance, lineCardId or selectorId.  Otherwise, processing the
   measured Flow data could lead to wrong results.

Notes:

s/lineCardID/lineCardId/
s/samplerID/selectorId/

Per the definitions in RFC5102, RFC5477 and IANA's IPFIX registry.

Report New Errata



Advanced Search