[db-wg] Future of "geoloc:"
- Previous message (by thread): [db-wg] Future of "geoloc:"
- Next message (by thread): [db-wg] Future of "geoloc:"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Laurent Pellegrino
laurent.pellegrino at ipregistry.co
Tue Apr 12 22:34:35 CEST 2022
Hi there, A quick suggestion you might have already thought about: why not deprecate the "geoloc:" attribute and make it clear it is deprecated in docs and all UI, without preventing its usage? Kind regards, Laurent Pellegrino On Tue, Apr 12, 2022 at 10:26 PM Daniel Suchy via db-wg <db-wg at ripe.net> wrote: > 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 > > > > -- > > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.ripe.net/ripe/mail/archives/db-wg/attachments/20220412/1001e5d3/attachment.html>
- Previous message (by thread): [db-wg] Future of "geoloc:"
- Next message (by thread): [db-wg] Future of "geoloc:"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]