@techreport{pauly-httpbis-geoip-hint-02,
    number =    {draft-pauly-httpbis-geoip-hint-02},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-pauly-httpbis-geoip-hint/02/},
    author =    {Tommy Pauly and David Schinazi and Ciara McMullin and Dustin Mitchell},
    title =     {{The IP Geolocation HTTP Client Hint}},
    pagetotal = 7,
    year =      2025,
    month =     sep,
    day =       30,
    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 HTTP clients to actively send their network geolocation to an HTTP server via an HTTP header field. This approach will not only enhance geolocation accuracy and reduce IP costs, but it also gives clients more transparency regarding their perceived geolocation. This is also particularly useful in the case of HTTP intermediaries that hide client IP addresses, such as Oblivious HTTP (OHTTP) relays.},
}