- ncc-announce - mailman.ripe.net

[meeting] RIPE 72 Opening Today
by Martina De Mas 23 May '16

23 May '16

Dear colleagues, RIPE Chair Hans Petter Holen will open the RIPE 72 Meeting in Copenhagen today at 14:00 local time (UTC +2). If you cannot be at RIPE 72 in person, you can follow the meeting and participate remotely by viewing the live webcast and using the chat facilities here: https://ripe72.ripe.net/attend/about-remote-participation To stay up-to-date with all RIPE Meeting updates, follow us on Twitter: @ripemeeting, #ripe72 Kind regards, Martina -- Martina de Mas Conference Coordinator RIPE Network Coordination Centre Singel 258, 1016 AB Amsterdam, The Netherlands T: +31 20 535 4444 www.ripe.net

1 0

[news] RIPE Policy Proposals - May Update
by Marco Schmidt 19 May '16

19 May '16

Dear colleagues, Here is our monthly overview of open policy proposals and their stage in the RIPE Policy Development Process (PDP). If you wish to join the discussion about a particular proposal, please do so on the relevant working group mailing list. Proposals Open for Discussion: NEW: 2016-02, "Resource Authentication Key ( RAK ) code for third party authentication" NEW: 2016-03, "Locking Down the Final /8 Policy" Proposals Awaiting Input: 2015-05, "Revision of Last /8 Allocation Criteria" 2015-04, "RIPE Resource Transfer Policies" 2016-01, "Include Legacy Internet Resource Holders in the Abuse-c Policy" Proposal Overviews: NEW PROPOSAL: 2016-02, "Resource Authentication Key ( RAK ) code for third party authentication" OVERVIEW: Aims to allow all number resources, in exacts and more specifics, to be authenticated via an API-key that expires on a certain date. STATUS: Discussion Phase WHERE TO COMMENT: RIPE NCC Services Working Group: ncc-services-wg(a)ripe.net DEADLINE: 31 May 2016 FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2016-02 NEW PROPOSAL: 2016-03, "Locking Down the Final /8 Policy" OVERVIEW: Aims to limit IPv4 from the remaining address pool to one /22 per LIR (regardless of how they were received). These allocations will receive a separate status with several restrictions, including that the address space will not be transferrable. STATUS: Discussion Phase WHERE TO COMMENT: Address Policy Working Group: address-policy-wg(a)ripe.net DEADLINE: 15 June 2016 FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2016-03 ===== The following proposals are awaiting input before they can go any further in the PDP. PROPOSAL: 2015-04, "RIPE Resource Transfer Policies" OVERVIEW: Aims to create a single transfer policy with all relevant information on the transfer of Internet number resources, replacing text in several RIPE Policies. The proposal also introduces a 24-month holding period for IPv4 addresses and 16-bit ASNs after any change of holdership. RIPE NCC IMPACT ANALYSIS: Describes how the 24-month holding period for scarce resources will be applied. STATUS: Review Phase – Awaiting decision from working group chair FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2015-04 PROPOSAL: 2015-05, "Revision of Last /8 Allocation Criteria" OVERVIEW: Aims to allow LIRs to request an additional /22 IPv4 allocation from the RIPE NCC every 18 months. The latest version of the proposal introduces several requirements, such as that the LIR cannot hold more than a /20 of IPv4, must document their IPv6 deployment, and must not have transferred any IPv4 address space before. STATUS: Discussion Phase – Awaiting decision from proposer FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2015-05 PROPOSAL: 2016-01, "Include Legacy Internet Resource Holders in the Abuse-c Policy" OVERVIEW: Aims for a mandatory abuse contact for Legacy Internet Resource holders in the RIPE Database. STATUS: Discussion Phase – Awaiting decision from proposer FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2016-01 The RIPE NCC provides an overview of current RIPE Policy Proposals on www.ripe.net: https://www.ripe.net/participate/policies/current-proposals/current-policy-… During the upcoming RIPE Meeting, the Address Policy Working Group will hold two sessions where ongoing and possible future policy proposals will be discussed. If you can not attend the RIPE Meeting in person, we invite you to join remotely. A live webcast and IRC chat facility will be available for remote participation. The two sessions will begin on 25 May at 7:00 and 9:00 (UTC). The remote participation will be available at: https://ripe72.ripe.net/ We look forward to your involvement in the PDP. Kind regards, Marco Schmidt RIPE Policy Development Officer RIPE NCC

1 0

[news] Improving the Management of RIPE Database Objects with Joint Responsibility
by Alex Band 18 May '16

18 May '16

Dear colleagues, As announced to the RIPE NCC Services Working Group on 22 April, we have been working on simplifying information management in the RIPE Database. Some objects in the RIPE Database have joint responsibility: allocations for IP resources and the ORGANISATION object. The result is that some attributes can only be changed by the RIPE NCC, and others could only be changed through the so-called LIR Portal Object Editors. Today we have deployed business rules in the RIPE Database to determine which attributes you can change and which ones can only be changed by the RIPE NCC. In addition, we have made improvements to the LIR Portal, making the Object Editors obsolete. What this means for you: 1. In the LIR Portal, users will have to go through a one-time operation of selecting a "default" maintainer, which is placed on all existing and new objects that have joint responsibility 2. Changes such as selecting another technical or administrative contact for an allocation for IP resources should be done in the RIPE Database from now on Please note that it is not required to take action immediately. It is only when you want to change information in one of your allocations for IP resources and the ORGANISATION object that you will first have to select the "default" maintainer on this page: https://my.ripe.net/#/account-details You can read more on this functionality in this article on RIPE Labs: https://labs.ripe.net/Members/AlexBand/improving-the-management-of-ripe-dat… Kind regards, Alex Band Product Manager RIPE NCC

1 0

[meeting] Plan Your RIPE 72
by Martina De Mas 16 May '16

16 May '16

Dear colleagues, RIPE 72 is just a few weeks away. If you haven’t yet registered, follow this link to secure your place: https://ripe72.ripe.net/register ------------------------ Check out the Programme! ------------------------ RIPE 72 Plenary agenda: https://ripe72.ripe.net/programme/meeting-plan/plenary/ Monday morning tutorials: https://ripe72.ripe.net/programme/meeting-plan/tutorials/ BoFs: https://ripe72.ripe.net/programme/meeting-plan/bof/ ------- Socials ------- RIPE Meetings are famed for their socials. Here’s what we have planned in Copenhagen: https://ripe72.ripe.net/programme/social-events/ ------------ Social Media ------------ Stay up-to-date via Twitter: @ripemeeting, #ripe72 Or via Facebook: https://www.facebook.com/ripemeetings See you in Copenhagen! Best regards, Martina -- Martina de Mas Conference Coordinator RIPE Network Coordination Centre Singel 258, 1016 AB Amsterdam, The Netherlands T: +31 20 535 4444 www.ripe.net

1 0

[GM] Confirmed Candidates for RIPE NCC Executive Board Election
by Axel Pawlik 09 May '16

09 May '16

Dear colleagues, The deadline for making nominations for the RIPE NCC Executive Board election has passed. There are four confirmed candidates: - Mohammadreza Karimi Badrabadi - Piery Garot - Remco van Mook - Nigel Titley The election is to fill two seats and will take place at the RIPE NCC General Meeting (GM), and the voting period for electronic voters will remain open from 25-27 May 2016. The submitted candidate biographies are posted at: https://www.ripe.net/participate/meetings/gm/meetings/may-2016/candidate-bi… The agenda for the meeting also contains the four resolutions that the membership will be asked to vote on at the GM: https://www.ripe.net/participate/meetings/gm/meetings/may-2016/agenda The RIPE NCC Executive Board strongly encourages all RIPE NCC members to register for the GM and exercise their voting rights. Over 700 RIPE NCC members are currently registered to vote at the GM, and we hope to see this number increase before the meeting takes place. You can register directly by clicking the GM Preferences link in the My LIR section in the LIR Portal: https://www.ripe.net/s/gm-registration-may-2016 All information about the meeting, including the supporting documentation and information on how to participate, is available from the GM pages: https://www.ripe.net/participate/meetings/gm/meetings/may-2016 If you have any questions about the GM or you have problems with registration, please contact <agm(a)ripe.net>. We look forward to your participation in this important meeting for the RIPE NCC membership. Kind regards, Axel Pawlik Managing Director RIPE NCC

1 0

[news] RIPE Policy Proposals - April Update
by Marco Schmidt 29 Apr '16

29 Apr '16

Dear colleagues, Here is our monthly overview of open policy proposals and their stage in the RIPE Policy Development Process (PDP). If you wish to join the discussion about a particular proposal, please do so on the relevant working group mailing list. Proposals Open for Discussion: 2015-05, "Revision of Last /8 Allocation Criteria" Proposals Awaiting Input: 2015-04, "RIPE Resource Transfer Policies" 2016-01, "Include Legacy Internet Resource Holders in the Abuse-c Policy" Proposal Overviews: PROPOSAL: 2015-05, "Revision of Last /8 Allocation Criteria" OVERVIEW: Aims to allow LIRs to request an additional /22 IPv4 allocation from the RIPE NCC every 18 months. The latest version of the proposal suggests several requirements, such as the LIR cannot hold more than a /20 IPv4, must document their IPv6 deployment and has not transferred any IPv4 address space before. STATUS: Discussion Phase WHERE TO COMMENT: Address Policy Working Group: address-policy-wg(a)ripe.net DEADLINE: 13 May 2016 FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2015-05 ===== The following proposals are awaiting input before they can go any further in the PDP. PROPOSAL: 2015-04, "RIPE Resource Transfer Policies" OVERVIEW: Aims to create a single transfer policy with all relevant information on the transfer of Internet number resources, replacing text in several RIPE Policies. The proposal also introduces a 24-month holding period for IPv4 addresses and 16-bit ASNs after any change of holdership. RIPE NCC IMPACT ANALYSIS: Includes the point how the 24-month holding period for scarce resources will be applied. STATUS: Review Phase – Awaiting decision from working group chair FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2015-04 PROPOSAL: 2016-01, "Include Legacy Internet Resource Holders in the Abuse-c Policy" OVERVIEW: Aims for a mandatory abuse contact for Legacy Internet Resource holders in the RIPE Database. STATUS: Discussion Phase – Awaiting decision from proposer FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2016-01 The RIPE NCC provides an overview of current RIPE Policy Proposals on www.ripe.net: https://www.ripe.net/participate/policies/current-proposals/current-policy-… We look forward to your involvement in the PDP. Kind regards, Marco Schmidt RIPE Policy Development Officer RIPE NCC

1 0

[news] RIPE-NCC-RPSL-MNT removed from "mnt-by:" on objects
by Tim Bruijnzeels 28 Apr '16

28 Apr '16

Dear Colleagues, As you may know, the RIPE-NCC-RPSL-MNT is used to authorise the creation of out-of-region AUT-NUM and ROUTE(6) objects. This maintainer has a well-known password so that anyone can create such objects in the RIPE Database. For the time being this maintainer is still used to authorise the creation of out-of-region objects, but the community has recognised that this model should be improved, and discussion on this topic is on the agenda of the coming RIPE Meeting. However, the RIPE NCC was instructed by the RIPE Database Working Group to limit the use of this maintainer on "mnt-by:" as a first step of improvement. The RIPE Database documentation as well as the "descr:" of this maintainer have always instructed that this maintainer should not be used on "mnt-by:", because it leaves objects vulnerable to hijacking by any database user. Therefore, as part of release 1.86 of the RIPE Database that was deployed to production on 21 March 2016, the RIPE NCC introduced a business rule that prevents the use of this maintainer on "mnt-by:" of new objects. As agreed with the RIPE Database Working Group, the RIPE NCC also removed RIPE-NCC-RPSL-MNT from "mnt-by:" on 13,630 existing objects on 25 April 2016. Holders of these objects were sent individual emails about the pending removal of this maintainer on 12 April 2016, and notifications about the update were sent. Of the objects affected, 2,571 objects did not have any other maintainer, and as a result these objects are now locked. The legitimate holder of the resources of these objects can contact ripe-dbm(a)ripe.net in case the objects need to be unlocked. Now that these changes are complete, there are no remaining objects in the RIPE Database that are vulnerable to hijacking because of the use of this maintainer, and no new cases can be introduced. We did not send an earlier general warning about this change to ncc-announce because in our judgement this would have given too much exposure to how these objects could be hijacked by any user. Kind regards Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC Database Group

1 0

[GM] Reminder: Executive Board Nominations Deadline Approaching
by Axel Pawlik 20 Apr '16

20 Apr '16

Dear RIPE NCC member, This is a reminder that the RIPE NCC is calling for nominations to the RIPE NCC Executive Board. The deadline for submitting nominations is *4 May 2016*. The election will be for two vacant seats and will take place at the RIPE NCC General Meeting (GM) from 25-27 May 2016. The seats are for three-year terms and are to fill the places currently held by Remco van Mook and Nigel Titley, whose terms expire in May 2016. All information relating to the Executive Board nominations process is available in the original announcement at: https://www.ripe.net/participate/meetings/gm/meetings/may-2016/call-for-nom… The form for making nominations or supporting a candidate is available at: https://www.ripe.net/participate/meetings/gm/meetings/may-2016/agm-nominati… Currently, there are three confirmed candidates for the election: https://www.ripe.net/participate/meetings/gm/meetings/may-2016/confirmed-ca… GM Participation ---------------- To take part in the GM and cast your vote in the election and on the resolutions, you need to register via the LIR Portal: https://www.ripe.net/participate/meetings/gm/meetings/may-2016/registration The supporting documents for the GM are published at: https://www.ripe.net/participate/meetings/gm/meetings/may-2016/supporting-d… The draft agenda for the GM contains the items to be discussed and voted on at the meeting: https://www.ripe.net/participate/meetings/gm/meetings/may-2016/agenda The RIPE NCC and its Executive Board encourage all members to participate in the GM and to make their voice heard by voting in the election and on the resolutions. If you have any questions about the GM, please email us at <agm(a)ripe.net>. Best regards, Axel Pawlik Managing Director RIPE NCC Important Dates 23 March - Call for nominations to RIPE NCC Executive Board 30 March - Open registration for GM 30 March - Open voting registration 13 April - Publish all GM documents, including RIPE NCC Annual Report and Financial Report 2015 4 May - Close nominations for Executive Board elections 11 May - Deadline for proxy vote nominations 11 May - Deadline for members to propose resolutions 11 May - Deadline to publish final GM agenda 25 May - Close registration for electronic voting 25 May - GM begins with main meeting 27 May - GM closes with votes announcement

1 0

[news] RIPE Database: Cleaning-up Organisation Names in "descr:"
by Tim Bruijnzeels 19 Apr '16

19 Apr '16

Dear colleagues, We want to let you know about a clean-up that we have been planning with the RIPE Database Working Group (WG) and explain why this is being done. As this is currently being discussed on the WG mailing list, there is still time to comment if you wish. Background ---------------- For a long time, there has been a requirement that the first "descr:" attribute of resource objects that were allocated/assigned by the RIPE NCC must match the name of the organisation that holds the resource. However, these resource objects have also had a reference to the organisation object of the holder of these resources for quite some time, and the RIPE NCC ensures that this organisation object matches what we have in the RIPE Registry. This means that we have been using two parallel approaches to achieve the same goal. Since we began using organisation objects, requiring the organisation name in the “descr:” attribute has become redundant. It creates the potential for a mismatch between the name recorded here and the name on the actual organisation object. It also leads to confusion about where the correct name of the organisation can be found, along with a number of other issues. This has been discussed at length on the RIPE Database WG mailing list and during WG sessions at RIPE 70, 71 and 72. Consensus was reached that going forward: - Organisation names should no longer be enforced in "descr:" attributes - LIRs should be allowed to modify the "descr:” attribute[1] and will be responsible for maintaining this (it will not be verified by the RIPE NCC) - The RIPE NCC should clean up existing cases where the organisation name is enforced - "descr:” should become an *optional* attribute Last Week’s Reverted Clean-up ------------------------------------------ The WG decided that a clean-up was needed to remove any confusion about where the organisation name should be found. Because there are 93,105 objects that need to be updated, it is not practical to send notifications to all of these resource holders individually. As this change was expected to have little operational impact, it was decided that this should be done as a silent update. However, while the WG was informed of our intention to run the clean-up, it was an oversight on our part not to send a notification to the wider RIPE community. We proceeded with our implementation of these changes in the RIPE Database and deployed release 1.86 to production on 21 March. We then communicated our intent to run the clean-up on 11 April to the Database WG[2]. When we ran the update last week, a community member alerted us to a problem and the clean-up was reverted the following day after it was completed[3]. There is now a discussion about how or whether to continue with this clean-up on the RIPE Database WG mailing list[4]. If the WG determines that we should proceed with this, we have a tentative date set for 9 May 2016. We invite you to discuss this further on the mailing list at <db-wg(a)ripe.net> if you have any opinions or concerns that you would like to share. We will also be reviewing our processes to ensure we give adequate notification for such changes in the future. Kind regards, Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC Database Group [1] "descr:" is currently not editable in the Allocation Object Editor, but will become editable by LIRs in the near future. [2] https://www.ripe.net/ripe/mail/archives/db-wg/2016-March/005136.html [3] https://www.ripe.net/ripe/mail/archives/db-wg/2016-April/005172.html [4] https://www.ripe.net/ripe/mail/archives/db-wg/2016-April/005173.html

1 0

[news] 105th RIPE NCC Executive Board Meeting Summary
by Axel Pawlik 14 Apr '16

14 Apr '16

Dear colleagues, The RIPE NCC Executive Board held its 105th meeting on 31 March 2016. A summary of the meeting minutes is now available: https://www.ripe.net/publications/news/announcements/105th-ripe-ncc-executi… You can give feedback on the minutes by emailing the Executive Board directly at: <exec-board at ripe.net> RIPE NCC members can also discuss matters among the entire membership by emailing: <members-discuss at ripe.net> Kind regards, Axel Pawlik Managing Director RIPE NCC

1 0

[news] RIPE NCC Members and Multiple LIR Accounts - Decisions and Next Steps
by Nigel Titley 14 Apr '16

14 Apr '16

Dear members, The RIPE NCC Executive Board would like to thank the members for their contributions to the discussion on the ability of RIPE NCC members to open additional LIR accounts. The Board initiated this discussion because it was concerned that, contrary to the spirit of the last /8 policy, there was the possibility of people acquiring IPv4 address space by opening multiple LIR accounts with the aim of transferring that address space to another entity. There were many considered and well-thought-out suggestions that represented a diverse range of opinions. Many of the suggestions put forward that could have a positive effect were matters for the Policy Development Process (PDP) to consider rather than the RIPE NCC membership. The Board believes that the matter should be taken up again at the next RIPE NCC General Meeting (GM) to be held on 25 May 2016. At the meeting, the members will be given the opportunity to hear from the Board, have a further discussion and vote on the matter. Until then, the Board resolution to temporarily suspend the ability to create additional LIRs will remain in place. The Board has decided on a measure to be taken immediately to deter the acquiring of /22s of address space with the sole purpose of transferring it to another legal entity. The RIPE NCC will therefore broaden the definition of policy transfers by including network acquisitions in the scope of the transfer policy. Therefore, all network acquisitions will fall under the RIPE transfer policy unless they are part of an organisation merger, organisation acquisition, bankruptcy or liquidation. Resources received following a policy transfer may not be transferred again to another organisation within 24 months, a limitation imposed by the RIPE community policy. This limitation does not apply to resources received through an organisation merger, acquisition, bankruptcy or liquidation. Mergers, acquisitions, bankruptcies and liquidations must be supported by official documentation issued by national authorities (e.g. Chamber of Commerce) whereas policy transfers are based on the RIPE community policies and supported by the transfer agreement signed by both parties. The RIPE NCC will update the "Transfer of Internet Number Resources and Change of a Member’s Official Legal Name" procedure and other relevant procedural documents. We will handle ongoing network acquisition requests using our current procedures for a 28-day period starting from today. All those who have requested a network acquisition will be contacted to make them aware of the situation. The Board has instructed the RIPE NCC to strengthen its due diligence procedures to clarify that transfer agreements are signed by a party that is officially authorised to do so according to national authority registration. We look forward to further discussion of the multiple LIR issue at the upcoming GM. The Board of course encourages you to continue the discussion on the members-discuss mailing list if you so wish. Registration for the upcoming GM is open and we urge all members to register so they can take part in the discussions and exercise their right to vote on this important matter. https://www.ripe.net/participate/meetings/gm/meetings/may-2016 Best regards, Nigel Titley RIPE NCC Executive Board Chairman

1 0

[GM] RIPE NCC Annual Report 2015 and Proposed Charging Scheme 2017
by Serge Radovcic 13 Apr '16

13 Apr '16

Dear members, The RIPE NCC Annual Report 2015, including the Financial Report 2015, is now available online. The Annual Report is a supporting document for the RIPE NCC General Meeting (GM), which takes place from 25-27 May 2016. The supporting documents also include the proposed Charging Scheme 2017 that members will vote on at the upcoming GM. All the documentation, including the Annual Report, is available at: https://www.ripe.net/participate/meetings/gm/meetings/may-2016/supporting-d… You can find out about the GM and the elections, including how to register for voting, at: https://www.ripe.net/participate/meetings/gm/meetings/may-2016 Annual Report Highlights ---------------------------------- The Annual Report documents the activities of the RIPE NCC in 2015 and contains the Financial Report 2015. Some other highlights in the Annual Report include: - Detailed statistics on the RIPE NCC’s allocation and assignment of Internet number resources - Statistics on IPv4, IPv6 and ASN transfers - Maps and statistics showing the various meetings and training courses held across our service region - Address hijacking in 2015 - Updates from the Chairman of the RIPE NCC Executive Board, the Managing Director of the RIPE NCC, the Executive Board Treasurer, and the RIPE NCC Senior Management Team - Much, much more… The Annual Report is only available online. It can be downloaded for those who wish to print it. We hope you take the time to read the report. If you have any feedback on it, please email <agm(a)ripe.net>. Best regards Serge Radovcic Chief Communications Officer RIPE NCC

1 0

[news] Locking unmaintained PERSON and ROLE objects in the RIPE Database
by Trudy Prins 07 Apr '16

07 Apr '16

Dear colleagues, The RIPE NCC Executive Board (EB) endorsed a proposal on how to deal with a vulnerability for RIPE Database users. Following their advice, the RIPE NCC proactively locked 848,986 unmaintained PERSON objects and 1,206 unmaintained ROLE objects on 6 April 2016. Since reaching the last /8, IPv4 address space has become more susceptible to hijacking. Unmaintained PERSON and ROLE objects are highly at risk of being found and hijacked. In addition, unmaintained PERSON and ROLE objects are an issue with regards to data protection obligations. The potential impact of abuse led us to consult with the EB on this intermediary solution before engaging with the community on the next steps. Exposing this issue without taking adequate measures would have left the RIPE NCC liable to third party damages. The proposed solution we outline below is a starting point, to be discussed by the community. Background: =========== Since 2010 it has been mandatory to protect PERSON and ROLE objects in the RIPE Database using a maintainer on "mnt-by:". A large number of PERSON and ROLE objects dating from before 2010 are still not protected in this way. Objects can be created that reference these unmaintained objects, but doing so will generate a warning. In recent years, given the scarcity of IPv4 address space, there is a higher risk of people searching for unmaintained PERSON or ROLE objects in order to pose as a resource holder to sell IPv4 space. In the case of legacy space, this could take place outside the view of the RIPE NCC if the address space is not registered with the RIPE NCC. Proposal: ========= 1) All unmaintained ROLE and PERSON objects are now locked. As the RIPE NCC will not be able to correctly check all claims on unmaintained database objects, unlocking is not available. Offering to unlock these objects could leave the RIPE NCC liable to third party damages if due diligence is not followed. 2) Furthermore, the RIPE NCC modifies the existing warning about referencing unmaintained persons/roles to a similar warning about referencing locked persons/roles. 3a) The locked objects can remain as they are. In time, all locked PERSON or ROLE objects no longer referenced by other objects could be automatically deleted: the current thinking is a 180-day deletion timeout for these locked, unreferenced objects. 3b) If there is an operational need, new PERSON or ROLE objects should be created by the object owners. This solution puts control back into the hands of the object owners. The user can follow the existing process for creating and referencing new objects. If there is a use case for supporting bulk migrations where a reference to a locked PERSON or ROLE object should be replaced, the RIPE NCC can create a wizard in the RIPE Database webupdates section of www.ripe.net <http://www.ripe.net/>. We look forward to your feedback. Kind regards, Trudy Prins Manager Software Engineering RIPE NCC

1 0

[training] Training Course: Exploring RIPE Database API
by Training Services 31 Mar '16

31 Mar '16

Dear colleagues, We are happy to announce that a RIPE NCC training course will take place on Sunday 22 May, before RIPE 72 begins on Monday 23 May, in Copenhagen. This course will focus on using RIPE Database RESTful API to programmatically manipulate RIPE Database objects. The course is free of charge and is open to anyone interested. ---------------- Course details ---------------- Exploring RIPE Database API ---------------- Course goals ---------------- By the end of this course, you will be able to perform operations on object in the RIPE Database using RESTful API. ---------------------------------------- Who will benefit from this course? ---------------------------------------- Anyone managing objects in the RIPE Database and considers automating this process or integrating with other software will find this course useful. --------------- Prerequisites: --------------- - Basic programming experience - Basic knowledge of the RIPE Database ------------------------- Course outline: ------------------------- - RIPE Database Overview - Exploring RESTful API - Using RESTful API - Building simple IPAM ---------------------------- Additional information ---------------------------- - Free of charge - Coffee and lunch will be provided - Delivered by the RIPE NCC’s Training Services ----------------------------------------- Registration for RIPE NCC members ----------------------------------------- Please register via the following page: https://lirportal.ripe.net/training/register/courseCode/LIR20160008 ------------------------------------ Registration for non-members ------------------------------------- Please fill out the following information email it to: <training(a)ripe.net>: - Email: - Course name: - Full name : - Vegetarian: yes/no Be quick - we only have 45 seats available on a first-come, first-served basis! If there is enough interest, we will continue to offer courses on different topics of interest alongside future RIPE Meetings. Kind regards, RIPE NCC Training Services

1 0

[GM] Register for the RIPE NCC General Meeting May 2016
by Axel Pawlik 30 Mar '16

30 Mar '16

Dear RIPE NCC members, On behalf of our Executive Board, I invite you to register for the RIPE NCC General Meeting (GM) May 2016. The membership will discuss important issues at the GM and there will be an election to fill two seats on the Executive Board, so I hope you will all take a few moments to register for this meeting. Find out how to register at: https://www.ripe.net/participate/meetings/gm/meetings/may-2016/registration… The GM will be held on Wednesday, 25 May from 16:00-20:00 UTC+2 at the Tivoli Hotel and Conference Center. All information on the GM is available at: https://www.ripe.net/participate/meetings/gm/meetings/may-2016?pk_campaign=… Registration - Attendance and Voting ------------------------------------- Registration for attendance and voting takes place through the LIR Portal. In order to register, you must be listed as an contact person for your organisation in the LIR Portal. You can register directly by clicking the GM Preferences link in the My LIR section in the LIR Portal: https://www.ripe.net/s/gm-registration-may-2016 Registration for electronic voting will remain open until 16:00 UTC+2 on the day of the GM, 25 May 2016. The window for casting electronic votes will remain open until Friday, 27 May at 09:00 UTC+2. If you have any questions about the registration process, please contact <agm(a)ripe.net>. Proxy Voting ------------ You can be represented by a third party who is not an authorised employee or director of your organisation. If you wish to do this, please fill out the proxy form and send it to us using the details on the form by 11 May 2016. Any proxy form sent to us after this date will not be valid. The proxy form is available at: https://www.ripe.net/participate/meetings/gm/meetings/may-2016/proxy-voting… Executive Board Election ------------------------ There will be an election for two vacant seats at the GM, which are for three-year terms. The seats are to fill the places currently held by Remco van Mook and Nigel Titley, whose terms expire in May 2016. Information on how to nominate a candidate or support a nomination is available at: https://www.ripe.net/participate/meetings/gm/meetings/may-2016/nominations-… All nominations and messages of support are publicly archived: https://www.ripe.net/ripe/mail/archives/agm-nominations/ If you have questions about the GM, please email us at <agm(a)ripe.net>. Best regards, Axel Pawlik Managing Director RIPE NCC Important Dates: 23 March - Call for nominations to RIPE NCC Executive Board 30 March - Open registration for GM 30 March - Open voting registration 13 April - Publish all GM documents, including RIPE NCC Annual Report and Financial Report 2015 4 May - Close nominations for Executive Board elections 11 May - Deadline for proxy vote nominations 11 May - Deadline for members to propose resolutions 11 May - Deadline to publish final GM agenda 25 May - Close registration for electronic voting 25 May - GM begins with main meeting 27 May - GM closes with votes announcement

1 0

[news] RIPE Policy Proposals - March Update
by Marco Schmidt 29 Mar '16

29 Mar '16

Dear colleagues, Here is our monthly overview of open policy proposals and their stage in the RIPE Policy Development Process (PDP). If you wish to join the discussion about a particular proposal, please do so on the relevant working group mailing list. Proposals Open for Discussion: 2016-01, "Include Legacy Internet Resource Holders in the Abuse-c Policy" Proposals Awaiting Input: 2015-05, "Revision of Last /8 Allocation Criteria" 2015-04, "RIPE Resource Transfer Policies" Proposal Overviews: PROPOSAL: 2016-01, "Include Legacy Internet Resource Holders in the Abuse-c Policy" OVERVIEW: Aims for a mandatory abuse contact for Legacy Internet Resource holders in the RIPE database. STATUS: Extended Discussion Phase WHERE TO COMMENT: Anti-Abuse Working Group: anti-abuse-wg(a)ripe.net DEADLINE: 5 April 2016 FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2016-01 ===== The following proposals are awaiting input before they can go any further in the PDP. PROPOSAL: 2015-04, "RIPE Resource Transfer Policies" OVERVIEW: Aims to create a single transfer policy with all relevant information on the transfer of Internet number resources, replacing text in several RIPE Policies. The proposal also introduces a 24-month holding period for IPv4 addresses and 16-bit ASNs after any change of holdership. RIPE NCC IMPACT ANALYSIS: Includes the point how the 24-month holding period for scare resources will be applied. STATUS: Review Phase – Awaiting Decision from Working Group Chair FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2015-04 PROPOSAL: 2015-05, "Revision of Last /8 Allocation Criteria" OVERVIEW: Aims to allow LIRs to request an additional /22 IPv4 allocation from the RIPE NCC every 18 months. This would only be possible if the LIR has not transferred any IPv4 address space before. STATUS: Discussion Phase – Awaiting decision from proposer FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2015-05 The RIPE NCC provides an overview of current RIPE Policy Proposals on www.ripe.net: https://www.ripe.net/participate/policies/current-proposals/current-policy-… We look forward to your involvement in the PDP. Kind regards, Marco Schmidt RIPE Policy Development Officer RIPE NCC

1 0

[GM] RIPE NCC Executive Board - Call for Nominations
by Axel Pawlik 23 Mar '16

23 Mar '16

Dear RIPE NCC member, The RIPE NCC is calling for nominations to the RIPE NCC Executive Board. There will be an election for two vacant seats at the RIPE NCC General Meeting (GM) on 25-27 May 2016, which are for three-year terms. The seats are to fill the places currently held by Remco van Mook and Nigel Titley, whose terms expire in May 2016. The document outlining the RIPE NCC Executive Board functions and expectations is available at: https://www.ripe.net/lir-services/ncc/executive-board/ripe-ncc-executive-bo… All those considering standing for election to the board are advised to read this information. Nominations ----------- A nomination for the appointment of a member of the Executive Board requires the support of at least five members. You must be a RIPE NCC member and a registered LIR contact to nominate a candidate or support a nomination. Nominations and support submissions should include the following information: - Your full name - Your email address - Your organisation - Your LIR RegID - Name of the candidate you wish to nominate/support - Email address of the candidate - Reason for nominating/supporting the candidate Nominations and support submissions must be submitted by Wednesday, 4 May 2016 following the guidelines outlined in article 9 of the RIPE NCC Articles of Association. To make a nomination or support a candidate, you can email the required information to <agm-nominations(a)ripe.net>. Or you can fill out the nomination form available at: https://www.ripe.net/participate/meetings/gm/meetings/may-2016/agm-nominati… Excerpts from the Articles of Association are available at the end of this email. Voting -------- Voting for the appointment of the RIPE NCC Executive Board members will take place at the upcoming GM. The GM will be held on Wednesday, 27 May from 16:00-20:00 (local time UTC+2) at the Tivoli Hotel and Conference Center in Copenhagen adjacent to the RIPE 72 Meeting, which takes place from 23-27 May. The GM begins with presentation of the reports from the RIPE NCC in the RIPE NCC Services Working Group session at 16:00. The formal, members-only section of the GM starts immediately after the RIPE NCC Services Working Group session. Information on the GM is available at: https://www.ripe.net/participate/meetings/gm/meetings/may-2016?pk_campaign=… If you would like to vote but cannot attend the GM, there are two options that enable you to vote in the Executive Board elections: 1. Electronic Voting Registration to vote electronically at the GM will open on 30 March 2016. All RIPE NCC members who are registered contacts will be sent invitations by email to register to vote electronically. If you wish to vote electronically, you must register to do so by 25 May 2016 at 16:00 (local time UTC+2). Please ensure you are listed as a contact person for your organisation in the LIR Portal to ensure you receive the invitation to register. 2. Proxy Voting You can be represented by a third party who is not an authorised employee or director of your organisation. If you wish to do this, please fill out the proxy form and send it to us using the details on the form by 11 May 2016. Any proxy sent to us after this date will not be valid. If you have any questions about the GM, please email us at <agm(a)ripe.net>. Best regards, Axel Pawlik Managing Director RIPE NCC Important Dates 23 March - Call for nominations to RIPE NCC Executive Board 30 March - Open registration for GM 30 March - Open voting registration 13 April - Publish all GM documents, including RIPE NCC Annual Report and Financial Report 2015 4 May - Close nominations for Executive Board elections 11 May - Deadline for proxy vote nominations 11 May - Deadline for members to propose resolutions 11 May - Deadline to publish final GM agenda 25 May - Close registration for electronic voting 25 May - GM begins with main meeting 27 May - GM closes with votes announcement Excerpts from the Articles of Association 8.2 The Executive Board of the Association shall consist of at least three and at most seven natural persons. They shall be members of the Board in a personal capacity and do not have to be Members of the Association. Employees of the Association cannot be appointed members of the Executive Board. 9.1 The members of the Executive Board shall be appointed by the General Meeting from a list of nominees to be drawn up by the Members. A nomination for the appointment of a member of the Executive Board shall need the written support of at least five Members and shall be submitted no later than three weeks before the General Meeting. If the number of nominees exceeds the number of vacancies, the General Meeting shall elect Executive Board members in accordance with Article 18.4.

1 0

[news] IANA Stewardship Transition Moves to Final Phase
by Nick Hyrka 15 Mar '16

15 Mar '16

This message is sent on behalf of the Number Resource Organization (NRO). —————————————————————————————————— IANA STEWARDSHIP TRANSITION MOVES TO FINAL PHASE 11 March 2016, Marrakech, Morocco – An historic proposal for the global community to assume stewardship of the IANA functions, produced after nearly two years of work by the global Internet community, has been delivered to the U.S. Government for its consideration. The proposal would remove U.S. Government oversight over a set of fundamental Internet administrative functions, including management of the global pool of Internet number resources (IPv4 and IPv6 addresses and Autonomous System Numbers), and replace it with a set of arrangements for community-based oversight. The proposal, developed by the IANA Stewardship Transition Coordination Group (ICG), is based on input from three operational communities, including the Internet Number Community (those with an interest in the global management of Internet number resources). The contributions of the Internet Number Community were coordinated via a Consolidated RIR IANA Stewardship Proposal (CRISP) Team made up of community members drawn from each of the five RIR regions. CRISP Team Chair Izumi Okutani said: “The discussions that have taken place over the last two years have been a showcase for the kind of bottom-up, community-driven processes that are a central feature of the Internet Number Community. This approach has been fundamental in making the Internet a truly global resource. It is very satisfying to see the input of so many stakeholders explicitly reflected in the ICG’s proposal, and I believe that the solution presented here successfully meets the needs of the Internet Number Community, and of all IANA stakeholders.” The ICG proposal includes mechanisms for stewardship of the number-related IANA functions, as developed by the Internet Number Community. These mechanisms include a contractual Service Level Agreement signed by the RIRs (as stewards of these functions) and ICANN (as the entity responsible for management of the functions). More information on this aspect of the proposal is available here. While the ICG published the final draft of its proposal in October 2015, elements of the proposal relied upon the adoption of a set of recommendations regarding the accountability of ICANN to its community. These recommendations were developed separately by a Cross Community Working Group on Enhancing ICANN Accountability (CCWG) and were adopted by the ICANN Board at its meeting this week in Marrakech, Morocco. The Board was at that point able to pass on both the ICG and CCWG documents to the National Telecommunication and Information Administration (NTIA), an agency of the U.S. Government. “The events of this week, here at ICANN 55 in Marrakech, represent another significant step in the long process to better operationalize the global community’s shared stewardship of the IANA functions,” said Number Resource Organization Chair and LACNIC CEO Oscar Robles. “We have not reached the end of this process yet, and we respect the attention that the U.S. Government must give to this proposal before making what will be a historic decision. At this point though, we recognize the achievement that this proposal represents: a huge, global community of people from different sectors and stakeholder groups has achieved agreement on a complex plan to achieve something of huge importance. It is something about which we, as a community, should feel justifiably proud, and it is a testament to the effectiveness of the multistakeholder model. The Regional Internet Registries have publicly supported the progressive steps taken by the U.S. Government over the years to reduce its oversight of global Internet administrative functions. Since the NTIA’s announcement in 2014, we have been pleased to help facilitate our communities’ contributions to this important IANA stewardship transition process. We now stand ready to work with ICANN and all of the IANA stakeholders towards full implementation of the ICG and CCWG proposals.” The U.S. Government will now review the proposal to ensure that it meets the criteria set out by the NTIA when they first announced their intention, in March 2014, to pass stewardship of the IANA functions to the global community. If approved, the RIRs and ICANN will continue their work towards implementation of the proposal, which will be completed prior to the expiration of ICANN’s current contract with NTIA in September 2016.

1 0

[news] Simplifying RIPE Registry Updates: Milestone 2
by Alex Band 10 Mar '16

10 Mar '16

Dear colleagues, We have just completed milestone two in our project to make updating the RIPE Registry easier and more efficient for LIRs. In this release, you will now be able to easily select resources you wish to transfer to another party. The wizard will take policy restrictions and exceptions such as Legacy resources into account, ensuring you only submit a request for eligible resources. We encourage everyone to submit feedback on the usability of the new wizard. It is aimed at making the process easier, more structured and less error prone, but that also means some options will be more limited. For example, only the offering party can request a transfer using this workflow. We would like to give you four weeks to submit your feedback. During this time, you can still submit your request using email if the wizard forms a roadblock. We will make small tweaks and improvements to the wizard if needed, after which it will become the only method to submit transfer requests. You can read about this project in more detail on RIPE Labs: https://labs.ripe.net/Members/matt_parker/keeping-the-registry-up-to-date You can find the new request form here: https://my.ripe.net/#/update-registry We will keep you updated as we complete further milestones. If you have any feedback, please don’t hesitate to reply to this email. Kind regards Alex Band Product Manager RIPE NCC

1 0

[news] RIPE NCC Receives /15 from IANA's Recovered Pool
by Andrea Cima 02 Mar '16

02 Mar '16

Dear colleagues, Yesterday, on 1 March 2016, the RIPE NCC and other Regional Internet Registries (RIRs) were each allocated the equivalent of a /15 of IPv4 address space from the Internet Assigned Numbers Authority (IANA). The RIPE NCC received the IPv4 address ranges 45.65.64.0/18, 147.78.0.0/16, 192.144.0.0/18 and 192.145.0.0/17. We are currently adding these to our available pool. Following the exhaustion of IANA's free pool of IPv4 addresses in 2011, when the RIRs received their final /8s, a global policy caused IANA to create a recovered pool of leftover and returned IPv4 address blocks. This policy was ratified by all five RIR communities in 2012 and stated that IANA would begin making equal, periodic allocations from the recovered pool when the first RIR reached a /9 of remaining addresses. This point was reached by LACNIC, the RIR for Latin America and the Caribbean on 20 May 2014, triggering the global policy and the first post-exhaustion allocation from IANA. You can read the global policy here: https://www.icann.org/resources/pages/allocation-ipv4-post-exhaustion-2012-… With the current policy in place, the RIPE NCC will receive one-fifth of any recovered addresses in the pool every six months (every March and September). The RIPE NCC will continue to distribute these according to the current last /8 policy, under which Local Internet Registries (LIRs) may receive a one-time /22 allocation (1,024 addresses). It is important that network operators continue to deploy IPv6 on their networks to ensure the future growth of the Internet. The RIPE NCC's IPv6 Act Now website provides more information about IPv6 deployment: https://www.ripe.net/publications/ipv6-info-centre Andrea Cima Registration Services Manager RIPE NCC

1 0

[meetings] ENOG 11 Registration Now Open
by ENOG 23 Feb '16

23 Feb '16

Dear colleagues, Registration is now open for the ENOG 11/RIPE NCC Regional Meeting in Moscow, 7-8 June 2016. The meeting is free of charge and open to everyone. Register here: http://www.enog.org/meetings/enog-11/registration The ENOG Meeting is an ideal place for network operators in Russia, as well as from other countries of Commonwealth of Independent States and Eastern Europe, to discuss challenges, tools, experiences and best practices in the following areas: Internet development trends - New technologies and applications - Evolution of the Internet ecosystem - Analytics and prediction of Internet development Internet coordination, governance and regulatory practices - Internet-related legislation and its impact, multi-stakeholder model, challenges and opportunities - Public initiatives and projects in the areas of Internet governance and coordination, research and deployment of new technologies Peering and Internet exchange points: - Business, technical and social aspects of peering and interconnection Network operations and security - Operational experience and best current practices, security trends and technologies Key Internet technologies - Real-life IPv6 and DNSSEC deployment experience, trends and statistics Content delivery - Technology, architecture and business models Call for Presentations ---------------------- The ENOG Programme Committee (PC) is now seeking content proposals from the community for the plenary session presentations, panels, workshops and lightning talks. More information is available at: http://www.enog.org/meetings/enog-11/cfp RACI ---- The RIPE Academic Cooperation Initiative (RACI) will cover the meeting ticket, travel and accommodation of academics to present their research at ENOG 11. The deadline to apply is 12 April. Read about the initiative here: https://www.ripe.net/raci ENOG 11 on Twitter and Facebook ------------------------------- Follow #ENOG11 Join the Facebook ENOG Meetings page: https://www.facebook.com/ENOG.org See you in Moscow! Martina de Mas Conference Coordinator RIPE NCC (On behalf of the ENOG Organising Committee)

1 0

[service] Mailing List Technical Issues
by Serge Radovcic 17 Feb '16

17 Feb '16

Dear colleagues, We recently discovered an issue affecting subscriptions to the <ncc-announce(a)ripe.net> mailing list. An error introduced into our automated processes was preventing subscription changes made via the LIR Portal from being reflected on this mailing list. This issue was in effect from 1 September 2015 and has now been resolved. The majority of you will not have been affected by this issue. However, during this time members were prevented from being subscribed and unsubscribed to the mailing list, and any changes that members may have made to their contact email used to receive messages from this list were not processed. These issues have now been resolved and no action is required on your part. A record of all emails sent to <ncc-announce(a)ripe.net> is available in the archives: https://www.ripe.net/ripe/mail/archives/ncc-announce/ All members specifically affected by this issue will receive a separate email. The <members-discuss(a)ripe.net> mailing list was also affected and subscribers to that list have also been notified. No other mailing lists were affected. Timely communications with our members is very important to us, and we sincerely regret this error. We have introduced measures to ensure this doesn’t happen again, and we apologise for any inconvenience this may have caused. Kind regards, Serge Radovcic Chief Communications Officer RIPE NCC

1 0

[news] RIPE NCC Members and Multiple LIR Accounts - Please Discuss
by Nigel Titley 11 Feb '16

11 Feb '16

Dear colleagues, The RIPE NCC Executive Board would like to ask the membership to discuss the issue of RIPE NCC members opening additional LIR accounts. There were comments at the RIPE NCC General Meeting (GM) in November 2015 that members having the ability to open additional LIR accounts, each of which can request a /22 of IPv4 address space, may run against the spirit of the last /8 policy. In light of this, the Board decided to temporarily suspend the ability of RIPE NCC members to open additional LIR accounts. The RIPE NCC began to allocate IPv4 address space from the last /8 policy on 14 September 2012. Since that time the RIPE NCC has allocated more than 8,600 /22s, yet there remains 0.94 of a /8 still in the pool. ACTION REQUIRED: The Board asks the membership to provide their opinion on and discuss the following points: 1. Is the activity of members opening additional LIR accounts a problem that must be prevented? 2. If this activity is a problem that must be prevented, what action should the RIPE NCC take to attempt its prevention? Statistics pertinent to this discussion are available in this article on RIPE Labs: https://labs.ripe.net/Members/laura_cobley/ripe-ncc-members-and-multiple-li… The Board asks that members discuss this issue on the Members Discuss mailing list <members-discuss(a)ripe.net>. The Board will monitor the discussion and will review it at the next Executive Board Meeting on 31 March 2016. Depending on the outcome of that meeting, the Board may propose a resolution for members to vote on at the RIPE NCC General Meeting in May 2016. Best regards, Nigel Titley RIPE NCC Executive Board

1 0

[news] RIPE NCC to start publishing opaque organisation ID in RIR stats
by Tim Bruijnzeels 04 Feb '16

04 Feb '16

Dear colleagues, The format for the RIR Statistics file has been modified by the RIRs: opaque organisation IDs are added to the statistics. The RIPE NCC is now also modifying its statistics to be in line with this change. In order to avoid issues for scripts, the RIPE NCC is rolling out the modification in a phased approach: 9 December 2015: Introduce new format 3 February 2016: New format takes precedence 2 March 2016: Old format deleted The details of the new format and each of the above phases are documented here: ftp://ftp.ripe.net/ripe/stats/RIR-Statistics-Exchange-Format.txt Kind regards, Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC

1 1

[news] RIPE Policy Proposals - February Update
by Marco Schmidt 04 Feb '16

04 Feb '16

Dear colleagues, Here is our monthly overview of open policy proposals and their stage in the RIPE Policy Development Process (PDP). If you wish to join the discussion about a particular proposal, please do so on the relevant working group mailing list. Proposals Open for Discussion: NEW: 2016-01, "Include Legacy Internet Resource Holders in the Abuse-c Policy" 2015-04, "RIPE Resource Transfer Policies" Proposals Awaiting Input: 2015-05, "Revision of Last /8 Allocation Criteria" ===== Proposal Overviews: NEW PROPOSAL: 2016-01, "Include Legacy Internet Resource Holders in the Abuse-c Policy" OVERVIEW: Aims for a mandatory abuse contact for Legacy Internet Resource holders in the RIPE Database. STATUS: Discussion Phase WHERE TO COMMENT: Anti-Abuse Working Group: anti-abuse-wg(a)ripe.net DEADLINE: 26 February 2016 FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2016-01 PROPOSAL: 2015-04, "RIPE Resource Transfer Policies" OVERVIEW: Aims to create a single transfer policy with all relevant information on the transfer of Internet number resources, replacing text in several RIPE Policies. The proposal also introduces a 24-month holding period for IPv4 addresses and 16-bit ASNs after any change of holdership. RIPE NCC IMPACT ANALYSIS: Details how the 24-month holding period for IPv4 addresses and 16-bit ASNs will be applied. STATUS: Review Phase WHERE TO COMMENT: Address Policy Working Group: address-policy-wg(a)ripe.net DEADLINE: 3 March 2016 FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2015-04 ===== The following proposals are awaiting input before they can go any further in the PDP. PROPOSAL: 2015-05, "Revision of Last /8 Allocation Criteria" OVERVIEW: Aims to allow LIRs to request an additional /22 IPv4 allocation from the RIPE NCC every 18 months. This would only be possible if the LIR has not transferred any IPv4 address space before. STATUS: Discussion Phase – Awaiting decision from proposer FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2015-05 The RIPE NCC provides an overview of current RIPE Policy Proposals on www.ripe.net: https://www.ripe.net/participate/policies/current-proposals/current-policy-… We look forward to your involvement in the PDP. Kind regards, Marco Schmidt RIPE Policy Development Officer RIPE NCC

1 0