Hi!
> -Original Message-
> From: iesg On Behalf Of Paul Hoffman
> Sent: Thursday, November 17, 2022 7:06 PM
> To: Roman Danyliw
> Cc: The IESG ; draft-ietf-dnsop-rfc5933-...@ietf.org; dnsop-
> cha...@ietf.org; dnsop@ietf.org; Tim Wicinski
> Subject: Re: [Ext] [DNSOP] Roman Danyliw's Dis
I didn't explain why, so let me add just a short pointer. No need to go
deeper here at this point of the draft, I think.
On 28/11/2022 19.26, Peter Thomassen wrote:
As such, I don't see any risk that would not be exposed immediately
during implementation/testing, and the fix is also trivial.
Hi Vladimir,
Thanks for your feedback! Please see below.
On 11/11/22 19:01, Vladimír Čunát wrote:
It's not a major thing in your design, but I see a risk that DNSKEYs at
non-apex might have trouble validating, so at some point I'd expect your
proposal to choose a different approach (e.g. allo
On 25/11/2022 18.26, Daniel Migault wrote:
So let me know how we came to this lines and I suspect we do share
some similar concerns. A recurrent question and reticence we receive
from MNO and ISPs regarding DNSSEC is that they are really scared
about having the cache with incoherent RRsets in t
Éric Vyncke has entered the following ballot position for
draft-ietf-dnsop-rfc5933-bis-12: No Objection
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please refer to
