Skip to main content

DNS PRIVate Exchange
charter-ietf-dprive-02

Revision differences

Document history

Date Rev. By Action
2019-03-27
02 Amy Vezza Responsible AD changed to Éric Vyncke from Terry Manderson
2018-05-25
02 Cindy Morgan New version available: charter-ietf-dprive-02.txt
2018-05-25
01-01 Cindy Morgan State changed to Approved from Internal review
2018-05-25
01-01 Cindy Morgan IESG has approved the charter
2018-05-25
01-01 Cindy Morgan Closed "Ready w/o external review" ballot
2018-05-25
01-01 Cindy Morgan WG action text was changed
2018-05-24
01-01 Alexey Melnikov [Ballot comment]
I am still trying to figure out if there are any any interactions between this work and what DOH WG is working on.
2018-05-24
01-01 Alexey Melnikov Ballot comment text updated for Alexey Melnikov
2018-05-24
01-01 Ignas Bagdonas [Ballot Position Update] New position, No Objection, has been recorded for Ignas Bagdonas
2018-05-24
01-01 Martin Vigoureux [Ballot Position Update] New position, No Objection, has been recorded for Martin Vigoureux
2018-05-23
01-01 Eric Rescorla
[Ballot comment]
LGTM.

I found this milestone a bit opaque. Perhaps a little expansion?

"Nov 2018 Unpublished document on requirements for DNS privacy services between …
[Ballot comment]
LGTM.

I found this milestone a bit opaque. Perhaps a little expansion?

"Nov 2018 Unpublished document on requirements for DNS privacy services between recursive and authoritative servers (Wiki) "
2018-05-23
01-01 Eric Rescorla [Ballot Position Update] New position, No Objection, has been recorded for Eric Rescorla
2018-05-23
01-01 Terry Manderson New version available: charter-ietf-dprive-01-01.txt
2018-05-23
01-00 Terry Manderson Added charter milestone "Submit draft on DNS privacy exchanges involving authoritative servers (Exp)", due November 2019
2018-05-23
01-00 Terry Manderson Added charter milestone "Submit draft on DNS privacy performance metrics and actual measurements (Info)", due March 2019
2018-05-23
01-00 Terry Manderson Added charter milestone "Submit draft on operating DNS privacy services for publication (BCP)", due March 2019
2018-05-23
01-00 Terry Manderson Added charter milestone "Unpublished document on requirements for DNS privacy services between recursive and authoritative servers (Wiki)", due November 2018
2018-05-23
01-00 Terry Manderson [Ballot Position Update] New position, Yes, has been recorded for Terry Manderson
2018-05-23
01-00 Benjamin Kaduk
[Ballot comment]
It took me a couple tries to read "performance data" as what I think
is intended, "efficacy in preserving privacy in the face …
[Ballot comment]
It took me a couple tries to read "performance data" as what I think
is intended, "efficacy in preserving privacy in the face of
pervasive monitoring attacks", as opposed to the more expected
interpretation as "cost in energy/CPU cycles/etc. per bits served". 

There seems to be a minor internal inconsistency between "some of
the results of this working group may be experimental" and the new
work item for potential solutions for confidentiality with
authoritative servers, marked definitively (?) as Experimental in a 
parenthetical.

I'm weakly inclined to go through External Review for these changes.
2018-05-23
01-00 Benjamin Kaduk [Ballot Position Update] New position, No Objection, has been recorded for Benjamin Kaduk
2018-05-23
01-00 Suresh Krishnan [Ballot Position Update] New position, No Objection, has been recorded for Suresh Krishnan
2018-05-23
01-00 Ben Campbell
[Ballot comment]
I'm fine for this going to external review, or directly to approval without an external review. However, if we do the latter it …
[Ballot comment]
I'm fine for this going to external review, or directly to approval without an external review. However, if we do the latter it would be nice to see milestones prior to approval.
2018-05-23
01-00 Ben Campbell [Ballot Position Update] New position, Yes, has been recorded for Ben Campbell
2018-05-23
01-00 Alissa Cooper [Ballot Position Update] New position, Yes, has been recorded for Alissa Cooper
2018-05-23
01-00 Adam Roach
[Ballot comment]
> development of documents focused on: 1) providing confidentiality
> to DNS transactions between Iterative Resolvers and Authoritative
> Servers, 2) measuring the …
[Ballot comment]
> development of documents focused on: 1) providing confidentiality
> to DNS transactions between Iterative Resolvers and Authoritative
> Servers, 2) measuring the performance of the proposed solutions
> against pervasive monitoring, and 3) define operational, policy, and

Nit: "defining"
2018-05-23
01-00 Adam Roach [Ballot Position Update] New position, Yes, has been recorded for Adam Roach
2018-05-23
01-00 Alvaro Retana [Ballot Position Update] New position, No Objection, has been recorded for Alvaro Retana
2018-05-22
01-00 Deborah Brungard [Ballot Position Update] New position, No Objection, has been recorded for Deborah Brungard
2018-05-18
01-00 Spencer Dawkins
[Ballot comment]
Please note - my ballot position is Yes, but the responsible AD hasn't balloted yet, so please don't charter this work based on …
[Ballot comment]
Please note - my ballot position is Yes, but the responsible AD hasn't balloted yet, so please don't charter this work based on MY Yes!

Beyond that, I'm a Yes with a thought, that doesn't even need to be discussed before this charter is approved, but I'm looking at this deliverable

"2) measuring the performance of the proposed solutions
against pervasive monitoring"

and the corresponding milestone

"- Define, collect and publish performance data measuring effectiveness
of DPRIVE-published technologies against pervasive monitoring
attacks."

and thinking that IFF this turns out to be performance data collection and measurement that could benefit from interaction with IPPM, MAPRG, or both, that might be a useful possibility to keep in mind.

I don't see any reason to adjust the charter to reflect that possibility, of course.  And I'm pretty sure that the more work you do on this, the clearer that will become, so please start doing the work, and if it turns out we should talk, we can talk then :-)
2018-05-18
01-00 Spencer Dawkins [Ballot Position Update] New position, Yes, has been recorded for Spencer Dawkins
2018-05-18
01-00 Mirja Kühlewind [Ballot comment]
Aren't the first two bullet points obsolete by now? If that works is already concluded, I would recommend to remove them.
2018-05-18
01-00 Mirja Kühlewind [Ballot Position Update] New position, No Objection, has been recorded for Mirja Kühlewind
2018-05-13
01-00 Alexey Melnikov [Ballot Position Update] New position, No Objection, has been recorded for Alexey Melnikov
2018-05-11
01-00 Amy Vezza Telechat date has been changed to 2018-05-24 from 2014-10-16
2018-05-10
01-00 Terry Manderson WG action text was changed
2018-05-10
01-00 Terry Manderson WG review text was changed
2018-05-10
01-00 Terry Manderson WG review text was changed
2018-05-10
01-00 Terry Manderson Created "Ready w/o external review" ballot
2018-05-10
01-00 Terry Manderson State changed to Internal review from Informal IESG review
2018-05-10
01-00 Cindy Morgan State changed to Informal IESG review from Approved
2018-05-10
01-00 Cindy Morgan New version available: charter-ietf-dprive-01-00.txt
2018-01-30
01 Amy Vezza Responsible AD changed to Terry Manderson from Brian Haberman
2015-10-14
01 (System) Notify list changed from warren@kumari.net, tjw.ietf@gmail.com to (None)
2014-10-17
01 Cindy Morgan New version available: charter-ietf-dprive-01.txt
2014-10-17
00-03 Cindy Morgan State changed to Approved from IESG review
2014-10-17
00-03 Cindy Morgan IESG has approved the charter
2014-10-17
00-03 Cindy Morgan Closed "Approve" ballot
2014-10-17
00-03 Cindy Morgan Closed "Ready for external review" ballot
2014-10-17
00-03 Cindy Morgan WG action text was changed
2014-10-16
00-03 Brian Haberman New version available: charter-ietf-dprive-00-03.txt
2014-10-16
00-02 Alia Atlas [Ballot Position Update] New position, No Objection, has been recorded for Alia Atlas
2014-10-16
00-02 Benoît Claise [Ballot comment]
Mar 2015 - WG selects one or more primary protocol directions

Not sure what "primary" and "directions" are intended to express.
2014-10-16
00-02 Benoît Claise [Ballot Position Update] New position, No Objection, has been recorded for Benoit Claise
2014-10-16
00-02 Ted Lemon [Ballot Position Update] New position, Yes, has been recorded for Ted Lemon
2014-10-16
00-02 Stephen Farrell [Ballot Position Update] New position, Yes, has been recorded for Stephen Farrell
2014-10-16
00-02 Joel Jaeggli [Ballot Position Update] New position, No Objection, has been recorded for Joel Jaeggli
2014-10-15
00-02 Richard Barnes
[Ballot comment]
"end users’ privacy" -- ZOMG, non-ASCII characters!

"The Working Group will also develop an evaluation document" -- As with Pete's comment on the …
[Ballot comment]
"end users’ privacy" -- ZOMG, non-ASCII characters!

"The Working Group will also develop an evaluation document" -- As with Pete's comment on the DTN charter, this seems like a very attractive rathole.
2014-10-15
00-02 Richard Barnes [Ballot Position Update] New position, No Objection, has been recorded for Richard Barnes
2014-10-15
00-02 Kathleen Moriarty
[Ballot comment]
Just one possible nit, there are a few ??? showing up toward the end of the charter that probably are not meant to …
[Ballot comment]
Just one possible nit, there are a few ??? showing up toward the end of the charter that probably are not meant to be there.
2014-10-15
00-02 Kathleen Moriarty [Ballot Position Update] New position, Yes, has been recorded for Kathleen Moriarty
2014-10-15
00-02 Jari Arkko [Ballot Position Update] New position, Yes, has been recorded for Jari Arkko
2014-10-15
00-02 Adrian Farrel [Ballot Position Update] New position, No Objection, has been recorded for Adrian Farrel
2014-10-15
00-02 Martin Stiemerling [Ballot Position Update] New position, Yes, has been recorded for Martin Stiemerling
2014-10-15
00-02 Brian Haberman New version available: charter-ietf-dprive-00-02.txt
2014-10-14
00-01 Pete Resnick [Ballot Position Update] New position, Yes, has been recorded for Pete Resnick
2014-10-14
00-01 Barry Leiba [Ballot Position Update] New position, Yes, has been recorded for Barry Leiba
2014-10-14
00-01 Spencer Dawkins [Ballot Position Update] New position, No Objection, has been recorded for Spencer Dawkins
2014-10-14
00-01 Brian Haberman [Ballot Position Update] New position, Yes, has been recorded for Brian Haberman
2014-10-14
00-01 Brian Haberman Created "Approve" ballot
2014-10-14
00-01 Brian Haberman State changed to IESG review from External review
2014-10-03
00-01 Amy Vezza Telechat date has been changed to 2014-10-16 from 2014-10-02
2014-10-03
00-01 Amy Vezza State changed to External review from Internal review
2014-10-03
00-01 Amy Vezza WG review text was changed
2014-10-03
00-00 Amy Vezza WG review text was changed
2014-10-03
00-00 Brian Haberman Added charter milestone "WG LC on primary protocol directions", due July 2015
2014-10-03
00-00 Brian Haberman Added charter milestone "WG selects one or more primary protocol directions", due March 2015
2014-10-03
00-00 Brian Haberman Added charter milestone "WG LC on an problem statement document", due December 2014
2014-10-03
00-01 Brian Haberman New version available: charter-ietf-dprive-00-01.txt
2014-10-02
00-00 Joel Jaeggli
[Ballot comment]
- Provide confidentiality to DNS transactions.

(for the querier)

resielience against pervasive monitoring is maybe not the only consequence. certain kinds of dns …
[Ballot comment]
- Provide confidentiality to DNS transactions.

(for the querier)

resielience against pervasive monitoring is maybe not the only consequence. certain kinds of dns based gtm may also be rendered less useful by them.
2014-10-02
00-00 Joel Jaeggli [Ballot Position Update] New position, No Objection, has been recorded for Joel Jaeggli
2014-10-02
00-00 Ted Lemon [Ballot Position Update] New position, No Objection, has been recorded for Ted Lemon
2014-10-02
00-00 Spencer Dawkins [Ballot Position Update] New position, Yes, has been recorded for Spencer Dawkins
2014-10-02
00-00 Benoît Claise
[Ballot comment]
Examples of the sorts of risks that DPRIVE will address can be found in
[draft-bortzmeyer-dnsop-dns-privacy], and include both sniffing traffic on …
[Ballot comment]
Examples of the sorts of risks that DPRIVE will address can be found in
[draft-bortzmeyer-dnsop-dns-privacy], and include both sniffing traffic on the
wire and more active attacks, such as MITM attacks.

I'm not too sure what kind of "risks" you have in mind here. Risk of doing what?, risk for whom?
Do you have in mind the "security threats"?
By spending about 1 min on [draft-bortzmeyer-dnsop-dns-privacy], I see that "privacy risk" is mentioned
2014-10-02
00-00 Benoît Claise [Ballot Position Update] New position, No Objection, has been recorded for Benoit Claise
2014-10-01
00-00 Richard Barnes [Ballot Position Update] New position, No Objection, has been recorded for Richard Barnes
2014-10-01
00-00 Jari Arkko [Ballot Position Update] New position, Yes, has been recorded for Jari Arkko
2014-10-01
00-00 Kathleen Moriarty
[Ballot comment]
I support this effort and just have a non-blocking wording question.

Instead of sniffing, should the term "passive wiretapping" be used instead? I …
[Ballot comment]
I support this effort and just have a non-blocking wording question.

Instead of sniffing, should the term "passive wiretapping" be used instead? I don't care too much either way on the wording as the intent is clear, but RFC4949 says the term sniffing has been deprecated.

Examples of the sorts of risks that DPRIVE will address can be found in
[draft-bortzmeyer-dnsop-dns-privacy], and include both sniffing traffic on the
wire and more active attacks, such as MITM attacks.

To maybe:
Examples of the sorts of risks that DPRIVE will address can be found in
[draft-bortzmeyer-dnsop-dns-privacy], and include both passive wiretapping
and more active attacks, such as MITM attacks.
2014-10-01
00-00 Kathleen Moriarty [Ballot Position Update] New position, No Objection, has been recorded for Kathleen Moriarty
2014-10-01
00-00 Alissa Cooper [Ballot Position Update] New position, Yes, has been recorded for Alissa Cooper
2014-10-01
00-00 Adrian Farrel
[Ballot comment]
I'm really glad that this work is happening.

At the level of nits, "The primary focus of this Working Group will be" could …
[Ballot comment]
I'm really glad that this work is happening.

At the level of nits, "The primary focus of this Working Group will be" could s/will be/is/
2014-10-01
00-00 Adrian Farrel [Ballot Position Update] New position, Yes, has been recorded for Adrian Farrel
2014-10-01
00-00 Martin Stiemerling [Ballot Position Update] New position, Yes, has been recorded for Martin Stiemerling
2014-10-01
00-00 Pete Resnick [Ballot Position Update] New position, Yes, has been recorded for Pete Resnick
2014-09-30
00-00 Alia Atlas [Ballot Position Update] New position, No Objection, has been recorded for Alia Atlas
2014-09-23
00-00 Stephen Farrell
[Ballot comment]

Yes, let's do this.

I love (but just don't believe) your timing optimism but am fine with
that if its a useful fiction. …
[Ballot comment]

Yes, let's do this.

I love (but just don't believe) your timing optimism but am fine with
that if its a useful fiction.

I forget if this was discussed or if a conclusion was reached: would
it save time to mention now that some of the results here might be
experimental or not? (I'm fine with any answer btw.)
2014-09-23
00-00 Stephen Farrell [Ballot Position Update] New position, Yes, has been recorded for Stephen Farrell
2014-09-23
00-00 Barry Leiba
[Ballot comment]
A fine charter, and one I fully support.

Just one small point that I question in the text:

    Some of the …
[Ballot comment]
A fine charter, and one I fully support.

Just one small point that I question in the text:

    Some of the main design goals (in no particular order) are:

...

    - Focus on developing deployable solutions.

It would seem to me that developing deployable solutions would be an absolute requirement, not one of the "in no particular order" design goals?  Of what value is a solution we deem not to be deployable?

It would also seem that some of the other design goals are part of how we get to deployable solutions: backward compatibility, minimal configuration effort, and so on.

I suggest just removing that bullet.  To maintain the "deployable" aim, you could also change "develops mechanisms" in the very first paragraph to "develops deployable mechanisms".
2014-09-23
00-00 Barry Leiba [Ballot Position Update] New position, Yes, has been recorded for Barry Leiba
2014-09-23
00-00 Cindy Morgan Placed on agenda for telechat - 2014-10-02
2014-09-23
00-00 Brian Haberman [Ballot Position Update] New position, Yes, has been recorded for Brian Haberman
2014-09-23
00-00 Brian Haberman WG action text was changed
2014-09-23
00-00 Brian Haberman WG review text was changed
2014-09-23
00-00 Brian Haberman Created "Ready for external review" ballot
2014-09-23
00-00 Brian Haberman State changed to Internal review from Informal IESG review
2014-09-16
00-00 Brian Haberman Notification list changed to warren@kumari.net, tjw.ietf@gmail.com
2014-09-16
00-00 Brian Haberman Responsible AD changed to Brian Haberman
2014-09-16
00-00 Brian Haberman Initial review time expires 2014-09-23
2014-09-16
00-00 Brian Haberman State changed to Informal IESG review from Not currently under review
2014-09-16
00-00 Brian Haberman New version available: charter-ietf-dprive-00-00.txt