RFC Errata
Found 5 records.
Status: Verified (5)
RFC 5655, "Specification of the IP Flow Information Export (IPFIX) File Format", October 2009
Source of RFC: ipfix (ops)
Errata ID: 3559
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Paul Aitken
Date Reported: 2013-03-20
Verifier Name: Benoit Claise
Date Verified: 2013-03-24
Section 8.2.1 says:
(none)
It should say:
Units: milliseconds
Notes:
collectionTimeMilliseconds requires units of milliseconds.
Compare with sections 8.2.7 and 8.2.14 in the same document.
IANA's IPFIX IE registry requires the corresponding update.
Errata ID: 3560
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Paul Aitken
Date Reported: 2013-03-20
Verifier Name: Benoit Claise
Date Verified: 2013-07-26
Section 8.2.11 + .18 says:
(none)
It should say:
Range: The valid range is 0-0.
Notes:
8.2.11 messageScope requires a value of 0 ("The value of this Information Element MUST be written as 0") but no range is given. The range should say "0-0". (Compare with text in RFC 5102).
Similarly for 8.2.18 sessionScope.
Note to IANA: the changes are already done in the IPFIX registry, via the IE doctors (draft-ietf-ipfix-ie-doctors-07 procedure)
Errata ID: 1988
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2009-12-28
Verifier Name: Dan Romascanu
Date Verified: 2010-05-11
Section 9.1.3, pg.39 says:
signedAttrs: an optional set of attributes that are signed along with the content. | digestAlgorithm: identifies the digital signature algorithm and associated parameters used to generate the signature. signature: the digital signature of the associated file. unsignedAttrs: an optional set of attributes that are not signed.
It should say:
signedAttrs: an optional set of attributes that are signed along with the content. | signatureAlgorithm: identifies the digital signature algorithm and associated parameters used to generate the signature. signature: the digital signature of the associated file. unsignedAttrs: an optional set of attributes that are not signed.
Notes:
Rationale:
Same SEQUENCE element name listed twice, for two different explanations.
Further Note (keep for update!):
In Section 9.1, in the ASN.1 on page 37, for a better approximation
to ASN.1, all pairs of curly braces, "{" ... "}", should better be
preceded by the keyword "SEQUENCE".
Errata ID: 4306
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Wayne Tackabury
Date Reported: 2015-03-19
Verifier Name: Benoit Claise
Date Verified: 2015-03-19
Section A.5 says:
224: 0A 47 0A B6 E5 47 0C 07 48 00|01 03 00 18 00 3E [ message checksum record ^ --> 240: 2B 37 08 CE B2 0E 30 11 32 12 4A 5F E3 AD DB 00 256:|00 0A 05 10 47 0A B6 E5 00 00 00 06 00 00 00 01
It should say:
224: 0A 47 0A B6 E5 47 0C 07 48 00|01 03 00 16 00 3E [ message checksum record ^ --> 240: 2B 37 08 CE B2 0E 30 11 32 12 4A 5F E3 AD DB 00 256:|00 0A 05 10 47 0A B6 E5 00 00 00 06 00 00 00 01
Notes:
First of all, note that per erratum #2030, the offsets in this whole section are wrong, it should begin (I think) at 192. I shall use the published (incorrect) offset for illuminating this point:
I believe the byte at #237 should be 0x16 and not 0x18. I suspect this checksum was copy-pasted from a prior instance in the example, where there were three pad bytes added to the data record for #259 (0x103). In this instance, there is only one pad byte at #255, hence the offset here should be two less (22 or 0x16 and not 24 or 0x18):
2 bytes set ID
2 bytes length
1 byte option data
16 bytes checksum data
1 byte pad (at #255)
...totalling 22. Thanks!
Errata ID: 2906
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 B.1.1 says:
Observation Domain ID: Similarly, the NetFlow V9 sourceID has become the IPFIX Observation Domain ID.
It should say:
Observation Domain ID: Similarly, the NetFlow V9 Source ID has become the IPFIX Observation Domain ID.
Notes:
s/sourceID/Source ID/
Per consistent usage in RFC3954, the correct term is "Source ID".