RFC 2845
E831088
RFC 2845 is the Internet standard that specifies the Transaction SIGnature (TSIG) mechanism for securing DNS transactions using shared secret keys and message authentication codes.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 2845 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T9932213 — 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.
Target entity: RFC 2845 Context triple: [TSIG, definedIn, RFC 2845]
-
A.
RFC 2865
RFC 2865 is the IETF standard that specifies the Remote Authentication Dial-In User Service (RADIUS) protocol for centralized authentication, authorization, and accounting in network access.
-
B.
RFC 2870
RFC 2870 is an Internet Engineering Task Force (IETF) document that specifies operational and technical requirements for the DNS root name server system.
-
C.
RFC 3445
RFC 3445 is an earlier Internet Engineering Task Force (IETF) specification related to DNS security that was later superseded by RFC 4033.
-
D.
RFC 2866
RFC 2866 is an IETF specification that defines the accounting extensions for the RADIUS (Remote Authentication Dial-In User Service) protocol used in network access and usage tracking.
-
E.
RFC 2487
RFC 2487 is an Internet standards document that originally defined the STARTTLS extension for securing SMTP connections with TLS, later superseded by RFC 3207.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Target entity: RFC 2845 Target entity description: RFC 2845 is the Internet standard that specifies the Transaction SIGnature (TSIG) mechanism for securing DNS transactions using shared secret keys and message authentication codes.
-
A.
RFC 2865
RFC 2865 is the IETF standard that specifies the Remote Authentication Dial-In User Service (RADIUS) protocol for centralized authentication, authorization, and accounting in network access.
-
B.
RFC 2870
RFC 2870 is an Internet Engineering Task Force (IETF) document that specifies operational and technical requirements for the DNS root name server system.
-
C.
RFC 3445
RFC 3445 is an earlier Internet Engineering Task Force (IETF) specification related to DNS security that was later superseded by RFC 4033.
-
D.
RFC 2866
RFC 2866 is an IETF specification that defines the accounting extensions for the RADIUS (Remote Authentication Dial-In User Service) protocol used in network access and usage tracking.
-
E.
RFC 2487
RFC 2487 is an Internet standards document that originally defined the STARTTLS extension for securing SMTP connections with TLS, later superseded by RFC 3207.
- F. None of above. chosen
Statements (50)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| appliesTo |
DNS transactions
ⓘ
Domain Name System NERFINISHED ⓘ |
| area | Internet NERFINISHED ⓘ |
| authenticationProperty |
provides data origin authentication for DNS messages
ⓘ
provides integrity protection for DNS messages ⓘ |
| category |
DNS security
ⓘ
Security ⓘ |
| context |
DNS dynamic update
ⓘ
DNS request messages ⓘ DNS response messages ⓘ DNS zone transfer ⓘ |
| defines |
TSIG
NERFINISHED
ⓘ
Transaction SIGnature mechanism ⓘ |
| definesField |
TSIG MAC field
ⓘ
TSIG error field ⓘ TSIG fudge field ⓘ TSIG other data field ⓘ TSIG time signed field ⓘ |
| doesNotProvide | confidentiality of DNS messages ⓘ |
| intendedUse | authentication of DNS messages between parties sharing a secret key ⓘ |
| language | English ⓘ |
| mechanismType | symmetric key authentication ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedTo |
DNS dynamic update
ⓘ
DNS zone transfer ⓘ DNSSEC NERFINISHED ⓘ RFC 1034 NERFINISHED ⓘ RFC 1035 NERFINISHED ⓘ |
| relatesTo |
DNS dynamic update security
ⓘ
DNS message authentication ⓘ DNS protocol ⓘ DNS zone transfer security ⓘ |
| securityGoal |
protect DNS transactions against spoofing
ⓘ
protect DNS transactions against tampering ⓘ |
| specifies |
mechanism for securing DNS transactions
ⓘ
use of message authentication codes for DNS ⓘ use of shared secret keys for DNS authentication ⓘ |
| standardizes |
TSIG error handling
ⓘ
TSIG processing rules ⓘ TSIG resource record format ⓘ TSIG time and replay protection ⓘ |
| status | Proposed Standard ⓘ |
| title | Secret Key Transaction Authentication for DNS (TSIG) ⓘ |
| uses |
HMAC
NERFINISHED
ⓘ
message authentication codes ⓘ shared secret keys ⓘ |
| usesRecordType | TSIG DNS resource record ⓘ |
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.
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.
Subject: RFC 2845 Description of subject: RFC 2845 is the Internet standard that specifies the Transaction SIGnature (TSIG) mechanism for securing DNS transactions using shared secret keys and message authentication codes.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.