Re: [DNSOP] [dnsdir] Dnsdir early review of draft-ietf-dnsop-qdcount-is-one-01

2024-01-17 Thread Jim Reid
> On 17 Jan 2024, at 20:42, Matt Brown via Datatracker via dnsdir > wrote: > > Reviewer: Matt Brown > Review result: Ready > > I have been selected as the DNS Directorate reviewer for this draft. > The draft itself is clear and understandable. Both the language and the > substance of th

[DNSOP] Dnsdir early review of draft-ietf-dnsop-qdcount-is-one-01

2024-01-17 Thread Matt Brown via Datatracker
Reviewer: Matt Brown Review result: Ready I have been selected as the DNS Directorate reviewer for this draft. The DNS Directorate seeks to review all DNS or DNS-related drafts as they pass through IETF last call and IESG review, and sometimes on special request. The purpose of the review is to pr

Re: [DNSOP] Resolver behaviour in the presence of unrequested answer records

2024-01-17 Thread Paul Wouters
On Jan 17, 2024, at 05:15, Bellebaum, Thomas wrote: > > 1. Caching of unrequested RRs would actually be fine, if they are > properly signed. At worst, a resolver would cache irrelevant records. This is not entirely true. By tailoring someone’s cache you might be able to track them. There is

Re: [DNSOP] Poll to select DNSOP Interim meeting last week January

2024-01-17 Thread Benno Overeinder
Dear DNSOP WG, I closed the doodle poll to select a suitable day and time. The selected day and time is *January 30, 2024, 17:00-18:00 UTC*. I will schedule the interim in the datatracker and more information about the interim meeting will appear on the mailing list. Best regards, -- Ben

Re: [DNSOP] Resolver behaviour in the presence of unrequested answer records

2024-01-17 Thread Bellebaum, Thomas
> That's cache poisoning.  Search for "Eugene Kashpureff" to learn all > about it. There is a relation in the sense that checking RRs for relevance to the query is mentioned as a partial defense against cache poisoning in RFC 3833, section 2.3. Note however some differences: 1. Caching of unrequ