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/[email protected]/
[ncc-announce] [news] RIPE Database: Organisation Names in "descr:" cleaned up and no longer enforced
- Previous message (by thread): [ncc-announce] [news] First iPad Winner: RIPE NCC Survey 2016
- Next message (by thread): [ncc-announce] [news] Creating Additional LIR Accounts
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Tim Bruijnzeels
tim at ripe.net
Thu Jun 2 15:49:11 CEST 2016
Dear colleague, Following consensus on the Database Working Group mailing list, the RIPE NCC is no longer enforcing that the first “descr:” attribute on inetnum, inet6num and aut-num objects reflects your organisation name for allocations and assignments created by the RIPE NCC. We have removed the first “descr:” attribute line from all these objects, leaving any multiple “descr:” attribute lines how they are. We sent notifications about this for all objects that had a “notify:” email address configured. No action is required from you. All holders of resource objects allocated or assigned by the RIPE NCC can now update the “descr:” attribute themselves. You can use any text on the “descr:” attribute, or leave it out all together. A reference to the holding organisation still exists on the “org:” attribute that the RIPE NCC maintains for these resources. If you have any questions or comments, please email <ripe-dbm at ripe.net> Kind regards, The RIPE NCC Database team
- Previous message (by thread): [ncc-announce] [news] First iPad Winner: RIPE NCC Survey 2016
- Next message (by thread): [ncc-announce] [news] Creating Additional LIR Accounts
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]