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

RIPE NCC Webinars - new dates
by Training Mailbox 08 Oct '12

08 Oct '12

[Apologies for duplicate emails] Dear colleagues, We're pleased to announce that we've added new RIPE NCC Webinar dates for RIPE NCC members. The RIPE NCC Webinars are live, one-hour online training courses that allow participants to interact with our trainers without leaving their desks. We focus on the topics and issues most important to RIPE NCC members. 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 <e-learning(a)ripe.net>. We look forward to seeing you online. Kind regards, RIPE NCC Training Services

1 1

Destruction of trust
by Havard Eidnes 21 Sep '12

21 Sep '12

Hi, as you may be aware, the RIPE NCC is currently engaged in an activity to establish contact with legacy address space holders, and among other things to set up a contractual relationship between the RIPE NCC and the legacy resource holders. However, it is my opinion that the current RIPE NCC actions with legacy resource holders is destroying some of the valuable trust they have built in the community over the years. It has been said that "the RIPE NCC does what the members tell them to do". That does however not appear to be the case for this action, where the RIPE NCC appears to act in a policy-free zone, simply on executive decision. Despite the RIPE NCCs knowledge that work is ongoing to formulate a policy for this area, they are barging ahead, possibly in an attempt to establish a fait accompli. The message sent to the legacy resource holders does not mention the option which would probably be most preferable to at least most of our customers, namely registering the resources via the LIR at their service provider. One could suspect the RIPE NCC has self-interest in driving up the number of LIRs, to increase the number of paying customers of the RIPE NCC. Some of the documents about the approach with legacy resource holders has mentioned a "stick and carrot" approach. I'll claim that the stick is needlessly sharp and the carrot reeks of decomposition. Explanation: * The stick is primarily the "we cannot guarantee in-addr.arpa name service". Without it, a user will in practice be unable to operate mail servers within the affected address space, which would be a severe blow to those who still actively use their address space. The freezing of the registry data is an inconvenience which will ensure that the accuracy of the data whittles over time, an action initiated by the RIPE NCC no less... Many legacy resource holders have not updated their records in a long time already (many didn't have an actual need to do so), so while inconvenient, it's not as strong a stick as the threat of removal of the in-addr.arpa delegation. It should however be noted that the whittling of the registration data over time also is detrimental for the RIPE community at large, not only for the address space holder. * What's the carrot? Only the removal of the stick from above? What makes the carrot particularly rotten is several things: * The open-ended and unliateral application of "all relevant RIPE NCC policies and procedures". The fear would be "we will mire you or your LIR (or both) down in pointless address policy work to document ancient history, and have the RIPE NCC verify (or deny, as the case may be) all assignments done over time" (applicable where address space has been used in PA-fashion). ...or for PI-style assignments, the assignment itself might be challenged. * The highly uncertain status of the charging scheme in the longer term for the legacy resource holders, where the initial proposal to modify today's model had, with no discussion, abolished the "age based discount", and where current discussion is rampant with "payment per IP address" schemes. The fear is that the RIPE NCC will gouge the legacy resource holders either directly or indirectly, "motivating" them to hand back the resource. * The lack of recognition that these addresses were assigned under a different policy. Anecdotal evidence suggests that at one time you would be handed a class-B instead of 4 class-Cs because there was fear of growth of the routing table. Does the RIPE NCC now want to challenge the assignments? In sum, this makes the RIPE NCC appear more as an extorting bully rather than an agent who has the accuracy of the address register as its foremost priority, and this destroys some of the valuable trust they have built in the community over the years. Regards, - Håvard

23 96

RIPE NCC Training Courses April-June 2012 - IL, BE, IS, PL, RU, FI, NL, DE, ES, HR
by Training Mailbox 23 Aug '12

23 Aug '12

Dear Colleagues, Our training team travels the RIPE NCC service region to deliver training courses to our members without any additional cost. Over the next few months, we'll be in Tel Aviv, Brussels, Reykjavik, Belfast, Gdansk, Yekaterinburg, Helsinki, Amsterdam, Munich, Seville and Croatia. Visit the following page to register and to check which training courses we are giving in your area: https://lirportal.ripe.net/training/courses The RIPE NCC delivers the following training courses: - LIR Training Course - IPv6 for LIRs Training Course - Routing Registry Training Course For more information visit: http://www.ripe.net/lir-services/training/courses With kind regards, Rumy Spratley-Kanis Training Services Manager

1 2

Classification of services as member-only, public, or something else
by Shane Kerr 30 Jul '12

30 Jul '12

All, This announcement appeared on the IPv6 working group mailing list a few weeks back: -------------------------------------------------------------------- Date: Tue, 17 Jul 2012 14:28:37 +0200 As announced in earlier, it is possible for RIPE NCC members to do IPv6-traceroutes from all RIPE Atlas probes to IPv6 destinations. In this new article on RIPE Labs we present a first experimental analysis and a prototype visualisation of the traceroute results: https://labs.ripe.net/Members/emileaben/visualise-your-ipv6-connectivity-us… -------------------------------------------------------------------- I'm interested in IPv6, but have no way to access this service since I do not work for an LIR. (To be fair, I might be able to get access by talking to the correct people at the RIPE NCC, but in general this is a closed service.) In the past, I felt like RIPE NCC services tended to be public, unless they were naturally member-oriented. However with this service, I don't see any particular connection with members... except for the fact that they pay for it of course! (An additional minor detail here is that the information comes from RIPE Atlas probes, which do not only sit in LIR networks.) What do other participants in the NCC services working group think about the RIPE NCC providing member-only services? Should there be guidelines about this, or is this something that the RIPE NCC and their members should decide on a case-by-case basis? Cheers, -- Shane

2 1

Due Diligence for the Quality of the RIPE NCC Registration Data
by Axel Pawlik 23 Jul '12

23 Jul '12

[Apologies for duplicate emails] Dear colleagues, The RIPE NCC procedural document, "Due Diligence for the Quality of the RIPE NCC Registration Data", has been published. The document is available at: https://www.ripe.net/ripe/docs/due-diligence The RIPE NCC has a mandate from the RIPE community to keep an up-to-date and correct Internet number resource registry. In order to comply with this mandate, the RIPE NCC performs due diligence on organisations the RIPE NCC registers Internet number resource for. This document outlines the minimum information and documentation the RIPE NCC requires to make sure that the registration data is valid and up-to-date. Regards, Axel Pawlik Managing Director RIPE NCC

1 0

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