IETF DPRIVE working group
E835286
The IETF DPRIVE working group is a standards body team focused on developing and improving privacy-enhancing technologies for DNS, such as encrypted DNS protocols.
All labels observed (1)
| Label | Occurrences |
|---|---|
| IETF DPRIVE working group canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T10024656 — 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: IETF DPRIVE working group Context triple: [IETF DNSOP, coordinatesWith, IETF DPRIVE working group]
-
A.
IETF ICE Working Group
The IETF ICE Working Group is a standards body team within the Internet Engineering Task Force responsible for developing and maintaining the Interactive Connectivity Establishment (ICE) protocols used for NAT traversal in real-time communications.
-
B.
IETF Internet Research Task Force
The IETF Internet Research Task Force (IRTF) is an organization that promotes long-term research on Internet protocols, architecture, and applications through focused research groups operating alongside the Internet Engineering Task Force.
-
C.
IETF MASQUE Working Group
The IETF MASQUE Working Group is a standards body team within the Internet Engineering Task Force focused on developing protocols for proxying IP traffic and other network flows over HTTP.
-
D.
IETF OPSAWG Working Group
The IETF OPSAWG Working Group is a standards body group within the Internet Engineering Task Force focused on developing and maintaining operational and management practices, guidelines, and related technologies for managing IP networks and services.
-
E.
IETF BEHAVE working group
The IETF BEHAVE working group was a standards body group within the Internet Engineering Task Force focused on defining and improving how Network Address Translators (NATs) interact with Internet protocols and applications.
- 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: IETF DPRIVE working group Target entity description: The IETF DPRIVE working group is a standards body team focused on developing and improving privacy-enhancing technologies for DNS, such as encrypted DNS protocols.
-
A.
IETF ICE Working Group
The IETF ICE Working Group is a standards body team within the Internet Engineering Task Force responsible for developing and maintaining the Interactive Connectivity Establishment (ICE) protocols used for NAT traversal in real-time communications.
-
B.
IETF Internet Research Task Force
The IETF Internet Research Task Force (IRTF) is an organization that promotes long-term research on Internet protocols, architecture, and applications through focused research groups operating alongside the Internet Engineering Task Force.
-
C.
IETF MASQUE Working Group
The IETF MASQUE Working Group is a standards body team within the Internet Engineering Task Force focused on developing protocols for proxying IP traffic and other network flows over HTTP.
-
D.
IETF OPSAWG Working Group
The IETF OPSAWG Working Group is a standards body group within the Internet Engineering Task Force focused on developing and maintaining operational and management practices, guidelines, and related technologies for managing IP networks and services.
-
E.
IETF BEHAVE working group
The IETF BEHAVE working group was a standards body group within the Internet Engineering Task Force focused on defining and improving how Network Address Translators (NATs) interact with Internet protocols and applications.
- F. None of above. chosen
Statements (40)
| Predicate | Object |
|---|---|
| instanceOf |
IETF working group
ⓘ
standards development working group ⓘ |
| acronym | DPRIVE NERFINISHED ⓘ |
| area | IETF Security Area NERFINISHED ⓘ |
| charteredBy | IETF Internet Engineering Steering Group NERFINISHED ⓘ |
| coordinatesWith |
IETF DNSOP working group
NERFINISHED
ⓘ
IETF HTTP working group NERFINISHED ⓘ IETF TLS working group NERFINISHED ⓘ |
| decisionMaking | rough consensus and running code ⓘ |
| focusesOn |
DNS privacy
ⓘ
encrypted DNS ⓘ on-the-wire confidentiality for DNS ⓘ privacy-enhancing technologies for DNS ⓘ |
| fullName | Domain Name System (DNS) PRIVate Exchange Working Group NERFINISHED ⓘ |
| goal |
to define mechanisms for encrypting DNS queries and responses
ⓘ
to improve confidentiality of DNS transactions between clients and resolvers ⓘ to mitigate pervasive monitoring of DNS traffic ⓘ |
| hasDatatrackerPage | https://datatracker.ietf.org/wg/dprive ⓘ |
| hasMailingList | [email protected] ⓘ |
| hasWiki | https://trac.ietf.org/trac/dprive ⓘ |
| language | English ⓘ |
| meetsAt | IETF meetings ⓘ |
| openParticipation | true ⓘ |
| outputType |
Best Current Practice RFCs
ⓘ
Proposed Standard RFCs ⓘ |
| parentOrganization | Internet Engineering Task Force NERFINISHED ⓘ |
| produces |
Internet-Drafts
NERFINISHED
ⓘ
RFCs NERFINISHED ⓘ |
| scope |
operational and deployment considerations for encrypted DNS
ⓘ
recursive-to-authoritative DNS privacy ⓘ stub-to-recursive resolver privacy ⓘ |
| standardizes |
DNS-over-DTLS
NERFINISHED
ⓘ
DNS-over-HTTPS privacy considerations NERFINISHED ⓘ DNS-over-TLS NERFINISHED ⓘ encrypted DNS transport profiles ⓘ |
| topic |
DNS resolver policy and configuration for privacy
ⓘ
performance and operational impact of encrypted DNS ⓘ privacy threat models for DNS ⓘ transport-layer security for DNS ⓘ |
| usesProcess | IETF consensus process ⓘ |
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: IETF DPRIVE working group Description of subject: The IETF DPRIVE working group is a standards body team focused on developing and improving privacy-enhancing technologies for DNS, such as encrypted DNS protocols.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.