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

I would also support adoption.

Thanks,
Ross


On Mon, Jul 13, 2026 at 4:27 PM Ben Schwartz <bemasc=
[email protected]> wrote:

> I support adoption.
>
> On Mon, Jul 13, 2026 at 3:21 PM Loganaden Velvindron
> <[email protected]> wrote:
> >
> > I also support adoption. On Mon, 13 Jul 2026 at 16: 01, Joe Abley
> <jabley=40strandkip. nl@ dmarc. ietf. org> wrote: > > I support adoption.
> > > The reasons for having a mechanism at all seem clear, and the benefits
> of interoperability
> >
> > I also support adoption.
> >
> >
> >
> > On Mon, 13 Jul 2026 at 16:01, Joe Abley <jabley=
> [email protected]> wrote:
> > >
> > > I support adoption.
> > >
> > > The reasons for having a mechanism at all seem clear, and the benefits
> of interoperability seem obvious. This builds on other work done in dnsop
> and hence seems like a reasonable place for it to be discussed.
> > >
> > >
> > > > On 9 Jul 2026, at 21:53, Benno Overeinder via Datatracker <
> [email protected]> 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]
> > >
> > > _______________________________________________
> > > 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]
>
> _______________________________________________
> 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]