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

New RIPE NCC Procedural Document Available
by Andrea Cima 28 Feb '11

28 Feb '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [Apologies for duplicate emails] Dear Colleagues, The RIPE NCC has published a new RIPE NCC procedural document: ripe-475, "Independent Internet Number Resources – Contractual Relationship Changes between sponsoring LIR and End User" This document describes the steps to be taken when there are changes in the contractual relationship between the End User of independent Internet number resources and the sponsoring Local Internet Registry (LIR). It also describes the scenarios in which the RIPE NCC may de-register independent Internet number resources and what happens to those resources once they are de-registered. The new document is available at: http://www.ripe.net/ripe/docs/ripe-475.html Kind regards, Andrea Cima RIPE NCC -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkpfPukACgkQXOgsmPkFrjNlEwCcDtE364DhQCU0USBoK3kJhord yBgAoMbRsLFCStkXfvEaV6Mtm5b2sfxW =fKC3 -----END PGP SIGNATURE-----

8 11

RIPE NCC Membership Statistics published on RIPE Labs
by Mirjam Kuehne 17 Feb '11

17 Feb '11

[apologies for duplicates] Dear colleagues, With the year 2009 behind us, we looked at RIPE NCC membership growth and demographics over time. You can find some interesting statistics on RIPE Labs: http://labs.ripe.net/content/ripe-ncc-membership-growth Next we will look at the distribution of number resources among the membership. Stay tuned! Kind Regards, Mirjam Kuehne

1 1

Independent Resource procedure and implementation
by Daniel Suchy 28 Oct '10

28 Oct '10

Hello, I would like to open discussion related to "Action Required: Contractual Relationship for Independent Resource Assignments" emails, that almost all LIRs received from RIPE NCC in the past. I have some notes from perspective of small LIR (or from perspective of person helping running multiple small LIRs). My first note points to system in general. Although RIPE NCC has many required informations in own existing databases already, it requires additional action from LIR in general. Typical small LIR has one or more PA allocations and exactly _one_ autonomous system registered. In RIPE database, there are records matching allocated PA prefix and ASN (route objects with proper origin AS and related inetnum objects, many ASNs has paired LIRs org: in aut-num object). In addition, RIS service (with history!) can be used for verification of these informations obtained automatically from database. For incomprehensible reason, RIPE NCC doesn't use these informations at all and instead of this abuses ALL LIRs with submiting simple form with exactly one record within it. I thing RIPE RCC has enough resources (financial and human) to do that automatically. My second note points to implementation of this new tool. I discovered, that I'm not able to "new" tool used for confirmation. I'm using PKI login feature and I have one identity paired with more LIRs. Although I'm able login to the LIR portal and modify everything I need with my certificate, I'm _NOT_ able to update informations on "Independent Resources" page. The main reason is, that RIPE NCC created new and separated (!) tool instead of simple integration of new feature/functionality to existing LIR portal. So, instead of reusing existing code used for LIR portal authentication, new outside code was developed for this new tool. And this new code doesn't implement all authentication features from LIR portal. In my point of view, this is quite unprofessional approach of modern application development. Aplications should be multi-layer, allowing easy new feature implementation. I reported this issue to RIPE NCC on friday last week, but first "answer" I received yesterday from RIPE NCC was initiation of audit in one LIR. Just fortuitous event? I don't believe. I have no problems with audit itself, I have all records, but this takes some additional time (and of course, money). Just because I claimed some problems to RIPE NCC staff due to problematic internal _implementation_ of new policy. Ok, I would like to open public discussions about this problem. There are some questions to answer and discuss: * why RIPE NCC just doesn't use informations from RIPE database in case of their availability and verifiability, why abuses small LIRs instead * why aren't RIS data used for automatic obtaining of requested informations, where this can be applicable * why RIPE NCC didn't integrate "confirmation" tool to existing LIR portal and why new outside application with _limited_ functionality was developed instead of reusing of existing code and functionality * what architecture is used for LIR portal in general, can be there easily implemented new features Of course, I understand, that there are large LIRs and some historic mess, where this action may be required due to lack of records in existing databases. But, I think this is NOT a case of LIRs started in past couple of years, where all required data should be available. With regards, Daniel

13 28

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