- db-wg - mailman.ripe.net

Mandatory maintainer on PERSON and ROLE objects
by Denis Walker 18 Feb '10

18 Feb '10

[Apologies for duplicate emails] Dear Colleagues, The Data Protection Task Force asked the RIPE NCC to enforce maintaining all data in the RIPE Database. Currently, the "mnt-by:" attribute is optional in PERSON and ROLE objects. The RIPE NCC has now made this attribute mandatory in both these object types in a test environment. We recommend that anyone who uses automated scripts to generate or modify these objects should test their procedures and scripts against the test facilities. The test server has a recent copy of the RIPE Database data. One significant effect of this change is the circular dependency between PERSON and MNTNER objects. For a new user with no data in the RIPE Database, these two objects must be created together. This cannot be done by the normal update methods. There is a new user start-up interface that creates this pair of objects: https://www.db.ripe.net/cgi-bin/new-user-startup.pl This start-up process is described in the new RIPE Database Update Reference Manual: http://www.ripe.net/db/docs.html The test service is available on a test server at the following URL: whois-mandatory-mntby.db.ripe.net Queries to this database instance can be directed to: whois-mandatory-mntby.db.ripe.net:43 Email updates can be sent to<auto-dbm-mandatory-mntby(a)ripe.net>. Synchronous updates are available at: https://syncupdates-mandatory-mntby.db.ripe.net/ Near Real-Time Mirror (NRTM) access is available at: whois-mandatory-mntby.db.ripe.net:4444 Regards Denis Walker Business Analyst RIPE NCC Database Group

1 0

New Update Reference Manual
by Denis Walker 18 Feb '10

18 Feb '10

Dear Colleagues, [Apologies for duplicates] An updated version of the RIPE Database Update Reference Manual has just been published. This reflects a number of changes made over the last year. It is available in both PDF and HTML formats at: http://www.ripe.net/db/docs.html Regards, Denis Walker Business Analyst RIPE NCC Database Group

1 0

Unreferenced personal data cleanup process
by Denis Walker 16 Feb '10

16 Feb '10

[Apologies for duplicates] Dear Colleagues The RIPE NCC was asked at RIPE 59 to explain in more detail the workings of the new clean-up process for unreferenced personal data. This expanded explanation is now available, with examples, at: http://www.ripe.net/db/support/unreferenced-personal-data-clean-up.html Regards Denis Walker Business Analyst RIPE NCC Database Group

1 0

country attribute: "ZZ" for unspecified?
by Christian 'wiwi' Wittenhorst 09 Feb '10

09 Feb '10

Dear DB-WG, might there be a consent for introducing "ZZ" as an allowed value for the "country"-attribute for "unspecified"? Reasoning: - ISO 3166-1 [1] specifies "ZZ" as "User-assigned code elements are codes at the disposal of users who need to add further names of countries, territories, or other geographical entities to their in-house application of ISO 3166-1, and the ISO 3166/MA will never use these codes in the updating process of the standard.". - Many current entries do not specify the correct/meaningful value for country. Examples includes: [2a] RIPE-NCC-K-ROOT: NL [2b] TELTEK-1: GB, but: country is really Europe and Middle East [2c] ORG-AFNC1-RIPE: EU, but: country is really somewhere in African Region [2d] IANA-BBLK-RESERVED1: EU, but RFC1918 network [2e] EU-ZZ-163: EU, but: Country is really world wide [2f] LUXLINK-003: DE, but: These IP's are really World-Wide - For automated statistics it would be nice to have a special designation for IPs which do not correspond to a specific location, so that they are easy to filter. - It could be used for (global) anycast services, too. - ARIN & AfriNIC legacy entries could get a "correct" country. - Documentation says: "There are no rules defined for this attribute.", but the attribute is mandatory? Shouldn't we change that? Either make the attribute optional or specify, what it is supposed to contain. - I am dreaming: Wouldn't it be <http://dict.leo.org/ende?lp=ende&p=5tY9AA&search=desirable>desirable to have a designation for "world", too? - We already have a least on strange countries "EU", which does not seem to be part of ISO 3166-1... I'd like to hear your opinion... Best regards, Christian [1] <http://en.wikipedia.org/wiki/ISO_3166-1> [2a] <http://www.db.ripe.net/whois?searchtext=193.0.14.129&object_type=inetnum> [2b] <http://www.db.ripe.net/whois?searchtext=193.9.152.0&object_type=inetnum> [2c] <http://www.db.ripe.net/whois?searchtext=193.189.128.0&object_type=inetnum> [2d] <http://www.db.ripe.net/whois?searchtext=172.16.0.0&object_type=inetnum> [2e] <http://www.db.ripe.net/whois?searchtext=163.0.0.0&object_type=inetnum> [2f] <http://www.db.ripe.net/whois?searchtext=91.142.59.0&object_type=inetnum>

6 8

[Fwd: Уважаемый Mr.Sergiy Viktorovich Shabatura (BUDREMYER2 - NET) !]
by Max Tulyev 30 Jan '09

30 Jan '09

Hi all, here is a sample of RIPE DB based SPAM. The funniest thing is address it was received is support(a)netassist.kiev.ua is listed only as changed: attribute at this net's (BUDREMYER2-NET) mntner! What is the data leak? -- WBR, Max Tulyev (MT6561-RIPE, 2:463/253@FIDO)

1 0

Уважаемый Mr.Sergiy Viktorovich Shabatura (BUDREMYER2 - NET) !
by Gabriella KOVACS 30 Jan '09

30 Jan '09

Уважаемый Mr.Sergiy Viktorovich Shabatura (BUDREMYER2 - NET) ! Мы Intron Electronics Hungary Ltd. Paботаем с Интернет провайдерами и по етому поводу мы нашли Вас, чтобы найти с Вами общий путь. Ознакомительный лист про нашу фирму мы прикрипили к письме. Зарегистрируйтесь на нашом сайте и Вы найдёте много интересных информаций для Вашей фирме. Спасибо! Всего Доброго! -- Best Regards /Udvozlettel: Gabriella Kovacs (Nemzetkozi Kapcsolattarto - International Contact Person) INTRON Electronics Hungary Kft. (INTRON Electronics Hungary Ltd.) Web: http://www.intron.hu Mail: kovacsg(a)intron.hu Tel.: +36/1/422-1755 Fax: +36/1/422-1756 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. !DSPAM:49828b54265012543113083!

1 0

Deletion of unreferenced PERSON and ROLE objects
by Denis Walker 20 Jan '09

20 Jan '09

Dear Colleagues, The RIPE NCC will start to delete unreferenced PERSON and ROLE objects from the RIPE Database on Monday, 26 January 2009. Any PERSON or ROLE object that remains unreferenced by any operational resource for 21 consecutive days will be marked for deletion. It can be deleted at any time after this period if it remains unreferenced. Unused MNTNER objects that only maintain unreferenced PERSON or ROLE objects will also be marked and then deleted. To minimise any impact on Database Services, a small number of objects will be deleted on a daily basis. The number of daily deletions will gradually increase. It is expected to take several months to remove the backlog of unreferenced objects. After the backlog is removed, all unreferenced PERSON and ROLE objects, and in some cases their MNTNER objects, will be deleted after being unreferenced for 21 consecutive days. For more details, please refer to this support page: http://www.ripe.net/db/support/cleanup-unreferenced-data.html If you have any questions about this, please contact <ripe-dbm(a)ripe.net>. Regards, Denis Walker Business Analyst RIPE NCC

1 0

Maintenance Announcement - 22/01/2009
by Ben O'Hara 19 Jan '09

19 Jan '09

[Apologies for duplicate mails] Dear Colleagues, Between 17:00 and 18:00 (UTC) on Thursday 22 Jan 2009, the RIPE NCC will carry out planned maintenance work on our network infrastructure. During this period all RIPE NCC services will suffer intermittent interruptions We apologise for any inconvenience that this may cause. Regards Ben -- Ben O'Hara RIPE Network Coordination Center Systems Engineer Singel 258, Amsterdam, NL http://www.ripe.net +31 20 535 4444 PGP Fingerprint: 080A 52FF BF0A A7FB F176 E7DB 513D 9A3D E968 7DBC

1 0

Outage report for the RIPE Database services
by Denis Walker 24 Nov '08

24 Nov '08

[ Apologies for duplicate mails ] Dear colleagues, >From approximately 07:30 (UTC) to 18:30 (UTC) on Saturday, 22 November 2008, the RIPE Database web based services were not available. This was due to the scheduled maintenance of our central filer system. During this period it was not possible to connect to the syncupdates or webupdates services or use the query web form or other web based forms. Email updates were also delayed. All the messages received by auto-dbm(a)ripe.net were stored on our mail server. All the saved update messages have been processed. If you sent an email update to the RIPE Database service during this period, you will have already received an acknowledgement message. There is no need to re-send any update messages. We apologise for any inconvenience that this may have caused. Regards, Denis Walker Business Analyst RIPE NCC Database Group

1 0

ANNOUNCEMENT: RIPE NCC Training Courses
by Training 20 Nov '08

20 Nov '08

[Apologies for duplicate e-mails] Dear Colleagues, The RIPE NCC invites you to register for one of our upcoming training courses: - The LIR Training Course This course teaches LIRs how to request Internet number resources and interact with the RIPE NCC. A course outline is available at: http://www.ripe.net/training/lir/outline.html - The Routing Registry Training Course This course teaches LIRs how to use the RIPE Database for routing. A course outline is available at: http://www.ripe.net/training/rr/outline.html - The DNS for LIRs Training Course This course teaches LIRs about the RIPE NCC's DNS-related services. A course outline is available at: http://www.ripe.net/training/dns/outline.html To see the location of upcoming courses and to register, please use the LIR Portal or complete the registration form on our website at: http://www.ripe.net/cgi-bin/trainingform.pl.cgi If you have any questions please do not hesitate to contact us at <training(a)ripe.net>. Kind regards, Rumy Kanis Training Services Manager RIPE NCC

1 0