RFC 7539
E50080
RFC 7539 is an IETF standard that specifies the ChaCha20 stream cipher and the Poly1305 message authentication code for use in secure Internet protocols.
All labels observed (2)
How this entity was disambiguated
This entity first appeared as the object of triple T338738 — 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 7539 Context triple: [ChaCha20, standardizedIn, RFC 7539]
-
A.
RFC 7950
RFC 7950 is the IETF specification that standardizes the YANG 1.1 data modeling language used for modeling configuration and state data in network management protocols.
-
B.
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.
-
C.
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.
-
D.
RFC 9205
RFC 9205 is an IETF specification that provides guidance and best practices for the use and deployment of HTTP, complementing the core protocol definitions in related HTTP RFCs.
-
E.
RFC 6557
RFC 6557 is an Internet Engineering Task Force (IETF) document that defines procedures and guidelines for the maintenance and distribution of the IANA time zone database.
- 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 7539 Target entity description: RFC 7539 is an IETF standard that specifies the ChaCha20 stream cipher and the Poly1305 message authentication code for use in secure Internet protocols.
-
A.
RFC 7950
RFC 7950 is the IETF specification that standardizes the YANG 1.1 data modeling language used for modeling configuration and state data in network management protocols.
-
B.
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.
-
C.
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.
-
D.
RFC 9205
RFC 9205 is an IETF specification that provides guidance and best practices for the use and deployment of HTTP, complementing the core protocol definitions in related HTTP RFCs.
-
E.
RFC 6557
RFC 6557 is an Internet Engineering Task Force (IETF) document that defines procedures and guidelines for the maintenance and distribution of the IANA time zone database.
- F. None of above. chosen
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
cryptography standard ⓘ |
| area | Security ⓘ |
| author |
Adam Langley
ⓘ
Adam Langley (editor) ⓘ
linked to:
Adam Langley
Yoav Nir ⓘ |
| basedOn |
ChaCha stream cipher by Daniel J. Bernstein
ⓘ
Poly1305 MAC by Daniel J. Bernstein ⓘ
linked to:
Poly1305
|
| category | Informational ⓘ |
| defines |
ChaCha20
ⓘ
ChaCha20-Poly1305 AEAD construction ⓘ
linked to:
AEAD_CHACHA20_POLY1305
IETF variant of ChaCha20 ⓘ IETF variant of ChaCha20-Poly1305 AEAD ⓘ Poly1305 ⓘ |
| definesBlockSize | 512-bit block for ChaCha20 ⓘ |
| definesKeySize | 256-bit key for ChaCha20 ⓘ |
| definesNonceReuseRequirement | nonces must not repeat under the same key ⓘ |
| definesNonceSize | 96-bit nonce for ChaCha20 in IETF variant ⓘ |
| definesTagSize | 128-bit authentication tag for Poly1305 ⓘ |
| definesTestVectors |
ChaCha20 test vectors
ⓘ
ChaCha20-Poly1305 AEAD test vectors ⓘ Poly1305 test vectors ⓘ |
| focusesOn |
high-speed software cryptography
ⓘ
message authentication codes ⓘ security of stream ciphers ⓘ |
| language | English ⓘ |
| obsoletes | RFC 8439 ⓘ |
| organization | Internet Research Task Force ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| recommends | use of ChaCha20-Poly1305 where AES hardware is not available ⓘ |
| RFCNumber | 7539 ⓘ |
| securityProperty |
authenticity via AEAD construction
ⓘ
confidentiality via ChaCha20 ⓘ integrity via Poly1305 ⓘ |
| specifies |
AEAD_CHACHA20_POLY1305
ⓘ
ChaCha20 stream cipher ⓘ
linked to:
ChaCha20
Poly1305 message authentication code ⓘ
linked to:
Poly1305
|
| status | Informational RFC ⓘ |
| stream |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| targetEnvironment |
general-purpose CPUs
ⓘ
software implementations ⓘ |
| title |
ChaCha20 and Poly1305 for IETF Protocols
ⓘ
linked to:
ChaCha20
|
| updates | None ⓘ |
| useCase |
IPsec
ⓘ
SSH ⓘ TLS ⓘ secure Internet protocols ⓘ |
| workingGroup |
CFRG (Crypto Forum Research Group)
ⓘ
linked to:
CFRG
|
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 7539 Description of subject: RFC 7539 is an IETF standard that specifies the ChaCha20 stream cipher and the Poly1305 message authentication code for use in secure Internet protocols.
Referenced by (6)
Full triples — surface form annotated when it differs from this entity's canonical label.
linked to: RFC 7539