I continue to view this proposal as interesting and potentially valuable. However, I think the integration with draft-ietf-dnsop-structured-dns-error creates an apparent conflict. Both drafts seem to present the same information, but by very different mechanisms. This conflict could result in interoperability failure, internal inconsistency and regulatory confusion.
My preference is to pause progression of draft-ietf-dnsop-structured-dns-error until we reach consensus on how best to convey this information. --Ben Schwartz ________________________________ From: Mark Nottingham <[email protected]> Sent: Friday, February 21, 2025 8:40 PM To: [email protected] <[email protected]> Subject: [DNSOP] Fwd: New Version Notification for draft-nottingham-public-resolver-errors-01.txt Hi DNS folk, See draft below for an update based upon feedback received. Note that the short name of the draft isn't really accurate any more, since some of the feedback was that this could/should be potentially applicable to other resolvers Hi DNS folk, See draft below for an update based upon feedback received. Note that the short name of the draft isn't really accurate any more, since some of the feedback was that this could/should be potentially applicable to other resolvers too. Happy to chat with folks about this in Bangkok, either in the hallways or the session if the chairs agree. Note that I have a conflict on Thursday (I'm chairing AIPREF at the same time). Cheers, Begin forwarded message: From: [email protected] Subject: New Version Notification for draft-nottingham-public-resolver-errors-01.txt Date: 22 February 2025 at 12:37:58 pm AEDT To: "Mark Nottingham" <[email protected]> A new version of Internet-Draft draft-nottingham-public-resolver-errors-01.txt has been successfully submitted by Mark Nottingham and posted to the IETF repository. Name: draft-nottingham-public-resolver-errors Revision: 01 Title: DNS Filtering Details for Applications Date: 2025-02-22 Group: Individual Submission Pages: 7 URL: https://www.ietf.org/archive/id/draft-nottingham-public-resolver-errors-01.txt<https://urldefense.com/v3/__https://www.ietf.org/archive/id/draft-nottingham-public-resolver-errors-01.txt__;!!Bt8RZUm9aw!7VicBEIXbx2KBB2dOl6CPVnEwKy1DoilmyDAb-wSRD7sRxaNtCMt6u1CwNg4Pg7skW46Ahp82ZPu7YLO5eMr3foDMw$> Status: https://datatracker.ietf.org/doc/draft-nottingham-public-resolver-errors/<https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-nottingham-public-resolver-errors/__;!!Bt8RZUm9aw!7VicBEIXbx2KBB2dOl6CPVnEwKy1DoilmyDAb-wSRD7sRxaNtCMt6u1CwNg4Pg7skW46Ahp82ZPu7YLO5eNq1Xnaxg$> HTML: https://www.ietf.org/archive/id/draft-nottingham-public-resolver-errors-01.html<https://urldefense.com/v3/__https://www.ietf.org/archive/id/draft-nottingham-public-resolver-errors-01.html__;!!Bt8RZUm9aw!7VicBEIXbx2KBB2dOl6CPVnEwKy1DoilmyDAb-wSRD7sRxaNtCMt6u1CwNg4Pg7skW46Ahp82ZPu7YLO5eOjoZAP0A$> HTMLized: https://datatracker.ietf.org/doc/html/draft-nottingham-public-resolver-errors<https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/draft-nottingham-public-resolver-errors__;!!Bt8RZUm9aw!7VicBEIXbx2KBB2dOl6CPVnEwKy1DoilmyDAb-wSRD7sRxaNtCMt6u1CwNg4Pg7skW46Ahp82ZPu7YLO5eNXoQrl0g$> Diff: https://author-tools.ietf.org/iddiff?url2=draft-nottingham-public-resolver-errors-01<https://urldefense.com/v3/__https://author-tools.ietf.org/iddiff?url2=draft-nottingham-public-resolver-errors-01__;!!Bt8RZUm9aw!7VicBEIXbx2KBB2dOl6CPVnEwKy1DoilmyDAb-wSRD7sRxaNtCMt6u1CwNg4Pg7skW46Ahp82ZPu7YLO5ePfz-EiSQ$> Abstract: [I-D.ietf-dnsop-structured-dns-error] introduces structured error data for DNS responses that have been filtered. This draft suggests additions to that mechanism that enable applications to convey the details of some filtering incidents to their users. Discussion Venues This note is to be removed before publishing as an RFC. Source for this draft and an issue tracker can be found at https://github.com/mnot/public-resolver-errors. The IETF Secretariat -- Mark Nottingham https://www.mnot.net/<https://urldefense.com/v3/__https://www.mnot.net/__;!!Bt8RZUm9aw!7VicBEIXbx2KBB2dOl6CPVnEwKy1DoilmyDAb-wSRD7sRxaNtCMt6u1CwNg4Pg7skW46Ahp82ZPu7YLO5eNHCJbu6w$>
_______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
