[DNSOP] Re: Alternative approach to draft-ietf-dnsop-structured-dns-error

[Mukund Sivaraman <[e-mail]>]

Hi Benno

On Wed, Mar 25, 2026 at 02:52:56PM +0100, Benno Overeinder wrote:
> Hi Mukund,
> 
> On 21/03/2026 16:14, Mukund Sivaraman wrote:
> > On Sat, Mar 21, 2026 at 03:11:08PM +0000, Mukund Sivaraman wrote:
> > > This is all I can do to show my displeasure at the design of
> > > dnsop-structured-dns-error, by describing how it should have been
> > > done. Feel free to use the contents of this draft as you wish.
> > 
> > To be fair, I understand I've come in really late in the WG process to
> > say these things. I am very sorry about that. My review of this draft on
> > 2023-06-28 is about the same.
> 
> As for the new draft, draft-muks-dns-filtering, it will be looked at and
> discussed on its own in the WG, not as part of the WGLC for
> draft-ietf-dnsop-structured-dns-error.

That sounds fine. As mentioned earlier, I do not intend to block the
last-call of this draft. My intention in preparing
draft-muks-dns-filtering was to demonstrate to the authors of
draft-ietf-dnsop-structured-dns-error how it should have been designed
and what that would have been like without using JSON or overriding RFC
8914. It appears we are dug in and don't agree, and that's ok.

We are half-way through implementing both
draft-ietf-dnsop-structured-dns-error as well as
draft-muks-dns-filtering in Loop as they can co-exist. If a client
signals that it wants a structured DNS error JSON, it will receive
it. Otherwise any client will receive the filtering EDNS options
alongside RFC 8914 EDE when filtering occurs.

I will update draft-muks-dns-filtering with a comparison
vs. draft-dnsop-structured-dns-error. As you intend to move ahead with
the WGLC for draft-dnsop-structured-dns-error, please do so as I can
then reference the contact URI schemes registry that
dnsop-structured-dns-error creates in draft-muks-dns-filtering.

So far draft-muks-dns-filtering hasn't received any responses at all in
support in the dnsop@ list, so I may leave it as a draft or submit it
independently. We will first get the EDNS option codepoints allocated
and finish implementing support in Loop.

Thank you.

		Mukund