RFC 4250
E46361
RFC 4250 is an Internet Engineering Task Force (IETF) document that defines and registers protocol parameters and message numbers used by the Secure Shell (SSH) protocol suite.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 4250 canonical | 9 |
How this entity was disambiguated
This entity first appeared as the object of triple T287033 — 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 4250 Context triple: [RFC 4251, obsoletes, RFC 4250]
-
A.
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.
-
B.
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.
-
C.
RFC 3410
RFC 3410 is an informational RFC that provides an overview, framework, and goals for the Simple Network Management Protocol version 3 (SNMPv3) and its related specifications.
-
D.
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.
-
E.
RFC 3415
RFC 3415 is an Internet standard that specifies the View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP), defining how access to management information is controlled.
- 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 4250 Target entity description: RFC 4250 is an Internet Engineering Task Force (IETF) document that defines and registers protocol parameters and message numbers used by the Secure Shell (SSH) protocol suite.
-
A.
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.
-
B.
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.
-
C.
RFC 3410
RFC 3410 is an informational RFC that provides an overview, framework, and goals for the Simple Network Management Protocol version 3 (SNMPv3) and its related specifications.
-
D.
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.
-
E.
RFC 3415
RFC 3415 is an Internet standard that specifies the View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP), defining how access to management information is controlled.
- F. None of above. chosen
Statements (48)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard-track document
ⓘ
Request for Comments ⓘ |
| appliesTo |
SSH
ⓘ
surface form:
SSH protocol suite
SSH ⓘ
surface form:
Secure Shell protocol
|
| area | Security ⓘ |
| category | Standards Track ⓘ |
| defines |
SSH message numbers
ⓘ
SSH protocol assigned numbers ⓘ SSH protocol parameters ⓘ algorithm name conventions for SSH ⓘ message number ranges for SSH ⓘ name allocation rules for SSH algorithms ⓘ procedures for registering new SSH parameters ⓘ |
| definesRegistry |
SSH Compression Algorithm Names
ⓘ
SSH Encryption Algorithm Names ⓘ SSH Key Exchange Method Names ⓘ SSH Language Tags ⓘ SHA-2 Data Integrity Verification for the Secure Shell (SSH) Transport Layer Protocol ⓘ
surface form:
SSH MAC Algorithm Names
SSH Message Numbers ⓘ SSH Protocol Parameters ⓘ |
| focusesOn |
SSH
ⓘ
surface form:
Secure Shell version 2
|
| format | text ⓘ |
| intendedAudience |
IANA registrants
ⓘ
protocol implementers ⓘ |
| language | English ⓘ |
| maintainedBy |
IANA
ⓘ
Internet Assigned Numbers Authority ⓘ |
| obsoletedBy |
RFC 4251
ⓘ
RFC 4253 ⓘ RFC 4254 ⓘ |
| obsoletes |
RFC 2433
ⓘ
RFC 2623 ⓘ |
| partOfSeries |
RFCs
ⓘ
surface form:
Request for Comments
|
| protocol | SSH ⓘ |
| protocolFamily | application layer ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| registers | SSH protocol parameters with IANA ⓘ |
| relatedTo |
RFC 4251
ⓘ
RFC 4252 ⓘ RFC 4253 ⓘ RFC 4254 ⓘ SSH ⓘ
surface form:
SSH-2
|
| standardizes | IANA registries for SSH ⓘ |
| status | Internet Standard-related specification ⓘ |
| title | The Secure Shell (SSH) Protocol Assigned Numbers ⓘ |
| type | technical specification ⓘ |
| useCase | interoperable SSH implementations ⓘ |
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 4250 Description of subject: RFC 4250 is an Internet Engineering Task Force (IETF) document that defines and registers protocol parameters and message numbers used by the Secure Shell (SSH) protocol suite.
Referenced by (9)
Full triples — surface form annotated when it differs from this entity's canonical label.