how about response codes to queries at the wrong grain size that
trigger client retries with fewer (or more) bits to get meaningful
responses?
I don't see how to do that and stay compatible with existing DNS.
"Response code" as used here does not necessarily have to be carried in
the rcode bits of the DNS packet. For example, a lookup could return
an A record with a TTL of zero and an address of 0.0.x.y; this allows
for 65536 different response codes without touching the DNS
infrastructure at all.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTML mouse(_at_)rodents-montreal(_dot_)org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
_______________________________________________
Asrg mailing list
Asrg(_at_)irtf(_dot_)org
http://www.irtf.org/mailman/listinfo/asrg