[IPFIX] [Editorial Errata Reported] RFC5655 (4308)

RFC Errata System <rfc-editor@rfc-editor.org> Thu, 19 March 2015 21:37 UTC

To: brian.trammell@hitachi-eu.com, elisa.boschi@hitachi-eu.com, lutz.mark@ifam.fraunhofer.de, tanja.zseby@fokus.fraunhofer.de, arno@wagner.name, bclaise@cisco.com, joelja@bogus.com, n.brownlee@auckland.ac.nz, quittek@neclab.eu
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20150319213641.71FEA180205@rfc-editor.org>
Date: Thu, 19 Mar 2015 14:36:41 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipfix/rgHdZ9cVClhEV_MKi_0jymJzmz8>
Cc: ipfix@ietf.org, rfc-editor@rfc-editor.org
Subject: [IPFIX] [Editorial Errata Reported] RFC5655 (4308)
Precedence: list

The following errata report has been submitted for RFC5655,
"Specification of the IP Flow Information Export (IPFIX) File Format".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=5655&eid=4308

--------------------------------------
Type: Editorial
Reported by: Paul Aitken <paitken@brocade.com>

Section: A.5

Original Text
-------------
A.5. Complete File Example

Bringing together the examples above and adding message headers as
appropriate, a hex dump of the first 317 bytes of the example File
constructed above would appear as in the annotated Figure 10 below.

Corrected Text
--------------
A.5. Complete File Example

Bringing together the examples above and adding message headers as
appropriate, a hex dump of the first 285 bytes of the example File
constructed above would appear as in the annotated Figure 10 below.

Notes
-----
s/317/285/

Figure 10 shows 18 lines of 16 octets each, less three octets in the final row.
(18 x 16 - 3) = 285 octets.

This can also be confirmed by the revised numbering in errata 2030 - though note that the dump is numbered from octet zero:

272: 80 02 00 50 06 00 00 46 50 00 00 00 41

Since the offset of the final octet ("41") is 284, the overall length must be 285.

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary.

--------------------------------------
RFC5655 (draft-ietf-ipfix-file-05)
--------------------------------------
Title : Specification of the IP Flow Information Export (IPFIX) File Format
Publication Date : October 2009
Author(s) : B. Trammell, E. Boschi, L. Mark, T. Zseby, A. Wagner
Category : PROPOSED STANDARD
Source : IP Flow Information Export
Area : Operations and Management
Stream : IETF
Verifying Party : IESG

[IPFIX] [Editorial Errata Reported] RFC5655 (4308) RFC Errata System
[IPFIX] [Errata Rejected] RFC5655 (4308) RFC Errata System