![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Hi Brian,
On 2007-04-20 09:21, Hannes Tschofenig wrote:I should have written "RFC 3825 is not a great choice in a cellular environment". It is fine for a WLAN hotspot and an enterprise environment.DHCP is not a great choice in a mobile environment and also not when it comes to more complex location representations.
Why can't a mobile system have a locally valid DHCP record (+/- the length
of a wireless link)? For that matter, why couldn't a DHCP server have
real-time triangulation data, if it exists at all?
Do you mean more complex than can be expressed by RFC 4776 and RFC 3825 together?RFC 3825 describes a point.
Location determination techniques produce other shape types. Please look at http://www.ietf.org/internet-drafts/draft-ietf-geopriv-pdif-lo-profile-06.txt
Brian
Ciao Hannes
_______________________________________________ Ietf mailing list Ietf at ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.