[db-wg] geolocation and current purposes
- Previous message (by thread): [db-wg] geolocation and current purposes
- Next message (by thread): [db-wg] 2022-01 Personal data in the RIPE Database Next Steps
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
denis walker
ripedenis at gmail.com
Mon Aug 22 15:52:21 CEST 2022
Hi It is optional for the resource holder, not for the end user or customer. For them it is a question of whether or not the contracts they signed permit the publication of this (personal) data. cheers denis co-chair DB-WG On Mon, 22 Aug 2022 at 11:30, Cynthia Revström via db-wg <db-wg at ripe.net> wrote: > > It is an optional attribute and as far as I know it is going to stay that way. > > -Cynthia > > On Mon, 22 Aug 2022, 10:13 Horváth Ágoston János via db-wg, <db-wg at ripe.net> wrote: >> >> I, for one, with my regular internet user hat on, am strongly against any form of geolocation and consider it an invasion of my privacy. >> I don't want any random guy on the internet to simply pinpoint the town I'm living in. >> >> Is there an opt-out from this? Users will demand that there is for sure. >> >> Just my $0.02 >> >> Agoston >> >> On Thu, Aug 4, 2022 at 7:24 PM Carlos Friaças via db-wg <db-wg at ripe.net> wrote: >>> >>> >>> >>> 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 >>> >>> >>> >>> -- >>> >>> To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/db-wg >> >> -- >> >> To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/db-wg > > -- > > To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/db-wg
- Previous message (by thread): [db-wg] geolocation and current purposes
- Next message (by thread): [db-wg] 2022-01 Personal data in the RIPE Database Next Steps
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]