> The mechanism defined here utilizes DHC relay agent
> sub-options (RFC3046) enabling the DHC server to perform host location
> determination.
Though that would be the easiest and most logical approach to determination, the protocol does not require this. I could implement a DHCP server that doesn't need RAIO in order to provide location information.
> -----Original Message-----
> From: geopriv-bounces@ietf.org [mailto:geopriv-bounces@ietf.org] On
> Behalf Of Marc Linsner
> Sent: Thursday, 19 August 2010 11:41 PM
> To: Bernard Aboba; trac@tools.ietf.org
> Cc: geopriv@ietf.org
> Subject: Re: [Geopriv] [geopriv] #38: Section 1
>
> Bernard,
>
> On 8/13/10 1:31 PM, "Bernard Aboba" <bernard_aboba@hotmail.com> wrote:
>
> > Yes, what you say below makes a lot of sense. If a mobile host
> wants an
> > updated
> > location, it has to obtain it somehow, regardless of the LCP it is
> using. In
> > the case
> > of DHCP this need not necessarily entail obtaining a new address.
> Given that,
> > is
> > the "applicability" text really unique to DHCP?
> >
> > Also, I'd also like to see some statement made about wireless usage,
> if only
> > to make
> > it clear that the mechanism is not purely for use in wired scenarios.
> >
>
> 3825 says,
>
> "
> Wireless hosts can utilize this option to gain knowledge of the
> location of the radio access point used during host configuration,
> but would need some more exotic mechanisms, maybe GPS, or maybe a
> future DHCP option, which includes a list of geo-locations like that
> defined here, containing the locations of the radio access points
> that are close to the client.
> "
>
> draft 3825bis says,
>
> "
> The options defined in this document have limited applicability for
> mobile hosts. Typically DHCP clients refresh their configuration in
> response to changes in interface state or pending lease expirations.
> As a result, when a mobile host changes location without
> subsequently
> completing another DHCP exchange, location configuration information
> initially obtained via DHCP could become outdated.
> "
>
> I suggest replacing the above with,
>
> "
> The options defined in this document may have limited applicability for
> mobile hosts. The mechanism defined here utilizes DHC relay agent
> sub-options (RFC3046) enabling the DHC server to perform host location
> determination. Currently, the relay agent sub-options do not include
> data
> sets required for device level location determination of mobile hosts.
> A
> mobile host can use this mechanism to discover location of the radio
> access
> point, or the area of coverage for the radio access point.
> "
>
> Comments?
>
> -Marc-
>
>
> _______________________________________________
> Geopriv mailing list
> Geopriv@ietf.org
> https://www.ietf.org/mailman/listinfo/geopriv
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv
