RFC 3164
E663653
RFC 3164 is an IETF specification that defines the traditional BSD syslog protocol used for transmitting system log messages over IP networks.
All labels observed (3)
| Label | Occurrences |
|---|---|
| RFC 3164 canonical | 3 |
| The BSD Syslog Protocol | 1 |
| Transmission of Syslog Messages over UDP | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T7427971 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 3164 Context triple: [Syslog, definedIn, RFC 3164]
-
A.
RFC 1653
RFC 1653 is an older Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
-
B.
RFC 1664
RFC 1664 is an early Internet standards document that defined a now-obsolete mechanism related to email or messaging services, later superseded by RFC 1901.
-
C.
RFC 1655
RFC 1655 is an early Internet standards document that specified the original Simple Network Management Protocol (SNMP) version 2 framework before being superseded by later revisions.
-
D.
Syslog
Syslog is a standard protocol used for message logging and event notification across network devices and computer systems.
-
E.
RFC 1652
RFC 1652 is an early Internet standards document that defines the 8BITMIME extension for SMTP, enabling the transfer of 8-bit character data in email.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 3164 Target entity description: RFC 3164 is an IETF specification that defines the traditional BSD syslog protocol used for transmitting system log messages over IP networks.
-
A.
RFC 1653
RFC 1653 is an older Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
-
B.
RFC 1664
RFC 1664 is an early Internet standards document that defined a now-obsolete mechanism related to email or messaging services, later superseded by RFC 1901.
-
C.
RFC 1655
RFC 1655 is an early Internet standards document that specified the original Simple Network Management Protocol (SNMP) version 2 framework before being superseded by later revisions.
-
D.
Syslog
Syslog is a standard protocol used for message logging and event notification across network devices and computer systems.
-
E.
RFC 1652
RFC 1652 is an early Internet standards document that defines the 8BITMIME extension for SMTP, enabling the transfer of 8-bit character data in email.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
technical standard ⓘ |
| appliesTo |
IP networks
ⓘ
system log messages ⓘ |
| area | Security ⓘ |
| author | C. Lonvick ⓘ |
| category | Informational RFC ⓘ |
| defines |
BSD syslog protocol
ⓘ
linked to:
Syslog
format of syslog messages ⓘ traditional syslog protocol ⓘ transport of syslog messages over UDP ⓘ |
| definesField |
CONTENT in syslog message
ⓘ
TAG in syslog message ⓘ hostname in syslog header ⓘ timestamp in syslog header ⓘ |
| documentType | Standards-related specification ⓘ |
| documentURI | https://www.rfc-editor.org/rfc/rfc3164 ⓘ |
| focusesOn | BSD-based systems ⓘ |
| intendedUse |
event reporting
ⓘ
logging ⓘ system monitoring ⓘ |
| keyword |
logging
ⓘ
management ⓘ security ⓘ syslog ⓘ |
| language | English ⓘ |
| obsoletedBy |
RFC 5424
ⓘ
RFC 5425 ⓘ RFC 5426 ⓘ |
| partOfSeries |
Request for Comments
ⓘ
linked to:
RFCs
|
| publicationDate | 2001-08 ⓘ |
| publicationYear | 2001 ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| relatedTo | syslog ⓘ |
| RFCNumber | 3164 ⓘ |
| specifies |
facility codes for syslog
ⓘ
severity levels for syslog ⓘ syslog message HEADER part ⓘ syslog message MSG part ⓘ syslog message PRI part ⓘ |
| specifiesEncoding | US-ASCII ⓘ |
| status | Informational ⓘ |
| stream |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| title |
The BSD Syslog Protocol
ⓘ
linked to:
RFC 3164
|
| usesDefaultPort | 514 ⓘ |
| usesTransportProtocol | UDP ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: RFC 3164 Description of subject: RFC 3164 is an IETF specification that defines the traditional BSD syslog protocol used for transmitting system log messages over IP networks.
Referenced by (5)
Full triples — surface form annotated when it differs from this entity's canonical label.