Yes , that's what I meant , a slight parser modification and subsequent
log interpretation, a very minor thing, it wasn't my intention to seed
confusion.
On 17/06/2026 23:09, Robert Edmonds wrote:
Carlos Horowicz wrote:
If I'm not mistaken, the only extra work for DNSTAP conversion, parsing and
log-shipping would be to capture the optional text in EDE 33 if or when bind9
implements it.
I'm confused what this could be referring to. I don't see any references
to dnstap in the draft, and since dnstap captures the complete DNS
response message in its original wire format there should be no extra
work required for dnstap to capture a newly defined EDE code point, or
EDNS option, etc. Only on the processing side, should a log consumer
want to extract that information.
_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]
