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

NOAUTO: IPv4 Exhaustion: PI-IP-addresses for end-user
by Jens Pickardt 25 Sep '12

25 Sep '12

Hello, the allocation of the last /8 was started. Is it right, that end-user don´t get PI-IPv4-addresses ? Concerns this only new PI-IP-end-users or also end-users, who want to extend the existing PI-IP-address-space ? This would be an important information for our customers. Thanks and regards Jens Pickardt _____________________________________________________________________________ teliko GmbH Telekommunikationsgesellschaft In den Fritzenstücker 17 D-65549 Limburg a. d. Lahn Fon +49 6431 73070-40 Fax +49 6431 73070-14 EMail: jens.pickardt(a)teliko.de Internet: www.teliko.de<http://www.teliko.de> ___________________________________________________________________________________ Besuchen Sie uns in der teliko-Lounge auf der Wincor World 2012! Fachmesse & Forum für Banken und Handel - Vom 16.- 18. Oktober 2012 in Rheda-Wiedenbrück ___________________________________________________________________________________ Fragen zu unseren Dienstleistungen? Kostenlose Hotline: 08000-teliko, wählen Sie dazu 08000 835456. Besuchen Sie unsere Webseite <<http://www.teliko.de>> Geschäftsführer: Frank Berkessel, Dipl.-Ing. Sascha Holste, Dipl.-Ing. Klaus Friederitzi; Dipl.-Ing. Klaus-Peter Altmann Vorsitzender des Aufsichtsrats: Werner Dommermuth Gerichtsstand: AG Limburg, HRB 1863 ********************************************************************************************************** DISCLAIMER: Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informa- tionen. Wenn Sie nicht der richtige Empfaenger sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail oder des Inhalts dieser Mail sind nicht gestattet. Ueber das Internet versandte E-Mails koennen leicht verfaelscht oder unter fremdem Namen erstellt werden. Zu Ihrer und unserer Sicherheit schließen wir daher die rechtliche Verbindlichkeit der vorstehenden Erklaerungen aus. DISCLAIMER: This e-mail is confidential and should not be used by anyone who is not the original intended recipient. If you have received this e-mail in error please inform the sender and delete it from your mailbox or any other storage mechanism. Due to the fact that e-mails are prone to manipulation and can be misleading as to the identity of the sender, the foregoing statements and comments shall have no legal validity. This is for your own protection as well as ours. **********************************************************************************************************

3 2

Meet Debbie, the RIPE Database Robot!
by Sandra Bras 24 Sep '12

24 Sep '12

[Apologies for duplicates] Dear colleagues, RIPE NCC E-Learning is pleased to introduce you to Debbie, the RIPE Database Robot. Debbie is your guide through a new series of e-learning videos designed to help you get the most out of the RIPE Database: http://www.ripe.net/lir-services/training/e-learning/ripe-database The RIPE Database e-learning collection has also expanded with the addition of three new videos: - Create More Specifics (Hierarchical Authorisation) - Create IPv4 Assignments - Create IPv6 Assignments There are now eight brief video tutorials (most around three minutes duration) giving step-by-step instructions for users to perform a range of different operations in the RIPE Database. If you have any comments or questions, please send an email to <e-learning(a)ripe.net>. Happy learning! Sandra Bras Trainer / E-Learning Project Manager, RIPE NCC

1 0

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

Questions about the fax the RIPE NCC received from United Against Nuclear Iran (UANI).
by Erik Bais 21 Sep '12

21 Sep '12

Dear all, For those that haven't seen the post by the RIPE NCC on the website ( https://www.ripe.net/internet-coordination/news/ripe-ncc-receives-communicat ion-from-united-against-nuclear-iran-uani ) If it wasn't written so seriously and someone would have told me this over a beer, I would actually have laughed and thought it was a joke. However as I read this not so funny letter from a former political diplomat, I probably missed the point when the RIPE GM meeting has become the location for political lobbyist to do their work and try to influence connectivity on the internet. I mean .. If the plan is to revoke all Iranian IP addresses, how would $Goverment get the next Stux malware updated to attack said plants. So, all jokes aside, what is the reply that is provided to the writer and if he would show up at the RIPE meeting, will he be provided any room to discuss the topic and will the request for a resolution be discussed during the GM meeting? Kind regards, Erik Bais

11 17

RIPE NCC Tools and Technical Talks at RIPE 65
by Mirjam Kuehne 20 Sep '12

20 Sep '12

[apologies for duplicates] Dear colleagues, We have published a schedule on RIPE Labs that lists various RIPE NCC presentations during the upcoming RIPE 65 meeting: https://labs.ripe.net/Members/becha/live-at-ripe65 Note that this is not a complete schedule and does not show all the regular RIPE Meeting reports. We have published this to make it easier for you to identify presentations and BoFs related to specific tools and technical projects provided by the RIPE NCC. Kind regards, Mirjam Kuehne RIPE NCC

1 0

LIR Portal APIs to simplify your IP Address Management
by Alex Band 20 Sep '12

20 Sep '12

Dear colleagues, Over the last couple of months we have been working on the IP Analyser in the LIR Portal. The application is currently still in beta, but it is proving to be very popular with over 20,000 page views since the launch. This week we have released an update to the API for the IP Analyser, in order to help you simply your local IP address management. It means the following is now available: The My Resources API: Access all registry information about your resources in JSON or XML format, including ASNs, IPv4 and IPv6 allocations, Assignment Window history, PI assignments, Legacy space, etc. The IP Analyser API: Access all information about your IPv4 assignments, available free space and invalid assignments that require your attention, in JSON or plain text format. The plain text output uses the same formatting as the asused tool, that many of you are familiar with. It also means that you no longer need to contact NCC Registration Services if you would like to have an overview of your invalid assignments. Before we make this a production service, we would really appreciate your input on this functionality; especially on the new JSON format for the IP Analyser. If there is anything missing or you would like to have changed, we can take it along in our planning and roadmap. There is also an opportunity to provide feedback in the NCC Services WG session at RIPE 65. Over the next couple of weeks, we will be expanding the IP Analyser UI, and add more IPv6 information. You can find the documentation for these, and all other APIs we offer at http://ripe.net/developers Looking forward to your feedback! Kind regards, Alex Band Product Manager RIPE NCC

1 0

New Resource Certification (RPKI) Management Interface
by Alex Band 19 Sep '12

19 Sep '12

Dear colleagues, The RIPE NCC is continuing to improve and enhance the Resource Certification (RPKI) service that was launched in 2011 in order to make our registry more robust and BGP routing more secure. As announced at RIPE 64, the main focus of our activities has been on security, resilience and operator autonomy. Most of this work has been at the back end, so users will not have noticed any visible changes in the system for quite some time. Today, I am proud to announce a major improvement to the service that can be experienced by all members: the new Resource Certification Management Interface. The standard for usability was set by the RIPE NCC RPKI Validator toolset, and the bar has been raised by this new LIR Portal interface to manage Route Origin Authorisations (ROAs). It sets a new standard in the services we offer to our members and the community, with an extreme focus on quality and user friendliness. The main driver for this has been the community wish for a high quality RPKI dataset, so operators can base reliable routing decisions on it. In order to achieve this, we have added some remarkable features: - There is a product tour to guide new users through the basic concepts of RPKI and BGP Origin Validation - The system can suggest ROAs to users, helping them to authorise legitimate BGP announcements - We offer a fine-grained, highly configurable alerting system, notifying users of BGP hijacks and configuration errors If you are a RIPE NCC member, please try out the new Resource Certification (RPKI) system and authorise all legitimate BGP announcements with your address space by creating ROAs for them. It is available at: https://certification.ripe.net (requires LIR Portal login) To use BGP Origin Validation in your routing workflow, please use the RIPE NCC RPKI Validator toolset. It is compatible with all Cisco and Juniper platforms that offer support for BGP Origin Validation. Learn more at: https://ripe.net/certification/validation Kind regards, Alex Band Product Manager RIPE NCC

1 0

Re: [ncc-services-wg] 2012-07 New Policy Proposal (RIPE NCC Services to Legacy Internet Resource Holders)
by Nick Hilliard 17 Sep '12

17 Sep '12

On 11/09/2012 13:20, Emilio Madaio wrote: > A new RIPE Policy Proposal has been made and is now available for > discussion. > > > You can find the full proposal at: > > https://www.ripe.net/ripe/policies/proposals/2012-07 Unless I'm mistaken, this is an almost verbatim copy of what Niall posted to this list on Aug 22 18:28:48. Some way down that discussion, Niall noted: > Background work on a new version of the policy proposal > has begun. It is premature for me to say more at this stage. So, given that it appears that the proposers of this policy are interested in a new version, is it appropriate for people to comment on this version? Perhaps a rep of one of the policy proposers could clarify this? thanks, Nick

8 16

RIPE NCC Begins to Allocate IPv4 Address Space From the Last /8
by Axel Pawlik 14 Sep '12

14 Sep '12

Dear colleagues, On Friday, 14 September 2012, the RIPE NCC, the Regional Internet Registry (RIR) for Europe, the Middle East and parts of Central Asia, distributed the last blocks of IPv4 address space from the available pool. This means that we are now distributing IPv4 address space to Local Internet Registries (LIRs) from the last /8 according to section 5.6 of "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region". This section states that an LIR may receive one /22 allocation (1,024 IPv4 addresses), even if they can justify a larger allocation. This /22 allocation will only be made to LIRs if they have already received an IPv6 allocation from an upstream LIR or the RIPE NCC. No new IPv4 Provider Independent (PI) space will be assigned. This policy can be found online at: https://www.ripe.net/ripe/docs/ripe-553 Those members with open requests for IPv4 address space will shortly receive an email regarding the status of their requests. It is now imperative that all stakeholders deploy IPv6 on their networks to ensure the continuity of their online operations and the future growth of the Internet. Regards, Axel Pawlik Managing Director RIPE NCC More Information ----------------- For more information on IPv6 and its deployment, advice from experts and where to get training, please see: http://www.ipv6actnow.org/ For more information on reaching the last /8, please see: https://www.ripe.net/internet-coordination/ipv4-exhaustion

1 0

New on RIPE Labs: Registration History for Members - A Demo
by Mirjam Kuehne 13 Sep '12

13 Sep '12

[apologies for duplicates] Dear colleagues, Please see a new article on RIPE Labs describing a way to look at registration history in RIPEstat. This is a first demo and is only available to members: https://labs.ripe.net/Members/dfk/registration-history-for-members-a-demo Please note the request for feedback at the end of the article. Kind regards, Mirjam Kuehne RIPE NCC

2 1