RFC 4880
E299181
RFC 4880 is the Internet Engineering Task Force (IETF) standard that defines the OpenPGP message format for encrypted and signed data.
All labels observed (10)
| Label | Occurrences |
|---|---|
| OpenPGP | 6 |
| OpenPGP standard | 3 |
| RFC 4880 canonical | 3 |
| OpenPGP message format | 2 |
| OpenPGP Message Format | 1 |
| OpenPGP notation data subpackets | 1 |
| OpenPGP preferred algorithms subpackets | 1 |
| OpenPGP specification | 1 |
| OpenPGP trust packets | 1 |
| RFC 4880: OpenPGP Message Format | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T2792422 — 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 4880 Context triple: [GNU Privacy Guard, supportsStandard, RFC 4880]
-
A.
RFC 8017
RFC 8017 is the Internet standard that specifies the RSA Cryptography Standard (PKCS #1), defining algorithms and formats for RSA encryption and digital signatures.
-
B.
PGP
PGP (Pretty Good Privacy) is an encryption program that provides cryptographic privacy and authentication for data communication, most notably for securing emails and files.
-
C.
RFC 2104
RFC 2104 is the Internet standard document that defines the HMAC (Hash-based Message Authentication Code) algorithm used for data integrity and authentication in cryptographic protocols.
-
D.
RFC 3447
RFC 3447 is an earlier IETF standard that specified the RSA Cryptography Standard (PKCS #1) before being superseded by RFC 8017.
-
E.
RFC 4380
RFC 4380 is an IETF standard that specifies the Teredo protocol for providing IPv6 connectivity to nodes located behind IPv4 network address translators (NATs).
- 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 4880 Target entity description: RFC 4880 is the Internet Engineering Task Force (IETF) standard that defines the OpenPGP message format for encrypted and signed data.
-
A.
RFC 8017
RFC 8017 is the Internet standard that specifies the RSA Cryptography Standard (PKCS #1), defining algorithms and formats for RSA encryption and digital signatures.
-
B.
PGP
PGP (Pretty Good Privacy) is an encryption program that provides cryptographic privacy and authentication for data communication, most notably for securing emails and files.
-
C.
RFC 2104
RFC 2104 is the Internet standard document that defines the HMAC (Hash-based Message Authentication Code) algorithm used for data integrity and authentication in cryptographic protocols.
-
D.
RFC 3447
RFC 3447 is an earlier IETF standard that specified the RSA Cryptography Standard (PKCS #1) before being superseded by RFC 8017.
-
E.
RFC 4380
RFC 4380 is an IETF standard that specifies the Teredo protocol for providing IPv6 connectivity to nodes located behind IPv4 network address translators (NATs).
- F. None of above. chosen
Statements (48)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
OpenPGP specification ⓘ Request for Comments ⓘ |
| abbreviation |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| area | Security ⓘ |
| category | Standards Track ⓘ |
| defines |
MIME-compatible armored messages
ⓘ
OpenPGP compressed data packets ⓘ OpenPGP encrypted data packets ⓘ OpenPGP literal data packets ⓘ OpenPGP message format ⓘ
linked to:
RFC 4880
OpenPGP notation data subpackets ⓘ
linked to:
RFC 4880
OpenPGP preferred algorithms subpackets ⓘ
linked to:
RFC 4880
OpenPGP public key format ⓘ OpenPGP secret key format ⓘ OpenPGP signature packets ⓘ OpenPGP trust packets ⓘ
linked to:
RFC 4880
OpenPGP user ID packets ⓘ |
| focusesOn |
digitally signed data
ⓘ
encrypted data ⓘ |
| fullTitle |
RFC 4880: OpenPGP Message Format
ⓘ
linked to:
RFC 4880
|
| governs | interoperability of OpenPGP implementations ⓘ |
| language | English ⓘ |
| obsoletes | RFC 2440 ⓘ |
| organization | IETF OpenPGP Working Group ⓘ |
| publishedBy | Internet Engineering Task Force ⓘ |
| relatedTo |
GnuPG
ⓘ
linked to:
GNU Privacy Guard
PGP ⓘ Pretty Good Privacy ⓘ
linked to:
PGP
|
| rfcNumber | 4880 ⓘ |
| series |
Request for Comments
ⓘ
linked to:
RFCs
|
| specifies |
OpenPGP armor format
ⓘ
OpenPGP packet types ⓘ
linked to:
PGP
compression options ⓘ digital signature formats ⓘ key management structures ⓘ packet-based message format ⓘ public-key encryption mechanisms ⓘ radix-64 encoding ⓘ symmetric-key encryption mechanisms ⓘ |
| standardizes |
OpenPGP
ⓘ
linked to:
PGP
|
| status | Internet Standard ⓘ |
| title | RFC 4880 ⓘ |
| updates |
OpenPGP specification
ⓘ
linked to:
RFC 4880
|
| usedFor |
authentication via digital signatures
ⓘ
data integrity protection ⓘ email encryption ⓘ file 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 4880 Description of subject: RFC 4880 is the Internet Engineering Task Force (IETF) standard that defines the OpenPGP message format for encrypted and signed data.
Referenced by (20)
Full triples — surface form annotated when it differs from this entity's canonical label.
linked to: RFC 4880
linked to: RFC 4880
linked to: RFC 4880
linked to: RFC 4880
linked to: RFC 4880
linked to: RFC 4880
linked to: RFC 4880
linked to: RFC 4880