is that supposed to be an
issue that is inherent, rather than implementation dependent?
Are you suggesting that the DNS standard be modified to account for this,
or that DNS vendors should have anticipated such a problem?
Apparently you missed this in my previous posting:
it is probably worth distinguishing between a) behaviors that will cause
problems with typical, current implementations, versus b) behaviors that
cause problems inherently due to the design of the DNS. Caching problems
well might be alleviated by different implementation schemes and/or
different key/name administration.
Having to change the implementation is, of course, significant, but it is
quite different from breaking core service design limits.
dcrocker a t ...
WE'VE MOVED to: www.bbiw.net