Based on discussion at the interim, this draft is renamed and contains a proposal for Privacy Considerations.
Cheers, > Begin forwarded message: > > From: [email protected] > Subject: New Version Notification for > draft-nottingham-dnsop-censorship-transparency-00.txt > Date: 20 February 2026 at 10:31:47 am AEDT > To: "David Adrian" <[email protected]>, "Mark Nottingham" <[email protected]> > > A new version of Internet-Draft > draft-nottingham-dnsop-censorship-transparency-00.txt has been successfully > submitted by Mark Nottingham and posted to the > IETF repository. > > Name: draft-nottingham-dnsop-censorship-transparency > Revision: 00 > Title: DNS Censorship Transparency > Date: 2026-02-19 > Group: Individual Submission > Pages: 9 > URL: > https://www.ietf.org/archive/id/draft-nottingham-dnsop-censorship-transparency-00.txt > Status: > https://datatracker.ietf.org/doc/draft-nottingham-dnsop-censorship-transparency/ > HTML: > https://www.ietf.org/archive/id/draft-nottingham-dnsop-censorship-transparency-00.html > HTMLized: > https://datatracker.ietf.org/doc/html/draft-nottingham-dnsop-censorship-transparency > > > 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]
