Review request: RFC text formatting

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

Author: mrgarris0n

_data/external_links.yml

@@ -430,25 +430,30 @@ welf:
 
 ### RFC links ###
 
+rfc-3164:
+  id: rfc-3164
+  url: https://www.ietf.org/rfc/rfc3164.txt
+  title: [ "RFC-3164" ]
+
 rfc-3526:
   id: rfc-3526
   url: https://www.ietf.org/rfc/rfc3526.txt
-  title: [ "RFC 3526" ]
+  title: [ "RFC-3526" ]
 
 rfc-4180:
   id: rfc-4180
   url: https://tools.ietf.org/html/rfc4180
-  title: [ "RFC4180 CSV format" ]
+  title: [ "RFC-4180 CSV format" ]
 
 rfc-4627:
   id: rfc-4627
   url: https://tools.ietf.org/html/rfc4627
-  title: [ "RFC 4627" ]
+  title: [ "RFC-4627" ]
 
 rfc-5424:
   id: rfc-5424
   url: https://tools.ietf.org/html/rfc5424#page-8
-  title: [ "RFC 5424-compliant form" ]
+  title: [ "RFC-5424" ]
 
 rfc-base64:
   id: rfc-base64
@@ -468,7 +473,7 @@ rfc-ietf-syslog-proto:
 rfc-octet:
   id: rfc-octet
   url: https://tools.ietf.org/html/rfc6587#section-3.4.1
-  title: [ "the octet counting method described in RFC6587" ]
+  title: [ "the octet counting method described in RFC-6587" ]
 
 rfc-sdid:
   id: rfc-sdid

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

@@ -7,11 +7,11 @@ description: >-
 
 Currently there are two standard syslog message formats:
 
-- The old standard described in RFC 3164 (also called the BSD-syslog
+- The old standard described in RFC-3164 (also called the BSD-syslog
     or the legacy-syslog protocol): see
     BSD-syslog or legacy-syslog messages.
 
-- The new standard described in RFC 5424 (also called the IETF-syslog
+- The new standard described in RFC-5424 (also called the IETF-syslog
     protocol): see IETF-syslog messages.
 
 - The Enterprise-wide message model or EWMM allows you to deliver

doc/_admin-guide/060_Sources/170_Syslog/README.md

@@ -15,7 +15,7 @@ BSD-syslog or legacy-syslog messages
 if they are sent using the IETF-syslog protocol.
 
 In syslog-ng OSE versions 3.1 and earlier, the syslog() driver could
-handle only messages in the IETF-syslog (RFC 5424-26) format.
+handle only messages in the IETF-syslog (RFC-5424) format.
 
 For the list of available optional parameters, see
 syslog() source options.

doc/_admin-guide/070_Destinations/290_Sumologic/README.md

@@ -77,7 +77,7 @@ destinations with syslog-ng OSE has the following limitations:
 
 - The minimum required version of syslog-ng OSE is version 3.27.1.
 
-- Message format must be in RFC 5424-compliant form. Messages over
+- Message format must be in RFC-5424 compliant form. Messages over
     64KB in length are truncated.
 
     For more information about the message format limitations, see the
@@ -86,10 +86,8 @@ destinations with syslog-ng OSE has the following limitations:
 - 64 characters long Sumo Logic tokens must be passed in the message
     body.
 
-    NOTE: Although RFC 5424
-    limits the structured data field
-    (SD-ID) to 32
-    characters, Sumo Logic tokens are 64 characters long. If your
+    NOTE: Although RFC-5424 limits the structured data field
+    (SD-ID) to 32 characters, Sumo Logic tokens are 64 characters long. If your
     logging client enforces the 32 characters length limit, you must
     pass the token in the message body.
 

doc/_admin-guide/100_TLS-encrypted_message_transfer/004_TLS_options.md

@@ -57,7 +57,7 @@ of the files must be .r0.
 generated using the openssl dhparam utility. Note that syslog-ng OSE
 supports only DH parameter files in the PEM format. If you do not set
 this parameter, syslog-ng OSE uses the 2048-bit MODP Group, as
-described in RFC 3526.
+described in RFC-3526.
 
 ## ecdh-curve-list()
 

doc/_admin-guide/120_Parser/003_JSON_parser/README.md

@@ -7,7 +7,7 @@ description: >-
     JavaScript Object Notation (JSON) is a text-based open standard designed
     for human-readable data interchange. It is used primarily to transmit
     data between a server and web application, serving as an alternative to
-    XML. It is described in RFC 4627.
+    XML. It is described in RFC-4627.
     The syslog-ng OSE application can separate parts of incoming
     JSON-encoded log messages to name-value pairs. For details on using
     value-pairs in syslog-ng OSE see

doc/_admin-guide/120_Parser/004_XML_parser/README.md

@@ -133,7 +133,7 @@ any of the following options:
 
   - In the case of TCP, you can encapsulate and send the document in
         syslog-protocol format, and use a syslog() source. Make sure
-        that the message conforms to the octet counting method described in RFC6587.
+        that the message conforms to the octet counting method described in RFC-6587.
 
     For example:
 

doc/_admin-guide/140_Enriching_log_messages_with_external_data/000_Adding_metadata_from_external_file/README.md

@@ -38,7 +38,7 @@ the IP address, and adds the host-role field to the log message.
 
 ## The database file
 
-The database file must comply with the RFC4180 CSV format,
+The database file must comply with the RFC-4180 CSV format,
 with the following exceptions and limitations:
 
 - The values of the CSV-file cannot contain line-breaks

doc/_admin-guide/200_About/002_Glossary.md

@@ -146,7 +146,7 @@ A name that identifies a host on the network.
 ### IETF-syslog protocol
 
 The syslog-protocol standard developed by the Internet Engineering Task
-Force (IETF), described in RFC 5424-5427.
+Force (IETF), described in RFC-5424.
 
 ## K