RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 5 records.

Status: Reported (4)

RFC 5424, "The Syslog Protocol", March 2009

Source of RFC: syslog (sec)

Errata ID: 5010
Status: Reported
Type: Technical
Publication Format(s) : TEXT

Reported By: Job Snijders
Date Reported: 2017-05-05

Section 8.1 says:

This document guards against the technical issues outlined in UTR36 by
REQUIRING "shortest form" encoding for syslog applications.

It should say:

"Shortest Form" encoding is REQUIRED for syslog applications to guard
against the technical issues outlined in UTR36.

Notes:

"REQUIRING" is not a RFC 2119 keyword.

Errata ID: 6927
Status: Reported
Type: Technical
Publication Format(s) : TEXT

Reported By: Ulrich Windl
Date Reported: 2022-04-07

Section 6 says:

SD-NAME         = 1*32PRINTUSASCII
                  ; except '=', SP, ']', %d34 (")
...

PRINTUSASCII    = %d33-126

It should say:

SD-NAME         = 1*32PRINTUSASCII
                  ; except '=', SP, ']', %d34 (")
...
PRINTUSASCII    = %d32-126

Notes:

When excluding SP %d32 from PRINTUSASCII, then it does not make sense to state "except ..SP .."
There are more issues with the grammar:
SD_NAME forbids ']', but it should also forbid '['

Errata ID: 4967
Status: Reported
Type: Editorial
Publication Format(s) : TEXT

Reported By: Muhammad Usman
Date Reported: 2017-03-14

Section 6.2.1 says:

4             security/authorization messages
10            security/authorization messages

It should say:

"10             security/authorization messages" should be removed

Notes:

There is a double entry in the facility list.

Errata ID: 6647
Status: Reported
Type: Editorial
Publication Format(s) : TEXT

Reported By: Anonymous User
Date Reported: 2021-07-23

Section 6.2.1 says:

4             security/authorization messages
10            security/authorization messages

It should say:

4             security/authorization messages (note 1)
10            security/authorization messages (note 1)

Note 1 - Various operating systems have been found to utilize
         facilities 4 and 10 for security/authorization
         messages which seem to be similar.

Notes:

Not including the note (adapted from the one in RFC3164) causes errata like the one with ID 4967 to be erroneously reported.

Status: Held for Document Update (1)

RFC 5424, "The Syslog Protocol", March 2009

Source of RFC: syslog (sec)

Errata ID: 2682
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT

Reported By: VicTor Smirnoff
Date Reported: 2011-01-07
Held for Document Update by: Sean Turner

Section 6.2.1. says:

 15             clock daemon (note 2)
(...)
 Table 1.  Syslog Message Facilities


It should say:

 15             clock daemon
(...)
 Table 1.  Syslog Message Facilities

Notes:

Note 2 isn't present in this document. It's an artefact from RFC 3164.

Report New Errata



Advanced Search