Hi everyone, After some more side discussions in Madrid, this draft takes a slightly different approach: it uses a registry of incident databases, rather than resolvers.
Feedback much appreciated. Cheers, > Begin forwarded message: > > From: [email protected] > Subject: New Version Notification for > draft-nottingham-public-resolver-errors-02.txt > Date: 8 August 2025 at 9:31:05 am AEST > To: "David Adrian" <[email protected]>, "Mark Nottingham" <[email protected]> > > A new version of Internet-Draft draft-nottingham-public-resolver-errors-02.txt > has been successfully submitted by Mark Nottingham and posted to the > IETF repository. > > Name: draft-nottingham-public-resolver-errors > Revision: 02 > Title: DNS Filtering Details for Applications > Date: 2025-08-07 > Group: Individual Submission > Pages: 8 > URL: > https://www.ietf.org/archive/id/draft-nottingham-public-resolver-errors-02.txt > Status: > https://datatracker.ietf.org/doc/draft-nottingham-public-resolver-errors/ > HTML: > https://www.ietf.org/archive/id/draft-nottingham-public-resolver-errors-02.html > HTMLized: > https://datatracker.ietf.org/doc/html/draft-nottingham-public-resolver-errors > Diff: > https://author-tools.ietf.org/iddiff?url2=draft-nottingham-public-resolver-errors-02 > > Abstract: > > [I-D.ietf-dnsop-structured-dns-error] introduces structured error > data for DNS responses that have been filtered. This specification > allows more specific details of filtering incidents to be conveyed. > > 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/
_______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
