- ncc-services-wg - mailman.ripe.net

LIR Locator Tool on RIPE Labs
by Mirjam Kuehne 16 Apr '10

16 Apr '10

Dear colleagues, The RIPE NCC is working on an LIR Locator tool. You can find some more details on RIPE Labs: http://labs.ripe.net/content/lir-locator-tool Please let us know what you think. Kind Regards, Mirjam Kühne RIPE NCC

2 1

Update to RIPE NCC LIR Portal
by Andrew de la Haye 15 Apr '10

15 Apr '10

[Apologies for duplicates] Dear RIPE NCC member, The RIPE NCC is currently in the process of upgrading the LIR Portal to a single sign-on system. Once implemented, this system will allow members to more easily access all RIPE NCC services that require the user to sign in. To help ensure a smooth deployment, the upgrade will be rolled out in stages over the coming months. The first stage of deployment, upgrading the Billing section of the site, was carried out on Wednesday, 14 April. Because the deployment of this new sign-in system so far applies to only part of the LIR Portal, users may find that they are asked to sign in more than once as they move between different sections of the site. This is to be expected, and will continue until the single sign- on system has been fully deployed throughout the LIR Portal. We apologise for any inconvenience this may cause users. If you have any questions or comments regarding this upgrade, please email <ncc(a)ripe.net >. Best regards, Andrew de la Haye Chief Operations Officer

1 0

RIPE NCC Operated K-Root Server Now Distributing Root Zone Signed with DNSSEC
by Anand Buddhdev 24 Mar '10

24 Mar '10

[Apologies for duplicate emails] Dear Colleagues, The K-root server, operated by the RIPE NCC, is now serving the signed root zone as part of a staged global deployment of DNSSEC across the root zone system. Starting with L-root in January 2010, the root servers began serving the signed root zone in batches in the form of a Deliberately Unvalidatable Root Zone (DURZ). This roll out period is scheduled to end in May 2010 and ICANN is scheduled to sign the root zone with real keys and release the trust anchor after 1 July 2010. For more information, please see: http://www.ripe.net/news/k-root-signed-dnssec.html If you have any questions about this, please don't hesitate to contact <dns-help(a)ripe.net>. Regards, Anand Buddhdev, DNS Services Manager, RIPE NCC

1 0

Call for Agenda Items - RIPE 60
by Sanghani, Bijal 24 Mar '10

24 Mar '10

Dear All, The count down has started to RIPE 60 in Prague, we are starting to put together a draft agenda for the NCC Services Working Group. If anyone would like to suggest a presentation or raise a topic for discussion please let either Kurtis or me know and we'll arrange a spot on the agenda for you. Regards, Bijal Sanghani The information contained in this e-mail message is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you should return it to the sender immediately. Please note that while we scan all e-mails for viruses we cannot guarantee that any e-mail is virus-free and accept no liability for any damage caused by any virus transmitted by this email.

1 0

Status Update - Independent Resource Assignments (Policy Proposal 2007-01)
by Andrew de la Haye 09 Mar '10

09 Mar '10

Dear Colleagues, In March 2009, the RIPE NCC began Phase 1 of the policy implementation "Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region". This phase focused on new assignments of independent Internet number resources only (PI assignments, AS Numbers, IPv6 Internet Exchange Point (IXP) assignments and Anycasting assignments). The implementation was carried out successfully and the majority of RIPE NCC members are aware of the policy and contractual requirements and are able to provide the necessary documentation when requesting independent resources on behalf of their End Users. Phase 2 of the policy implementation began at the end of May 2009. This phase focuses on existing assignments (almost 27,000). In the first step of this phase, the RIPE NCC approached LIRs and asked them to specify whether: - The resources were used for the LIR's network infrastructure - The resources were used by one of the LIR's End Users - The End User was no longer the LIR's customer LIRs must provide documentation for the resources marked as "My End User" by the end of Phase 2. This documentation should be the "End User Assignment Agreement" between the LIR and the End User regarding the registration of the independent Internet resources the End User holds and the official company registration documents of the End User organisation. Initially, Phase 2 was scheduled to end on 31 December 2009. However, due to the lower-than-expected number of documents received, the deadline was first extended until 1 March 2010 and then until 17 May 2010, which will be the final deadline. The figures showing the progress of Phase 2, as of 1 March 2010, are presented below. LIRs Participating ----------------------- Total LIRs to participate in Phase 2: 4,903 Number of LIRs participated at 1 March: 4,178 Percentage of participating LIRs: 85.2% Total Resources Marked ------------------------------ Total amount of resources to be marked in Phase 2: 26,940 Total amount of resources marked at 1 March: 22,958 Percentage of resources marked: 85.2% Status of 22,958 Resources Marked ------------------------------------------ - 5,373 are marked "My Infrastructure" (23.4%) by 3,956 LIRs - 6,025 are marked "Not My End User" (26.25%) by 712 LIRs - 11,560 are marked "My End User" (50.35%) by 996 LIRs Status of 11,560 Resources Marked "My End User" ------------------------------------------------------------- - 4,849 have missing documents (42%) - 4,522 have submitted documents (39%) - 2,189 have approved documents (19%) Regards, Andrew de la Haye

3 2

Clean-up of backlog of unreferenced personal data completed
by Denis Walker 08 Mar '10

08 Mar '10

[Apologies for duplicate emails] Dear Colleagues, The RIPE NCC has now completed the clean-up of the backlog of unreferenced PERSON and ROLE objects in the RIPE Database. The results of this process can be seen on the RIPE Database inconsistency graph for Unreferenced Person/Role Objects: http://www.ripe.net/projects/dbconstat/cons-unrefpero.html Since this process began, almost half a million objects have been deleted. Our Customer Services Department received only a handful of tickets related to these object deletions. The clean-up script will continue to run and keep the RIPE Database clear of unreferenced PERSON and ROLE objects. For details of this process, see: http://www.ripe.net/db/support/unreferenced-personal-data-clean-up.html Users of the RIPE Database should only create these objects containing personal data when there is a need for them. They should not be created until there is an imminent need to reference them. Regards, Denis Walker Business Analyst RIPE NCC Database Group

1 0

2007-01 Policy Implementation - Phase Two Deadline - Final Extension
by Arne Kiessling 25 Feb '10

25 Feb '10

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 2.5 months. LIRs now have until 17 May, 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

Clean-up of unreferenced personal data in RIPE Database
by Denis Walker 23 Feb '10

23 Feb '10

[Apologies for duplicate emails] Dear Colleagues, The RIPE NCC Database Group has restarted the clean-up of unreferenced personal data. This follows the process outlined in the document recently published at: http://www.ripe.net/db/support/unreferenced-personal-data-clean-up.html Regards Denis Walker Business Analyst RIPE NCC Database Group

1 0

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