The IP Geolocation HTTP Client Hint
draft-pauly-httpbis-geoip-hint-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Tommy Pauly , David Schinazi , Ciara McMullin , Dustin Mitchell | ||
| Last updated | 2025-04-21 (Latest revision 2024-10-18) | ||
| Replaces | draft-pauly-httpbis-geohash-hint | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Techniques that improve user privacy by hiding original client IP addresses, such as VPNs and proxies, have faced challenges with server that rely on IP addresses to determine client location. Maintaining a geographically relevant user experience requires large pools of IP addresses, which can be costly. Additionally, users often receive inaccurate geolocation results because servers rely on geo-IP feeds that can be outdated. To address these challenges, we can allow clients to actively send their network geolocation directly to the origin server via an HTTP Client Hint. This approach will not only enhance geolocation accuracy and reduce IP costs, but it also gives clients more transparency regarding their perceived geolocation.
Authors
Tommy Pauly
David Schinazi
Ciara McMullin
Dustin Mitchell
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)