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

Highlight edge cases of geolocation based on IP Address #123

Closed
PieterKas opened this issue Apr 23, 2024 · 0 comments
Closed

Highlight edge cases of geolocation based on IP Address #123

PieterKas opened this issue Apr 23, 2024 · 0 comments

Comments

@PieterKas
Copy link
Collaborator

Add guidance on potential edge cases for implementors to be aware off when using network address as a proximity measure.

  1. In the case of 6.1.1 establishing proximity, there is a boundary (pun not intended) case where a device will shift between two different cellular providers. The IETF's Drone effort were examining the same problem as the drone flies close to an international boundary and flips back and forth to roaming and not. How to deal with this case or whether it is dependable is a question. I know that Pieter is suggesting Fido2, but the way this section is written a Consumption device may be on a weak Wifi and the authentication device has shifted to Cellular.

https://mailarchive.ietf.org/arch/msg/oauth/wC0iOyc9bPxcvv8OmnAt0EcKw6I/

PieterKas added a commit that referenced this issue Apr 26, 2024
Added guidance on GNSS and IP location inaccuracies (see issue #123).

cc @roywill
PieterKas added a commit that referenced this issue Apr 30, 2024
Added guidance on geo-location inaccuracies (see issue #123)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant