draft-ietf-dnsop-filtering-transparency?

I suspect there may still need to be some adjustment of the title, but I think 
this works for now.

Cheers,


> On 30 Jul 2026, at 10:59 pm, Benno Overeinder <[email protected]> wrote:
> 
> All,
> 
> Thank you for your input on the call for adoption of draft 
> draft-nottingham-dnsop-censorship-transparency.  All respondents said yes to 
> the call for adoption.  This email concludes the call for adoption, and the 
> draft is now adopted as a WG document.
> 
> It has been suggested (twice, if I am correct) that, upon adoption by the 
> DNSOP WG, the file name should be changed to something like 
> "dns-filtering-transparency" to reflect the title change.
> 
> Best regards,
> 
> -- Benno
> 
> On 09/07/2026 21:53, Benno Overeinder via Datatracker wrote:
>> 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://github.com/mnot/public-resolver-errors.
>> 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://datatracker.ietf.org/doc/bcp78/
>> [2] https://datatracker.ietf.org/doc/bcp79/
>> [3] https://datatracker.ietf.org/doc/rfc6701/
>> The IETF datatracker status page for this Internet-Draft is:
>> https://datatracker.ietf.org/doc/draft-nottingham-dnsop-censorship-transparency/
>> There is also an HTML version available at:
>> https://www.ietf.org/archive/id/draft-nottingham-dnsop-censorship-transparency-01.html
>> A diff from the previous version is available at:
>> https://author-tools.ietf.org/iddiff?url2=draft-nottingham-dnsop-censorship-transparency-01
>> _______________________________________________
>> DNSOP mailing list -- [email protected]
>> To unsubscribe send an email to [email protected]
> 

--
Mark Nottingham   https://mnot.net/

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

Reply via email to