ietf
[Top] [All Lists]

Re: [Geopriv] Confirmation of GEOPRIV IETF 68 Working Group Hums

2007-04-20 06:36:13
Brian E Carpenter wrote:
On 2007-04-20 09:21, Hannes Tschofenig wrote:
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?
If you look at DOCSIS cable, a single head end can subtend a huge amount
of cable in a single bridged domain. I seem to recall that in a rural Canadian
MSO I worked with it was 10's if not 100's of miles. I have no clue how
accurate GEOPRIV tries to be, but it sure seems that if the location of the
headend/dhcp relay is only piece of information you have, your accuracy is
going to be pretty lousy in many cases. If this information is intended for
first responders, it seems that all you're doing is pointing to the right haystack
to start searching for the needle.

      Mike, who probably shouldn't open his mouth here

_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf

<Prev in Thread] Current Thread [Next in Thread>