> -Original Message-
> From: dns-privacy On Behalf Of Paul Hoffman
> Sent: Tuesday, June 27, 2023 9:40 PM
> To: dns-privacy@ietf.org
> Subject: [EXTERNAL] [dns-privacy] Key metrics
>
> Caution: This email originated from outside the organization. Do not click
> links
> or open
From: Tim Wicinski
Sent: Friday, June 9, 2023 9:44 PM
To: Hollenbeck, Scott
Cc: paul.hoff...@icann.org; dns-privacy@ietf.org
Subject: [EXTERNAL] Re: [dns-privacy] [Ext] WGLC :
draft-ietf-dprive-unilateral-probing
Caution: This email originated from outside the organization. Do not click
> -Original Message-
> From: dns-privacy On Behalf Of Paul Hoffman
> Sent: Friday, June 9, 2023 10:52 AM
> To: dns-privacy@ietf.org
> Subject: [EXTERNAL] Re: [dns-privacy] [Ext] WGLC :
> draft-ietf-dprive-unilateral-
> probing
>
> Caution: This email originated from outside the
From: Rob Sayre
Sent: Thursday, June 8, 2023 6:11 PM
To: Hollenbeck, Scott
Cc: paul.hoff...@icann.org; dns-privacy@ietf.org
Subject: [EXTERNAL] Re: Re: [dns-privacy] [Ext] WGLC :
draft-ietf-dprive-unilateral-probing
Caution: This email originated from outside the organization. Do not click
On Jun 6, 2023, at 8:42 PM, Rob Sayre wrote:
Caution: This email originated from outside the organization. Do not click
links or open attachments unless you recognize the sender and know the content
is safe.
On Tue, Jun 6, 2023 at 11:23 AM Hollenbeck, Scott
mailto:40verisign
> -Original Message-
> From: Paul Hoffman
> Sent: Tuesday, June 6, 2023 11:05 AM
> To: Hollenbeck, Scott
> Cc: dns-privacy@ietf.org
> Subject: [EXTERNAL] Re: [dns-privacy] [Ext] WGLC :
> draft-ietf-dprive-unilateral-
> probing
>
> Caution: This
> -Original Message-
> From: dns-privacy On Behalf Of Paul Hoffman
> Sent: Tuesday, June 6, 2023 9:44 AM
> To: dns-privacy@ietf.org
> Subject: [EXTERNAL] Re: [dns-privacy] [Ext] WGLC :
> draft-ietf-dprive-unilateral-
> probing
>
> Caution: This email originated from outside the
> -Original Message-
> From: dns-privacy On Behalf Of Paul Hoffman
> Sent: Monday, June 5, 2023 4:02 PM
> To: Tim Wicinski
> Cc: dns-privacy@ietf.org
> Subject: [EXTERNAL] Re: [dns-privacy] [Ext] WGLC :
> draft-ietf-dprive-unilateral-
> probing
>
> Caution: This email originated from
> -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: [EXTERNAL] Re: [dns-privacy] [Ext] WGLC :
> draft-ietf-dprive-unilateral-
> probing
>
> Caution: This email originated from
> -Original Message-
> From: dns-privacy On Behalf Of Paul Hoffman
> Sent: Friday, May 26, 2023 2:01 PM
> To: dns-privacy@ietf.org
> Cc: George Thessalonikefs
> Subject: [EXTERNAL] Re: [dns-privacy] [Ext] WGLC :
> draft-ietf-dprive-unilateral-
> probing
>
> Caution: This email
> -Original Message-
> From: dns-privacy On Behalf Of Brian
> Haberman
> Sent: Sunday, March 12, 2023 11:43 AM
> To: dns-privacy@ietf.org
> Subject: [EXTERNAL] [dns-privacy] WGLC :
> draft-ietf-dprive-unilateral-probing
>
> All,
> This starts a 2-week WGLC for
>
oes the fact that we will not request publication until there are 2 or more
> interoperable implementations affect your thought process?
>
> Would descriptive text in the text starting WGLC that points out the
> process
> suffice?
>
> Regards,
> Brian
>
followed here.
Scott
From: dns-privacy On Behalf Of Eric Vyncke
(evyncke)
Sent: Monday, March 6, 2023 1:48 AM
To: Hollenbeck, Scott ;
tjw.i...@gmail.com
Cc: paul.hoff...@icann.org; dpr...@ietf.org
Subject: [EXTERNAL] Re: [dns-privacy] [Ext] Intended Status for
draft-ietf-dprive-unilateral
From: Tim Wicinski
Sent: Friday, March 3, 2023 12:59 PM
To: Hollenbeck, Scott
Cc: paul.hoff...@icann.org; dpr...@ietf.org
Subject: [EXTERNAL] Re: [dns-privacy] [Ext] Intended Status for
draft-ietf-dprive-unilateral-probing
Caution: This email originated from outside the organization. Do
> -Original Message-
> From: Paul Hoffman
> Sent: Thursday, March 2, 2023 1:48 PM
> To: Hollenbeck, Scott
> Cc: dpr...@ietf.org
> Subject: [EXTERNAL] Re: [dns-privacy] [Ext] Intended Status for draft-ietf-
> dprive-unilateral-probing
>
> Caution: This em
> -Original Message-
> From: Paul Hoffman
> Sent: Wednesday, March 1, 2023 2:51 PM
> To: Hollenbeck, Scott
> Cc: dpr...@ietf.org
> Subject: [EXTERNAL] Re: [Ext] [dns-privacy] Intended Status for
draft-ietf-
> dprive-unilateral-probing
>
> Caution: This em
After a recent-re-read of draft-ietf-dprive-unilateral-probing and its
normative dependencies, I have a strong belief that the draft describes more of
an experiment than a Proposed Standard. The reason we need "opportunistic" and
"unilateral" actions is because there are gaps in specification,
During yesterday's working group meeting, there was some discussion of
authoritative name server operator positions on support for encryption. I
mentioned Verisign's position back in 2019:
https://mailarchive.ietf.org/arch/msg/dns-privacy/9LsjkTwEjGT46CXH7IsTTLCBqm4/
Verisign also supports the
> -Original Message-
> From: Paul Wouters
> Sent: Monday, August 16, 2021 1:05 PM
> To: Hollenbeck, Scott
> Cc: paul.hoff...@icann.org; dpr...@ietf.org
> Subject: [EXTERNAL] Re: [dns-privacy] [Ext] Security Considerations: Traffic
> Analysis
>
> Caution:
> -Original Message-
> From: Paul Hoffman
> Sent: Monday, August 16, 2021 11:28 AM
> To: Hollenbeck, Scott
> Cc: dpr...@ietf.org
> Subject: [EXTERNAL] Re: [dns-privacy] [Ext] Security Considerations: Traffic
> Analysis
>
> On Aug 16, 2021, at 7:51 AM,
> -Original Message-
> From: Paul Hoffman
> Sent: Monday, August 16, 2021 10:19 AM
> To: Hollenbeck, Scott
> Cc: dpr...@ietf.org
> Subject: [EXTERNAL] Re: [Ext] [dns-privacy] Security Considerations: Traffic
> Analysis
>
> On Aug 16, 2021, at 5:14 AM,
> -Original Message-
> From: dns-privacy On Behalf Of Paul
> Wouters
> Sent: Monday, August 16, 2021 8:38 AM
> To: Hollenbeck, Scott
> Cc: dpr...@ietf.org
> Subject: [EXTERNAL] Re: [dns-privacy] Security Considerations: Traffic
> Analysis
>
> Caution: This
The iterative nature of recursive resolution gives an on-path monitor multiple
opportunities to observe query traffic between a recursive resolver and an
authoritative name server. Even with encryption, the name server IP addresses
can be used to draw accurate conclusions about qnames by
> -Original Message-
> From: Paul Hoffman
> Sent: Tuesday, July 13, 2021 12:18 PM
> To: Hollenbeck, Scott
> Cc: dns-privacy@ietf.org
> Subject: [EXTERNAL] Re: [dns-privacy] [Ext] WG strategy on opportunistic vs
> authenticated moving forward
>
> On Jul 13, 2
> -Original Message-
> From: dns-privacy On Behalf Of Paul
> Hoffman
> Sent: Tuesday, July 13, 2021 11:34 AM
> To: dns-privacy@ietf.org
> Subject: [EXTERNAL] Re: [dns-privacy] [Ext] WG strategy on opportunistic vs
> authenticated moving forward
>
> On Jul 13, 2
From: dns-privacy On Behalf Of Tim Wicinski
Sent: Monday, July 12, 2021 1:12 PM
To: DNS Privacy Working Group
Cc: dprive-cha...@ietf.org
Subject: [EXTERNAL] [dns-privacy] WG strategy on opportunistic vs authenticated
moving forward
Caution: This email originated from outside the
> -Original Message-
> From: dns-privacy On Behalf Of Alexander
> Mayrhofer
> Sent: Wednesday, July 7, 2021 8:36 AM
> To: Andrew Campling
> Cc: Brian Haberman ; dns-privacy@ietf.org
> Subject: [EXTERNAL] Re: [dns-privacy] How do we want to use draft-ietf-
> dprive-phase2-requirements?
>
child zones MAY include those DNS SCVB records in the Additional
> >section of responses to queries to a parent authoritative server.
> >
> > This sounds like a restatement of the definition of "glue". Can we simply
> declare that these records are "glue"?
&
From: dns-privacy On Behalf Of Ben Schwartz
Sent: Monday, May 3, 2021 5:07 PM
To: Peter van Dijk
Cc: DNS Privacy Working Group
Subject: [EXTERNAL] Re: [dns-privacy] Common Features for Encrypted Recursive
to Authoritative DNS
Thanks for this draft; I think it's clear and could be a
> -Original Message-
> From: dns-privacy On Behalf Of Brian
> Haberman
> Sent: Monday, April 19, 2021 5:13 PM
> To: dns-privacy@ietf.org
> Subject: [EXTERNAL] [dns-privacy] How do we want to use draft-ietf-dprive-
> phase2-requirements?
>
> All,
> As was raised on the thread
> -Original Message-
> From: dns-privacy On Behalf Of Paul
> Hoffman
> Sent: Monday, April 19, 2021 1:15 PM
> To: dpr...@ietf.org
> Subject: [EXTERNAL] Re: [dns-privacy] [Ext] A Few More Suggestions for the
> Requirements Draft
>
> On Apr 19, 2021, at 8:08 AM,
I have a few more suggestions for draft-ietf-dprive-phase2-requirements. In
Section 5.1:
After the current requirement #7, I'd like to suggest adding a requirement like
this to make it clear that the authoritative name server determines if server
authentication is required, or not:
"The
> -Original Message-
> From: dns-privacy On Behalf Of Stephen
> Farrell
> Sent: Wednesday, March 31, 2021 8:58 AM
> To: Jim Reid ; Brian Haberman
>
> Cc: dns-privacy@ietf.org
> Subject: [EXTERNAL] Re: [dns-privacy] Root Server Operators Statement on
> DNS Encryption
>
>
> Hiya,
>
> On
This is worth reading:
https://root-servers.org/media/news/Statement_on_DNS_Encryption.pdf
Scott
___
dns-privacy mailing list
dns-privacy@ietf.org
https://www.ietf.org/mailman/listinfo/dns-privacy
> -Original Message-
> From: dns-privacy On Behalf Of Stephen
> Farrell
> Sent: Friday, March 26, 2021 10:02 PM
> To: Eric Rescorla ; Jim Reid
> Cc: DNS Privacy Working Group ; Bill Woodcock
>
> Subject: [EXTERNAL] Re: [dns-privacy] [Ext] next steps for draft-
> opportunistic-adotq
>
>
t;
> Caution: This email originated from outside the organization. Do not click
> links
> or open attachments unless you recognize the sender and know the content
> is safe.
>
> Hi Scott,
>
> On 3/23/21 11:26 AM, Hollenbeck, Scott wrote:
>
> >> >From the pure
;
> Caution: This email originated from outside the organization. Do not click
> links
> or open attachments unless you recognize the sender and know the content
> is safe.
>
> Hi Scott,
> Thanks for kicking this discussion off. A question (or two) inline for
> us to
> con
Section 9.1 of draft-ietf-dprive-phase2-requirements currently contains this
text:
"As recursors typically forwards queries received from the user to
authoritative servers. This creates a transitive trust between the user and
the recursor, as well as the authoritative server, since
> -Original Message-
> From: dns-privacy On Behalf Of Paul
> Hoffman
> Sent: Monday, February 22, 2021 4:28 PM
> To: dpr...@ietf.org
> Subject: [EXTERNAL] [dns-privacy] Complete changes to the (no longer just)
> opportunistic ADoT draft
>
> Greetings again. You probably just saw the
From: dns-privacy On Behalf Of Ben Schwartz
Sent: Tuesday, February 16, 2021 12:01 PM
To: Paul Wouters
Cc: Paul Hoffman ; dpr...@ietf.org
Subject: [EXTERNAL] Re: [dns-privacy] Authentication in
draft-ietf-dprive-opportunistic-adotq
[SAH] [snip]
I think the scary part is that
> -Original Message-
> From: dns-privacy On Behalf Of Tony Finch
> Sent: Wednesday, November 11, 2020 2:07 PM
> To: dns-privacy@ietf.org
> Subject: [EXTERNAL] [dns-privacy] how can we ADoT?
>
> Caution: This email originated from outside the organization. Do not click
> links
> or open
> -Original Message-
> From: dns-privacy On Behalf Of Paul
> Hoffman
> Sent: Friday, October 30, 2020 4:46 PM
> To: Eric Rescorla
> Cc: dpr...@ietf.org
> Subject: [EXTERNAL] Re: [dns-privacy] [Ext] Revised opportunistic encryption
> draft
>
> On Oct 30, 2020, at 12:32 PM, Eric Rescorla
> -Original Message-
> From: Benno Overeinder
> Sent: Monday, October 26, 2020 6:30 PM
> To: Hollenbeck, Scott ; dns-privacy@ietf.org
> Cc: br...@innovationslab.net
> Subject: [EXTERNAL] Re: [dns-privacy] Logistics for IETF 109
>
> Hi Scott,
>
> > On
> -Original Message-
> From: dns-privacy On Behalf Of Brian
> Haberman
> Sent: Monday, October 26, 2020 7:56 AM
> To: dns-privacy@ietf.org
> Subject: [EXTERNAL] [dns-privacy] Logistics for IETF 109
>
> Hi all,
> As you may have seen, we have a 2-hour session allocated to us for IETF
> -Original Message-
> From: dns-privacy On Behalf Of John Levine
> Sent: Thursday, October 31, 2019 3:39 PM
> To: dns-privacy@ietf.org
> Cc: brian.peter.dick...@gmail.com
> Subject: [EXTERNAL] Re: [dns-privacy] [Ext] Re: ADoT requirements for
> signalling?
>
> In article
> ail.com> you
From: Sara Dickinson
Sent: Friday, August 23, 2019 12:57 PM
To: Hollenbeck, Scott
Cc: vladimir.cunat+i...@nic.cz; dns-privacy@ietf.org
Subject: [EXTERNAL] Re: [dns-privacy] Working Group Last Call for
draft-ietf-dprive-rfc7626-bis
On 21 Aug 2019, at 19:21, Hollenbeck, Scott
> -Original Message-
> From: dns-privacy On Behalf Of Vladimír
> Cunát
> Sent: Monday, August 19, 2019 8:58 AM
> To: dns-privacy@ietf.org
> Subject: [EXTERNAL] Re: [dns-privacy] Working Group Last Call for draft-ietf-
> dprive-rfc7626-bis
>
> Hello,
>
> I now read through the whole
> -Original Message-
> From: dns-privacy On Behalf Of Brian
> Haberman
> Sent: Wednesday, August 14, 2019 4:40 PM
> To: dns-privacy@ietf.org
> Subject: [EXTERNAL] [dns-privacy] Call for Adoption: draft-hal-adot-
> operational-considerations
>
> This starts a Call for Adoption for
>
> -Original Message-
> From: Paul Wouters
> Sent: Friday, November 30, 2018 11:15 AM
> To: Hollenbeck, Scott
> Cc: 'wo...@pch.net' ; 'dns-privacy@ietf.org' priv...@ietf.org>; 'KHenderson=40verisign@dmarc.ietf.org'
>
> Subject: [EXTERNAL] RE: [dns-priva
From: Tim Wicinski
Sent: Thursday, July 19, 2018 4:47 PM
To: Jim Reid
Cc: Hollenbeck, Scott ; br...@innovationslab.net;
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
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
Jim
We're not ignoring TLD operators. But the TLD operator space is
51 matches
Mail list logo
