Re: [DNSOP] Call for Adoption: Structured Data for Filtered DNS

["Livingood, Jason" <[e-mail]>]

I support adoption.


I also suggest the authors take a look at two long-ago-expired I-Ds that are related to this subject:
https://www.ietf.org/archive/id/draft-livingood-dns-malwareprotect-02.html
https://www.ietf.org/archive/id/draft-livingood-dns-redirect-03.html

Lastly, to the contents of the current draft, I offer the authors the following:

  *   Section 10: Initial sub-errors. There is too little difference between the various options (e.g., phishing & spam). I suggest instead using more clearly differentiated reasons, such as:
0: Reserved
1: Security Policy
2: Privacy Policy (e.g., ad-blocking)
3: Content Policy (e.g., age-limited content)
4: Network Operator Policy
5: Government Policy
  *   Should any implementer make available a public recursive interface of some type (whether DNS or a web page – does not matter) to allow 3rd party auth domains to check whether their FQDN is filtered? Or just certain types of implementers (e.g., ISPs)?
  *   Is there a mechanism for auth domains to determine why their FQDN was filtered and to request a review? For example, similar to email bulk senders and spam, can they determine what list is responsible for the filter and work with that provider to remediate their practices and get the FQDN re-classified and unfiltered?


Thanks
Jason

From: DNSOP <[e-mail]> on behalf of Tim Wicinski <[e-mail]>
Date: Sunday, January 22, 2023 at 15:36
To: dnsop <[e-mail]>
Cc: dnsop-chairs <[e-mail]>
Subject: [DNSOP] Call for Adoption: Structured Data for Filtered DNS


All

The chairs have received feedback for DNSOP to adopt this document, and I've
wrestled with this document.    We have received feedback when presented
to adopt this work.  We've also had some conversations with folks who
offer DNS services to enterprises they have had some customer interest.
I will say personally that I am sure I can find some individuals at my
current employer who would get very interested in this also.
So the best thing to do is - see what the Working Group says.

If you work for someone who is interested in this, please let us know.
If you work for someone who has customers interested in this, please let us know.
If you plan on implementing this (or not!), please let us know.

If you feel less comfortable speaking publicly, please reach out to the chairs.


This starts a Call for Adoption for draft-wing-dnsop-structured-dns-error-page

The draft is available here:
https://datatracker.ietf.org/doc/draft-wing-dnsop-structured-dns-error-page/<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-wing-dnsop-structured-dns-error-page/__;!!CQl3mcHX2A!HKmlmIrovTfkWYeTeuUoE4mf8b4Ps2sX2AYSpFVPs4SNQF0CBU31kJKYYaKf51ZZ0xASDce2ybx1dKMOQM-_RcS-Ug$>
Please review this draft to see if you think it is suitable for adoption
by DNSOP, and send any comments to the list, clearly stating your view.

Please also indicate if you are willing to contribute text, review, etc.

This call for adoption ends: February 5th, 2023

Thanks,
tim wicinski
For DNSOP co-chairs