Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

geo hint "city" field is ambiguous #195

Open
npdoty opened this issue Apr 27, 2022 · 1 comment
Open

geo hint "city" field is ambiguous #195

npdoty opened this issue Apr 27, 2022 · 1 comment
Labels

Comments

@npdoty
Copy link

npdoty commented Apr 27, 2022

RFC 8805 didn't specify what city meant, except that it's a free form string. There is a hint that it's equivalent to RFC 4119's A2 element, but that appears to be incorrect in practice. A2 is described as "county" and the common examples don't seem to be at that administrative level (most that I can see are city or city division).

If IETF is going to publish new geolocation format standards, I would recommend working from geopriv, or providing a precise mapping (like the sample XML in RFC 8805) or at least pointing to other standards that are less ambiguous.

@tfpauly
Copy link
Owner

tfpauly commented Jun 21, 2022

The point here would be to include literally what is in a Geo IP feed file, and align with that rather than sharing new information that would not be available from the IP address itself. To that end, I don't think it makes sense to change this to be divergent? It would be better to revise 8805?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants