> On 26 Oct 2022, at 11:05, Eduardo Duarte
> <[email protected]> wrote:
>
> Hi all,
>
> I'm not active in the WG but some one point out this draft during last week
> DNS-OARC meeting and I have a question for the Authors.
> So from my understanding after reading the Draft all the reporting is done
> over DNS itself. Did the Authors think of adding other reporting mechanisms
> like REST+JSON or even email?
> I'm bringing this up because I think it will be easier to integrate the error
> reporting to other monitoring tools in this way instead of reading the log
> file from a Reporting Agent.
Hi Eduardo,
First off, thanks for reading it and commenting on it. All input is greatly
appreciated!
The simplest method available, that included facilities to dampen the amount of
reports (such as caching) and reducing the additional complexity in validating
resolvers, was using the DNS.
All of the additional complexity, such as REST+JSON, email etcetera can be
added to the reporting agent, where all reports come in over DNS, and
subsequently more audited, in-depth, aggregated, curated and even human
readable reports can go out via various APIs, protocols, transports, etc.
Hope this helps.
Roy
_______________________________________________
DNSOP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsop
