Re: Tutorial: Query the Apple database with Python for your access point BSSID

On Thu, 1 Jan 2026 21:05:12 +0100, "R.Wieser" <[email protected]>
wrote:

>Jeff,
>
>> Adding location information to DNS, DHCP, SNMP etc have been proposed.
>...
>> An early scheme is RFC 1712
>
>proposed in 1994.  Its now more than 36 years later (which is, for 
>technology, a loooong time), and nothing like it has been implemented.

I'm 77 years old and am still proposing ideas which could easily be
labeled as science fiction.  I've also seen projects that were
proposed, complete with detailed documentation, that didn't function
until funding was found many years later.  I suggest you not pass
judgment on technology that you might consider old and instead
concentrate on whether they might actually work.  Also, if you wish to
pass judgment on whether some technology is worth doing, there are
seats in the various houses of government awaiting your political
involvement.

>Maybe that is because there is no automated way to determine the "floor 
>number".   Especially for devices which task it is to do DNS, DHCP and so 
>on - those do not even contain hardware to determine their own X/Y location.

Quoting myself:  "Note that the data does not need to be derived from
GPS data.  Since it doesn't change (often), it could be entered into
the database when the DNS record was created."

That means that in 1994, there was no requirement to identify the
location of a router, server, computer, etc using GPS.  Merely
entering the location data the SNMP MIB (management information base)
would be sufficient.  Obviously, that won't work for moving objects,
but GPS was not fully operational until 1995 and was not useable for
indoor applications until High Sensitivity GPS arrived in about 1999
<https://www.furuno.com/en/gnss/technical/tec_high>
and Selective Availability was disabled in May 2000.  If someone
proposes a geographic network equipment location system prior to about
2000, it wouldn't have worked very well.

>I must say that that RFC does have a joke smell to it.  You know, like the 
>"I'm a teapot" HTTP status, the "evil bit" for ethernet packets and lets not 
>forget "IP over avian carriers" (which, by the way /does/ work).

The RFC's I mentioned don't seem to be in the official book of April
Fools RFC's.
<https://www.rfchumor.com>

>And although most/all smartphones do have a GPS, those are notoriously bad 
>at determing elevation (which is not really a surprise, if you look at where 
>the GPS satelites are located in relation to the GPS receiver).

That's true which is why sports GPS receivers often include a
barometric altimeter:
<https://support.garmin.com/en-US/?faq=WlvNrOungC28xGtwB7hLY5>
"With proper calibration, the barometric altimeter of a Garmin watch
or outdoor handheld will report elevation readings ranging from -2,000
to 30,000 feet with an accuracy of +/-10 feet at any given point."
"Elevation calibrated by GPS is accurate to +/-400 feet at any given
point with a strong GPS signal"

>Regards,
>Rudy Wieser


-- 
Jeff Liebermann                 [email protected]
PO Box 272      http://www.LearnByDestroying.com
Ben Lomond CA 95005-0272   AE6KS    831-336-2558