Update benchmarks: resolver use-cases

benchmarks.md

@@ -56,6 +56,7 @@ Just a short list of the most important ones. Not a full list by a long shot.
   - RD=1 queries
   - DO=1 queries
   - CD=1 queries
+  - [Client Subnet in DNS Queries](https://datatracker.ietf.org/doc/html/rfc7871) (aka ENS Client Subnet, ECS)
 - Client transport
   - UDP with TCP fallback
   - DoT
@@ -82,12 +83,21 @@ Just a short list of the most important ones. Not a full list by a long shot.
   - content of RPZ zones
   - update size
   - update frequency
+- views / GeoIP
 - Auth side (i.e. how does the Internet behave)
   - TTL of answers
   - size of answers
   - validity of answers
   - weird answers - very long CNAME chains etc.
 
+### Typical setups
+Cartesian product of
+- (recursor, forwarder)
+- (no ECS, ECS)
+- (no RPZ, lots of RPZ)
+- (one view, more views with GeoIP)
+- (closed resolver, open resolver)
+
 ## Authoritative
 - :warning: Different queries have different processing cost - and it also depends on zone contents!
   - See e.g. https://www.knot-dns.cz/benchmark/ with test results for half a dozen different test setups