[80440] in North American Network Operators' Group
Re: FCC To Require 911 for VoIP
daemon@ATHENA.MIT.EDU (Jay R. Ashworth)
Sun May 1 13:09:00 2005
Date: Sun, 1 May 2005 13:04:25 -0400
From: "Jay R. Ashworth" <jra@baylink.com>
To: nanog list <nanog@merit.edu>
In-Reply-To: <200505011651.j41GpX6T025846@paixhost.pch.net>; from Bill Woodcock <woody@pch.net> on Sun, May 01, 2005 at 09:51:33AM -0700
Errors-To: owner-nanog@merit.edu
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
