<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<br>
<div class="moz-cite-prefix">On 01-May-22 05:03, Bob Harold wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CA+nkc8AP=nBDAW-1cDBCkVfoGtUX2TQMRacnYmGn7Vj5E8h0Tg@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr"><br>
</div>
<div class="gmail_quote" style="">
<div dir="ltr" class="gmail_attr">On Wed, Apr 13, 2022 at 9:39
AM Bjørn Mork <<a href="mailto:bjorn@mork.no"
moz-do-not-send="true" class="moz-txt-link-freetext">bjorn@mork.no</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">Timothe Litt <<a
href="mailto:litt@acm.org" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">litt@acm.org</a>>
writes:<br>
<br>
> Anyhow, it's not clear exactly what problem you're
asking LOC (or<br>
> anything) to solve.<br>
<br>
Which problems do LOC solve?<br>
<br>
I remember adding LOC records for fun?() in the previous
millennium when<br>
RFC 1876 was fresh out of the press. But even back then
paranoia<br>
finally took over, and I deleted all of them.<br>
<br>
Don't think I ever found anything to actually use them for.<br>
<br>
<br>
Bjørn<br>
-- <br>
<br>
</blockquote>
<div><br>
</div>
<div>WIth regard to locating access points:</div>
<div>Self-locating wifi APs</div>
<div><a href="https://www.youtube.com/watch?v=kVdFNR0R3EE"
moz-do-not-send="true" class="moz-txt-link-freetext">https://www.youtube.com/watch?v=kVdFNR0R3EE</a></div>
<div><br>
</div>
</div>
</div>
</blockquote>
<p>That's interesting, and clever work to solve the problem of
making APs into reliable location references. <br>
</p>
<p>They are doing a more involved/automated version of what I
suggested - using GPS (in their case built-in GPS, plus AP-AP
communication) for APs to locate themselves. Once the AP knows
where it is, the clients can find out where they are in physical
(WGS84 coordinate) space using the APs as references. Note that
it's an enterprise solution - definitely not for most homes -
since it requires at least 4, and probably many more suitable APs.<br>
</p>
<p>But LOC records don't have any role in what's described. They
*could* be an output (e.g. an AP could use DNS UPDATE to install
LOC records). But there's still no obviously useful consumer for
the LOCs...so why bother?</p>
<p>If you're in WiFi range of the AP, a client is better off getting
precise information from its broadcast. If not, it's useless.
And as previously noted, LOC for servers suffers from AnyCast,
cache, and CDN uncertainty.</p>
<p>LOC was proposed in simpler times.<br>
</p>
<p><br>
</p>
<pre class="moz-signature" cols="72">Timothe Litt
ACM Distinguished Engineer
--------------------------
This communication may not represent the ACM or my employer's views,
if any, on the matters discussed.
</pre>
<blockquote type="cite"
cite="mid:CA+nkc8AP=nBDAW-1cDBCkVfoGtUX2TQMRacnYmGn7Vj5E8h0Tg@mail.gmail.com">
<div dir="ltr"><input name="virtru-metadata" type="hidden"
value="{"email-policy":{"state":"closed","expirationUnit":"days","disableCopyPaste":false,"disablePrint":false,"disableForwarding":false,"enableNoauth":false,"persistentProtection":false,"expandedWatermarking":false,"expires":false,"isManaged":false},"attachments":{},"compose-id":"9","compose-window":{"secure":false}}"></div>
</blockquote>
</body>
</html>