Re: [Geopriv] Proposed resolution of Ticket #44 (Jari's DISCUSS on RFC3825bis)

I would agree that if a value is outside the normal ranges for lat and long, then there is an error somewhere in the workflow. As such, an error message should be reported to the application or the user. Clamping to +90 is actually creating even more erroneous data. Thanks, Bernard.

 

Carl

 

----- Original Message -----

From: Bernard Aboba

To: geopriv@ietf.org

Sent: Wednesday, January 19, 2011 9:50 AM

Subject: [Geopriv] Proposed resolution of Ticket #44 (Jari's DISCUSS on RFC3825bis)

Ari Keränen's review (see below) included a comment on issues arising from clamping of
latitude/longitude values outside the range. 

Comments?
===========================================
2.3. Latitude and Longitude Fields

Latitude values encoded by the DHCP server MUST be constrained to the
range from -90 to +90 degrees. Location consumers MUST be prepared
to normalize values outside this range. Values outside the range are
normalized by clamping [...]

If the values MUST be within those boundaries, doesn't it mean that a
value that is out of the range is somewhat likely completely wrong (due
to a broken implementation) and thus it would make sense to ignore it
rather than try to normalize the value and make it appear as if it was
valid? I'm not sure if I'd like to be liberal in what I accept when it
comes to information that could literally be a matter of life and death.

---

_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv