[dns-privacy] NOTE Updated date and time of DPRIVE session at IETF113

All Please note the new date and time for DPRIVE * Date: Thursday 24 March 2022 * Time: 1430-1515 CEST (UTC+1) In preparing for this meeting we realized we would not need a full two hour session. In discussion with Eric our AD it was suggested we share the time slot with the ADD WG *for time opt

Re: [dns-privacy] DPRIVE WG action items

All Thanks for the reviews from folks. I just want to point out (and thank!) Paul Hoffman for taking the review comments and putting them in the gitlab issue tracker for the document https://gitlab.com/dkg/dprive-unilateral-probing/-/issues?sort=created_date&state=opened The bigger discussions

Re: [dns-privacy] dprive - Cancelling a meeting request for IETF 114

FYI The DPRIVE session isn't being cancelled, but we're sharing time with the folks in ADD. tim On Fri, Jul 1, 2022 at 5:00 PM IETF Meeting Session Request Tool < session-requ...@ietf.org> wrote: > > > A request to cancel a meeting session has just been submitted by Liz > Flynn, on behalf of t

[dns-privacy] Minutes from IETF114

that does not seem right. Perhaps by the London IETF there could be some unilateral probing experiments during the Hackathon. thanks tim Minutes: - DPRIVE WG 2022-07-26 Chairs: Tim Wicinski and Brian Haberman Notes here only cover comments at the mic, not from the slides Admin stuff and

Re: [dns-privacy] [core] WGA call for draft-lenders-dns-over-coap

DPRIVE is also a fine location. Has anyone implemented DNS over DTLS for your use case? tim On Mon, Aug 15, 2022 at 6:04 AM Jaime Jiménez wrote: > CCing the right DNSOP mailing list now. > > On 15.8.2022 11.26, Jaime Jiménez wrote: > > Dear CoRE WG, > > We would like to start the call for adop

[dns-privacy] Fwd: dprive - Cancelling a meeting request for IETF 115

FYI We are not cancelling, but are doing another combined meeting with ADD. thanks tim -- Forwarded message - From: IETF Meeting Session Request Tool Date: Fri, Oct 14, 2022 at 6:12 PM Subject: dprive - Cancelling a meeting request for IETF 115 To: Cc: , , , < lfl...@amsl.com>

[dns-privacy] IETF NomCom: Selecting Leadership

All The NomCom is tasked with selecting the IETF leadership, like the IESG and the IAB. For the NomCom to be able to make an informed decision, they need feedback from the wider IETF community. Please, allocate some time to provide feedback on people that you interacted with the NomCom with

[dns-privacy] Meeting at IETF116

All The chairs have been discussing and we are currently planning on NOT having a meeting at IETF116. If anyone has issues with this please take this up with the chairs. thanks Tim/Brian ___ dns-privacy mailing list dns-privacy@ietf.org https://www.iet

Re: [dns-privacy] [Ext] Intended Status for draft-ietf-dprive-unilateral-probing

All As Brian and I have stated a few times, and Eric our AD has supported, the plan with this draft is once the authors are ready is to take it to WGLC, and then park it while we wait for implementations, and some signs of interoperability testing. Once we and the working group feel there has bee

Re: [dns-privacy] [Ext] WGLC : draft-ietf-dprive-unilateral-probing

Thanks Paul ! We've been following the gitlab updates and do like the updated version. Brian, we should change the datatracker to say "Waiting for WG Chairs go-ahead" (me bossing Brian around) tim On Fri, May 26, 2023 at 2:01 PM Paul Hoffman wrote: > On Apr 14, 2023, at 11:14 AM, Brian Haberm

Re: [dns-privacy] [Ext] WGLC : draft-ietf-dprive-unilateral-probing

Scott On Mon, Jun 5, 2023 at 3:36 PM Hollenbeck, Scott wrote: > > -Original Message- > > From: dns-privacy On Behalf Of Paul > Hoffman > > Sent: Monday, June 5, 2023 3:32 PM > > To: Tim Wicinski > > Cc: dns-privacy@ietf.org > > Subject:

[dns-privacy] Fwd: NomCom 2023 Call for Volunteers

DNSOP/DPRIVE Martin Thompson is chairing this year's version of the IETF Nominating Committee. It's a good thing to volunteer, and I can speak strongly on the fact that 10+ years of volunteering, and I have not been selected(*). tim (8) Now that I've said that -- Forwarded message -

Re: [dns-privacy] Secdir early review of draft-ietf-dprive-unilateral-probing-07

I pointed out to Mr Salz that Alajuela is the location of the author in question, not their employer. He apologizes for his lack of Geography. (or he should) tim On Fri, Jun 9, 2023 at 4:20 PM Rich Salz via Datatracker wrote: > Reviewer: Rich Salz > Review result: Has Nits > > The term "unila

Re: [dns-privacy] [Ext] WGLC : draft-ietf-dprive-unilateral-probing

Scott On Fri, Jun 9, 2023 at 1:42 PM Hollenbeck, Scott wrote: > > > [SAH] We might be disagreeing on the nature of experimentation, but I most > definitely provided examples of specific, measurable metrics that could be > used to evaluate an experiment: > > > https://mailarchive.ietf.org/arch/ms

Re: [dns-privacy] WG Review: DNS PRIVate Exchange (dprive)

Our thought process (or perhaps mine) was that it's so easy to offer to solve everything and you end up solving nothing. I've been reticent to put forth the qname-minimisation work in DNSOP not because I don't think it belongs there, but the time spent on the editorial minutia of the DNSOP r

Re: [dns-privacy] Agenda time.

On 10/12/14 7:35 PM, Paul Hoffman wrote: On Oct 12, 2014, at 4:04 PM, Mankin, Allison wrote: I would like to request a 5 minute slot to introduce the idea of a draft on methods of evaluating DNS privacy. 5 minutes is not enough; it should be more. I agree with Paul. I think 15 minutes

Re: [dns-privacy] Call for Adoption: draft-bortzmeyer-dnsop-dns-privacy

With no hat, I too support adoption of this document. tim On 10/17/14 9:54 AM, Olafur Gudmundsson wrote: On Oct 17, 2014, at 12:41 PM, Warren Kumari wrote: Dear DPRIVE WG, This starts a Call for Adoption for draft-bortzmeyer-dnsop-dns-privacy. [ Please note: I am assuming that Stephane

Re: [dns-privacy] The case for both ends of 'end-to-end'

On 10/24/14 8:36 AM, Frederico A C Neves wrote: On Fri, Oct 24, 2014 at 08:18:54AM -0400, Phillip Hallam-Baker wrote: On Fri, Oct 24, 2014 at 1:57 AM, Watson Ladd wrote: ... The DoS and amplification attacks are the reasons why I believe that whatever mechanism we choose needs to authenti

[dns-privacy] DPRIVE next steps

(I was waiting to confirm the wording with Warren, but I failed to remember he was away last week). Coming out of IETF91, we saw good discussion around the problem statement; the beginnings of a discussion around evaluation metrics; and several different solutions searching for the appropria

Re: [dns-privacy] DPRIVE next steps

. tim On 11/24/14 5:02 PM, Phillip Hallam-Baker wrote: On Mon, Nov 24, 2014 at 4:22 PM, Tim Wicinski wrote: (I was waiting to confirm the wording with Warren, but I failed to remember he was away last week). Coming out of IETF91, we saw good discussion around the problem statement; the beginnings

Re: [dns-privacy] DPRIVE next steps

On 11/24/14 5:26 PM, Melinda Shore wrote: On 11/24/14 1:05 PM, Tim Wicinski wrote: I did not say a requirements document. I said the Problem Statement, and evaluation metrics. Neither are requirements. I've been concerned about the proliferation of problem statement documents (and use

Re: [dns-privacy] (re-)identifying from sets of queries (was Re: Start of WGLC for draft-ietf-dprive-problem-statement - please review.)

On 2/27/15 2:30 AM, John Heidemann wrote: On Thu, 26 Feb 2015 12:51:23 +, Stephen Farrell wrote: Hiya, On 26/02/15 12:43, Brian Haberman wrote: Are you thinking of looking at patterns of qname values/labels or just some number of packets going towards a DNS resolver within a certain tim

Re: [dns-privacy] (re-)identifying from sets of queries (was Re: Start of WGLC for draft-ietf-dprive-problem-statement - please review.)

On 2/27/15 10:46 AM, Stephane Bortzmeyer wrote: On Fri, Feb 27, 2015 at 10:38:53AM -0500, Phillip Hallam-Baker wrote a message of 78 lines which said: BTW are we planning to IETF last call this doc and publish as an RFC or is this internal only? The charter is silent about it. My goal

Re: [dns-privacy] Start of WGLC for draft-ietf-dprive-problem-statement - please review.

I agree with Warren that there is solid consensus. tim (I'm traveling as well the next two weeks, working with a slight delay) On 3/9/15 2:18 PM, Warren Kumari wrote: Oh, I should mention that I'm at IEEE in Berlin at the moment, and so I haven't confirmed this call with my co-chair. It's p

[dns-privacy] Looking for minute takers and Jabber Scribes for dprive session

All We're soliciting Jabber Scribes and Minute takers for Monday's session. Please let us know if you're willing to assist. I've been told that such folks will be given shiny stickers to commemorate their assistance. Who can say no to shiny stickers? thanks tim _

Re: [dns-privacy] Draft minutes posted.

There are here: http://www.ietf.org/proceedings/92/minutes/minutes-92-dprive tim On 4/3/15 11:24 PM, Stephane Bortzmeyer wrote: On Wed, Apr 01, 2015 at 06:11:19PM -0400, Warren Kumari wrote a message of 20 lines which said: Draft minutes for DPRIVE have been posted. Posted where? _

Re: [dns-privacy] Draft minutes posted.

I've updated the minutes with the changes submitted and pushed them to up. http://www.ietf.org/proceedings/92/minutes/minutes-92-dprive tim On 4/3/15 11:40 AM, Tim Wicinski wrote: There are here: http://www.ietf.org/proceedings/92/minutes/minutes-92-dprive tim On 4/3/15 11:

Re: [dns-privacy] Call for Adoptions on the 3 documents.

On 4/23/15 7:11 AM, Ilari Liusvaara wrote: Also, it occurs to me that if there is NAT with non-sticky behaviour with UDP DNS (UDP DNS might very well be special-cased), things are not going to work at all without channel identifier (because the ports change constantly). Dunno if such middlebox

Re: [dns-privacy] Call for Adoptions on the 3 documents.

All The Call for Adoption for these three documents has ended. I will attempt to summarize what appears to be the group consensus: TLS for DNS: Initiation and Performance Considerations: http://datatracker.ietf.org/doc/draft-hzhwm-dprive-start-tls-for-dns/ This document has rough con

[dns-privacy] Call For Adoption: draft-wing-dprive-dnsodtls

During the previous Call for Adoption a number of participants expressed interest in adopting this work. WG members felt it needed some improvements, but thought it had potential. The authors addressed the issues and feel it meets what the working group was seeking, and have requested that we

[dns-privacy] Fwd: IETF 93 Preliminary Agenda

All The draft IETF agenda has been published, and it has DPRIVE with a Friday Morning slot for 2.5 hours. Now, Warren and I requested a 1.5 hour slot, but since there were more requests for slots, we can only assume they made the best of the situation. Please do take as a sign for an hour o

[dns-privacy] Last Call for Agenda Time for Prague

The deadline for submitting agenda items is July 5th. If you have any last minute items to put on the agenda, please let us know. thanks tim ___ dns-privacy mailing list dns-privacy@ietf.org https://www.ietf.org/mailman/listinfo/dns-privacy

[dns-privacy] Draft WG Agenda Published

ge (dprive) Meeting:IETF 93, Prague Location: Hilton Prague, Karlin I/II Date: 24 July 2015 Time: 09:00-11:30 CEST Chairs: Warren Kumari Tim Wicinski - Agenda Bashing, Blue Sheets, etc (10 min)

[dns-privacy] Preliminary Minutes Posted

All, I posted the preliminary minutes for the dprive meeting. They can be found here: https://www.ietf.org/proceedings/93/minutes/minutes-93-dprive Thanks to Stephane for note taking at the last minute, even with flaky wireless. To summarize the chairs actions, the first ones were around

Re: [dns-privacy] Start of WGLC for draft-ietf-dprive-dns-over-tls-01

Bob https://datatracker.ietf.org/doc/draft-ietf-dprive-dns-over-tls/ is a working URL thanks for pointing that out tim On 10/22/15 6:59 PM, Bob Harold wrote: On Thu, Oct 22, 2015 at 5:23 AM, Warren Kumari mailto:war...@kumari.net>> wrote: Dear DPRIVE WG, The authors of draft-ietf

[dns-privacy] Minute Takers and Jabber Scribers

Hi We're looking for Jabber Scribes and Minute takers for the DPRIVE meeting monday afternoon. Drop us a note if you're able to help. thanks tim ___ dns-privacy mailing list dns-privacy@ietf.org https://www.ietf.org/mailman/listinfo/dns-privacy

Re: [dns-privacy] draft-am-dprive-eval-02

(no hats) With this new version, I think the document is useful and provides a solid discussion of how to quantify privacy mechanisms for a DNS implementer who is not a security subject matter expert. tim On 11/2/15 6:22 PM, Andrew Sullivan wrote: Despite my comments against the hum at the

[dns-privacy] Call for Adoption: draft-mayrhofer-edns0-padding

stating your view. Please also indicate if you are willing to contribute text, review, etc. This call for adoption ends 17 November, 2015 12:00 UTC Thanks, tim wicinski ___ dns-privacy mailing list dns-privacy@ietf.org https://www.ietf.org/mailman

[dns-privacy] Initial Minutes from Monday's dprive meeting

TF 94, Yokohama Location: Pacifico Yokohama Date: 2 Nov 2015 Time: 17:10-19:10 Chairs: Warren Kumari Tim Wicinski Minutes:Shane Kerr Administrivia Warren / Tim 10 minutes Status report fr

Re: [dns-privacy] Initial Minutes from Monday's dprive meeting

On 11/4/15 11:56 PM, Bob Harold wrote: On Tue, Nov 3, 2015 at 12:52 PM, Tim Wicinski mailto:tjw.i...@gmail.com>> wrote: All I've uploaded the initial minutes from the meeting. Big Big Thanks to Shane Kerr for most excellent note taking. Take a look to make su

Re: [dns-privacy] Call for Adoption: draft-mayrhofer-edns0-padding

dkg, I've already reached out for the EDNS Option Code, and it has been approved by the ExpertReview and we are awaiting IANA. tim On 11/5/15 8:49 AM, Daniel Kahn Gillmor wrote: On Tue 2015-11-03 21:54:27 +0900, Tim Wicinski wrote: During the meeting on Monday, it was obvious the Wo

[dns-privacy] Fwd: [IANA #878759] General Request for Assignment (dns-parameters - draft-mayrhofer-edns0-padding)

ialist ICANN On Tue Nov 03 08:10:21 2015, tjw.i...@gmail.com wrote: > > Contact Name: > Tim Wicinski > > Contact Email: > tjw.i...@gmail.com > > Type of Assignment: > New EDNS EDNS0 Option Codes (OPT) > > > Registry: > http://www.iana.org/assignments

Re: [dns-privacy] Start of WGLC for draft-ietf-dprive-dns-over-tls-01

(as chair) I don't see the point in holding up this document for the other DTLS document(s). Using the "running code" practice, there is code out here which supports dns-over-tls. The authors of dns-over-dtls do not have a plan to implement any solutions at this time. However, as chair,

Re: [dns-privacy] Start of WGLC for draft-ietf-dprive-dns-over-tls-01

All, The WGLC has finished, and it appears to be rough consensus on moving forward. I want to touch base with my co-chair and AD on one issue, but I will work on the Shepherd write up over the next few days and submit it into the pipeline. I plan on mentioning the issues raised about waitin

Re: [dns-privacy] Start of WGLC for draft-ietf-dprive-dns-over-tls-01

On 11/13/15 8:22 AM, Paul Hoffman wrote: Just to be clear: do the chairs read the rough consensus to be that the draft needs to remove Sections 3.2 and all of Section 4, and move them to a new document? --Paul Hoffman Yes, I do (once I remembered). I am circling back with the others, but

Re: [dns-privacy] Non-zero padding (was EDNS0 padding with non-0 MUST respond with FORMERR?)

Alex Why don't you propose some text, as we have a bandwidth delay product with you. thanks tim On 11/17/15 5:30 PM, Alex Mayrhofer wrote: Hello, Jumping into this thread late, sorry. Anyways, my proposal: - I think we should stick with requiring 0x00 padding (I am avoiding the term 'payl

Re: [dns-privacy] Call for Adoption: draft-mayrhofer-edns0-padding

Hi The Call for Adoption ended and we have strong consensus to adopt the document. The document is also very close to WGLC, once the padding discussion has been sussed out. Thank you all for your comments and reviews. tim On 11/3/15 7:54 AM, Tim Wicinski wrote: During the meeting on

[dns-privacy] Working Group Last Call for draft-ietf-dprive-edns0-padding

This starts a Working Group Last Call for draft-ietf-dprive-edns0-padding Current versions of the draft is available here: https://datatracker.ietf.org/doc/draft-ietf-dprive-edns0-padding/ Please review the draft and offer relevant comments. Also, if someone feels the document is *not

[dns-privacy] Call for Adoption: draft-dgr-dprive-dtls-and-tls-profiles

to contribute text, review, etc. This call for adoption ends 26 January 2016 Thanks, tim wicinski DPRIVE co-chair ___ dns-privacy mailing list dns-privacy@ietf.org https://www.ietf.org/mailman/listinfo/dns-privacy

Re: [dns-privacy] Fwd: [DNSOP] Confusing title of draft-ietf-dprive-dns-over-tls

This traveling chair agrees with the other traveling chair. tim On 2/20/16 4:49 PM, Warren Kumari wrote: On Fri, Feb 19, 2016 at 12:04 PM Wessels, Duane mailto:dwess...@verisign.com>> wrote: The message below was sent to dnsop rather than dprive. Myself and coauthor Paul Hoffman a

Re: [dns-privacy] Spencer Dawkins' Yes on draft-ietf-dprive-edns0-padding-02: (with COMMENT)

Shane's explanation on padding is a great summary of the mailing list discussion during the document review. tim (as DocumentShepherd) On 3/1/16 5:39 AM, Shane Kerr wrote: Spencer, At 2016-02-29 20:38:34 -0800 "Spencer Dawkins" wrote: Thanks for producing this draft. I do have one questio

[dns-privacy] Jabber Scribes and note takes for DPRIVE

All We don't have a long agenda, but we could use a jabber scribe(s) and note takes for DPRIVE Wednesday morning @10am. Please drop us a note if you are able to assist and we would be grateful thanks tim ___ dns-privacy mailing list dns-privacy@i

[dns-privacy] DNS + 0-RTT

As many of you are aware, with the TLS1.3 spec, there is some security concerns around DNS+TLS1.3 0-RTT. dkg put together some threat models and instead of forwarding some long thread, I figure I would put this out there and let Mr. Gilmor lay out his theories. Daniel, you're it. tim

[dns-privacy] DPRIVe Agenda requests for Berlin

All Since the last meeting, the DNS over TLS draft has been published as RFC7858. The drafts on DNS over DTLS and the Profiles drafts received feedback during the last meeting and we are awaiting updates. The chairs have requested a slot for the upcoming Berlin meeting, though we feel that

Re: [dns-privacy] DPRIVe Agenda requests for Berlin

, Tim Wicinski wrote: All Since the last meeting, the DNS over TLS draft has been published as RFC7858. The drafts on DNS over DTLS and the Profiles drafts received feedback during the last meeting and we are awaiting updates. The chairs have requested a slot for the upcoming Berlin meeting

Re: [dns-privacy] Recharter discussion? (was DPRIVe Agenda requests for Berlin)

lysis, but it seems like encrypting resolver-to-authority is more-or-less well understood. Cheers, -- Shane At 2016-06-02 12:00:43 -0400 Tim Wicinski wrote: All Since we never heard anything back from folks about needed face time in Berlin, Warren and I have decided to cancel our time slot a

Re: [dns-privacy] I-D Action: draft-ietf-dprive-dtls-and-tls-profiles-03.txt

All, I know everyone wants to work on the Next Thing, but we'd like to get some reviews of this draft. The chairs are hoping to have this in WGLC before the next meeting. thanks tim On 7/8/16 6:37 PM, Sara Dickinson wrote: Hi All, This is a minor update which adds some additional text t

[dns-privacy] Status of draft-ietf-dprive-dnsodtls and moving forward

All We've seen the updates from the authors on this draft, and their addressing all the review comments, and that the document is "ready for Working Group Last Call." However, there is a question on to the Intended Status of the document as it moves forward. The document has always claims

Re: [dns-privacy] Start of WGLC for draft-ietf-dprive-dnsodtls.

On 8/31/16 1:54 AM, Tirumaleswar Reddy (tireddy) wrote: Hi Allison, Thanks for the review. Please see inline [TR] *From:*Allison Mankin [mailto:allison.man...@gmail.com] *Sent:* Wednesday, August 31, 2016 5:36 AM *To:* Tirumaleswar Reddy (tireddy) *Cc:* Warren Kumari ; dns-privacy@ietf.o

[dns-privacy] Working Group Last Call draft-ietf-dprive-dtls-and-tls-profile

All, This document has been in holding pattern while the dns-over-dtls document was addressed and moved forward. Also, the authors were waiting to hear from one straggler author (dkg, the secure courtesy phone please). The chairs feel we will use the WGLC as a forcing function the latter is

Re: [dns-privacy] Draft minutes form IETF97

The most excellent summary Sara said at the mic was "Hard Fail is Toast". Also, Paul's memory is correct - Leave Fallback alone. tim On 11/25/16 3:58 PM, Paul Hoffman wrote: On 25 Nov 2016, at 11:38, Warren Kumari wrote: Hi all, I have uploaded draft minutes from the DPRIVE meeting in Seo

[dns-privacy] Thanks for input on padding-profile draft....now can we talk TLS Profiles?

All We are grateful for the feedback on edns-padding-profile document, The Chairs would like to get some more comments on the TLS Profiles draft, found here: https://datatracker.ietf.org/doc/draft-ietf-dprive-dtls-and-tls-profiles/ There was some good discussion during the meeting in Seoul,

Re: [dns-privacy] Padding policies draft

On 6/28/17 12:01 PM, Sara Dickinson wrote: On 13 Jun 2017, at 08:37, Shane Kerr > wrote: Alexander and all, tl;dr Lets move forward with our best guesses now. dkg's recommendations seem good, but maybe we can tweak these based on expected maximum

[dns-privacy] Administrative: Minute Takers, Jabber Scribe and

All Putting out a call for folks to take minutes at DPRIVE Tuesday Morning, as well as Jabber Scribe. If you can please drop the chairs a note. Also, if you are presenting, we would like to see slides by Tomorrow afternoon. Thanks and see you all Tuesday Morning bright and early tim __

[dns-privacy] Draft Minutes from DPRIVE,

NS Privacy Exchange (DPRIVE) WG IETF 99, Prague Tuesday, 18 July 2017, 09:30-12:00 CEST Chairs: Tim Wicinski and Brian Haberman Minutes taken by Paul Hoffman Text from the slides is not reproduced here draft-ietf-dprive-dtls-and-tls-profiles Give it a Review! People need to

[dns-privacy] IETF101 Call for Agenda Requests

All The preliminary agenda for IETF101 was released: https://datatracker.ietf.org/meeting/101/agenda.html DPRIVE is slated for Wednesday 21 March, 2018  in the first afternoon slot (13:30-15:00) This is a call for requests for agenda topics. Additionally, we have been discussing a DPRIVE

[dns-privacy] IETF102 Agenda

DPRIVE) WG ## IETF 102, Montreal * Date: Wednesday, 18 July 2017 * Time: 13:30-15:00 CEST * Room: Place du Canada * Chair: Tim Wicinski * Chair: Brian Haberman * IESG Overlord: Terry Manderson * [DataTracker](https://datatracker.ietf.org/group/dprive/documents/) --- ## Agenda ### Adm

[dns-privacy] Call for Adoption: draft-dickinson-dprive-bcp-op

This starts a Call for Adoption for draft-dickinson-dprive-bcp-op The draft is available here: https://datatracker.ietf.org/doc/draft-dickinson-dprive-bcp-op/ Please review this draft to see if you think it is suitable for adoption by DPRIVE, and comments to the list, clearly stating your view.

Re: [dns-privacy] Resolver to authoritative discussion guidance

Also If you feel the chairs are missing some aspect of this, please speak up and let's make sure those are covered. thanks Tim On Thu, Jul 19, 2018 at 2:10 PM, Brian Haberman wrote: > All, > The chairs would like to get the WG discussion started on exploring > privacy solutions for recur

Re: [dns-privacy] Resolver to authoritative discussion guidance

is is incorrect, we'd like to hear that. Tim On Thu, Jul 19, 2018 at 2:56 PM, Jim Reid wrote: > On 19 Jul 2018, at 19:30, Tim Wicinski wrote: > > > > For the time being, we would like to bypass the TLD server operator > > perspective. While we are in this phase

Re: [dns-privacy] Resolver to authoritative discussion guidance

ng records vs serving delegations? Tim On Thu, Jul 19, 2018 at 3:28 PM, Hollenbeck, Scott wrote: > *From:* dns-privacy *On Behalf Of *Tim > Wicinski > *Sent:* Thursday, July 19, 2018 3:01 PM > *To:* Jim Reid > *Cc:* Brian Haberman ; dns-privacy@ietf.org > *Subject:* [EXTERNAL

Re: [dns-privacy] Resolver to authoritative discussion guidance

OK, I'll chat with Brian since he's in charge of sending those emails for now, and go there. Tim On Thu, Jul 19, 2018 at 4:43 PM, Jim Reid wrote: > On 19 Jul 2018, at 21:17, Tim Wicinski wrote: > > > > For example, Verisign has .com which is quite large. My Empl

Re: [dns-privacy] Call for Adoption: draft-dickinson-dprive-bcp-op

All Thanks for the feedback -the call for adoption has ended and we have solid consensus to adopt and work on this document. The chairs will work with the authors to upload an updated version. On Mon, Jul 23, 2018 at 3:24 AM, Matthijs Mekking wrote: > > > On 07/18/2018 08:33 PM, Jim Reid wrote

[dns-privacy] Rough Agenda for IETF103

Time: 09:00-11:00 IST * Room: Meeting 1 * Chair: Tim Wicinski * Chair: Brian Haberman * IESG Overlord: Terry Manderson * [DataTracker](https://datatracker.ietf.org/group/dprive/documents/) --- ## Agenda ### Administrivia * Agenda Bashing, Blue Sheets, etc, 10 min ### Step 2 Discussio

Re: [dns-privacy] DNS PRIVate Exchange (dprive) WG Virtual Meeting: 2018-12-10

I see dialing info of 1-650-479-3208 Call-in toll number (US/Canada) Access code: 640 873 331 I am digging up alternative numbers. On Mon, Dec 10, 2018 at 9:18 AM Henderson, Karl wrote: > Is there a dial-in number for the dprive webex meeting today? > _

[dns-privacy] Draft Minutes from DPRIVE IETF104

All Here are the draft minutes from this morning's meeting. https://datatracker.ietf.org/meeting/104/materials/minutes-104-dprive-00 Please drop a note to the chairs or the list with any updates, comments, etc. Tim ___ dns-privacy mailing list dns-pri

[dns-privacy] Draft Minutes for IETF105

-materials/blob/master/dprive-ietf105/dprive-ietf105-minutes.txt Thanks for Brian for running the meeting and Suzanne for filling in for me. Tim DNS Privacy Exchange (DPRIVE) WG IETF 105, Montreal 2019-07-25 15:50 local time Chairs: Brian Haberman and Tim Wicinski Suzanne Woolf sitting in for Tim

[dns-privacy] Working Group Last Call for draft-ietf-dprive-rfc7626-bis

This starts a Working Group Last Call for draft-ietf-dprive-rfc7626-bis Current versions of the draft is available here: https://datatracker.ietf.org/doc/draft-ietf-dprive-rfc7626-bis/ The Current Intended Status of this document is: Informational Please review the draft and offer relevant comm

[dns-privacy] Working Group Last Call for draft-ietf-dprive-bcp-op

This starts a Working Group Last Call for draft-ietf-dprive-bcp-op Current versions of the draft is available here: https://datatracker.ietf.org/doc/draft-ietf-dprive-bcp-op/ The Current Intended Status of this document is: Best Current Practices Please review the draft and offer relevant comme

[dns-privacy] Call for Adoption: draft-hzpa-dprive-xfr-over-tls

This starts a Call for Adoption for draft-hzpa-dprive-xfr-over-tls The draft is available here: https://datatracker.ietf.org/doc/draft-hzpa-dprive-xfr-over-tls/ Please review this draft to see if you think it is suitable for adoption by DPRIVE, and comments to the list, clearly stating your view.

Re: [dns-privacy] I-D Action: draft-ietf-dprive-bcp-op-05.txt

Thanks Stephen (Follow up on this in another email) On Thu, Oct 31, 2019 at 9:16 AM Stephen Farrell wrote: > > Hiya, > > On 31/10/2019 13:12, Sara Dickinson wrote: > > Hi All, > > > > Following the DPRIVE interim meeting earlier this week I’ve done an > > update to the draft with two main chan

[dns-privacy] Second Working Group Last Call for draft-ietf-dprive-bcp-op

The working group has given lots of feedback on this and the authors have worked to address all these concerns. The last larger item was discussed and resolved during our interim. We want to run a 1 Week WGLC to confirm all outstanding items have been resolved. This starts a Second Working Gr

[dns-privacy] Tentative agenda for DPRIVE IETF 106

o be there remotely. We will need minute takers and jabber scribes. Thanks Tim/Brian # DNS Privacy Exchange (DPRIVE) WG ## IETF 106, Singapore * Date: 22 November 2019 * Time: 1000-1200 SST 1500-1700 UTC * Room: Collyer * Chair: Tim Wicinski * Chair: Brian Haberman * Very Responsible Are

Re: [dns-privacy] Call for Adoption: draft-hzpa-dprive-xfr-over-tls

Hi The call for adoption for this document has finished and we've received consensus on adopting this work. On Wed, Nov 6, 2019 at 11:24 AM Robert Edmonds wrote: > Tim Wicinski wrote: > > This starts a Call for Adoption for draft-hzpa-dprive-xfr-over-tls > > > > T

[dns-privacy] Draft Minutes from IETF106 meeting

DPRIVE WG IETF 106, Singapore Chairs: Tim Wicinski, Brian Haberman (remote) Minutes taken by Paul Hoffman Text from slides not given here Admiistrivia Adaptive DNS: Improving Privacy of Name Resolution draft-pauly-dprive-adaptive-dns-privacy Tommy Pauly Tim: Which list for discussion

Re: [dns-privacy] [Errata Held for Document Update] RFC7858 (5375)

I agree with Patrick's comment that the folks from DNScrypt should be the ones giving us the guidance here. Tim (wearing the hat today, so Warren doesn't have to) On Mon, Dec 23, 2019 at 1:01 PM Patrick Mevzek wrote: > On 23/12/2019 12:54, Warren Kumari wrote: > > > W > > p.s: if it were mine,

[dns-privacy] DPRIVE Interim Meeting 8 April 2020 16:00-17:30 UTC

All, Here’s some more information and preparation material for DPRIVE WG Virtual meeting: Date: Wednesday April 8th, 2020 Time: 16:00-17:30 (UTC) Location: WebEx https://ietf.webex.com/ietf/j.php?MTID=m88e3d0d091544ea59c79eb5e610a115a Jabber: xmpp:dpr...@jabber.ietf.org?join

[dns-privacy] Call for Adoption: draft-huitema-dprive-dnsoquic

This starts a Call for Adoption for draft-huitema-dprive-dnsoquic The draft is available here: https://datatracker.ietf.org/doc/draft-huitema-dprive-dnsoquic/ Please review this draft to see if you think it is suitable for adoption by DPRIVE, and comments to the list, clearly stating your view.

[dns-privacy] Call for Adoption: draft-ghedini-dprive-early-data

This starts a Call for Adoption for draft-ghedini-dprive-early-data The draft is available here: https://datatracker.ietf.org/doc/draft-ghedini-dprive-early-data/ Please review this draft to see if you think it is suitable for adoption by DPRIVE, and comments to the list, clearly stating your vie

[dns-privacy] DPRIVE Interim 2020-01 Minutes, Actions

All Brian and I thank all for attending the DPRIVE interim yesterday, and we want to thank Eric our AD for helping out with slides at the last minute. I've uploaded the minutes which were in the Etherpad (Thanks Benno!) https://datatracker.ietf.org/doc/minutes-interim-2020-dprive-01-202004081600

Re: [dns-privacy] Call for Adoption: draft-huitema-dprive-dnsoquic

All The call for adoption has ended and strong consensus to adopt. Thanks for all the feedback. tim On Wed, Apr 22, 2020 at 6:18 AM Benno Overeinder wrote: > I support the adoption of the draft and I am willing to contribute/review. > > -- Benno > > > On 08/04/2020 18:41,

Re: [dns-privacy] Call for Adoption: draft-ghedini-dprive-early-data

> > Best, > Chris > > On Tue, Apr 14, 2020, at 2:42 AM, Stephen Farrell wrote: > > > > I support adoption. There's work to be done on it, but > > it's a good start and should be a useful document. > > > > S. > > > > On 08/04/2020

Re: [dns-privacy] Possible use case: Opportunistic encryption for recursive to authoritative

(speaking not as a chair) I think this is worth doing. tim On Thu, Aug 6, 2020 at 3:45 PM John R. Levine wrote: > Yes, this is worth doing. Agree with comments that it has to be > compatible with non-opportunistic encryption. > > R's, > John > > PS: RFC 7435. > > > Greetings again. The foll

Re: [dns-privacy] Warren Kumari's Discuss on draft-ietf-dprive-rfc7626-bis-06: (with DISCUSS and COMMENT)

Warren On Wed, Oct 7, 2020 at 4:40 PM Warren Kumari wrote: > On Wed, Oct 7, 2020 at 3:29 PM Brian Haberman > wrote: > > > > Hi Warren, > > Thanks for the feedback. I have a couple of responses (as document > > shepherd) inline... > > > > On 10/5/20 5:42 PM, Warren Kumari via Datatracker w

Re: [dns-privacy] Warren Kumari's Discuss on draft-ietf-dprive-rfc7626-bis-06: (with DISCUSS and COMMENT)

Warren There are many ways in which supposed "private" resources currently leak. A few examples are DNSSEC NSEC zone walking; passive-DNS services; etc. with the references added in. and changing the section title tim On Wed, Oct 7, 2020 at 8:16 PM Warren Kumari wrote: > On Wed, O

Re: [dns-privacy] Erik Kline's Yes on draft-ietf-dprive-rfc7626-bis-06: (with COMMENT)

On Tue, Oct 6, 2020 at 2:04 AM Erik Kline via Datatracker wrote: > Erik Kline has entered the following ballot position for > draft-ietf-dprive-rfc7626-bis-06: Yes > > When responding, please keep the subject line intact and reply to all > email addresses included in the To and CC lines. (Feel fr

Re: [dns-privacy] Robert Wilton's No Objection on draft-ietf-dprive-rfc7626-bis-06: (with COMMENT)

Rob On Mon, Oct 5, 2020 at 8:40 AM Robert Wilton via Datatracker < nore...@ietf.org> wrote: > Robert Wilton has entered the following ballot position for > draft-ietf-dprive-rfc7626-bis-06: No Objection > > When responding, please keep the subject line intact and reply to all > email addresses in

Re: [dns-privacy] Murray Kucherawy's No Objection on draft-ietf-dprive-rfc7626-bis-06: (with COMMENT)

On Thu, Oct 8, 2020 at 2:23 AM Murray Kucherawy via Datatracker < nore...@ietf.org> wrote: > Murray Kucherawy has entered the following ballot position for > draft-ietf-dprive-rfc7626-bis-06: No Objection > > When responding, please keep the subject line intact and reply to all > email addresses i

Re: [dns-privacy] Benjamin Kaduk's No Objection on draft-ietf-dprive-rfc7626-bis-06: (with COMMENT)

Rob You are not the only person to request the summary of changes. It's a fine idea and we'll pull something together. tim On Wed, Oct 7, 2020 at 1:29 AM Rob Sayre wrote: > On Tue, Oct 6, 2020 at 10:23 PM Benjamin Kaduk wrote: > >> Perhaps "search" was not the best word to use >> > > I thin

Re: [dns-privacy] Roman Danyliw's No Objection on draft-ietf-dprive-rfc7626-bis-06: (with COMMENT)

On Wed, Oct 7, 2020 at 8:44 AM Roman Danyliw via Datatracker < nore...@ietf.org> wrote: > Roman Danyliw has entered the following ballot position for > draft-ietf-dprive-rfc7626-bis-06: No Objection > > When responding, please keep the subject line intact and reply to all > email addresses include

  1   2   >