[e2e] scheduled name space

[David G. Andersen]

On Fri, Apr 16, 2004 at 03:29:23PM -0700, Joe Touch scribed:
> 
> Jon Crowcroft wrote:
>
> >i might impleent a policy based on similar olocation (eg. using bloom 
> >filters on the source address space) or on
> >request similairity (using rabin fingerprints on query keys) or whatever, 
> >but the schedule can be different to the
> >result of the match...
> 
> Sure - it's OK if you give different replies to different sources, but 
> the answers have to provide (ultimately) consistent content, or you're 
> changing what a DNS query means.
> 
> Otherwise, it may be a lookup service, but it's not DNS, IMO ;-)

  Why does DNS have to provide access to consistent content?
Does that mean that geotargeting through DNS responses is not a valid
use of the DNS system?  Or only if it's not deterministic?

  Google and others have been known to use round-robin DNS
to direct you to one of several geographically distributed
datacenters, each of which may, at various times, give
different replies to queries.  Is this not DNS?

  -Dave

-- 
work: dga at lcs.mit.edu                          me:  dga at pobox.com
      MIT Laboratory for Computer Science           http://www.angio.net/