RFC 7748
E831074
RFC 7748 is an IETF standard that specifies the elliptic curves Curve25519 and Curve448 for secure key exchange in modern cryptographic protocols.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 7748 canonical | 3 |
How this entity was disambiguated
This entity first appeared as the object of triple T9931851 — 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 7748 Context triple: [Curve25519-based schemes, standardizedIn, RFC 7748]
-
A.
RFC 7144
RFC 7144 is an Internet Engineering Task Force (IETF) standards-track document that updates and replaces the original iSCSI protocol specification defined in RFC 3720.
-
B.
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.
-
C.
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.
-
D.
RFC 7143
RFC 7143 is the Internet Engineering Task Force (IETF) standard that defines the updated core specification for the iSCSI (Internet Small Computer Systems Interface) protocol used for block-level storage over IP networks.
-
E.
RFC 7484
RFC 7484 is an IETF standards document that specifies how the Registration Data Access Protocol (RDAP) uses HTTP-based bootstrapping to locate authoritative servers for domain, IP address, and autonomous system number registration data.
- 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 7748 Target entity description: RFC 7748 is an IETF standard that specifies the elliptic curves Curve25519 and Curve448 for secure key exchange in modern cryptographic protocols.
-
A.
RFC 7144
RFC 7144 is an Internet Engineering Task Force (IETF) standards-track document that updates and replaces the original iSCSI protocol specification defined in RFC 3720.
-
B.
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.
-
C.
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.
-
D.
RFC 7143
RFC 7143 is the Internet Engineering Task Force (IETF) standard that defines the updated core specification for the iSCSI (Internet Small Computer Systems Interface) protocol used for block-level storage over IP networks.
-
E.
RFC 7484
RFC 7484 is an IETF standards document that specifies how the Registration Data Access Protocol (RDAP) uses HTTP-based bootstrapping to locate authoritative servers for domain, IP address, and autonomous system number registration data.
- F. None of above. chosen
Statements (46)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
cryptography standard ⓘ |
| area | Security ⓘ |
| author |
Adam Langley
ⓘ
Mike Hamburg ⓘ Sean Turner ⓘ |
| category | Informational ⓘ |
| curveType | Montgomery curve ⓘ |
| defines |
Curve25519
ⓘ
linked to:
Curve25519-based schemes
Curve448 ⓘ |
| definesCoordinateSystem | Montgomery x-coordinate ⓘ |
| definesOperation | scalar multiplication on elliptic curves ⓘ |
| fieldSizeOfCurve25519 | 2^255 - 19 ⓘ |
| fieldSizeOfCurve448 | 2^448 - 2^224 - 1 ⓘ |
| focusesOn |
elliptic-curve cryptography
ⓘ
key exchange ⓘ public-key cryptography ⓘ |
| intendedFor |
high-performance cryptography
ⓘ
interoperable implementations ⓘ |
| intendedUse | modern cryptographic protocols ⓘ |
| language | English ⓘ |
| obsoletedBy | none ⓘ |
| obsoletes | none ⓘ |
| partOf | IETF cryptographic algorithm portfolio ⓘ |
| publicationDate | 2016-01 ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| recommends | constant-time implementations ⓘ |
| relatedTo |
Curve25519
ⓘ
linked to:
Curve25519-based schemes
Curve448 ⓘ RFC 8032 ⓘ |
| RFCNumber | 7748 ⓘ |
| securityGoal |
forward secrecy
ⓘ
resistance to side-channel attacks ⓘ |
| specifies |
Diffie–Hellman key exchange using Curve25519
ⓘ
linked to:
Diffie–Hellman key exchange
Diffie–Hellman key exchange using Curve448 ⓘ
linked to:
Curve448
Montgomery curves over prime fields ⓘ elliptic curves for key agreement ⓘ |
| status |
Internet Standard Track Document
ⓘ
linked to:
IETF Internet standards process
|
| stream |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| title | Elliptic Curves for Security ⓘ |
| usedIn |
Noise Protocol Framework
ⓘ
linked to:
Noise protocol framework
SSH key exchange extensions ⓘ TLS 1.3 ⓘ
linked to:
RFC 8446
Transport Layer Security ⓘ
linked to:
TLS
|
| year | 2016 ⓘ |
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 7748 Description of subject: RFC 7748 is an IETF standard that specifies the elliptic curves Curve25519 and Curve448 for secure key exchange in modern cryptographic protocols.
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.