Re: Radius-Geopriv: Precision

[Jari Arkko <jari.arkko@piuha.net>]

Bernard Aboba wrote:

> I think the document needs to clearly differentiate NAS location from user
> location.
>
> Today shipping 802.11 APs can estimate the user location to a significant
>  
(snip)

> If NAS location and user location are clearly delineated, then it will not
> be necessary to take that into account within a precision attribute.
>  
I agree. Here are some text suggestions. Change

    Precision (8 bits):
      Describes which location this attribute refers to:
      (0) describes the location of the NAS
      (1) describes the location of the AAA server
      (2) describes the location of the end host (user)
      (3) describes the location of the network

to

    Entity (4 bits):
       Describes whose location this attribute carries:
       (0) Describes the location of the user's client device,
            as estimated by the network.
       (1) Describes the location of the NAS

Justification: I could not think of any case where the location
of AAA server would have to figured out. Also, "NAS" and
"network" are too imprecise to be useful. What about a
distributed NAS, a concentrator/dummy AP combination?
I would just give a the user's location or no location at all
if we get into that kind of things. But if you really need the
network's location, you might consider adding a subfield
for "cell size", that shows how large area this "NAS" covers.
But I don't think its essential functionality.

--Jari



--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>