I support this draft. I would only like to see a bit more consideration on section 5 about how to deter malicious attempts from forged/spoofed addresses that might trigger amplification attacks in the future, as this could lead to multiple queries being sent out.
Thank you, Mauricio On Thu, Dec 19, 2024 at 10:53 AM Tim Wicinski <tjw.i...@gmail.com> wrote: > All > > This is just a reminder of the Working Group Last Call > for draft-ietf-dnsop-generalized-notify that is ongoing. > It will continue through the new year and will end January 3, 2025. The > Chairs would like to hear from the working group on this document. > > thanks > tim > > > On Thu, Dec 12, 2024 at 6:53 AM Tim Wicinski <tjw.i...@gmail.com> wrote: > >> All >> >> I've been working with Peter and the Authors on updates to their >> document, and we feel it's ready to move forward. >> >> This starts a *four week* Working Group Last Call for >> draft-ietf-dnsop-generalized-notify >> "Generalized DNS Notifications" >> >> Current versions of the draft is available here: >> https://datatracker.ietf.org/doc/draft-ietf-dnsop-generalized-notify/ >> >> The Current Intended Status of this document is: Proposed Standard >> >> Please review the draft and offer relevant comments. >> >> For WGLC, we need positive support and constructive comments; lack of >> objection is not enough. >> So if you think this draft should be published as an RFC, please say so. >> >> If you feel the document is *not* ready for publication, please speak out >> with your reasons. >> >> >> This starts a two week Working Group Last Call process, and ends on: >> January 3, 2025 >> >> thanks >> > _______________________________________________ > DNSOP mailing list -- dnsop@ietf.org > To unsubscribe send an email to dnsop-le...@ietf.org > -- Mauricio Vergara Ereche keybase.io/mave
_______________________________________________ DNSOP mailing list -- dnsop@ietf.org To unsubscribe send an email to dnsop-le...@ietf.org
