RFC 3447
E192659
RFC 3447 is an earlier IETF standard that specified the RSA Cryptography Standard (PKCS #1) before being superseded by RFC 8017.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 3447 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1711888 — 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 3447 Context triple: [RFC 8017, obsoletes, RFC 3447]
-
A.
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.
-
B.
RFC 3710
RFC 3710 is an IETF document that defines the purpose, structure, and procedures of the Internet Engineering Steering Group (IESG) within the Internet standards process.
-
C.
RFC 4254
RFC 4254 is the Internet standard that specifies the Secure Shell (SSH) connection protocol, defining how multiple logical channels are multiplexed over a single encrypted SSH transport.
-
D.
RFC 3546
RFC 3546 is an Internet Engineering Task Force (IETF) specification that originally defined the use of extensions within the Transport Layer Security (TLS) protocol.
-
E.
RFC 2467
RFC 2467 is an Internet Engineering Task Force (IETF) standards document that originally specified aspects of IPv6 over certain network technologies before later being superseded by RFC 6557.
- 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 3447 Target entity description: RFC 3447 is an earlier IETF standard that specified the RSA Cryptography Standard (PKCS #1) before being superseded by RFC 8017.
-
A.
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.
-
B.
RFC 3710
RFC 3710 is an IETF document that defines the purpose, structure, and procedures of the Internet Engineering Steering Group (IESG) within the Internet standards process.
-
C.
RFC 4254
RFC 4254 is the Internet standard that specifies the Secure Shell (SSH) connection protocol, defining how multiple logical channels are multiplexed over a single encrypted SSH transport.
-
D.
RFC 3546
RFC 3546 is an Internet Engineering Task Force (IETF) specification that originally defined the use of extensions within the Transport Layer Security (TLS) protocol.
-
E.
RFC 2467
RFC 2467 is an Internet Engineering Task Force (IETF) standards document that originally specified aspects of IPv6 over certain network technologies before later being superseded by RFC 6557.
- F. None of above. chosen
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
technical standard ⓘ |
| area | Security ⓘ |
| basedOn |
PKCS #1
ⓘ
surface form:
PKCS #1 Version 2.0
|
| category | Informational ⓘ |
| defines |
ASN.1 syntax for RSA cryptographic values
ⓘ
ASN.1 syntax for RSA keys ⓘ ASN.1 syntax for RSA parameters ⓘ PKCS #1 ⓘ
surface form:
EME-OAEP
PKCS #1 ⓘ
surface form:
EME-PKCS1-v1_5
PKCS #1 ⓘ
surface form:
EMSA-PKCS1-v1_5
EMSA-PSS ⓘ PKCS #1 ⓘ
surface form:
RSAES-OAEP
PKCS #1 ⓘ
surface form:
RSAES-PKCS1-v1_5
RSASSA-PKCS1-v1_5 ⓘ PSS (Probabilistic Signature Scheme) ⓘ
surface form:
RSASSA-PSS
|
| language | English ⓘ |
| obsoletedBy | RFC 8017 ⓘ |
| obsoletes | earlier PKCS #1 specifications ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| publisher | RFC Editor ⓘ |
| revises |
PKCS #1
ⓘ
surface form:
PKCS #1 Version 2.0
|
| RFCNumber | 3447 ⓘ |
| series |
RFCs
ⓘ
surface form:
Request for Comments
|
| shortTitle |
PKCS #1
ⓘ
surface form:
PKCS #1: RSA Cryptography Specifications Version 2.1
|
| specifies |
PKCS #1
ⓘ
surface form:
PKCS #1 Version 2.1
RSA ⓘ
surface form:
RSA Cryptography Standard
RSA ⓘ
surface form:
RSA encryption schemes
RSA key generation requirements ⓘ RSA key representation ⓘ RSA public-key cryptography ⓘ RSA signature schemes ⓘ encoding methods for RSA ⓘ |
| standardizes |
use of RSA with hash functions
ⓘ
use of RSA with padding schemes ⓘ |
| status | Obsoleted ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| targetAudience |
cryptographic protocol designers
ⓘ
implementers of cryptographic libraries ⓘ security protocol engineers ⓘ |
| title |
PKCS #1
ⓘ
surface form:
Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography Specifications Version 2.1
|
| topic |
RSA
ⓘ
cryptographic standards ⓘ public-key cryptography ⓘ |
| updates | PKCS #1 ⓘ |
| usedIn |
IPsec implementations
ⓘ
S/MIME implementations ⓘ TLS 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 3447 Description of subject: RFC 3447 is an earlier IETF standard that specified the RSA Cryptography Standard (PKCS #1) before being superseded by RFC 8017.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.