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

Request for use case: GeoIP #130

Open
AramZS opened this issue Nov 16, 2021 · 8 comments
Open

Request for use case: GeoIP #130

AramZS opened this issue Nov 16, 2021 · 8 comments

Comments

@AramZS
Copy link
Member

AramZS commented Nov 16, 2021

There is an interest in understanding how GeoIP is used and why, what are the use cases that are reflected by participants in this group. This would be highly relevant to a discussion around this in an IETF working group - https://datatracker.ietf.org/rg/pearg/meetings/

And potentially here to our antifraud group in the W3C here - https://www.w3.org/community/antifraud/

What follows is our use case questions and we would like to see answers from all participants that can be collected into a use case.


What is the use case?

Describe the use case in detail. What does it do?

Why is it important to preserve this use case?

Describe why this feature is critical to effective web advertising - both benefits to businesses as well as benefits to consumers.

How is it functionally achieved today?

Describe how this functionality is achieved today

@AramZS AramZS added the agenda+ Request meeting agenda time label Feb 1, 2022
@AramZS
Copy link
Member Author

AramZS commented Mar 1, 2022

Please open issues on this repo with proposals and changes, especially of value is PRs with text additions - https://github.com/ShivanKaul/draft-ip-address-privacy/blob/main/draft-irtf-pearg-ip-address-privacy-considerations.md#rough-geolocation

@AramZS
Copy link
Member Author

AramZS commented Mar 1, 2022

  • We also want to update the Antifraud group on this

@AramZS AramZS removed the agenda+ Request meeting agenda time label Mar 1, 2022
@AramZS
Copy link
Member Author

AramZS commented Mar 1, 2022

Noting an explicit need for use cases on the basis of the questions of regulatory contradictions, especially in terms of privacy and how cache sharding might be dependent on that.

@AramZS
Copy link
Member Author

AramZS commented Mar 1, 2022

Noting from Kris Chapman that there is a need, even when the user is not necessarily under a contradicting regime, to have geo-based decisions around storage and control.

@AramZS
Copy link
Member Author

AramZS commented Mar 1, 2022

@AramZS
Copy link
Member Author

AramZS commented Mar 1, 2022

Noting that for ad targeting use cases, they usually want to resolve to DMA - Designated Market Area. Often zipcode-level data is needed for things like weather ads by region, or by anticipated travel. Some advertisers like insurance are dependent on state-level understandings (which is not covered by DMA because DMA can cross states)

@AramZS
Copy link
Member Author

AramZS commented Mar 1, 2022

Another use case is about using lat/long to understand weather based on IP and target ads on that basis.

Another use case restricts the targeting to specific places because of some level of compliance.

There is also negative geofencing - where one might limit an ad on the basis of the geo - for example one doesn't want to show cigarette ads to IPs coming from schools.

@wseltzer
Copy link
Member

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

No branches or pull requests

2 participants