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

Charges for legacy holders
by Nigel Titley 26 Apr '14

26 Apr '14

Dear colleagues, I'd like to provide some background on the Executive Board's decision to propose the provisions regarding charges for legacy holders in the 2015 Charging Scheme. The board discussed these at length and wanted to achieve a balance between meeting the needs of legacy holders and meeting the needs of RIPE NCC members, who the board is tasked with representing. First of all, the four options in the Charging Scheme regarding legacy space correspond directly to the four options (sections 2.1, 2.2, 2.3 and 2.4) in Policy Proposal 2012-07: http://www.ripe.net/ripe/policies/proposals/2012-07 Option 2.4, according to the proposal, is for those legacy holders who meet the criteria to engage with a sponsoring LIR "but cannot find a Sponsoring LIR with which a mutually satisfactory contract of the kind mentioned in that section". The board sees this option as being for legacy holders who are*unable* to find a sponsoring LIR rather than those who*do not want* to find a sponsoring LIR. The fourth option in the Charging Scheme addresses this need to provide a direct contract for those who cannot find a sponsoring LIR with which to engage. For the RIPE NCC to provide this option, a new category of service provision will have to be established. Aside from the legal and administrative work involved, the RIPE NCC's support, operating and business systems will need to be updated. The board feels that membership should not fully subsidise the cost of this work but that the costs should mainly rest with those for whom the service is being provided. The work involved in bringing legacy holders into the membership requires little work on the RIPE NCC's part by comparison, hence the waiving of the sign-up fee. The board is also keen to keep the Charging Scheme in line with the "one-LIR, one fee" principle accepted by the membership in 2012. By charging the same fee for LIRs and those legacy holders who would like to have a direct contract with the RIPE NCC, the board believes that this does not put the RIPE NCC in a position where it is competing with its members. In 2011, when the RIPE NCC previously charged Direct Assignment Users (DAUs) who wished to have a contract directly with the RIPE NCC rather than a sponsoring LIR, the DAUs were charged the same sign-up fee as members as well as an annual fee of 1,300 euros (the same as an Extra Small LIR at the time). We believe the proposed Charging Scheme 2015 follows this precedent. The board will set aside as much time as is necessary at the upcoming General Meeting to discuss the issue of charging for services to legacy holders. If the membership feels the Charging Scheme 2015 is not acceptable and decides to vote against it, the board will discuss the issue over the Summer and present a new Charging Scheme 2015 at the Autumn GM in London. The 1,600 euro fee for LIRs proposed in the Charging Scheme would remain the same, so members can still budget for the year ahead. On a separate note, the proposed implementation plan for the RIPE Policy "RIPE NCC Services to Legacy Internet resource Holders" deals with the contractual changes necessary for the RIPE NCC to implement new processes and is independent of charging issues. I hope this helps you to understand the board's thinking in proposing the charging scheme. We will continue to follow discussions on the mailing list and look forward to hearing your views at the RIPE NCC Service Working Group and the RIPE NCC General Meeting on 14 May. If you would like to contact the board directly, you can email us at <exec-board(a)ripe.net>. Best regards, Nigel Titley RIPE NCC Executive Board Chairman

3 4

RPKI Certification for PI End Users pre-production launch
by Alex Band 23 Apr '14

23 Apr '14

Hello everyone, We are getting close to the production launch of Resource Certification (RPKI) for Provider Independent End User space. Last week, we started testing with a small number of users to see if the system was behaving as desired. This was a success, and the first certificates and ROAs for PI space have been published using the production system. As there are quite some corner cases with PI space, we’d like to open up the testing group a bit more, so we can make sure we iron out any quirks before we go live. If you’d like to request a certificate and create ROAs for your PI End User address space, please contact me and we’ll guide you through the process. At the moment, you’ll have to take some manual steps. When we launch we’ll have an easy to use wizard available to help you. Kind regards, Alex Band Product Manager RIPE NCC

1 0

Re: [ncc-services-wg] 2012-07's direct engagement option
by Janos Zsako 22 Apr '14

22 Apr '14

Dear Sascha, [I am still investigating why my mailer sent two empty mails to the list. I suspect this is due to some special character in the message I was replying to. I am sorry for the inconvenience.] >> The annual fee is the same, yes, but also in the 2015 charging scheme: "Legacy Internet resource holders that become a member do not have to pay a sign-up fee." So for the audience of 2012-07, becoming a LIR is a flat one-off EUR 2000 cheaper than a separate direct agreement. > > At least it makes the intention clear - the NCC wants to gain control of > these legacy resources I am afraid I do not understand why you think the charging scheme could help the RIPE NCC gain control over legacy resources. To my understanding, all legacy resources would be marked as "legacy" irrespective of the fact that the holder (1) becomes a member, (2) is already a member an extends the contract to cover the legacy resources as well, (3) uses a sponsoring LIR, (4) enters in direct contractual relationship wit the NCC or (5) does not sign any contract at all. The RIPE NCC may not de-register the legacy resources unless asked to do so by the resource holder. Moreover, if the contract (with the member, the sponsoring LIR or DAU) is terminated, the resource is simply flagged "No contract". Best regards, Janos > (whereas the goal of 2012-07, AIUI, is to ensure > a way to keep resources registered, without the holders giving up > control). IMO this implementation negates many of the changes that came > out of the long debate on this proposal... > > rgds, > Sascha Luck

2 2

Implementation plan for 2012-07, "RIPE NCC Services to Legacy Internet Resource Holders"
by Xavier Le Bris 17 Apr '14

17 Apr '14

Dear colleagues, The RIPE NCC has updated the implementation plan for ripe-605 "RIPE NCC Services to Legacy Internet Resource Holders" (accepted policy proposal 2012-07): https://www.ripe.net/lir-services/resource-management/policy-implementation… The implementation that specifically relates to the RIPE Database has been updated in line with these revisions: https://www.ripe.net/lir-services/resource-management/policy-implementation… We have revised this plan so that all AUT-NUM and parent legacy Internet resource holders will be notified of status changes in one batch. These notifications will be sent when the software is deployed to the Resource Candidate (RC) Test Environment. When the software is deployed to production, after RIPE 68, all status values will be generated or set on the same day. Notifying all resource holders in the same, single batch ensures consistency and accuracy across the entries in the RIPE Database. The process of contacting all resource holders in multiple batches would have been a more time-consuming and drawn out process. Please do not hesitate to contact us if you have any questions or feedback. Kind regards, Xavier Le Bris IP Resource Analyst

1 0

Question about AW history in the LIR Portal
by Erik Bais 09 Apr '14

09 Apr '14

Hi, Having seen the email from Alex on Monday in regards to the changes about invalids in the ASUSED report, the question that came to my mind is what the (future) use is for: - Assignment Window (and history) >From what we see, is that the RIPE NCC is currently adjusting the tools (Like the Portal and APIs) for the 2013-03 implementation. I think that is a good thing and I would like to ask here in the group if there are people who require their AW status or history from the past, now that there is no need for justification. For all I care you can assign your complete allocation for 1 customer as long as you document it properly in the database The same probably goes for the list of Assignments Made by RIPE NCC in the Portal the approved assignments outside your AW by the RIPE NCC hostmasters. Obviously it is nice for historic reference .. however .. is it needed ? Is it required for future use ? These could be removed imho and people can document them in the database themselves and it will make the way that we look as assignments within PA space a lot easier I think. Perhaps it is currently still required for audit reasons by the IPRAs ? But if we are getting rid of the invalids .. why not get rid of the AW and RIPE Approved Assignments as well ? Regards, Erik Bais

1 0

Assisted Registry Check - First Results
by Matt Parker 08 Apr '14

08 Apr '14

Dear colleagues, In the final quarter of 2013, the RIPE NCC launched the Assisted Registry Check (ARC) for our members. This enhancement to the RIPE NCC's audit activities was initiated after feedback from members indicated that our earlier audit process could do with some improvement. The initial group of Assisted Registry Checks were concluded in the first quarter of 2014 and the RIPE NCC has carried out an in-depth review of the feedback we received. The results of this review have now been published in the following RIPE Labs article: https://labs.ripe.net/Members/matt_parker/assisted-registry-check-first-res… We have also incorporated this feedback into our procedures for future Assisted Registry Checks, to ensure they remain useful and relevant for our members. If you would like to volunteer for an Assisted Registry Check, please send an email to <lir-help(a)ripe.net> and we will contact you with further details. Kind regards, Matt Parker Registration Services RIPE NCC

1 0

[training] RIPE NCC Webinars - new dates
by Training Services 08 Apr '14

08 Apr '14

Dear colleagues, We are pleased to announce the launch of new dates for our Webinars. The RIPE NCC Webinars are live and take only one hour. You can interact with our trainers without leaving your desk. We focus on the topics and issues most important for LIRs. Register now at https://www.ripe.net/lir-services/training/e-learning/webinars Participation is limited to 20 people, so don't hesitate if you want to take part! If you have questions, please email <training(a)ripe.net>. We look forward to seeing you online. Kind regards, RIPE NCC Training Services

1 0

Call for Agenda Items RIPE68 - RIPE NCC Services WG
by Bijal Sanghani 07 Apr '14

07 Apr '14

Dear NCC-Services WG, RIPE68 is a few weeks away and we are putting the agenda together for the NCC Services WG. This is your opportunity to let the RIPE NCC know what you want from them, if you would like to suggest a topic for discussion or have a presentation you have or would like to see presented please get in touch with the working group chairs at ncc-services-wg-chairs(a)ripe.net. Best regards, Bijal Sanghani RIPE NCC Services WG Co-Chair

1 0

Changes to IP Analyser web interface and API (incl. "asused")
by Alex Band 07 Apr '14

07 Apr '14

Dear colleagues, We are in the process of implementing the policy regarding Post Depletion Adjustment of Procedures (2013-03). One of the services that will be affected is the IP Analyser. This tool provides an overview of all invalid assignments, as described here: https://www.ripe.net/lir-services/resource-management/number-resources/inva… Some elements have become redundant, which means we will be making several changes to the web interface, as well as the API which offers JSON and plain text “asused” style output. If you have any scripts that use this output, please check the following article on RIPE Labs so you can prepare for the upcoming changes: https://labs.ripe.net/Members/AlexBand/modifications-to-the-ip-analyser-to-… We intend to implement these changes on 16 April 2014. Kind regards, Alex Band Product Manager RIPE NCC

1 0

RIPE Database Release 1.72 - including SSO Integration
by Denis Walker 26 Mar '14

26 Mar '14

Dear colleagues, We are pleased to announce RIPE Database release 1.72. For more information about the features, changes and how this release might affect your operations, please see these release notes: https://www.ripe.net/data-tools/db/release-notes/ripe-database-release-1.72 A major feature introduced in this release is the integration of RIPE Database services with RIPE NCC Access. This gives maintainers the option to use their RIPE NCC Access account for authorising updates to the RIPE Database. The first applications that utilise this feature are Webupdates and Syncupdates from a web form. Linking a RIPE NCC Access account to an organisation is a requirement for certifying PI address space. No change has been made to existing authorisation options. This release also fixes a number of issues, so please read the release notes. By fixing certain issues with the JSON output from the REST API, the structure of that output has changed slightly. This should not affect any users as it was broken in the first place. To ensure this is the case, please test your implementation in the Release Candidate environment. More information about the Release Candidate environment is described in this document: https://www.ripe.net/data-tools/db/release-notes/rc-release-candidate-envir… We look forward to hearing any questions or comments you might have. Regards, Denis Walker Business Analyst RIPE NCC Database Team

6 10