RFC 854
E35267
RFC 854 is the foundational Internet standard that specifies the Telnet protocol for remote, text-based communication over TCP/IP networks.
All labels observed (3)
| Label | Occurrences |
|---|---|
| RFC 854 canonical | 2 |
| Telnet Option Specifications | 1 |
| Telnet option specifications | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T270607 — 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 854 Context triple: [Telnet, definedInRFC, RFC 854]
-
A.
RFC 4251
RFC 4251 is the core specification that defines the architecture and protocol framework of the Secure Shell (SSH) protocol used for secure remote communication.
-
B.
RFC 4252
RFC 4252 is an Internet standard that specifies the authentication protocol used by Secure Shell (SSH) for secure remote login and other network services.
-
C.
RFC 2131
RFC 2131 is the Internet Engineering Task Force (IETF) standard that specifies the Dynamic Host Configuration Protocol (DHCP) used for automatic IP address and configuration assignment in IP networks.
-
D.
RFC 792
RFC 792 is the Internet standard document that specifies the Internet Control Message Protocol (ICMP), which is used for network diagnostics and error reporting in IP networks.
-
E.
RFC 4253
RFC 4253 is the Internet standard that specifies the Secure Shell (SSH) transport layer protocol, including encryption, key exchange, and server authentication mechanisms.
- 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 854 Target entity description: RFC 854 is the foundational Internet standard that specifies the Telnet protocol for remote, text-based communication over TCP/IP networks.
-
A.
RFC 4251
RFC 4251 is the core specification that defines the architecture and protocol framework of the Secure Shell (SSH) protocol used for secure remote communication.
-
B.
RFC 4252
RFC 4252 is an Internet standard that specifies the authentication protocol used by Secure Shell (SSH) for secure remote login and other network services.
-
C.
RFC 2131
RFC 2131 is the Internet Engineering Task Force (IETF) standard that specifies the Dynamic Host Configuration Protocol (DHCP) used for automatic IP address and configuration assignment in IP networks.
-
D.
RFC 792
RFC 792 is the Internet standard document that specifies the Internet Control Message Protocol (ICMP), which is used for network diagnostics and error reporting in IP networks.
-
E.
RFC 4253
RFC 4253 is the Internet standard that specifies the Secure Shell (SSH) transport layer protocol, including encryption, key exchange, and server authentication mechanisms.
- F. None of above. chosen
Statements (77)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ network protocol specification ⓘ |
| appliesTo |
client-server terminal sessions
ⓘ
interactive text sessions over TCP ⓘ |
| area |
remote terminal access
ⓘ
text-based communication ⓘ |
| category | Standards Track ⓘ |
| defines |
Telnet DO command
ⓘ
Telnet ⓘ
surface form:
Telnet DONT command
Telnet IAC byte ⓘ Telnet ⓘ
surface form:
Telnet WILL command
Telnet ⓘ
surface form:
Telnet WONT command
Telnet abort output signal ⓘ Telnet ⓘ
surface form:
Telnet are-you-there signal
Telnet binary transmission mode ⓘ Telnet break signal ⓘ Telnet command structure ⓘ Telnet connection semantics ⓘ Telnet control characters ⓘ Telnet data representation ⓘ Telnet echo handling ⓘ Telnet ⓘ
surface form:
Telnet end-of-line conventions
Telnet end-of-record marker ⓘ Telnet erase character function ⓘ Telnet erase line function ⓘ Telnet go-ahead signal ⓘ Telnet interrupt process signal ⓘ Telnet network virtual terminal concept ⓘ Telnet option negotiation ⓘ Telnet option subnegotiation ⓘ Telnet ⓘ
surface form:
Telnet timing and synchronization commands
interpret-as-command mechanism ⓘ |
| historicalRole | foundational standard for early Internet remote access ⓘ |
| influenced |
SSH protocol design
ⓘ
later remote shell protocols ⓘ |
| networkLayer | application layer ⓘ |
| protocolSpecified | Telnet ⓘ |
| purpose |
to enable interoperable text-based communication between hosts
ⓘ
to specify a standard protocol for remote terminal access over TCP/IP ⓘ |
| relatedProtocol | Telnet ⓘ |
| relatedRFC |
RFC 855
ⓘ
RFC 856 ⓘ RFC 857 ⓘ RFC 858 ⓘ RFC 858 ⓘ
surface form:
RFC 859
RFC 860 ⓘ RFC 861 ⓘ RFC 862 ⓘ RFC 863 ⓘ RFC 864 ⓘ RFC 865 ⓘ RFC 866 ⓘ RFC 867 ⓘ RFC 868 ⓘ RFC 869 ⓘ RFC 870 ⓘ RFC 871 ⓘ RFC 872 ⓘ RFC 873 ⓘ RFC 874 ⓘ RFC 875 ⓘ RFC 876 ⓘ RFC 877 ⓘ RFC 878 ⓘ RFC 879 ⓘ |
| securityProperties |
does not provide encryption
ⓘ
does not provide strong authentication ⓘ transmits data in cleartext ⓘ |
| standardizes |
handling of control functions across heterogeneous systems
ⓘ
negotiation of terminal capabilities ⓘ |
| status | Internet Standard ⓘ |
| title |
Telnet
ⓘ
surface form:
Telnet Protocol Specification
|
| transportProtocol |
Transmission Control Protocol
ⓘ
surface form:
TCP
|
| useCase |
remote command-line administration
ⓘ
remote login to timesharing systems ⓘ |
| usesUnderlyingProtocolSuite | TCP/IP ⓘ |
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 854 Description of subject: RFC 854 is the foundational Internet standard that specifies the Telnet protocol for remote, text-based communication over TCP/IP networks.
Referenced by (4)
Full triples — surface form annotated when it differs from this entity's canonical label.