This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/db-wg@ripe.net/
[db-wg] status and use/fulness of the geoloc: attribute
- Previous message (by thread): [db-wg] New on RIPE Labs: Registration History for Members - A Demo
- Next message (by thread): [db-wg] status and use/fulness of the geoloc: attribute
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Wilfried Woeber
Woeber at CC.UniVie.ac.at
Wed Sep 19 16:44:45 CEST 2012
Dear DB-Folks, in preparation for the upcoming WG Meeting in Amsterdam, and following up on dicussions during the previous one, I'd like to start the review and discussion on the geoloc: attribute in IPv4 and IPv6 inetnum objects. To get things going I'd like to solicit input from people and entities who/which have populated objects, and those making use of the information. What was your experience? Is this stuff useful? On a more general basis I'd like the community to review the current (sort of experimental) functionality and comment on the problems - if any - or suggest improvements! At the same time I am asking the NCC to provide us with some insight on the current use of this attribute. Thanks, Wilfried.
- Previous message (by thread): [db-wg] New on RIPE Labs: Registration History for Members - A Demo
- Next message (by thread): [db-wg] status and use/fulness of the geoloc: attribute
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]