RFC Errata
Found 3 records.
Status: Verified (3)
RFC 6759, "Cisco Systems Export of Application Information in IP Flow Information Export (IPFIX)", November 2012
Source of RFC: IETF - NON WORKING GROUPArea Assignment: ops
Errata ID: 3909
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Andrew Feren
Date Reported: 2014-03-03
Verifier Name: Benoit Claise
Date Verified: 2014-04-17
Section 7.1.8 says:
Description:
Specifies if the Application ID is based on peer-to-peer
technology. Possible values are { "yes", "y", 1 },
{ "no", "n", 2 }, and { "unassigned", "u", 0 }.
It should say:
Description:
Specifies if the Application ID is based on peer-to-peer
technology. Possible values are { "yes", "y", 1 },
{ "no", "n", 2 }, and { "unassigned", "u", 0 }.
Note that 0, 1, and 2 above are integer values; as UTF-8
characters they are U+0000(NUL), U+0001(SOH), and U+0002(STX).
WARNING: the overloading of a string value with an integer
representation that can take the value 0 requires careful
handling on collectors and exporters which use this value
to signify the end of a string.
Notes:
Added clarifying text. The difference between a quoted and unquoted
digit (1 vs "1") is extremely subtle and easily missed.
See, for example,
http://www.ietf.org/mail-archive/web/ipfix/current/msg07151.html.
Errata ID: 3910
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Andrew Feren
Date Reported: 2014-03-03
Verifier Name: Benoit Claise
Date Verified: 2014-04-17
Section 7.1.9 says:
Description:
Specifies if the Application ID is used as a tunnel technology.
Possible values are { "yes", "y", 1 }, { "no", "n", 2 },
and { "unassigned", "u", 0 }.
It should say:
Description:
Specifies if the Application ID is used as a tunnel technology.
Possible values are { "yes", "y", 1 }, { "no", "n", 2 },
and { "unassigned", "u", 0 }.
Note that 0, 1, and 2 above are integer values; as UTF-8
characters they are U+0000(NUL), U+0001(SOH), and U+0002(STX).
WARNING: the overloading of a string value with an integer
representation that can take the value 0 requires careful
handling on collectors and exporters which use this value
to signify the end of a string.
Notes:
Added clarifying text. The difference between a quoted and unquoted
digit (1 vs "1") is extremely subtle and easily missed.
See, for example,
http://www.ietf.org/mail-archive/web/ipfix/current/msg07151.html.
Errata ID: 3911
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Andrew Feren
Date Reported: 2014-03-03
Verifier Name: Benoit Claise
Date Verified: 2014-04-17
Section 7.1.10 says:
Description:
Specifies if the Application ID is an encrypted networking
protocol. Possible values are { "yes", "y", 1 },
{ "no", "n", 2 }, and { "unassigned", "u", 0 }.
It should say:
Description:
Specifies if the Application ID is an encrypted networking
protocol. Possible values are { "yes", "y", 1 },
{ "no", "n", 2 }, and { "unassigned", "u", 0 }.
Note that 0, 1, and 2 above are integer values; as UTF-8
characters they are U+0000(NUL), U+0001(SOH), and U+0002(STX).
WARNING: the overloading of a string value with an integer
representation that can take the value 0 requires careful
handling on collectors and exporters which use this value
to signify the end of a string.
Notes:
Added clarifying text. The difference between a quoted and unquoted
digit (1 vs "1") is extremely subtle and easily missed.
See, for example,
http://www.ietf.org/mail-archive/web/ipfix/current/msg07151.html.