RFC 866
E197375
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.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 866 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T1631608 — 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 866 Context triple: [RFC 854, relatedRFC, RFC 866]
-
A.
RFC 860
RFC 860 is an Internet standard that defines the Telnet Timing Mark option, used to synchronize and manage timing in Telnet connections.
-
B.
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.
-
C.
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.
-
D.
RFC 1906
RFC 1906 is an Internet standard that specifies the transport mappings for SNMPv2, detailing how SNMP messages are carried over various network protocols.
-
E.
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.
- 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 866 Target entity description: 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.
-
A.
RFC 860
RFC 860 is an Internet standard that defines the Telnet Timing Mark option, used to synchronize and manage timing in Telnet connections.
-
B.
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.
-
C.
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.
-
D.
RFC 1906
RFC 1906 is an Internet standard that specifies the transport mappings for SNMPv2, detailing how SNMP messages are carried over various network protocols.
-
E.
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.
- F. None of above. chosen
Statements (45)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| accessMethod | Publicly available via RFC repositories ⓘ |
| category | Network protocol specification ⓘ |
| connectionDirection | Client initiates connection to server ⓘ |
| connectionModel | Client-server ⓘ |
| dataFormat | ASCII text ⓘ |
| definesService | Daytime service ⓘ |
| describes | Daytime Protocol ⓘ |
| documentSeries |
RFC series
ⓘ
linked to:
RFCs
|
| intendedClients | Any host capable of opening TCP or UDP connections ⓘ |
| language | English ⓘ |
| medium | Text document ⓘ |
| networkLayer | Application layer ⓘ |
| obsoletedBy | More modern time synchronization protocols ⓘ |
| operatesOver |
IP networks
ⓘ
Internet ⓘ
linked to:
the internet
|
| organizationContext |
Internet Engineering community
ⓘ
linked to:
IETF community
|
| originalPurpose | Provide a simple daytime service for testing and demonstration ⓘ |
| outputCharacteristic | Implementation-dependent date and time format ⓘ |
| portAssignmentAuthority | IANA ⓘ |
| portType | Well-known port ⓘ |
| protocolName | Daytime Protocol ⓘ |
| publicationMonth | May ⓘ |
| publicationYear | 1983 ⓘ |
| relatedTo |
RFC 867
ⓘ
Time Protocol ⓘ |
| responseContent |
Current date
ⓘ
Current time ⓘ |
| responseTermination | Server closes connection after sending time ⓘ |
| responseTrigger | Server sends time upon connection ⓘ |
| scope | Simple time reporting, not time synchronization ⓘ |
| securityConsideration | No authentication or encryption defined ⓘ |
| serviceFunction | Return current date and time as human-readable text ⓘ |
| standardType | Informational protocol specification ⓘ |
| status | Historic ⓘ |
| tcpPort | 13 ⓘ |
| terminology |
Daytime client
ⓘ
Daytime server ⓘ |
| title | Daytime Protocol ⓘ |
| transportProtocol |
TCP
ⓘ
linked to:
Transmission Control Protocol
UDP ⓘ |
| udpPort | 13 ⓘ |
| useCase |
Providing simple time-of-day information
ⓘ
Testing and debugging network connectivity ⓘ |
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 866 Description of subject: 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.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.