👍
For those having trouble finding the draft:
https://datatracker.ietf.org/doc/draft-aviram-tls-deprecate-obsolete-kex/
I assume that this is going up on GitHub somewhere as well?
On Tue, Jun 14, 2022, at 09:51, Joseph Salowey wrote:
> draft-aviram-deprecate-obsolete-kex-01 has been revised and
draft-aviram-deprecate-obsolete-kex-01 has been revised and merged in
content from draft-bartle-tls-deprecate-ffdh to address some of the
concerns raised in the adoption call. The chairs think this is a good
starting point for adoption as a working group item. Authors please submit
the draft as dra
On Mon, Jun 13, 2022 at 02:16:03PM -0400, Daniel Migault wrote:
> Thanks for the detailed response, that is very much appreciated. When I
> wrote the initial email, I had more in mind some sort of configuration - as
> opposed to DANE. I agree that the use of PSKI should not cause any of the
> head
Thanks for the detailed response, that is very much appreciated. When I
wrote the initial email, I had more in mind some sort of configuration - as
opposed to DANE. I agree that the use of PSKI should not cause any of the
headaches associated with pinning.
Yours,
Daniel
On Mon, Jun 13, 2022 at 11
On Mon, Jun 13, 2022 at 10:42:51AM -0400, Daniel Migault wrote:
> I sent this question regarding the use of SPKI Fingerprints to the
> add mailing list, but I am also eventually interested to feed backs not
> necessarily restricted to encrypted resolvers.
>
> RFC 7858 (DNS over TLS) indicates the
Hi,
I sent this question regarding the use of SPKI Fingerprints to the
add mailing list, but I am also eventually interested to feed backs not
necessarily restricted to encrypted resolvers.
RFC 7858 (DNS over TLS) indicates the use of SPKI Fingerprints in an
analogous manner to that described in
