Re: [Geopriv] [geopriv] #38: Section 1

From: Thomson, Martin ^lt;Martin.Thomson@andrew.com>
Date: Sun Aug 22 2010 - 19:47:37 EDT

I can live with that.

> -----Original Message-----
> From: geopriv-bounces@ietf.org [mailto:geopriv-bounces@ietf.org] On
> Behalf Of Bernard Aboba
> Sent: Saturday, 21 August 2010 12:59 AM
> To: Marc Linsner
> Cc: <geopriv@ietf.org>; <trac@tools.ietf.org>
> Subject: Re: [Geopriv] [geopriv] #38: Section 1
>
> Works for me.
>
> On Aug 20, 2010, at 5:56 AM, Marc Linsner <mlinsner@cisco.com> wrote:
>
> > In an effort to cover Martin's concern about the DHC server using
> > alternative location determination methods. How about:
> >
> > "The mechanism defined here may also be utilized to provide location
> to
> > wireless hosts. DHC relay agent sub-options (RAIO) [RFC3046] is one
> method
> > a DHC server might use to perform host location determination.
> Currently,
> > the relay agent sub-options do not include data sets required for
> device
> > level location determination of wireless hosts. In cases where the
> DHC
> > server uses RAIO for location determination, a wireless host can use
> this
> > mechanism to discover location of the radio access point, or the area
> of
> > coverage for the radio access point."
> >
> > (this may be too wordy for the Intro section)
> >
> > Comments?
> >
> > -Marc-
> >
> >
> >
> > On 8/20/10 2:26 AM, "Bernard Aboba" <bernard_aboba@hotmail.com>
> wrote:
> >
> >> Within the wireless case there are static, nomadic and mobile cases.
> I
> >> think that some of the text you suggest relates to all wireless
> cases, not
> >> just mobile. So how about this?
> >>
> >> "The mechanism defined here may also be utilized to provide location
> to
> >> wireless hosts. DHC relay agent sub-options [RFC3046] enable the
> DHCP
> >> server to perform host location determination. Currently, the relay
> agent
> >> sub-options do not include data sets required for device level
> location
> >> determination of wireless hosts. A wireless host can use this
> mechanism
> >> to discover location of the radio access point, or the area of
> coverage for
> >> the radio access point."
> >>
> >>
> >>
> >> -----Original Message-----
> >> From: Marc Linsner [mailto:mlinsner@cisco.com]
> >> Sent: Thursday, August 19, 2010 6:41 AM
> >> 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
Received on Mon, 23 Aug 2010 07:47:37 +0800

This archive was generated by hypermail 2.1.8 : Sun Aug 22 2010 - 19:45:36 EDT