> To prevent this discrepancy between how dry-run and real validation > is done, the resolver either needs to halve its work bounds (which > is a disadvantage for real deployments), or commit to twice the > work it is willing to do.
This would be a problem is the work a validator can reasonably do is close to the amount of work that is needed in real world scenarios. I don't think that's the case. So giving twice the resources to a DS RRset that includes dry-run should not be a problem. Even if it would be a problem for some particularly busy resolvers, the world is full of validators that are 99% idle. So the internet as a whole has enough resources for dry-run. _______________________________________________ DNSOP mailing list -- dnsop@ietf.org To unsubscribe send an email to dnsop-le...@ietf.org
