RFC 7919
E36660
RFC 7919 is an Internet standard that specifies the use of predefined Diffie–Hellman groups for secure key exchange in TLS and related protocols.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 7919 canonical | 3 |
How this entity was disambiguated
This entity first appeared as the object of triple T272179 — 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 7919 Context triple: [Diffie–Hellman key exchange, standardizedIn, RFC 7919]
-
A.
RFC 9113
RFC 9113 is the Internet standards document that specifies the HTTP/2 protocol, defining its framing, semantics, and operational behavior on the web.
-
B.
RFC 9114
RFC 9114 is the Internet standard that specifies HTTP/3, the version of the Hypertext Transfer Protocol that runs over the QUIC transport protocol.
-
C.
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.
-
D.
RFC 9111
RFC 9111 is an IETF specification that defines HTTP caching semantics, detailing how responses can be stored, reused, and validated to improve web performance and efficiency.
-
E.
RFC 9112
RFC 9112 is the IETF specification that standardizes the semantics and behavior of HTTP/1.1.
- 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 7919 Target entity description: RFC 7919 is an Internet standard that specifies the use of predefined Diffie–Hellman groups for secure key exchange in TLS and related protocols.
-
A.
RFC 9113
RFC 9113 is the Internet standards document that specifies the HTTP/2 protocol, defining its framing, semantics, and operational behavior on the web.
-
B.
RFC 9114
RFC 9114 is the Internet standard that specifies HTTP/3, the version of the Hypertext Transfer Protocol that runs over the QUIC transport protocol.
-
C.
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.
-
D.
RFC 9111
RFC 9111 is an IETF specification that defines HTTP caching semantics, detailing how responses can be stored, reused, and validated to improve web performance and efficiency.
-
E.
RFC 9112
RFC 9112 is the IETF specification that standardizes the semantics and behavior of HTTP/1.1.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| aimsTo |
promote interoperability between TLS implementations
ⓘ
simplify configuration of secure DH parameters in TLS ⓘ |
| appliesToProtocol |
DTLS 1.0
ⓘ
linked to:
DTLS
DTLS 1.2 ⓘ
linked to:
DTLS
TLS 1.0 ⓘ TLS 1.1 ⓘ TLS 1.2 ⓘ
linked to:
RFC 5246
|
| area | Security ⓘ |
| category | Standards Track ⓘ |
| defines |
FFDHE groups
ⓘ
IANA registry for FFDHE groups ⓘ TLS FFDHE extension ⓘ
linked to:
Negotiated Finite Field Diffie-Hellman Ephemeral Parameters for Transport Layer Security (TLS)
TLS extension for negotiating FFDHE parameters ⓘ predefined finite-field Diffie-Hellman groups ⓘ |
| definesGroup |
ffdhe2048
ⓘ
ffdhe3072 ⓘ ffdhe4096 ⓘ ffdhe6144 ⓘ ffdhe8192 ⓘ |
| fieldType | finite field modulo a prime ⓘ |
| groupType | safe prime groups ⓘ |
| intendedUse |
DTLS clients
ⓘ
DTLS servers ⓘ TLS clients ⓘ TLS servers ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| purpose |
to avoid weak or poorly generated Diffie-Hellman parameters
ⓘ
to improve security of finite-field Diffie-Hellman in TLS ⓘ to specify standardized Diffie-Hellman parameters for TLS key exchange ⓘ |
| recommends | use of standardized FFDHE groups instead of custom groups ⓘ |
| recommendsKeyExchange |
DHE
ⓘ
DHE_RSA ⓘ |
| relatedTo |
Diffie–Hellman key exchange
ⓘ
TLS key exchange ⓘ cryptographic parameters ⓘ |
| securityProperty |
mitigates risks from weak Diffie-Hellman groups
ⓘ
provides stronger assurance about group parameters ⓘ |
| standardizes | named finite-field DH groups for TLS ⓘ |
| status | Proposed Standard ⓘ |
| title | Negotiated Finite Field Diffie-Hellman Ephemeral Parameters for Transport Layer Security (TLS) ⓘ |
| updatesProtocol |
TLS
ⓘ
Transport Layer Security ⓘ
linked to:
TLS
|
| usesAlgorithm |
ephemeral Diffie-Hellman
ⓘ
linked to:
Diffie–Hellman key exchange
finite-field Diffie-Hellman ⓘ
linked to:
Diffie–Hellman key exchange
|
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 7919 Description of subject: RFC 7919 is an Internet standard that specifies the use of predefined Diffie–Hellman groups for secure key exchange in TLS and related protocols.
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.