February 2016 - ncc-announce - mailman.ripe.net

[training] RIPE NCC Training Courses April-June 2016
by Training Services 01 Jun '16

01 Jun '16

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 Budapest, Tirana, Manchester, Lisbon, Bologna, Munich, Tallinn, Moscow, Vienna, Valletta, Reykjavik. 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 - RIPE Database Training Course - Basic IPv6 Training Course - DNSSEC Training Course - 2 days Advanced IPv6 Training Course - 2 days BGP Operations and Security Training Course For more information visit: https://www.ripe.net/support/training/courses With kind regards, Rumy Spratley-Kanis Training Services Manager

1 1

[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

[service] The "changed:" attribute will be deprecated from the RIPE Database release on Monday, 1 February 2016
by Tim Bruijnzeels 02 Feb '16

02 Feb '16

Dear colleagues, As requested by the RIPE Database Working Group, the RIPE NCC has been working on deprecating the “changed:” attribute in the RIPE Database. This attribute was used mostly to determine when database objects were last changed, but in practice the attribute was poorly maintained. We are now in the process of replacing the “changed:” attribute by the server-generated attributes “created:” and “last-modified”. We are conducting the replacement in three phases*: 1. (Completed) 28 April 2015 “created:” and “last-modified:” were introduced to all objects 2. (Completed) 13 July 2015 “changed:” became optional for all objects 3. 1 February 2016 “changed:” will be deprecated from all objects When phase 3 is deployed to production we will remove the “changed:” attribute from all objects in the RIPE Database. However, contrary to the earlier plan communicated on this, we will not reject object updates if they include the “changed:” attribute. Instead, we will remove the “changed:” attribute from the object and issue a warning, but accept the remaining object (provided it passed other validation rules). The reason for this is that we still see a large number of updates that include the “changed:” attribute. We expect this number to go down over time when the “changed:” attribute is removed from the object templates, and when the attribute is no longer present on objects that are being updated. We will monitor this carefully over the coming months before implementing stricter regulations concerning the attribute. However, users are still strongly advised to exclude the "changed:" attribute in updates, but rather to rely on "created:" and "last-modified:", or use "remarks:" instead. Phase 3 was deployed to the RIPE Database Release Candidate environment on 22 December, and an announcement was sent to the RIPE Database Working Group along with a request to test the changes and report issues to the RIPE NCC. No issues have been reported so far. If no issues are found over the coming two weeks, it is our intention to deploy this release to production on Monday, 1 February. With this email we also want to make sure that those who are not following the RIPE Database Working Group discussions are aware of this pending change and have an opportunity to run their own tests. Please let us know if you have any comments or concerns, Kind regards, Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC *: https://labs.ripe.net/Members/tim/deprecating-the-changed-attribute-in-the-…

1 1