RFC 857
E186435
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.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 857 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1631599 — 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 857 Context triple: [RFC 854, relatedRFC, RFC 857]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
RFC 1195
RFC 1195 is the IETF standard that extends the IS-IS routing protocol to support multiple network layer protocols, including IP.
-
E.
RFC 3207
RFC 3207 is the Internet standard that specifies the STARTTLS extension for upgrading plain text email connections to use TLS encryption in SMTP.
- 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 857 Target entity description: 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.
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
RFC 1195
RFC 1195 is the IETF standard that extends the IS-IS routing protocol to support multiple network layer protocols, including IP.
-
E.
RFC 3207
RFC 3207 is the Internet standard that specifies the STARTTLS extension for upgrading plain text email connections to use TLS encryption in SMTP.
- F. None of above. chosen
Statements (28)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| appliesTo | interactive Telnet sessions ⓘ |
| area | Application layer ⓘ |
| category | Internet protocol specification ⓘ |
| concerns | local vs remote echo in Telnet ⓘ |
| defines |
Telnet Echo option
ⓘ
Telnet protocol option for echoing characters ⓘ |
| definesRoleOf |
client in echoing characters
ⓘ
server in echoing characters ⓘ |
| documentType | Standards-track RFC ⓘ |
| ensures | consistent echo behavior across Telnet implementations ⓘ |
| language | English ⓘ |
| layer | Application layer of the Internet protocol suite ⓘ |
| partOf |
RFC 854
ⓘ
surface form:
Telnet option specifications
|
| protocolOptionCode | 1 ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
Internet Society ⓘ |
| relatedTo |
RFC 854
ⓘ
Telnet ⓘ
surface form:
Telnet protocol
|
| relatesTo |
Telnet
ⓘ
surface form:
Telnet option negotiation
|
| specifies | how user input is echoed back in Telnet sessions ⓘ |
| specifiesProtocol | Telnet ⓘ |
| standardizesBehaviorOf | character echo in Telnet ⓘ |
| status | Internet Standard ⓘ |
| title | Telnet Echo Option ⓘ |
| useCase | remote terminal access ⓘ |
| usesMechanism | WILL/WONT/DO/DONT Telnet option negotiation ⓘ |
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 857 Description of subject: 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.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.