[DNSOP] Re: Call for adoption: draft-nottingham-dnsop-cens orship-transparency-01 (Ends 2026-07-23)

Greetings,

I support the call for adoption.

Regards,--
Felix S. Mertins

This email may contain confidential information. If you are not the intended recipient, please let the author know and delete this message.



13. Juli 2026, 11:44 von [email protected]:

> Hi Chairs,
>
> I support the call for adoption.
>
> I suggest the draft is changed (maybe just a filename thing?) to reflect the title of DNS Filtering Transparency.
>
> Cheers, Jim
>
>
> On 2026-07-09, 20:54, "Benno Overeinder via Datatracker" <[email protected]> wrote:
>
> !-------------------------------------------------------------------|
>    This Message Is From an External Sender
>    This message came from outside your organization.
>  |-------------------------------------------------------------------!
>  
>  This message starts a dnsop WG Call for Adoption of:
>  draft-nottingham-dnsop-censorship-transparency-01
>  
>  This Working Group Call for Adoption ends on 2026-07-23
>  
>  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://urldefense.com/v3/__https://github.com/mnot/public-resolver-errors__;!!JYsgTRAg6ZQ!KhsMiJnuZcLL46DzHcEMd6O7nAEjC9sRMRL0alLlewO-BPz8zbRz1CISrylK36VRqCuHJ7s5s8otD3emOg$>  .
>  
>  Please reply to this message and indicate whether or not you support adoption
>  of this Internet-Draft by the dnsop WG. Comments to explain your preference
>  are greatly appreciated. Please reply to all recipients of this message and
>  include this message in your response.
>  
>  Authors, and WG participants in general, are reminded of the Intellectual
>  Property Rights (IPR) disclosure obligations described in BCP 79 [2].
>  Appropriate IPR disclosures required for full conformance with the provisions
>  of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any.
>  Sanctions available for application to violators of IETF IPR Policy can be
>  found at [3].
>  
>  Thank you.
>  [1] >  https://urldefense.com/v3/__https://datatracker.ietf.org/doc/bcp78/__;!!JYsgTRAg6ZQ!KhsMiJnuZcLL46DzHcEMd6O7nAEjC9sRMRL0alLlewO-BPz8zbRz1CISrylK36VRqCuHJ7s5s8rktaVXbw$
>  [2] >  https://urldefense.com/v3/__https://datatracker.ietf.org/doc/bcp79/__;!!JYsgTRAg6ZQ!KhsMiJnuZcLL46DzHcEMd6O7nAEjC9sRMRL0alLlewO-BPz8zbRz1CISrylK36VRqCuHJ7s5s8q0MVUMrg$
>  [3] >  https://urldefense.com/v3/__https://datatracker.ietf.org/doc/rfc6701/__;!!JYsgTRAg6ZQ!KhsMiJnuZcLL46DzHcEMd6O7nAEjC9sRMRL0alLlewO-BPz8zbRz1CISrylK36VRqCuHJ7s5s8qIwq0LhQ$
>  
>  The IETF datatracker status page for this Internet-Draft is:
>  > https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-nottingham-dnsop-censorship-transparency/__;!!JYsgTRAg6ZQ!KhsMiJnuZcLL46DzHcEMd6O7nAEjC9sRMRL0alLlewO-BPz8zbRz1CISrylK36VRqCuHJ7s5s8oVD_TLlg$
>  
>  There is also an HTML version available at:
>  > https://urldefense.com/v3/__https://www.ietf.org/archive/id/draft-nottingham-dnsop-censorship-transparency-01.html__;!!JYsgTRAg6ZQ!KhsMiJnuZcLL46DzHcEMd6O7nAEjC9sRMRL0alLlewO-BPz8zbRz1CISrylK36VRqCuHJ7s5s8o3AK6FGw$
>  
>  A diff from the previous version is available at:
>  > https://urldefense.com/v3/__https://author-tools.ietf.org/iddiff?url2=draft-nottingham-dnsop-censorship-transparency-01__;!!JYsgTRAg6ZQ!KhsMiJnuZcLL46DzHcEMd6O7nAEjC9sRMRL0alLlewO-BPz8zbRz1CISrylK36VRqCuHJ7s5s8pwzvfzpw$
>  
>  _______________________________________________
>  DNSOP mailing list -- [email protected]
>  To unsubscribe send an email to [email protected]
>

_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]