RFC 7218
E832822
RFC 7218 is an IETF standards document that specifies naming conventions and TLSA record usage guidelines for the DANE (DNS-Based Authentication of Named Entities) protocol.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 7218 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T9932171 — 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 7218 Context triple: [DANE, definedIn, RFC 7218]
-
A.
RFC 7158
RFC 7158 is an IETF specification that updates and clarifies the JSON (JavaScript Object Notation) data interchange format previously defined in RFC 4627.
-
B.
RFC 7868
RFC 7868 is the IETF specification that documents and standardizes the Enhanced Interior Gateway Routing Protocol (EIGRP) as an informational routing protocol.
-
C.
RFC 8078
RFC 8078 is an Internet Engineering Task Force (IETF) standard that specifies guidelines and procedures for automatically signing DNSSEC delegations to improve the security and manageability of DNS.
-
D.
RFC 7888
RFC 7888 is an Internet Engineering Task Force (IETF) standards document that refines and updates email-related protocols originally defined in RFC 6856.
-
E.
RFC 8881
RFC 8881 is the Internet Engineering Task Force (IETF) standard that specifies the Network File System (NFS) version 4.1 protocol, updating and replacing the original NFSv4 specification.
- 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 7218 Target entity description: RFC 7218 is an IETF standards document that specifies naming conventions and TLSA record usage guidelines for the DANE (DNS-Based Authentication of Named Entities) protocol.
-
A.
RFC 7158
RFC 7158 is an IETF specification that updates and clarifies the JSON (JavaScript Object Notation) data interchange format previously defined in RFC 4627.
-
B.
RFC 7868
RFC 7868 is the IETF specification that documents and standardizes the Enhanced Interior Gateway Routing Protocol (EIGRP) as an informational routing protocol.
-
C.
RFC 8078
RFC 8078 is an Internet Engineering Task Force (IETF) standard that specifies guidelines and procedures for automatically signing DNSSEC delegations to improve the security and manageability of DNS.
-
D.
RFC 7888
RFC 7888 is an Internet Engineering Task Force (IETF) standards document that refines and updates email-related protocols originally defined in RFC 6856.
-
E.
RFC 8881
RFC 8881 is the Internet Engineering Task Force (IETF) standard that specifies the Network File System (NFS) version 4.1 protocol, updating and replacing the original NFSv4 specification.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
standards document ⓘ |
| addresses |
clarity of terminology in DANE discussions
ⓘ
interoperability of DANE deployments ⓘ |
| area | Security ⓘ |
| basedOn | DANE protocol defined in RFC 6698 ⓘ |
| category | Best Current Practice ⓘ |
| definesAcronym |
DANE
NERFINISHED
ⓘ
DANE-EE NERFINISHED ⓘ DANE-EE(3) ⓘ DANE-TA NERFINISHED ⓘ DANE-TA(2) NERFINISHED ⓘ PKIX-EE NERFINISHED ⓘ PKIX-EE(1) ⓘ PKIX-TA NERFINISHED ⓘ PKIX-TA(0) NERFINISHED ⓘ TLSA NERFINISHED ⓘ |
| focusesOn |
PKIX certificate validation models
ⓘ
TLS server authentication ⓘ |
| intendedFor |
implementers of DANE
ⓘ
operators of DNSSEC-enabled services ⓘ protocol designers ⓘ |
| language | English ⓘ |
| obsoletedBy | none ⓘ |
| obsoletes | none ⓘ |
| providesGuidelinesFor |
use of TLSA records with DANE trust anchors
ⓘ
use of TLSA records with PKIX ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedTo | RFC 6698 NERFINISHED ⓘ |
| relatedToProtocol |
DANE
NERFINISHED
ⓘ
DNS-Based Authentication of Named Entities NERFINISHED ⓘ |
| specifies |
TLSA record usage guidelines
ⓘ
naming conventions for DANE usage ⓘ terminology for TLSA certificate usages ⓘ terminology for TLSA matching types ⓘ terminology for TLSA selectors ⓘ |
| status | Best Current Practice ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| subject |
DNSSEC-secured TLSA records
ⓘ
certificate usage field semantics ⓘ matching type field semantics ⓘ selector field semantics ⓘ |
| title | Adding Acronyms to Simplify Conversations about DNS-Based Authentication of Named Entities (DANE) NERFINISHED ⓘ |
| updatesUsageOf | TLSA resource records ⓘ |
| usesResourceRecordType | TLSA NERFINISHED ⓘ |
| workingGroup | DANE NERFINISHED ⓘ |
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 7218 Description of subject: RFC 7218 is an IETF standards document that specifies naming conventions and TLSA record usage guidelines for the DANE (DNS-Based Authentication of Named Entities) protocol.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.