RFC 862
E194171
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.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 862 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1631604 — 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 862 Context triple: [RFC 854, relatedRFC, RFC 862]
-
A.
RFC 882
RFC 882 was an early Internet standard that originally specified the Domain Name System (DNS) protocol before being superseded by later RFCs such as RFC 1035.
-
B.
RFC 860
RFC 860 is an Internet standard that defines the Telnet Timing Mark option, used to synchronize and manage timing in Telnet connections.
-
C.
RFC 883
RFC 883 was an early Internet standard that originally specified the Domain Name System (DNS) before being superseded by later DNS specifications.
-
D.
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.
-
E.
RFC 950
RFC 950 is an Internet standard that defines the procedures and format for subnetting IP networks, extending the original IPv4 addressing scheme.
- 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 862 Target entity description: 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.
-
A.
RFC 882
RFC 882 was an early Internet standard that originally specified the Domain Name System (DNS) protocol before being superseded by later RFCs such as RFC 1035.
-
B.
RFC 860
RFC 860 is an Internet standard that defines the Telnet Timing Mark option, used to synchronize and manage timing in Telnet connections.
-
C.
RFC 883
RFC 883 was an early Internet standard that originally specified the Domain Name System (DNS) before being superseded by later DNS specifications.
-
D.
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.
-
E.
RFC 950
RFC 950 is an Internet standard that defines the procedures and format for subnetting IP networks, extending the original IPv4 addressing scheme.
- F. None of above. chosen
Statements (42)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| appliesTo |
hosts implementing TCP
ⓘ
hosts implementing UDP ⓘ |
| area |
the internet
ⓘ
surface form:
Internet
|
| category | Internet protocol ⓘ |
| connectionMode |
connection-oriented over TCP
ⓘ
connectionless over UDP ⓘ |
| definedIn | STD 20 ⓘ |
| definesRole |
Echo client
ⓘ
Echo server ⓘ |
| definesService | Echo service ⓘ |
| describesBehavior | server returns received data unchanged ⓘ |
| documentType | standards-track RFC ⓘ |
| echoes | arbitrary data payloads ⓘ |
| intendedUse |
latency measurement
ⓘ
simple reachability tests ⓘ throughput testing ⓘ |
| interactionModel | request-response ⓘ |
| language | English ⓘ |
| operatesOver | IP networks ⓘ |
| protocolType | application layer protocol ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
Internet Society ⓘ |
| purpose |
measurement
ⓘ
testing ⓘ troubleshooting ⓘ |
| relatedTo |
diagnostic protocols
ⓘ
network testing tools ⓘ |
| similarTo |
Discard Protocol
ⓘ
RFC 863 ⓘ |
| specifies | Echo Protocol ⓘ |
| standardizes |
Echo protocol message format
ⓘ
Echo protocol port assignment ⓘ |
| status | Historic ⓘ |
| title | Echo Protocol ⓘ |
| transportLayer |
Transmission Control Protocol
ⓘ
surface form:
TCP
UDP ⓘ |
| useCase |
network debugging
ⓘ
service availability checks ⓘ |
| usesPort |
TCP port 7
ⓘ
UDP port 7 ⓘ |
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 862 Description of subject: 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.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.