[dns-operations] DEADLINE EXTENSION until Jan 18: NDSS DNS Privacy Workshop

[Allison Mankin]

[Apologies for possible multiple copies]

We have extended the submission deadline for the NDSS DNS Privacy Workshop
to Wednesday, January 18 because of the intervening holidays for many
interested people.  Please contact us (Sara and Allison) if you have
questions.  Note that the formats are flexed a bit as well:  page lengths
and format are flexible now and we are also willing to receive draft
presentations as long as they have an abstract early in the deck.  The goal
of the workshop is interchange and advancing the state of play for DNS
privacy and its adjacent technologies.

The call for papers is here:   DPRIV17
<https://www.internetsociety.org/events/ndss-symposium/ndss-symposium-2017/dns-privacy-workshop-2017-call-papers>.
The deadline on the web page at NDSS hasn't been changed yet, but the
submission system is set with the new deadline.

Elevator pitch:  DNS queries and domain names are metadata and there are
many new directions (and open questions) for mitigating privacy issues for
them.

Location and Important dates:
Workshop Location: San Diego, CA, USA

Workshop date: 2017-02-26 (co-located with NDSS 2017)

Submissions: 2017-01-18 anywhere-on-earth

Final date for notifications and invitations to present at the workshop:
2017-02-03
Submissions may be new papers, papers already published, Short Papers, or
Position Papers.  Also, please contact the TPC chairs if you want to
suggest a panel.

Allison and Sara

allison.mankin at gmail.com
sara at sinodun.com

------------
*Workshop on DNS Privacy DPRIV17 (#NoMoreCowbell)* BackgroundDNS Privacy
has been a growing concern of the IETF and others in the Internet
engineering community for the last few years.  Almost every activity on the
Internet starts with a DNS query (and often several).

   - Those queries can reveal not only what websites an individual visits
   but also metadata about other services such as the domains of email
   contacts or chat services.
   - Whilst the data in the DNS is public, individual DNS transactions made
   by an end user *should not* be public.
   - Today, however DNS queries are sent in *clear text* (using UDP or TCP)
   which means passive eavesdroppers can observe all the DNS lookups
   performed.
   - The DNS is a globally distributed system that crosses international
   boundaries and often uses servers in many different countries in order to
   provide resilience.
   - It is well known that the NSA used the MORECOWBELL tool to perform
   mass surveillance of DNS traffic, and other surveillance techniques
   involving DNS almost certainly are in play today.
   - Some ISPs embed user information (e.g. a user ID or MAC address)
   within DNS queries that go to the ISP’s resolver in order to provide
   services such as Parental Filtering. This allows for fingerprinting of
   individual users.
   - Some CDNs embed user information (e.g. client subnets) in queries from
   resolvers to authoritative servers (to geo-locate end users). This allows
   for correlation of queries to particular subnets.
   - Some ISPs log DNS queries at the resolver and share this information
   with third-parties in ways not known or obvious to end users.

The IETF's DPRIVE (*D*NS *PRIV*ate *E*xchange) Working Group has taken
initial protocol steps to address these concerns (with much of the early
work focussing on the stub to resolver problem), publishing DNS Privacy
Considerations (RFC 7626), Specification for DNS over Transport Layer
Security (RFC 7858), and The EDNS(0) Padding Option (RFC 7830), and DNS
Query Name Minimisation to Improve Privacy (RFC 7816). However because of
the great diversity of the DNS ecosystem, and the pervasive role of DNS and
domain names in Internet applications and security, much is not fully
understood or resolved.

The goal of this workshop is to bring together privacy and Internet
researchers with a diversity of backgrounds and views, to identify
promising long-term mitigations of the broad space of DNS privacy risks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.dns-oarc.net/pipermail/dns-operations/attachments/20170111/9f61a203/attachment.html>