RFC 867
E198538
RFC 867 is an early Internet standard that defines the "Daytime Protocol," a simple service for returning the current date and time over a network connection.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 867 canonical | 3 |
How this entity was disambiguated
This entity first appeared as the object of triple T1631609 — 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 867 Context triple: [RFC 854, relatedRFC, RFC 867]
-
A.
RFC 862
RFC 862 is an Internet standard that specifies the Echo Protocol, a simple service used primarily for testing and measurement by sending data to a server that returns it unchanged.
-
B.
RFC 857
RFC 857 is an Internet standard that defines the Telnet protocol option for echoing characters, specifying how user input is echoed back in Telnet sessions.
-
C.
RFC 866
RFC 866 is an early Internet standard that specifies the "Daytime Protocol," a simple service for returning the current date and time over a network connection.
-
D.
RFC 860
RFC 860 is an Internet standard that defines the Telnet Timing Mark option, used to synchronize and manage timing in Telnet connections.
-
E.
RFC 855
RFC 855 is an Internet standards document that specifies the Telnet protocol’s options and mechanisms for remote terminal communication over TCP/IP networks.
- 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 867 Target entity description: RFC 867 is an early Internet standard that defines the "Daytime Protocol," a simple service for returning the current date and time over a network connection.
-
A.
RFC 862
RFC 862 is an Internet standard that specifies the Echo Protocol, a simple service used primarily for testing and measurement by sending data to a server that returns it unchanged.
-
B.
RFC 857
RFC 857 is an Internet standard that defines the Telnet protocol option for echoing characters, specifying how user input is echoed back in Telnet sessions.
-
C.
RFC 866
RFC 866 is an early Internet standard that specifies the "Daytime Protocol," a simple service for returning the current date and time over a network connection.
-
D.
RFC 860
RFC 860 is an Internet standard that defines the Telnet Timing Mark option, used to synchronize and manage timing in Telnet connections.
-
E.
RFC 855
RFC 855 is an Internet standards document that specifies the Telnet protocol’s options and mechanisms for remote terminal communication over TCP/IP networks.
- F. None of above. chosen
Statements (41)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| category | Network protocol specification ⓘ |
| clientBehavior | Connects to server and reads date and time ⓘ |
| connectionDirection | Server listens on well-known port ⓘ |
| connectionModel | Client-server ⓘ |
| dataFormat | Human-readable ASCII text ⓘ |
| defines | Daytime Protocol ⓘ |
| designGoal |
Ease of implementation
ⓘ
Simplicity ⓘ |
| documentType | Standards Track (historic classification) ⓘ |
| exampleImplementation | Daytime service on many Unix systems ⓘ |
| hasPortNumber | 13 ⓘ |
| identifier | RFC 867 self-link ⓘ |
| intendedEnvironment |
the internet
ⓘ
surface form:
Internet
TCP/IP networks ⓘ |
| layerInOSIModel | Application layer ⓘ |
| protocolFamily |
TCP/IP
ⓘ
surface form:
Internet Protocol Suite
|
| protocolType | Application layer protocol ⓘ |
| publicationMonth | May ⓘ |
| publicationYear | 1983 ⓘ |
| publishedBy | Internet Engineering Task Force ⓘ |
| publishedInSeries |
RFCs
ⓘ
surface form:
RFC series
|
| relatedTo |
RFC 868
ⓘ
Time Protocol ⓘ |
| requires | TCP or UDP stack ⓘ |
| responseContent |
Current date
ⓘ
Current time ⓘ |
| responseEncoding | ASCII ⓘ |
| serverBehavior | Sends date and time then closes connection ⓘ |
| serviceProvided | Return current date and time ⓘ |
| status | Historic ⓘ |
| supersededBy | More modern time synchronization protocols ⓘ |
| tcpPort | 13 ⓘ |
| title | Daytime Protocol ⓘ |
| transportProtocol |
TCP
ⓘ
UDP ⓘ |
| udpPort | 13 ⓘ |
| useCase |
Providing simple time-of-day information
ⓘ
Testing network connectivity ⓘ |
| usesPortNumberAssignedBy | IANA ⓘ |
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 867 Description of subject: RFC 867 is an early Internet standard that defines the "Daytime Protocol," a simple service for returning the current date and time over a network connection.
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.