It should probably change TCP to “source IP validated transports (dns over 
stuff, tcp and udp cookies)

Sent using a virtual keyboard on a phone

> On Dec 13, 2023, at 10:14, Zaheduzzaman Sarker via Datatracker 
> <nore...@ietf.org> wrote:
> 
> Zaheduzzaman Sarker has entered the following ballot position for
> draft-ietf-dnsop-dns-error-reporting-07: No Objection
> 
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
> 
> 
> Please refer to 
> https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/
> for more information about how to handle DISCUSS and COMMENT positions.
> 
> 
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-dnsop-dns-error-reporting/
> 
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> Thanks for working on this specification. Thanks to Gorry for the TSVART 
> review.
> 
> I have only two questions
> 
> - is this protocol (error reporting) not applicable to DoQ? The question came
> as TCP is the preferred transport and only tells what to do when UDP is used
> for queries and reports, so wondering what happens when QUIC is as transport
> for DNS.
> 
> - what would be a typical rate of error reporting?
> 
> 
> 
> _______________________________________________
> 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

Reply via email to