RFC 6979
E831965
RFC 6979 is an IETF standard that defines a deterministic method for generating nonces in digital signature algorithms like ECDSA to improve security and reproducibility.
All labels observed (2)
| Label | Occurrences |
|---|---|
| Deterministic ECDSA | 1 |
| RFC 6979 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T9961875 — 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 6979 Context triple: [Elliptic Curve Digital Signature Algorithm, deterministicVariantSpecifiedIn, RFC 6979]
-
A.
RFC 7919
RFC 7919 is an Internet standard that specifies the use of predefined Diffie–Hellman groups for secure key exchange in TLS and related protocols.
-
B.
RFC 7748
RFC 7748 is an IETF standard that specifies the elliptic curves Curve25519 and Curve448 for secure key exchange in modern cryptographic protocols.
-
C.
RFC 8016
RFC 8016 is an Internet Engineering Task Force (IETF) specification that updates the TURN protocol to improve how it relays traffic for clients behind Network Address Translators (NATs).
-
D.
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.
-
E.
RFC 6121
RFC 6121 is an IETF standard that defines the core instant messaging and presence functionality for the Extensible Messaging and Presence Protocol (XMPP).
- 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 6979 Target entity description: RFC 6979 is an IETF standard that defines a deterministic method for generating nonces in digital signature algorithms like ECDSA to improve security and reproducibility.
-
A.
RFC 7919
RFC 7919 is an Internet standard that specifies the use of predefined Diffie–Hellman groups for secure key exchange in TLS and related protocols.
-
B.
RFC 7748
RFC 7748 is an IETF standard that specifies the elliptic curves Curve25519 and Curve448 for secure key exchange in modern cryptographic protocols.
-
C.
RFC 8016
RFC 8016 is an Internet Engineering Task Force (IETF) specification that updates the TURN protocol to improve how it relays traffic for clients behind Network Address Translators (NATs).
-
D.
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.
-
E.
RFC 6121
RFC 6121 is an IETF standard that defines the core instant messaging and presence functionality for the Extensible Messaging and Presence Protocol (XMPP).
- F. None of above. chosen
Statements (48)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
technical standard ⓘ |
| addresses |
nonce generation in digital signature algorithms
ⓘ
vulnerabilities due to poor randomness in nonces ⓘ |
| aimsTo |
eliminate dependence on random number generators for nonces
ⓘ
improve reproducibility of digital signatures ⓘ improve security of digital signatures ⓘ |
| appliesTo |
DSA
ⓘ
EC-DSA-style signature schemes ⓘ ECDSA ⓘ
linked to:
Elliptic Curve Digital Signature Algorithm
|
| area | Security ⓘ |
| author | Thomas Pornin ⓘ |
| authorName | Thomas Pornin ⓘ |
| basedOn |
FIPS 186-4 Digital Signature Standard concepts
ⓘ
linked to:
FIPS 186-4
|
| category | Informational ⓘ |
| compatibleWith |
existing DSA implementations
ⓘ
existing ECDSA implementations ⓘ |
| defines |
deterministic nonce generation for DSA
ⓘ
deterministic nonce generation for ECDSA ⓘ deterministic usage of DSA ⓘ deterministic usage of ECDSA ⓘ |
| documentType |
RFC
ⓘ
linked to:
RFCs
|
| ensures |
nonces are unpredictable to adversaries without the private key
ⓘ
same message and key produce same nonce ⓘ |
| focusesOn |
cryptographic nonce generation
ⓘ
digital signatures ⓘ |
| language | English ⓘ |
| motivatedBy |
attacks exploiting biased or repeated nonces
ⓘ
failures of random number generators in signature implementations ⓘ |
| number | 6979 ⓘ |
| obsoletedBy | none ⓘ |
| obsoletes | none ⓘ |
| publicationDate | 2013-08 ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| publishedYear | 2013 ⓘ |
| securityProperty |
prevents private key leakage from nonce reuse
ⓘ
resistance to bad randomness in nonce generation ⓘ |
| series |
Request for Comments
ⓘ
linked to:
RFCs
|
| specifies | algorithm for computing deterministic k (nonce) from private key and message hash ⓘ |
| standardizedBy | Internet Engineering Task Force ⓘ |
| status | Informational RFC ⓘ |
| title |
Deterministic Usage of the Digital Signature Algorithm (DSA) and Elliptic Curve Digital Signature Algorithm (ECDSA)
ⓘ
linked to:
Elliptic Curve Digital Signature Algorithm
|
| usedIn |
TLS and other security protocols implementations
ⓘ
blockchain and cryptocurrency software ⓘ cryptographic libraries ⓘ |
| uses |
HMAC-based deterministic random bit generation
ⓘ
HMAC_DRBG ⓘ |
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 6979 Description of subject: RFC 6979 is an IETF standard that defines a deterministic method for generating nonces in digital signature algorithms like ECDSA to improve security and reproducibility.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.
linked to: RFC 6979