More RFC text fixes #62

Signed-off-by: mrgarris0n <gergely.karacsonyi@gmail.com>

Author: mrgarris0n

_data/external_links.yml

@@ -430,16 +430,36 @@ welf:
 
 ### RFC links ###
 
+rfc-822:
+  id: rfc-822
+  url: https://www.ietf.org/rfc/rfc822.txt
+  title: [ "RFC-822" ]
+
+rfc-3162:
+  id: rfc-3162
+  url: https://www.ietf.org/rfc/rfc3162.txt
+  title: [ "RFC-3162" ]
+
 rfc-3164:
   id: rfc-3164
   url: https://www.ietf.org/rfc/rfc3164.txt
   title: [ "RFC-3164" ]
 
+rfc-3339:
+  id: rfc-3339
+  url: https://www.ietf.org/rfc/rfc3339.txt
+  title: [ "RFC-3339" ]
+
 rfc-3526:
   id: rfc-3526
   url: https://www.ietf.org/rfc/rfc3526.txt
   title: [ "RFC-3526" ]
 
+rfc-4122:
+  id: rfc-4122
+  url: https://www.ietf.org/rfc/rfc4122.txt
+  title: [ "RFC-4122" ]
+
 rfc-4180:
   id: rfc-4180
   url: https://tools.ietf.org/html/rfc4180

_includes/doc/admin-guide/options/destination-flags.md

@@ -10,7 +10,7 @@
 
 - *syslog-protocol*: The syslog-protocol flag instructs the driver to
     format the messages according to the new IETF syslog protocol
-    standard (RFC5424), but without the frame header. If this flag is
+    standard (RFC-5424), but without the frame header. If this flag is
     enabled, macros used for the message have effect only for the text
     of the message, the message header is formatted to the new standard.
     Note that this flag is not needed for the syslog driver, and that

_includes/doc/admin-guide/options/log-msg-size.md

@@ -7,7 +7,7 @@
 length includes the entire message (the data structure and individual
 fields). The maximal value that can be set is 268435456 bytes (256 MiB).
 
-For messages using the IETF-syslog message format (RFC5424), the maximal
+For messages using the IETF-syslog message format (RFC-5424), the maximal
 size of the value of an SDATA field is 64 KiB.
 
 **NOTE:** In most cases, log-msg-size() does not need to be set higher than

_includes/doc/admin-guide/options/source-flags.md

@@ -109,7 +109,7 @@
 
 - *syslog-protocol*: The syslog-protocol flag specifies that incoming
     messages are expected to be formatted according to the new IETF
-    syslog protocol standard (RFC5424), but without the frame header.
+    syslog protocol standard (RFC-5424), but without the frame header.
     Note that this flag is not needed for the syslog driver, which
     handles only messages that have a frame header.
 

_includes/doc/admin-guide/options/value-pairs.md

@@ -196,17 +196,17 @@ The rekey() option can be used with the format-json template-function as well, u
 
 - *all-nv-pairs*: Include every soft macro (name-value pair). Equivalent to using both nv-pairs and dot-nv-pairs.
 
-- *rfc3164*: The macros that correspond to the RFC3164 (legacy or BSD-syslog) message format: ${FACILITY}, ${PRIORITY}, ${HOST}, ${PROGRAM}, ${PID},${MESSAGE}, and ${DATE}.
+- *rfc3164*: The macros that correspond to the RFC-3164 (legacy or BSD-syslog) message format: ${FACILITY}, ${PRIORITY}, ${HOST}, ${PROGRAM}, ${PID},${MESSAGE}, and ${DATE}.
 
-- *rfc5424*: The macros that correspond to the RFC5424 (IETF-syslog) message format: ${FACILITY}, ${PRIORITY}, ${HOST}, ${PROGRAM}, ${PID}, ${MESSAGE},   ${MSGID}, ${R_DATE}, and the metadata from the structured-data (SDATA) part of RFC5424-formatted messages, that is, every macro that starts with .SDATA..
+- *rfc5424*: The macros that correspond to the RFC-5424 (IETF-syslog) message format: ${FACILITY}, ${PRIORITY}, ${HOST}, ${PROGRAM}, ${PID}, ${MESSAGE},   ${MSGID}, ${R_DATE}, and the metadata from the structured-data (SDATA) part of RFC-5424 formatted messages, that is, every macro that starts with .SDATA..
 
   The rfc5424 group also has the following alias: syslog-proto. Note that the value of ${R_DATE} will be listed under the DATE key. The rfc5424 group does not contain any metadata about the message, only information that was present in the original message. To include the most commonly used metadata (for example, the ${SOURCEIP} macro), use the selected-macros group instead.
 
 - *all-macros*: Include every hard macro. This group is mainly useful for debugging, as it contains redundant information (for example, the date-related macros include the date-related information several times in various formats).
 
 - *selected-macros*: Include the macros of the rfc3164 groups, and the most commonly used metadata about the log message: the ${TAGS}, ${SOURCEIP}, and ${SEQNUM} macros.
 
-- *sdata*: The metadata from the structured-data (SDATA) part of RFC5424-formatted messages, that is, every macro that starts with .SDATA.
+- *sdata*: The metadata from the structured-data (SDATA) part of RFC-5424 formatted messages, that is, every macro that starts with .SDATA.
 
 - *everything*: Include every hard and soft macros. This group is mainly useful for debugging, as it contains redundant information (for example, the date-related macros include the date-related information several times in various formats).
 

doc/_admin-guide/010_Introduction_to_syslog-ng/000_What_syslog-ng_is.md

@@ -92,8 +92,8 @@ monitoring system.
 
 ## syslog protocol standards
 
-syslog-ng not only supports legacy BSD syslog (RFC3164) and the enhanced
-RFC5424 protocols but also JavaScript Object Notation (JSON) and
+syslog-ng not only supports legacy BSD syslog (RFC-3164) and the enhanced
+RFC-5424 protocols but also JavaScript Object Notation (JSON) and
 journald message formats.
 
 ## Heterogeneous environments

doc/_admin-guide/020_The_concepts_of_syslog-ng/004_Timezones_and_daylight_saving.md

@@ -8,7 +8,7 @@ description: >-
 ---
 
 The syslog-ng application supports messages originating from different
-timezones. The original syslog protocol (RFC3164) does not include
+timezones. The original syslog protocol (RFC-3164) does not include
 timezone information, but syslog-ng provides a solution by extending the
 syslog protocol to include the timezone in the log messages. The
 syslog-ng application also enables administrators to supply timezone
@@ -63,7 +63,7 @@ to the message using the following algorithm.
 
     ![]({{ site.baseurl}}/assets/images/caution.png) **CAUTION:** If syslog-ng
     OSE sends the message is to the destination using the legacy-syslog protocol
-    (RFC3164) which does not support timezone information in its timestamps,
+    (RFC-3164) which does not support timezone information in its timestamps,
     the timezone information cannot be encapsulated into the sent timestamp,
     so syslog-ng OSE will convert the hour:min values based on the explicitly
     specified timezone.

doc/_admin-guide/020_The_concepts_of_syslog-ng/007_The_structure_of_a_log_message/001_IETF_syslog_messages.md

@@ -83,7 +83,7 @@ The HEADER part contains the following elements:
 
 **NOTE:** The syslog-ng application supports other timestamp formats as
 well, like ISO, or the PIX extended format. The timestamp used in the
-IETF-syslog protocol is derived from RFC3339, which is based on ISO8601.
+IETF-syslog protocol is derived from RFC-3339, which is based on ISO8601.
 For details, see the ts-format() option in Global options.
 {: .notice--info}
 

doc/_admin-guide/020_The_concepts_of_syslog-ng/007_The_structure_of_a_log_message/002_EWMM_messages.md

@@ -28,7 +28,7 @@ The following is a sample log message in EWMM format.
 The message has the following parts:
 
 - The header of the complies with the
-    IETF-syslog messages RFC5424 message format,
+    IETF-syslog messages RFC-5424 message format,
     where the PROGRAM field is set to @syslog-ng, and the SDATA field is empty.
 
 - The MESSAGE part is in JSON format, and contains the actual message,

doc/_admin-guide/020_The_concepts_of_syslog-ng/008_Message_representation.md

@@ -4,8 +4,8 @@ id: adm-conc-msg
 description: >-
     When the syslog-ng OSE application receives a message, it automatically
     parses the message. The syslog-ng OSE application can automatically
-    parse log messages that conform to the RFC3164 (BSD or legacy-syslog) or
-    the RFC5424 (IETF-syslog) message formats. If syslog-ng OSE cannot parse
+    parse log messages that conform to the RFC-3164 (BSD or legacy-syslog) or
+    the RFC-5424 (IETF-syslog) message formats. If syslog-ng OSE cannot parse
     a message, it results in an error.
 ---
 
@@ -67,7 +67,7 @@ Soft macros (sometimes also called name-value pairs) are either
 built-in macros automatically generated from the log message (for
 example, ${HOST}), or custom user-created macros generated by using
 the syslog-ng pattern database or a CSV-parser. The SDATA fields of
-RFC5424-formatted log messages become soft macros as well. In
+RFC-5424 formatted log messages become soft macros as well. In
 contrast with hard macros, soft macros are writable and can be
 modified within syslog-ng OSE, for example, using rewrite rules.