Hi Roy,
Thank you for the explanation. Hopefully there will software that does
the translation to other reporting tools soon after the Draft is accepted.
eduardo_sign
Best regards,
Aviso de Confidencialidade/Disclaimer:
Este e-mail foi escrito de acordo com o novo acordo ortográfico.
Esta mensagem é exclusivamente destinada ao seu destinatário, podendo
conter informação CONFIDENCIAL, cuja divulgação está expressamente
vedada nos termos da lei. Caso tenha recepcionado indevidamente
esta mensagem, solicitamos-lhe que nos comunique esse mesmo facto por
esta via devendo apagar o seu conteúdo de imediato.
This message is intended exclusively for its addressee. It may contain
CONFIDENTIAL information protected by law. If this message has been
received by error, please notify us via e-mail and delete it immediately.
[ Antes de imprimir esta mensagem pense no ambiente. Before printing
this message, think about environment ]
Às 13:38 de 26/10/22, Roy Arends escreveu:
On 26 Oct 2022, at 11:05, Eduardo
Duarte<eduardo.duarte=40dns...@dmarc.ietf.org> 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
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
