Hi, A small comment inline: On Thu, 4 Aug 2022, denis walker via db-wg wrote: (...)
So in what ways is "geofeed:" going to make it easy for network operators to coordinate some activity? One of the ways network operators have talked about how they want/need to use "geofeed:" data is to provide content based on location of an IP address.
Yes. Although *some* geolocation providers INSIST that their location assessment is better than the owner's network. They do this by ignoring messages or form data sent by owners. Keeping the attribute in the RIPE database may show ANYONE what is the location the owner says it is the correct location. And hopefully that should be the mandatory source for this information.
If a content providing network operator wishes to offer this content to anyone in a specific location, that can be seen as a coordination activity. The content provider can coordinate with other network operators to establish that their customers are within this location so they can access this content. If this interpretation is accepted by the community then the context has changed. The legal team can now reassess their advice in the context that the use of the "geofeed:" data is now covered by the existing database purposes.
Yes, please :-) Cheers, Carlos