geofeed is quite new attribute... you cannot expect quick adoption in field. At this time, geoloc should simply remain as-is. Daniel On 4/12/22 21:17, denis walker via db-wg wrote:

Colleagues

Now we have the "geofeed:" attribute, what should we do with "geoloc:"? Right now far more people are using "geoloc:" than "geofeed:".

denis$ zgrep "^geofeed:" ~/Desktop/ripe.db.inetnum.gz | wc -l 289 denis$ zgrep "^remarks:\s*geofeed" ~/Desktop/ripe.db.inetnum.gz | wc -l 13

Although from the 289 there are only 161 unique organisations.

denis$ zgrep "^geoloc:" ~/Desktop/ripe.db.inetnum.gz | wc -l 35453

cheers denis co-chair DB-WG

Hi Denis, You have an interesting question. Possibly, as Laurent suggested, we could inform the users to use geofeed instead of geoloc. On 12/04/2022 21:17, denis walker via db-wg wrote:

Right now far more people are using "geoloc:" than "geofeed:".

This is definitely true. However, in this comparison keep in mind that while geoloc is a lat,long specified for each inetnum, a geofeed can be associated to a parent inetnum and contain definitions valid for multiple more-specific inetnums (and prefixes).

denis$ zgrep "^geofeed:" ~/Desktop/ripe.db.inetnum.gz | wc -l 289

including inet6num they are 352

denis$ zgrep "^remarks:\s*geofeed" ~/Desktop/ripe.db.inetnum.gz | wc -l 13

There are 537 inet(6)nums with "Geofeed" remarks (uppercase G) and 19 with "geofeed". Ciao, Massimo