- ncc-services-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

RIPE NCC Membership Growth Statistics (Part 2) on RIPE Labs
by Mirjam Kuehne 17 Feb '10

17 Feb '10

[apologies for duplicates] Dear colleagues, As announced in an earlier mail, we looked at the distribution of Internet number resources among the RIPE NCC membership. You can find the details on RIPE Labs: http://labs.ripe.net/content/members-and-their-number-resources Kind Regards, Mirjam Kühne

1 0

Announcement: RIPE NCC Training Courses
by Olivia Mijnals-Ruimwijk 16 Feb '10

16 Feb '10

[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 IPv6 Training Course This course teaches LIRs about the need for IPv6 and includes basic information on how to plan your deployment. A course outline is available at: http://www.ripe.net/training/ipv6/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: RIPE NCC Upcoming Courses List & Registration https://lirportal.ripe.net/lirportal/training/course-list.html 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

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

32-bit AS Number status?
by Shane Kerr 01 Feb '10

01 Feb '10

All, I noticed that the proposed updated AS Number policy was sent to the address-policy-wg recently. There is a timeline for 32-bit AS Number in both the old and new versions, which says: "From 1 January 2010 the RIPE NCC will cease to make any distinction between 16-bit AS Numbers and 32-bit only AS Numbers, and will operate AS Number assignments from an undifferentiated 32-bit AS Number allocation pool." I'm not sure exactly what this means, but I think it is supposed to mean that people get 32-bit AS Numbers now. Did this happen? If it didn't, why not? Do we need to change "2010" to "2011"? Is it ever going to happen? If it did, was there any effect? I mean both from humans (angry LIRs, peasants marching on the castle with torches, riots in the streets), or on the Intertubes (ugly routing artifacts, mass reboots of boxes with old firmware, monitoring systems gone wild)? Just wondering. :) -- Shane

4 4

Reverse DNS Outage Announcement
by Sjoerd Oostdijck 22 Jan '10

22 Jan '10

[Apologies for duplicates] Dear Colleagues, At 13:50 on Thursday, 21 January, an error was introduced into the RIPE NCC's reverse DNS provisioning system. This caused reverse DNS delegations to stop working for allocations in the following range: 77.0.0.0 to 77.220.7.255 This error was triggered by an internal cleanup of our Early Registration Transfer (ERX) DNS delegations, which was being conducted as part of the RIPE NCC's Registration Data Quality (RDQ) project. The reverse DNS provisioning system was corrected again on 22 January at 09:50 (UTC). However, due to negative caching in DNS resolvers, the problem may have remained visible for a further two hours. The RIPE NCC is currently revising the reverse DNS provisioning system to prevent errors such as this occurring in future. If you have any questions or comments, please send an email to <ncc(a)ripe.net>. Regards, Sjoerd Oostdijck DNS Services Group, RIPE NCC

1 0

2009-03 "Run-out fairly" implemented
by Xavier Le Bris 21 Jan '10

21 Jan '10

[Apologies for duplicate e-mails.] Dear Colleagues, We are pleased to announce that the policy described in proposal 2009-03,"Run Out Fairly", has been implemented. Requests for IPv4 address space received on or after Friday, 22 January will be evaluated by the RIPE NCC Registration Services Department under the new policy. Full text of the policy proposal can be found at: http://ripe.net/ripe/policies/proposals/2009-03.html The following RIPE documents have been updated to reflect this policy implementation: http://www.ripe.net/ripe/docs/ripe-488.html http://www.ripe.net/ripe/docs/ripe-489.html http://www.ripe.net/ripe/docs/ripe-490.html http://www.ripe.net/ripe/docs/ripe-491.html Regards, Xavier Le Bris Registration Services

1 0

2007-01 Policy Implementation - Phase Two Deadline Extended
by Arne Kiessling 30 Dec '09

30 Dec '09

Dear Colleagues, We would like to inform you that the RIPE NCC has extended the deadline for phase two of the 2007-01 policy implementation ("Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region") by two months. LIRs now have until 1 March, 2010 to provide the required documentation for the independent resources that they have marked as "My End User". For further information on the documentation required please see: http://ripe.net/rs/pi-existing-assignments.html If you have any comments or questions, please contact <enduser-contract(a)ripe.net>. Kind regards, Arne Kiessling IP Resource Analyst RIPE NCC

1 0

RE: [ncc-services-wg] FW: [ncc-announce] New RIPE NCC PGP Key
by Thor Kottelin 18 Dec '09

18 Dec '09

> From: "Cosku Yilmaz" <cosku(a)cccmos.com> > To: <ncc-services-wg(a)ripe.net>, > <ncc-announce(a)ripe.net> > Date: Fri, 18 Dec 2009 12:39:15 +0300 > Would you please explain what is need to be done and what the steps > are. Do you use, or intend to start using, PGP? If not, you do not need to do anything. If you do use PGP, the steps are basically: download the key, check its authenticity, sign it using your copy of PGP and add it to a key ring. Then use the new key (instead of the previous one) to verify the email messages you receive from the RIPE NCC. -- Thor Kottelin http://www.anta.net/

2 3