On Sun, May 01, 2005 at 09:51:33AM -0700, Bill Woodcock wrote:

That said, a widely-implemented well-known anycast address that would give you location information is a really cool idea. A smoother imlementation might be to just have a well-known address that you'd do a DNS LOC query against, since describing locations better than postal-codes do is a problem the DNS folks have already solved.

Which address would resolve differently, depending on which DNS server you're talking to? I'm not sure that's good enough; being able to identify the *network ingress point* is the thing I'm after. For wired connections, that's the access concentrator, for wireless ones, the nearest tower. It would be necessary to be able to tailor the response to the inquiry based on that, I think, to fulfill the requirement *I'm* trying to fulfill in this posited design -- which is not guaranteed to be the same as any possible regulatory requirement. Cheers, -- jra -- Jay R. Ashworth jra@baylink.com Designer Baylink RFC 2100 Ashworth & Associates The Things I Think '87 e24 St Petersburg FL USA http://baylink.pitas.com +1 727 647 1274 If you can read this... thank a system administrator. Or two. --me