RFC 8032
E831075
RFC 8032 is an IETF standard that specifies the EdDSA family of high-speed, secure digital signature schemes, including Ed25519 and Ed448, for use in modern cryptographic applications.
All labels observed (2)
| Label | Occurrences |
|---|---|
| RFC 8032 canonical | 4 |
| RFC 8032, Section 5 | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T9931852 — 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 8032 Context triple: [Curve25519-based schemes, standardizedIn, RFC 8032]
-
A.
RFC 8332
RFC 8332 is an Internet Engineering Task Force (IETF) standard that updates and replaces earlier SSH protocol specifications to enhance security and functionality.
-
B.
RFC 8552
RFC 8552 is an Internet Engineering Task Force (IETF) standards document that specifies technical protocols and procedures used in Internet communications.
-
C.
RFC 8056
RFC 8056 is an IETF specification that extends the Registration Data Access Protocol (RDAP) with support for RDAP object tags and other features to improve registration data management and retrieval.
-
D.
RFC 7432
RFC 7432 is an IETF standard that defines Ethernet VPN (EVPN), a BGP-based control plane for multipoint Layer 2 VPN services over IP/MPLS networks.
-
E.
RFC 8314
RFC 8314 is an Internet standard that specifies the use of mandatory encryption (TLS) for email submission and access protocols to improve the security of email communications.
- 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 8032 Target entity description: RFC 8032 is an IETF standard that specifies the EdDSA family of high-speed, secure digital signature schemes, including Ed25519 and Ed448, for use in modern cryptographic applications.
-
A.
RFC 8332
RFC 8332 is an Internet Engineering Task Force (IETF) standard that updates and replaces earlier SSH protocol specifications to enhance security and functionality.
-
B.
RFC 8552
RFC 8552 is an Internet Engineering Task Force (IETF) standards document that specifies technical protocols and procedures used in Internet communications.
-
C.
RFC 8056
RFC 8056 is an IETF specification that extends the Registration Data Access Protocol (RDAP) with support for RDAP object tags and other features to improve registration data management and retrieval.
-
D.
RFC 7432
RFC 7432 is an IETF standard that defines Ethernet VPN (EVPN), a BGP-based control plane for multipoint Layer 2 VPN services over IP/MPLS networks.
-
E.
RFC 8314
RFC 8314 is an Internet standard that specifies the use of mandatory encryption (TLS) for email submission and access protocols to improve the security of email communications.
- F. None of above. chosen
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
cryptography standard ⓘ |
| abbreviation | EdDSA NERFINISHED ⓘ |
| algorithmFamily |
elliptic-curve signature scheme
ⓘ
public-key digital signature ⓘ |
| applicationDomain |
JSON Web Signatures
NERFINISHED
ⓘ
OpenPGP NERFINISHED ⓘ SSH NERFINISHED ⓘ TLS NERFINISHED ⓘ cryptographic libraries ⓘ |
| area | Security ⓘ |
| category | Standards Track ⓘ |
| defines |
encoding formats for EdDSA private keys
ⓘ
encoding formats for EdDSA public keys ⓘ encoding formats for EdDSA signatures ⓘ signature generation procedures for EdDSA ⓘ signature verification procedures for EdDSA ⓘ |
| hashFunction |
SHA-512
NERFINISHED
ⓘ
SHAKE256 NERFINISHED ⓘ |
| language | English ⓘ |
| obsoletes | no earlier RFCs ⓘ |
| property |
deterministic signatures
ⓘ
high-speed digital signatures ⓘ side-channel resistance goals ⓘ suitable for modern cryptographic applications ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedTo |
Curve25519 key agreement
ⓘ
Curve448 key agreement ⓘ RFC 7748 NERFINISHED ⓘ |
| RFCNumber | 8032 ⓘ |
| securityLevel |
128-bit security for Ed25519
ⓘ
224-bit security for Ed448 ⓘ |
| specifies |
Ed25519
NERFINISHED
ⓘ
Ed25519ph ⓘ Ed448 NERFINISHED ⓘ Ed448ph ⓘ EdDSA NERFINISHED ⓘ Edwards-curve Digital Signature Algorithm NERFINISHED ⓘ prehash variants of EdDSA ⓘ |
| standardizes | test vectors for EdDSA ⓘ |
| status | Proposed Standard ⓘ |
| stream | IETF Stream NERFINISHED ⓘ |
| title | Edwards-Curve Digital Signature Algorithm (EdDSA) NERFINISHED ⓘ |
| updatedBy |
RFC 8410
NERFINISHED
ⓘ
RFC 8709 NERFINISHED ⓘ |
| usesCurve |
Curve25519
NERFINISHED
ⓘ
Curve448 NERFINISHED ⓘ |
| workingGroup | Crypto Forum Research Group NERFINISHED ⓘ |
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 8032 Description of subject: RFC 8032 is an IETF standard that specifies the EdDSA family of high-speed, secure digital signature schemes, including Ed25519 and Ed448, for use in modern cryptographic applications.
Referenced by (5)
Full triples — surface form annotated when it differs from this entity's canonical label.
this entity surface form:
RFC 8032, Section 5