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

RIPE Document Published - ripe-555, Address Space Managed by the RIPE NCC
by Andrea Cima 20 Jul '12

20 Jul '12

Dear colleagues, The RIPE Document ripe-555, "Address Space Managed by the RIPE NCC", has been published. The document is available at: https://www.ripe.net/ripe/docs/ripe-555/ This RIPE Document updates ripe-510 and now points to the extended delegated statistics containing the full list of resources that the RIPE NCC manages. The document also reflects the fact that the RIPE NCC needs to be able to issue blocks of any size from any /8, so the document was updated accordingly. Best regards, Andrea Cima Registration Services Manager RIPE NCC

4 6

Transfer of Internet Number Resource Records and Change of a Member’s Official Legal Name - Draft Document
by Axel Pawlik 16 Jul '12

16 Jul '12

Dear colleagues, The RIPE NCC has created a draft procedural document, “Transfer of Internet Number Resource Records and Change of a Member’s Official Legal Name”. A PDF of the document is available at: http://www.ripe.net/lir-services/ncc/legal/Transferofrecords_namechange.v20… The draft document refers to the current procedures the RIPE NCC follows in order to maintain an accurate registry in the case of changes regarding: - The Internet number resource records that are registered to a person; or - The official name of the person holding a registration of Internet number resources The procedures were originally discussed at the RIPE 62 Meeting in Amsterdam. The text of this document is intended to replace relevant sections of ripe-515, “Mergers, Acquisitions, Takeovers and Closures of Organisations Operating an LIR”. The original RIPE Document is available at: https://www.ripe.net/ripe/docs/ripe-515 The RIPE NCC would like to receive feedback on this draft document from its members and the RIPE community. Based on this feedback, the RIPE NCC Executive Board will decide on a final version of the document. If you would like to give feedback on the document, please email the RIPE NCC Services Working Group mailing list at <ncc-services-wg(a)ripe.net>. Kind regards, Axel Pawlik Managing Director RIPE NCC

1 0

Using API Keys To Access (Private) LIR Portal Data Locally
by Alex Band 12 Jul '12

12 Jul '12

Dear colleagues, There have been many requests from the membership to provide a way to access private LIR data that is not locked into the LIR Portal web interface. This is especially relevant for larger LIRs who have to manage a large amount of IP address space. In order to offer our members better local access to our tools and data sets, it is now possible to create API access keys in the LIR Portal. The keys can be used to grant applications and scripts access to your (private) LIR data. The information will be fetched securely over HTTPS and can be used in your IP address management tools, for example. You can read more about it in this article on RIPE Labs: https://labs.ripe.net/Members/AlexBand/lir-portal-api-keys We hope you appreciate this functionality and look forward to your feedback. Kind regards, Alex Band Product Manager RIPE NCC

1 0

Short update on TTM service
by Vesna Manojlovic 05 Jul '12

05 Jul '12

Dear colleagues, We received a lot of feedback from the community after we announced our proposal to discontinue TTM at RIPE 64. After reviewing the RIPE community's feedback and reevaluating our own planning, we are pleased to announce that we will continue supporting TTM until sometime in 2013. As presented during the MAT Working Group and RIPE NCC Services Working Group sessions at RIPE 64, we plan to implement RIPE Atlas Anchors and to migrate DNSMON functionality to RIPE Atlas. We will do this in parallel to the current TTM infrastructure in order to give the RIPE community enough time to build confidence in and test the new infrastructure. We will give you more details about transition in early September and look forward to discussing our proposed plans with you at RIPE 65 in Amsterdam. If you are a TTM host you have received a more detailed version of this email, if this is not the case then please contact with me and I would be more than happy to provide further information for you. I wish you relaxed summer holidays. Kind regards, Vesna -- Vesna Manojlovic BECHA(a)ripe.net Senior Community Builder +31205354444 for Measurement Tools RIPE NCC http://ripe.net

2 1

Database Updates service recovery
by Kaveh Ranjbar 30 Jun '12

30 Jun '12

Dear Colleagues, The issues with our RIPE Database update services is resolved. All mail sent during the downtime is now processed and sync updates, web updates and API updates are back to normal. If you experience any problems, please contact ripe-dbm(a)ripe.net. The update service was down between 07:58 CET (05:58 UTC) until 9:55 CET (07:55 UTC) due to hardware issues. Further details on this issue will be posted to RIPE Database Working Group mailing list at db-wg(a)ripe.net. Kind Regards, Kaveh Ranjbar RIPE NCC Database Group Manager

1 0

Database Updates service disruptions
by Kaveh Ranjbar 30 Jun '12

30 Jun '12

Dear Colleagues, RIPE Database sync updates, web-updates and API updates are not responding at the moment. We are dealing with hardware problems on the machines used for the database update cluster. The service was affected from from 07:58 CET (05:58 UTC) and we are working to recover it as soon as possible. Queries will keep working and updates via emails are queued and will be processed as soon as the service is up. We will send an update message as soon as the service is up or when we have an estimate on how long it takes to fix the problem. Kind Regards, Kaveh Ranjbar RIPE NCC Database Group Manager

1 0

Draft Minutes RIPE NCC Services WG - RIPE 64
by Bijal Sanghani 27 Jun '12

27 Jun '12

Greetings, The draft minutes from the NCC Services Working Group at RIPE 64 are now online - https://www.ripe.net/ripe/groups/wg/services/minutes/ripe-64 Please send any questions, comments or clarifications to Kurtis, myself or the mailing list. regards, Bijal

1 0

Fwd: Re: Extended delegated statistics
by Hank Nussbacher 01 Jun '12

01 Jun '12

>Date: Thu, 24 May 2012 08:47:17 +0300 >To: Tore Anderson <tore.anderson(a)redpill-linpro.com>, Alex Le Heux ><alexlh(a)ripe.net> >From: Hank Nussbacher <hank(a)efes.iucc.ac.il> >Subject: Re: [ncc-services-wg] Extended delegated statistics >Cc: ncc-services-wg(a)ripe.net > >At 07:24 24/05/2012 +0200, Tore Anderson wrote: >>* Alex Le Heux >> >> > Starting from Wednesday 23 May 2012, the extended delegated files will >> > be published at the following URL: >> > >> > ftp://ftp.ripe.net/pub/stats/ripencc >> >>Hello, >> >>There are some problems with the delegated-ripencc-20120423 and >>delegated-ripencc-extended-20120423 currently available on the FTP: > >Another problem is that the previous file was sorted by IP and now it is >sorted by allocated/assigned field and then only by IP so one needs to >know whether the IP block is allocated or assigned and jumping back and >forth between the 2 sections. Can the file be sorted once gain by IP? > >Thanks, >Hank I see that the file is still sorted by allocated/assigned and then by IP. Why was this changed and why can't it be changed back to the way it was? -Hank

2 1

Legacy resources: some idea of what will be in the policy proposal
by Niall O'Reilly 31 May '12

31 May '12

The transcript of the RIPE NCC Services WG session at RIPE 64 (https://ripe64.ripe.net/archives/steno/16/) records the following exchange: > AUDIENCE SPEAKER: Nigel Titley, Chairman of the board of the RIPE NCC. Just a very quick note. The charging scheme task force has delivered its report. The board is due to consider that report starting in June of this year. Could I urge you to at least give us some idea of what your policy might say fairly early on so that we can consider that? > > NIALL O'REILLY: Noted. The group of us working on drafting a policy proposal have identified most of the key elements which will be included, but a presentable proposal won't be ready without some more work. In order not to miss the opportunity which Nigel kindly took care to point out, here is "some idea of what [the] policy [proposal] might say". I expect that the main elements of the forthcoming policy proposal will include the following. Current inaccuracies in the RIPE database should be corrected without additional formality, and specifically without forcing a contractual relationship. Each legacy resource holder should have the choice of registering holdings either directly as a "small" member or indirectly as a customer of a sponsoring LIR. We understand that this matches current NCC thinking. Clarity is needed as to which RIR policies will apply to legacy resources. It is not sufficient to declare these resources subject to "all" policies, as the RIR may not have authority to apply certain policies in respect of legacy resources. It will be necessary to itemize which policies are applicable. Whenever an "obvious" potential sponsoring LIR can be identified, the NCC should request this LIR to make contact with the resource holder rather than do so directly. Such cases might be identified either from existing RIPE DB records or from current routing information. There is specific concern in the NREN community that NCC members' relationships with their customers be respected in this way. We gave more detailed attention to the question of charging, as we understand that this is a current priority of the RIPE NCC Board. We are aware of two current documents relating to charging: one, the report of the Charging Scheme Task Force (CSTF); the other, a limited-circulation document co-authored by a group for which Daniel Karrenberg has been acting as editor. The latter document may perhaps be most conveniently described as a memorandum for the Board, giving an example of how the recommendations of the CSTF might concretely be implemented. We welcome the specific attention given in this "Karrenberg document" to the situation of legacy resource holders, and particularly the idea of encouraging engagement of legacy resource holders by waiving the sign-up fee. We also appreciate the suggestion made at the TERENA conference in Reykjavík recently by Mirjam Kühne, representing the RIPE NCC, that fees would not be charged in respect of legacy resources. Some clarification as to the conditions attached to this offer, including an indication of how long it will continue, would be helpful. Although it is certain to be superseded, we have used RIPE-499, which documents the 2011 charging scheme, as the starting point for indicating how we feel that legacy resources should be assessed in case a resource accounting assessment model is to be used in the new charging scheme. We propose that legacy address blocks are assessed with a score of one eighth of the score assessed for a PA block of equal size. We also suggest a modification to the "Karrenberg document" so that a sponsoring LIR will not be inhibited from accommodating legacy resource holders by concern over a possible change of charging band. Attached are modified versions of Appendix 1 of RIPE-499 and of Appendix F of the "Karrenberg document" which make these suggestions explicit. Best regards, Niall O'Reilly

1 0

Extended delegated statistics
by Alex Le Heux 25 May '12

25 May '12

Dear Colleagues, Since 2003, the RIPE NCC and the other RIRs have published daily files detailing all assigned and allocated IP resources. These are also known as the "delegated files" In 2011, a RIPE Labs article was published describing an extension to these files. This article is available at: https://labs.ripe.net/Members/mirjam/new-ripe-ncc-address-statistics-reports Starting from Wednesday 23 May 2012, the extended delegated files will be published at the following URL: ftp://ftp.ripe.net/pub/stats/ripencc The extended delegated files will list all resources managed by the RIPE NCC, including those which make up part of the free pool. The resources will be listed like this: ripencc||ipv4|5.22.224.0|73728||available We have overhauled the code that generates the regular delegated files. One area which has been improved is the accuracy of the country code attribute for all entries, especially for direct assignments such as PI and AS Numbers. For all resources the country code was lifted from the RIPE Database object describing the resource. This was done as a one-time import and stored in our internal records. This has resulted in a massive decrease in the occurrence of the catch-all country code "EU" in both the regular and extended delegated files. However, it is still possible that there are inaccuracies with regards to the country code for some entries. Please contact lir-help(a)ripe.net in such cases. Regards, Alex Le Heux Policy Implementation & Coordination RIPE NCC

3 7