RFC 2419
E50648
RFC 2419 is an earlier Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4253.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 2419 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T311037 — 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 2419 Context triple: [RFC 4253, obsoletes, RFC 2419]
-
A.
RFC 1939
RFC 1939 is the Internet standard document that specifies the Post Office Protocol version 3 (POP3) used for retrieving email from a mail server.
-
B.
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.
-
C.
RFC 3414
RFC 3414 is an Internet standard that specifies the User-based Security Model (USM) for securing SNMPv3 communications, including authentication and privacy mechanisms.
-
D.
RFC 3417
RFC 3417 is an Internet standard that specifies the transport mappings for the Simple Network Management Protocol (SNMP), defining how SNMP messages are carried over various network protocols such as UDP.
-
E.
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.
- 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 2419 Target entity description: RFC 2419 is an earlier Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4253.
-
A.
RFC 1939
RFC 1939 is the Internet standard document that specifies the Post Office Protocol version 3 (POP3) used for retrieving email from a mail server.
-
B.
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.
-
C.
RFC 3414
RFC 3414 is an Internet standard that specifies the User-based Security Model (USM) for securing SNMPv3 communications, including authentication and privacy mechanisms.
-
D.
RFC 3417
RFC 3417 is an Internet standard that specifies the transport mappings for the Simple Network Management Protocol (SNMP), defining how SNMP messages are carried over various network protocols such as UDP.
-
E.
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.
- F. None of above. chosen
Statements (26)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| appliesTo |
Internet
ⓘ
linked to:
the internet
TCP/IP networks ⓘ |
| area | Security ⓘ |
| category | Standards Track ⓘ |
| defines | key exchange algorithm for SSH transport layer ⓘ |
| focus |
cryptographic key exchange
ⓘ
security for SSH connections ⓘ |
| format | Text ⓘ |
| language | English ⓘ |
| number | 2419 ⓘ |
| obsoletedBy | RFC 4253 ⓘ |
| partOfSeries | RFC series ⓘ |
| protocolLayer | Transport layer ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| relatedToProtocol |
SSH
ⓘ
Secure Shell ⓘ
linked to:
SSH
|
| replacedBy | RFC 4253 ⓘ |
| seriesNumber | 2419 ⓘ |
| standardizes | SSH key exchange mechanism ⓘ |
| standardsBody |
IETF Network Working Group
ⓘ
linked to:
Network Working Group
|
| status | Obsoleted ⓘ |
| title |
Key Exchange Algorithm for the Secure Shell (SSH) Transport Layer Protocol
ⓘ
linked to:
Diffie–Hellman key exchange
|
| updatesProtocol | SSH Transport Layer Protocol ⓘ |
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 2419 Description of subject: RFC 2419 is an earlier Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4253.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.