RFC 2623
E260811
RFC 2623 was an early Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4250.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 2623 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T2383371 — 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 2623 Context triple: [RFC 4250, obsoletes, RFC 2623]
-
A.
RFC 2026
RFC 2026 is an Internet Engineering Task Force (IETF) document that defines the standardization process and procedures for developing and approving Internet Standards.
-
B.
RFC 1663
RFC 1663 is an early Internet standards document that specifies the Point-to-Point Protocol (PPP) for serial line communication.
-
C.
RFC 2228
RFC 2228 is an Internet standard that extends the File Transfer Protocol (FTP) with security mechanisms such as authentication, integrity, and confidentiality.
-
D.
RFC 1652
RFC 1652 is an early Internet standards document that defines the 8BITMIME extension for SMTP, enabling the transfer of 8-bit character data in email.
-
E.
RFC 2060
RFC 2060 was the original specification of the Internet Message Access Protocol version 4 (IMAP4), defining how email clients access and manage messages on a mail server.
- 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 2623 Target entity description: RFC 2623 was an early Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4250.
-
A.
RFC 2026
RFC 2026 is an Internet Engineering Task Force (IETF) document that defines the standardization process and procedures for developing and approving Internet Standards.
-
B.
RFC 1663
RFC 1663 is an early Internet standards document that specifies the Point-to-Point Protocol (PPP) for serial line communication.
-
C.
RFC 2228
RFC 2228 is an Internet standard that extends the File Transfer Protocol (FTP) with security mechanisms such as authentication, integrity, and confidentiality.
-
D.
RFC 1652
RFC 1652 is an early Internet standards document that defines the 8BITMIME extension for SMTP, enabling the transfer of 8-bit character data in email.
-
E.
RFC 2060
RFC 2060 was the original specification of the Internet Message Access Protocol version 4 (IMAP4), defining how email clients access and manage messages on a mail server.
- F. None of above. chosen
Statements (27)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| abbreviation | RFC 2623 ⓘ |
| area |
Internet
ⓘ
linked to:
the internet
Security ⓘ |
| category | Standards Track ⓘ |
| definesUsageOf | SSH for PPP transport ⓘ |
| documentType | Technical specification ⓘ |
| focusesOn | Secure transport of PPP frames over SSH ⓘ |
| governingBody | Internet Engineering Steering Group ⓘ |
| hasSuccessor | RFC 4250 ⓘ |
| language | English ⓘ |
| obsoletedBy | RFC 4250 ⓘ |
| partOf |
Internet Standards
ⓘ
linked to:
Internet Standard
|
| protocolLayer | Data link layer ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| relatedToProtocol |
PPP
ⓘ
Point-to-Point Protocol ⓘ SSH ⓘ Secure Shell ⓘ
linked to:
SSH
|
| series | STD document series ⓘ |
| standardizes | PPP over SSH ⓘ |
| status | Obsoleted ⓘ |
| title | PPP over Secure Shell (SSH) ⓘ |
| usesSecurityMechanism |
Authentication
ⓘ
Encryption ⓘ |
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 2623 Description of subject: RFC 2623 was an early Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4250.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.