> The ICANN Board acted > based on recommendations from the ICANN SSAC in SSAC113: > https://itp.cdn.icann.org/en/files/security-and-stability-advisory-committee- > ssac-reports/sac-113-en.pdf > > There are plenty of SSAC members on this mailing list; they can > explain why the report (and thus the recommendations to the board) > do not include a recommendation for insecure delegation.
Obviously, what happens in ICANN, happens in ICANN with ICANN procedures, etc. No need to have a discussion about that. But I want to say I'm surprised that a document by 'the ICANN Security and Stability Advisory Committe' does not mention DNSSEC at all, except in a footnote in an appendix. And does not analyse an insecure delegation from the root. For this working group, I think it is safe to assume that ICANN will not create an insecure delegation for internal. So in my opinion this draft should not be adopted. The best solution is no IETF document at all. That leaves the IETF out of this issue. _______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
