I'm OK with this, although personally I'm happy to just wait for ECH. I
had hoped for a simpler solution (like marking SVCB's dependency on ECH as
Informative), but I can understand if the IESG thinks there's no other way.
If we are chopping the ECH parts out of SVCB, I would prefer to publish
th
On Thu, Feb 23, 2023 at 1:41 PM David Schinazi
wrote:
> Moving the ECH/ESNI bits from draft-ietf-dnsop-svcb-https
> to draft-ietf-tls-esni seems to be the simplest option by far here. I
> strongly support that.
> David
>
Currently, draft-ietf-tls-esni runs to 40 pages excluding the references
an
The draft's opening words are "DNS filtering is widely deployed for network
security". This is true, but by far the "widest" deployment of DNS
filtering is for authoritarian national censorship, to prevent citizens
from engaging with forbidden ideas.
The EDE draft acknowledges and rebukes this ra
On Mon, Apr 10, 2023 at 1:46 AM Éric Vyncke via Datatracker <
nore...@ietf.org> wrote:
...
> COMMENTS
>
> Slight regret that some of my -08 comments were not addressed (e.g.,
> expanding
> HSTS) even if most of them were indeed addressed.
>
I'm sorry if we missed some comments at an earlier stage
On Tue, Apr 18, 2023 at 7:49 AM Ralf Weber wrote:
> Moin!
>
> On 18 Apr 2023, at 13:11, Benjamin Schwartz wrote:
>
> > The draft's opening words are "DNS filtering is widely deployed for
> network
> > security". This is true, but by far the "
On Tue, Apr 18, 2023 at 10:19 AM Ralf Weber wrote:
> Moin!
>
> On 18 Apr 2023, at 15:54, Benjamin Schwartz wrote:
> > If the suberror field is mainly for communication from resolvers to
> > browsers, then any solution should only move forward if it's satisfactory
&
On Wed, Apr 19, 2023 at 10:04 AM tirumal reddy wrote:
> On Tue, 18 Apr 2023 at 16:41, Benjamin Schwartz wrote:
>
>> The draft's opening words are "DNS filtering is widely deployed for
>> network security". This is true, but by far the "widest&
