RFC 2104
E192651
RFC 2104 is the Internet standard document that defines the HMAC (Hash-based Message Authentication Code) algorithm used for data integrity and authentication in cryptographic protocols.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 2104 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T1711775 — 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 2104 Context triple: [HMAC, standardizedIn, RFC 2104]
-
A.
RFC 3412
RFC 3412 is an Internet standard that specifies the message processing and dispatching procedures for the Simple Network Management Protocol (SNMP) within the SNMPv3 framework.
-
B.
RFC 4254
RFC 4254 is the Internet standard that specifies the Secure Shell (SSH) connection protocol, defining how multiple logical channels are multiplexed over a single encrypted SSH transport.
-
C.
RFC 2419
RFC 2419 is an earlier Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4253.
-
D.
RFC 4844
RFC 4844 is an Internet Engineering Task Force (IETF) document that defines the framework and responsibilities of the RFC Editor function within the RFC Series.
-
E.
RFC 2449
RFC 2449 is an Internet standards document that extends the POP3 email protocol with additional capabilities and commands to improve flexibility and interoperability.
- 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 2104 Target entity description: RFC 2104 is the Internet standard document that defines the HMAC (Hash-based Message Authentication Code) algorithm used for data integrity and authentication in cryptographic protocols.
-
A.
RFC 3412
RFC 3412 is an Internet standard that specifies the message processing and dispatching procedures for the Simple Network Management Protocol (SNMP) within the SNMPv3 framework.
-
B.
RFC 4254
RFC 4254 is the Internet standard that specifies the Secure Shell (SSH) connection protocol, defining how multiple logical channels are multiplexed over a single encrypted SSH transport.
-
C.
RFC 2419
RFC 2419 is an earlier Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4253.
-
D.
RFC 4844
RFC 4844 is an Internet Engineering Task Force (IETF) document that defines the framework and responsibilities of the RFC Editor function within the RFC Series.
-
E.
RFC 2449
RFC 2449 is an Internet standards document that extends the POP3 email protocol with additional capabilities and commands to improve flexibility and interoperability.
- F. None of above. chosen
Statements (43)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard document
ⓘ
Request for Comments ⓘ |
| appliesTo |
application protocols
ⓘ
network protocols ⓘ |
| category |
Cryptographic techniques
ⓘ
Security ⓘ |
| defines |
HMAC
ⓘ
Hash-based Message Authentication Code ⓘ |
| definesConcept | keyed-hash message authentication code ⓘ |
| definesProperty |
HMAC output length equals hash function output length
ⓘ
HMAC security depends on underlying hash function ⓘ HMAC supports variable-length keys ⓘ HMAC uses inner and outer padding ⓘ |
| field |
computer security
ⓘ
cryptography ⓘ data integrity ⓘ data origin authentication ⓘ message authentication ⓘ |
| intendedAudience |
implementers of cryptographic protocols
ⓘ
protocol designers ⓘ security engineers ⓘ |
| language | English ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| purpose |
provide data integrity
ⓘ
provide data origin authentication ⓘ provide message authentication ⓘ |
| relatedTo | RFC 2202 ⓘ |
| series | Request for Comments ⓘ |
| specifies |
construction of HMAC from a cryptographic hash function
ⓘ
implementation considerations for HMAC ⓘ security goals of HMAC ⓘ test cases for HMAC ⓘ use of a secret key with a hash function for authentication ⓘ |
| standardizes | HMAC algorithm ⓘ |
| standardizesUsageIn |
IPsec
ⓘ
SSH ⓘ TLS ⓘ |
| status | Informational ⓘ |
| title |
HMAC: Keyed-Hashing for Message Authentication
ⓘ
linked to:
HMAC
|
| usesConcept |
cryptographic hash function
ⓘ
message authentication code ⓘ secret key ⓘ |
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 2104 Description of subject: RFC 2104 is the Internet standard document that defines the HMAC (Hash-based Message Authentication Code) algorithm used for data integrity and authentication in cryptographic protocols.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.