RFC 7858
E835283
RFC 7858 is the Internet standard that specifies how to secure DNS queries and responses using Transport Layer Security (TLS), commonly known as DNS over TLS.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 7858 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T10024586 — 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 7858 Context triple: [DNS over TLS, definedIn, RFC 7858]
-
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 5838
RFC 5838 is an IETF specification that updates and extends OSPFv3 to support multiple address families, including IPv4 and IPv6, within a single protocol instance.
- 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 7858 Target entity description: RFC 7858 is the Internet standard that specifies how to secure DNS queries and responses using Transport Layer Security (TLS), commonly known as DNS over TLS.
-
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 5838
RFC 5838 is an IETF specification that updates and extends OSPFv3 to support multiple address families, including IPv4 and IPv6, within a single protocol instance.
- F. None of above. chosen
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| abbreviation | DoT NERFINISHED ⓘ |
| appliesTo |
DNS queries
ⓘ
DNS responses ⓘ |
| area | Internet Area NERFINISHED ⓘ |
| author |
Adam Langley
NERFINISHED
ⓘ
John R. Levine NERFINISHED ⓘ Paul Hoffman NERFINISHED ⓘ Willem Toorop NERFINISHED ⓘ Zi Hu NERFINISHED ⓘ |
| category | Standards Track ⓘ |
| defaultPort | 853 ⓘ |
| defines | use of TLS to protect DNS traffic between a client and a recursive resolver ⓘ |
| definesProtocol | DNS over TLS NERFINISHED ⓘ |
| documentType | Standards Track RFC ⓘ |
| editor | Zi Hu NERFINISHED ⓘ |
| hasURL | https://www.rfc-editor.org/rfc/rfc7858 ⓘ |
| language | English ⓘ |
| obsoletedBy | RFC 8310 NERFINISHED ⓘ |
| obsoletes | none ⓘ |
| portNumber | 853 ⓘ |
| protocolLayer | transport layer ⓘ |
| providesProperty |
confidentiality of DNS traffic
ⓘ
integrity of DNS traffic ⓘ server authentication ⓘ |
| publicationDate | 2016-05 ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedTo |
DNS privacy
ⓘ
DNS security ⓘ RFC 8310 NERFINISHED ⓘ encrypted DNS ⓘ |
| scope | stub-to-recursive DNS communication ⓘ |
| securesProtocol |
DNS
ⓘ
Domain Name System NERFINISHED ⓘ |
| shortName | DNS over TLS NERFINISHED ⓘ |
| standardsBody | Internet Engineering Task Force NERFINISHED ⓘ |
| status | Proposed Standard ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| title | Specification for DNS over Transport Layer Security (TLS) NERFINISHED ⓘ |
| transport | TCP NERFINISHED ⓘ |
| updatedBy | RFC 8310 NERFINISHED ⓘ |
| updates | none ⓘ |
| usesProtocol |
TLS
NERFINISHED
ⓘ
Transport Layer Security NERFINISHED ⓘ |
| workingGroup |
DNS PRIVate Exchange
NERFINISHED
ⓘ
DPRIVE NERFINISHED ⓘ |
| 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 7858 Description of subject: RFC 7858 is the Internet standard that specifies how to secure DNS queries and responses using Transport Layer Security (TLS), commonly known as DNS over TLS.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.