Hi DNSOP,

Public DNS resolvers (such as 1.1.1.1, 8.8.8.8, and others) are increasingly 
subject to requirements to censor responses flowing through them. When this 
happens, it's important to be transparent to end users. The mechanism in this 
draft is intended to allow that in a way that addresses the concerns that 
browser engineers have about security and user experience.

I know this is late notice for this meeting, but I'm happy to chat with folks 
about it in the hallways.

Cheers,


> Begin forwarded message:
> 
> From: [email protected]
> Subject: New Version Notification for 
> draft-nottingham-public-resolver-errors-00.txt
> Date: 5 November 2024 at 10:17:51 AM GMT
> To: "Mark Nottingham" <[email protected]>
> 
> A new version of Internet-Draft draft-nottingham-public-resolver-errors-00.txt
> has been successfully submitted by Mark Nottingham and posted to the
> IETF repository.
> 
> Name:     draft-nottingham-public-resolver-errors
> Revision: 00
> Title:    Extensions for DNS Public Resolvers
> Date:     2024-11-05
> Group:    Individual Submission
> Pages:    6
> URL:      
> https://www.ietf.org/archive/id/draft-nottingham-public-resolver-errors-00.txt
> Status:   
> https://datatracker.ietf.org/doc/draft-nottingham-public-resolver-errors/
> HTML:     
> https://www.ietf.org/archive/id/draft-nottingham-public-resolver-errors-00.html
> HTMLized: 
> https://datatracker.ietf.org/doc/html/draft-nottingham-public-resolver-errors
> 
> 
> 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.
> 
> 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]

Reply via email to