RFC Errata
Found 2 records.
Status: Verified (1)
RFC 7270, "Cisco-Specific Information Elements Reused in IP Flow Information Export (IPFIX)", June 2014
Source of RFC: IETF - NON WORKING GROUPArea Assignment: ops
Errata ID: 5262
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Paul Aitken
Date Reported: 2018-02-15
Verifier Name: Benoit Claise
Date Verified: 2018-02-16
Section 4.12 says:
value : 0x89 = 137 binary: 10001001 decode: 10 -> Drop 001001 -> Fragmentation and DF set
It should say:
value : 0x89 = 137 binary: 10001001 decode: 10 -> Drop 001001 -> Bad TTL
Notes:
Per the "Reason Code (status = 10b, Dropped)" table, "Fragmentation and DF set" is code 000101b:
10 000101b = 133 = Fragmentation and DF set
whereas code 001001b is "Bad TTL":
10 001001b = 137 = bad TTL
IANA's IPFIX registry has been updated accordingly: https://www.iana.org/assignments/ipfix.
Status: Reported (1)
RFC 7270, "Cisco-Specific Information Elements Reused in IP Flow Information Export (IPFIX)", June 2014
Source of RFC: IETF - NON WORKING GROUPArea Assignment: ops
Errata ID: 7775
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Paul Aitken
Date Reported: 2024-01-23
Section 4.12 says:
Abstract Data Type: unsigned32
It should say:
Abstract Data Type: unsigned8
Notes:
Section 4.12 describes an 8-bit forwardingStatus field, and xrefs CCO-NF9FMT where FORWARDING STATUS has a length of 1 (ie, 8 bits).
IANA's IPFIX registry lists the Abstract Data Type for forwardingStatus as "unsigned8".
The "unsigned32" Abstract Data Type is out of sync with these other documents.