RFC 860
E190515
RFC 860 is an Internet standard that defines the Telnet Timing Mark option, used to synchronize and manage timing in Telnet connections.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 860 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T1631602 — 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 860 Context triple: [RFC 854, relatedRFC, RFC 860]
-
A.
RFC 760
RFC 760 is an early Internet standard document authored by Jon Postel that specifies the original Internet Protocol (IP).
-
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 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 783
RFC 783 is the original specification that defines the Trivial File Transfer Protocol (TFTP), a simple protocol for transferring files over a network.
-
E.
RFC 858
RFC 858 is an early Internet standard that defines the Telnet protocol’s status option, specifying how a Telnet client and server can exchange information about their current status.
- 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 860 Target entity description: RFC 860 is an Internet standard that defines the Telnet Timing Mark option, used to synchronize and manage timing in Telnet connections.
-
A.
RFC 760
RFC 760 is an early Internet standard document authored by Jon Postel that specifies the original Internet Protocol (IP).
-
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 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 783
RFC 783 is the original specification that defines the Trivial File Transfer Protocol (TFTP), a simple protocol for transferring files over a network.
-
E.
RFC 858
RFC 858 is an early Internet standard that defines the Telnet protocol’s status option, specifying how a Telnet client and server can exchange information about their current status.
- F. None of above. chosen
Statements (39)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| aimsTo |
improve reliability of interactive Telnet communication
ⓘ
provide a standard timing control mechanism for Telnet ⓘ |
| appliesTo | TCP-based Telnet connections ⓘ |
| area | Application layer ⓘ |
| category | Standards Track ⓘ |
| concerns |
management of timing in interactive Telnet sessions
ⓘ
synchronization of Telnet client and server ⓘ |
| defines |
Telnet Timing Mark option
ⓘ
linked to:
Telnet Timing Mark Option
|
| definesConcept |
Telnet option negotiation for timing
ⓘ
Timing Mark ⓘ |
| documentType | technical specification ⓘ |
| field |
Internet protocols
ⓘ
computer networking ⓘ |
| hasKeyword |
Telnet
ⓘ
Timing Mark ⓘ interactive protocols ⓘ synchronization ⓘ |
| isPartOf |
RFC series
ⓘ
linked to:
RFCs
|
| language | English ⓘ |
| layer | Application layer of the Internet protocol suite ⓘ |
| networkProtocol | Telnet ⓘ |
| partOf | Telnet protocol option set ⓘ |
| protocolNumber | Telnet option ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
Internet Society ⓘ |
| relatesToProtocol | Telnet ⓘ |
| series |
RFC series
ⓘ
linked to:
RFCs
|
| specifies |
Telnet option negotiation for Timing Mark
ⓘ
linked to:
Telnet Timing Mark Option
semantics of the Telnet Timing Mark signal ⓘ use of Timing Mark to synchronize Telnet data streams ⓘ |
| standardizes |
synchronization mechanism for Telnet connections
ⓘ
timing management for Telnet connections ⓘ |
| status | Internet Standard ⓘ |
| title | Telnet Timing Mark Option ⓘ |
| typeOfStandard | protocol option specification ⓘ |
| useCase |
interactive terminal sessions over networks
ⓘ
synchronizing remote command execution over Telnet ⓘ |
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 860 Description of subject: RFC 860 is an Internet standard that defines the Telnet Timing Mark option, used to synchronize and manage timing in Telnet connections.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.