Mark Andrews writes:
> If we go ahead with this these two sentences
[... snip ...]
That seems like a good suggestion considering the direction of the
conversation. Both drafts changed accordingly, thanks for the text.
--
Wes Hardaker
USC/ISI
___
If we go ahead with this these two sentences
Validating resolvers MUST treat
RRSIG records created from DNSKEY records using these algorithms as
insecure. If no other RRSIG records of accepted cryptographic
algorithms are available, the validating resolver MUST
On Apr 27, 2024, at 20:39, Tim Wicinski wrote:
>
> M
>
>
> This starts a Call for Adoption for:
> draft-hardaker-dnsop-rfc8624-bis
> draft-hardaker-dnsop-must-not-sha1
> draft-hardaker-dnsop-must-not-ecc-gost
I support adoption for all three drafts. Willing to help with text and
All
These were discussed at the last IETF and the chairs felt there was
consensus to request adoption.
This starts a Call for Adoption for:
draft-hardaker-dnsop-rfc8624-bis
draft-hardaker-dnsop-must-not-sha1
draft-hardaker-dnsop-must-not-ecc-gost
The drafts are available here:
