> Il 4 ottobre 2019 15:26 Sara Dickinson ha scritto:
>
> "In some cases, networks might block access to remote resolvers for security
> reasons, for example to cripple malware and bots or to prevent data
> exfiltration methods that use encrypted DNS communications as transport. In
> these
> On 3 Oct 2019, at 12:16, Vittorio Bertola
> wrote:
>
>
>
>> Il 27 settembre 2019 17:54 Sara Dickinson ha scritto:
>>
>> I hope the changes address most of your concerns - please review and let me
>> know.
>
> I went through the changes, and I like them - you did a really good job in
> Il 27 settembre 2019 17:54 Sara Dickinson ha scritto:
>
> I hope the changes address most of your concerns - please review and let me
> know.
I went through the changes, and I like them - you did a really good job in
capturing my comments and more generally the recent development of the
Hi Vittorio,
Many thanks for the detailed review - I’ve published an updated -01 version
with several changes to hopefully address your comments and the others made
during WGLC.
> Here are my comments after going through the document. I think it still needs
> further work, reflecting how
Il 16 agosto 2019 13:49 Tim Wicinski ha scritto:
This starts a Working Group Last Call for draft-ietf-dprive-rfc7626-bis
Current versions of the
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
> On 21 Aug 2019, at 19:21, Hollenbeck, Scott
> wrote:
>
>> -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-pr
> On 19 Aug 2019, at 13:58, Vladimír Čunát wrote:
>
> Hello,
>
> I now read through the whole document, and I see one thing that might be
> a little bit confusing - the beginning of page three reads like QNAME
> minimization is not possible or at least never done, and contrary to
> rfc7626
> On 19 Aug 2019, at 10:58 pm, Vladimír Čunát
> wrote:
>
> Hello,
>
> I now read through the whole document, and I see one thing that might be
> a little bit confusing - the beginning of page three reads like QNAME
> minimization is not possible or at least never done, and contrary to
>
> -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,
>
Hello,
I now read through the whole document, and I see one thing that might be
a little bit confusing - the beginning of page three reads like QNAME
minimization is not possible or at least never done, and contrary to
rfc7626 itself it isn't even mentioned in the whole document. I would
suggest
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
12 matches
Mail list logo