RE: [Geopriv] Moving Forward on 3825 update

From: Dawson, Martin ^lt;>
Date: Sun Feb 04 2007 - 00:04:04 EST

I didn't send an answer to Henning's question because I didn't even see how it was relevant to the discussion. Here's the full substance of the post: "I'm curious how you would do this with fixed-point binary numbers, unless you add a length or mask parameter of some sort." What is it actually asking, how is it the same as adding a resolution parameter, and why is it fundamentally decisive to the discussion? Cheers, Martin ________________________________ From: Andrew Newton [] Sent: Sun 2/4/2007 1:14 PM To: GEOPRIV WG Subject: [Geopriv] Moving Forward on 3825 update All, Brian is right. We need to come to conclusions on this document and move on. The following are how I see the consensus of the GEOPRIV working group on this topic. 1) We've had long discussions regarding the difference between uncertainty and resolution. While some people believe uncertainty information should be communicated with 3825 coordinates, there is no consensus within the working group to do this. 2) Likewise, there is no consensus in the working group that resolution should not be communicated with 3825 coordinates. With this particular issue, I also weighed the chair's right to demand technical soundness of a document. There were no valid answers to Henning's question ( current/msg02665.html), so I am left to conclude that this is a technically sound and reasonable thing to do. 3) There is rough consensus that RFC 3825 is unclear or misleading with respect to the type of information to be conveyed in DHCP. Therefore, the decision made in San Diego at IETF 67 to produce an update to RFC 3825 clarifying any misleading text and adding new, clarifying text is still the course of action for this working group. -andy, GEOPRIV co-chair _______________________________________________ Geopriv mailing list ------------------------------------------------------------------------------------------------ This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any unauthorized use of this email is prohibited. ------------------------------------------------------------------------------------------------ [mf2]

Geopriv mailing list
Received on Sat, 3 Feb 2007 23:04:04 -0600

This archive was generated by hypermail 2.1.8 : Sun Feb 04 2007 - 00:04:22 EST