RFC 2228
E52457
RFC 2228 is an Internet standard that extends the File Transfer Protocol (FTP) with security mechanisms such as authentication, integrity, and confidentiality.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 2228 canonical | 5 |
How this entity was disambiguated
This entity first appeared as the object of triple T338792 — 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 2228 Context triple: [FTPS, definedIn, RFC 2228]
-
A.
RFC 2419
RFC 2419 is an earlier Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4253.
-
B.
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.
-
C.
RFC 3720
RFC 3720 is the Internet Engineering Task Force (IETF) standard that specifies the Internet Small Computer Systems Interface (iSCSI) protocol for transporting SCSI commands over IP networks.
-
D.
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.
-
E.
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.
- 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 2228 Target entity description: RFC 2228 is an Internet standard that extends the File Transfer Protocol (FTP) with security mechanisms such as authentication, integrity, and confidentiality.
-
A.
RFC 2419
RFC 2419 is an earlier Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4253.
-
B.
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.
-
C.
RFC 3720
RFC 3720 is the Internet Engineering Task Force (IETF) standard that specifies the Internet Small Computer Systems Interface (iSCSI) protocol for transporting SCSI commands over IP networks.
-
D.
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.
-
E.
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.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| appliesTo |
FTP control connection
ⓘ
FTP data connection ⓘ |
| area | Security ⓘ |
| category |
FTP extension
ⓘ
network security standard ⓘ |
| definesCommand |
ADAT
ⓘ
AUTH ⓘ CCC ⓘ CONF ⓘ ENC ⓘ MIC ⓘ PBSZ ⓘ PROT ⓘ |
| definesMechanism |
access control
ⓘ
authentication ⓘ confidentiality ⓘ integrity ⓘ |
| definesReplyCode |
234
ⓘ
334 ⓘ 631 ⓘ 632 ⓘ 633 ⓘ 634 ⓘ 635 ⓘ 636 ⓘ 637 ⓘ 638 ⓘ 639 ⓘ |
| extendsProtocol |
FTP
ⓘ
surface form:
File Transfer Protocol
|
| goal | to add security to FTP without changing its basic model ⓘ |
| introducesConcept |
clear command channel using CCC
ⓘ
confidentiality protection using CONF ⓘ data channel protection level using PROT ⓘ message integrity check using MIC ⓘ privacy and integrity using ENC ⓘ protection buffer size using PBSZ ⓘ security data exchange using ADAT ⓘ |
| provides | mechanisms for secure FTP sessions ⓘ |
| standardizes | security extensions for FTP ⓘ |
| status | Proposed Standard ⓘ |
| supports |
negotiation of security mechanisms
ⓘ
protection of FTP control channel ⓘ protection of FTP data channel ⓘ |
| title |
FTPS
ⓘ
surface form:
FTP Security Extensions
|
| updates | FTP protocol security handling ⓘ |
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 2228 Description of subject: RFC 2228 is an Internet standard that extends the File Transfer Protocol (FTP) with security mechanisms such as authentication, integrity, and confidentiality.
Referenced by (5)
Full triples — surface form annotated when it differs from this entity's canonical label.