minimise-any: prefer popular and not large RRset #22
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
NSD4's RFC8482 (minimizing response for ANY query) just picks one rrset element in linked list with no preference. This can pick a large rrset (e.g. DNSKEY, RRSIG) for response, but this is not suitable for RFC8482 purpose. For example
dig @h.root-servers.net . ANY
often gets all RRSIGs of ".". (H-root adopts NSD4).This patch introduces simple preference between rtypes on selecting a rrset. It prefers popular and not large rtypes (A, AAAA,..), and lowers large rtypes (DNSKEY, RRSIG,..).
Preferece order is: