- ncc-announce - mailman.ripe.net

[training] RIPE NCC Webinars
by Training Services 26 Jan '15

26 Jan '15

Dear colleagues, The RIPE NCC Training Services Department invites you to register for our Webinars. The RIPE NCC Webinars are live and take only one hour. You can interact with our trainers without leaving your desk. We focus on the topics and issues most important for LIRs. 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 <training(a)ripe.net>. We look forward to seeing you online. Kind regards, RIPE NCC Training Services

1 0

[Service] Resolved Security Issue in LIR Portal
by Ivo Dijkhuis 23 Jan '15

23 Jan '15

Dear colleagues, A security issue in the RIPE NCC LIR Portal was reported to us on Monday, 19 January 2015. This issue allowed authenticated LIR Portal users to potentially access the invoices of other RIPE NCC members. Our investigation has shown that the issue was introduced on Monday morning, the same day it was discovered. A fix for this issue was deployed on Wednesday, 21 January 2015. We found no evidence that the issue was abused. No action is required from LIR Portal users. Measures have been taken to improve our internal software development processes with regard to security. We would like to thank Marco Näf, the RIPE NCC member who reported this issue, allowing us to resolve this issue quickly. Kind regards, Ivo Dijkhuis Information Security Officer RIPE NCC

1 0

[news] RIPE NCC website becoming HTTPS-only
by Mihnea-Costin Grigore 22 Jan '15

22 Jan '15

Dear colleagues, We plan to make the www.ripe.net website available over HTTPS only as of 5 February 2015. We believe this change will provide a more secure, efficient website for our users. Regular visitors to the website will not notice any change (other than "https://" in the website’s URL). A small number of users running scripts against the website could potentially be affected, and may need to update their scripts to run over HTTPS instead of HTTP. Those using very old and unsupported browser versions (such as Internet Explorer 6 running on Windows XP) may no longer be able to access the website. The www.ripe.net website has been available over HTTPS for some time already, and we are now making it HTTPS-only for two reasons: to improve the website’s security, and because we plan to integrate RIPE NCC Access (our single sign-on system) with www.ripe.net as part of our larger website redesign project, which requires us to use HTTPS throughout the site. If you have any questions or comments, please let me know. Regards, -- Mihnea-Costin Grigore RIPE NCC Web Services Team Leader - http://www.ripe.net/

1 0

[news] RIPE Policy Proposals - January Update
by Marco Schmidt 21 Jan '15

21 Jan '15

Dear colleagues, This mail provides a simple overview of open policy proposals and the stage they have reached in the RIPE Policy Development Process (PDP). We will send one of these summary emails every month. By doing so, we hope to make the PDP more accessible to the community and help people keep track of what is being discussed. If you wish to join the discussions about a proposal, please do so on the relevant working group mailing list. If you have feedback on how we can improve these emails, please respond to me directly. Proposals Open for Discussion: 2014-03, “Remove Multihoming Requirement for AS Number Assignments” – Discussion open until 22 January 2015 2014-05, “Policy for Inter-RIR Transfers of Internet Resources” - Discussion open until 9 February 2015 2014-12, “Allow IPv6 Transfers” - Discussion open until 21 January 2015 2014-13, “Allow AS Number Transfers” - Discussion open until 21 January 2015 Proposals at Last Call: 2014-04, “Removing IPv6 Requirement for Receiving Space from the Final /8” – Opinion can be stated until 12 February 2015 2014-06, “Publication of Sponsoring LIR for Legacy Internet Resource Holders” – Opinion can be stated until 13 February 2015 Proposal Overviews: PROPOSAL: 2014-03, “Remove Multihoming Requirement for AS Number Assignments” OVERVIEW: This proposal aims to ease the requirements when requesting an Autonomous System (AS) Number. It is proposed to remove the need evaluation, limit the amount of AS Numbers per organization to 1,000 and require that 16-bit AS Numbers are multihomed after nine months. RIPE NCC IMPACT ANALYSIS: Includes point that it will be the End User that decides if the need for the AS Number is technically reasonable. STATUS: Review Phase WHERE TO COMMENT: The Address Policy Working Group – address-policy-wg(a)ripe.net DEADLINE: 22 January 2015 FULL PROPOSAL: http://www.ripe.net/ripe/policies/proposals/2014-03 PROPOSAL: 2014-05, “Policy for Inter-RIR Transfers of Internet Resources” OVERVIEW: This proposal aims to allow the global transfer of Internet resources. For transfers to the RIPE NCC service region from RIRs that require needs-based policies, recipients must provide the RIPE NCC with a plan for the use of at least 50% of the transferred resources within five years. RIPE NCC IMPACT ANALYSIS: Includes point that the RIRs ARIN (North America) and APNIC (Asia-Pacific) confirmed that the proposed text is compatible with their transfer policies. Currently, the proposed inter-RIR transfer policy would apply to IPv4 PA allocations, IPv4 PI assignments and legacy resources. STATUS: Review Phase WHERE TO COMMENT: The Address Policy Working Group – address-policy-wg(a)ripe.net DEADLINE: 9 February FULL PROPOSAL: http://www.ripe.net/ripe/policies/proposals/2014-05 PROPOSAL: 2014-12, “Allow IPv6 Transfers” OVERVIEW: The goal of this new proposal is to allow the transfer of IPv6 address space within the RIPE NCC service region. RIPE NCC IMPACT ANALYSIS: Includes point that the proposal would allow the transfer of IPv6 allocations and IPv6 Provider Independent (PI) assignments (or parts of them) from the rightfully registered resource holder to a new resource holder. STATUS:Review Phase WHERE TO COMMENT: The Address Policy Working Group – address-policy-wg(a)ripe.net DEADLINE: 21 January FULL PROPOSAL: http://www.ripe.net/ripe/policies/proposals/2014-12 PROPOSAL: 2014-13, “Allow AS Number Transfers” OVERVIEW: The goal of this new proposal is to allow the transfer of AS Numbers within the RIPE NCC service region. RIPE NCC IMPACT ANALYSIS: Includes point that the proposal would allow the transfer of AS Numbers from the rightfully registered resource holder to a new resource holder. STATUS: Review Phase WHERE TO COMMENT: The Address Policy Working Group – address-policy-wg(a)ripe.net DEADLINE: 21 January FULL PROPOSAL: http://www.ripe.net/ripe/policies/proposals/2014-13 ===== The following proposals are in Last Call. Rough consensus was declared and the purpose of this phase is to give the community a final opportunity to present well-justified objections in case anyone wants to oppose the proposal. PROPOSAL: 2014-04, “Removing IPv6 Requirement for Receiving Space from the Final /8” OVERVIEW: Currently, in order to receive a final /22 IPv4 allocation from the RIPE NCC, Local Internet Registries (LIRs) must have an IPv6 allocation in the RIPE NCC service region. This proposal aims to remove this requirement. STATUS: Last Call WHERE TO COMMENT: The Address Policy Working Group – address-policy-wg(a)ripe.net DEADLINE: 12 February FULL PROPOSAL: http://www.ripe.net/ripe/policies/proposals/2014-04 PROPOSAL: 2014-06, “Publication of Sponsoring LIR for Legacy Internet Resource Holders” OVERVIEW: This proposal aims to publish the link between legacy Internet resource holders and their sponsoring Local Internet Registry (LIR). STATUS: Last Call WHERE TO COMMENT: The RIPE NCC Services Working Group – ncc-services-wg(a)ripe.net DEADLINE: 13 February FULL PROPOSAL: http://www.ripe.net/ripe/policies/proposals/2014-06 The RIPE NCC provides an overview of current RIPE Policy Proposals on ripe.net: https://www.ripe.net/ripe/policies/current-proposals/current-policy-proposa… Full information about how the PDP works is available in ripe-614, “Policy Development Process in RIPE”: http://www.ripe.net/ripe/docs/ripe-614 We look forward to your involvement in the PDP. Kind regards, Marco Schmidt RIPE Policy Development Officer RIPE NCC

1 0

[news] Simplifying Contact Management in the LIR Portal
by Laura Cobley 19 Jan '15

19 Jan '15

Dear colleagues, As part of a wider RIPE NCC effort to improve usability for our members, and to make our processes more intuitive and easier to understand, we are planning to improve the way members can manage their contact information in the LIR Portal. In short: - We will reduce the number of LIR Portal user categories from six to three - We will merge the two separate lists of LIR contacts - We will create RIPE NCC Access accounts for LIR contacts who don’t have them - Users in the “Administrator” category will be able to approve/reject the migration of LIR contacts to RIPE NCC Access and into the single list of contacts - We will separate public and private information in the LIR Portal This work forms part of the update to the LIR Portal’s infrastructure, design and functionality as outlined in the RIPE NCC Activity Plan and Budget 2015: http://www.ripe.net/ripe/docs/ripe-630#1-4-lir-portal You can find more details about our approach, including the reasons why we need to carry out this work, in the RIPE Labs article: https://labs.ripe.net/Members/laura_cobley/simplifying-contact-management-i… Please share your feedback by contacting me directly or by emailing ncc-services-wg(a)ripe.net by 1 February 2015. We look forward to your input. Kind regards, Laura Cobley RIPE NCC Customer Services Manager

1 0

[news] Internet Number Community IANA Proposal Published and Submitted
by Paul Rendek 16 Jan '15

16 Jan '15

Dear colleagues, On 15 January, the Consolidated RIR IANA Stewardship Proposal (CRISP) team submitted the Internet numbers community’s proposal on IANA stewardship to the IANA Stewardship Transition Coordination Team (ICG), as requested by the ICG. The proposal is available on the NRO website: https://www.nro.net/news/final-proposal-crisp This submission represents the culmination of discussions in each of the five Regional Internet Registry (RIR) communities, and around six weeks of intense work on the part of the CRISP team (made up of three representatives from each regional community) to consolidate the output from those discussions. This process involved publishing two earlier drafts and incorporating feedback received from the community to produce a final proposal that represents a consensus position of the global Internet numbers community. The key elements of the proposal are: - That the RIRs will establish a binding Service Level Agreement (SLA) with the IANA functions operator concerning provision of IANA services relating to the Internet number registries. - That ICANN will continue in its current role as IANA functions operator to ensure stability and continuity of IANA services, but with mechanisms in place for the Internet number community to change operator, should the need arise. - That a community-based Review Committee will be established to advise the RIRs on the performance of the IANA functions operator. - That all involved parties affirm that all relevant intellectual property rights (including trademarks, domain names and other rights) reside either in the public domain or, where appropriate, with the RIRs or another agreed entity. Over the coming months, the ICG will work to consolidate proposals received from the three affected communities (numbers, names and protocol parameters), with the goal of producing a single proposal on IANA stewardship for the National Telecommunications and Information Administration (NTIA) by the June 2015. Feedback from the global community will be an important element of this process, and regular updates will be posted to the RIPE Cooperation Working Group mailing list. More information on the IANA stewardship transition is available at: https://www.ripe.net/iana-stewardship-transition Best regards, Paul Rendek Director of External Relations RIPE NCC RIPE NCC CRISP Team representative

1 0

Network Maintenance: 17/01/2015 11:00-12:00 (UTC)
by Menno Schepers 14 Jan '15

14 Jan '15

Dear colleagues, On Saturday, 17 December 2015 between 11:00 and 12:00 (UTC), the RIPE NCC will carry out maintenance work on its core network infrastructure. During this period, some services hosted by the RIPE NCC may be affected, including the RIPE NCC website, RIPE Labs, the RIPE Database and the LIR Portal. Public DNS services operated by the RIPE NCC should be available as normal. We apologise for any inconvenience this may cause. If you have any questions, please contact <ops(a)ripe.net>. Kind regards, Menno Schepers Senior Systems Engineer RIPE NCC

1 1

[news] Second Draft of Numbers Community IANA Stewardship Proposal Published
by Paul Rendek 08 Jan '15

08 Jan '15

Dear colleagues, The Consolidated RIR IANA Stewardship Proposal (CRISP) team has published a second draft of the Internet numbers community proposal on the transition of the IANA stewardship. A final call for community feedback has been issued, with the CRISP team planning to submit the finalised proposal to the IANA Stewardship Transition Coordination Group (ICG) on Thursday, 15 January. The second draft of the proposal is available at: http://www.nro.net/crisp-proposal-second-draft There is also a “redline version” that shows all changes made since the first draft: http:/www.nro.net/crisp-proposal-second-draft-change-control The deadline for providing feedback is Monday, 12 January 2015. The CRISP team strongly encourages community members in favour of this proposal to express their support, either via the RIPE Cooperation Working Group mailing list or via the ianaxfer(a)nro.net mailing list, as demonstrated community support may be important later in the IANA stewardship transition process. Some of the key points to note in this second draft: - Additional description on contract details, review committee and intellectual property rights - Description revised on Section V. NITA Requirements and Section VI. Community Process for more clarity - No changes to key elements of the proposal The CRISP team timeline for the coming weeks is as follows: Second draft to be published: 8 Jan 2015 Second draft comments close: 12 Jan 2015 Final proposal to be sent to ICG: 15 Jan 2015 More background on the IANA stewardship transition process is available at: https://www.ripe.net/iana-oversight-transition Details on the CRISP team, including members, timelines and working methods, are available at: https://nro.net/crisp-team Best regards, Paul Rendek Director of External Relations RIPE NCC

1 0

[news] 97th RIPE NCC Executive Board Meeting Summary Notes and Minutes
by Axel Pawlik 07 Jan '15

07 Jan '15

Dear colleagues, The RIPE NCC Executive Board held its 97th meeting on 11 December 2014. The draft minutes of this meeting are now available: https://www.ripe.net/lir-services/ncc/executive-board/minutes/2014/minutes-… The Executive Board publishes the minutes of its meetings so that the workings of the Board and the decisions it makes are transparent for the membership that it represents. The following is a summary of the main items from the meeting. Further details are available in the minutes: - The Board approved several documents: the RIPE NCC Data Protection Report, the RIPE Database Acceptable Use Policy, the IPv4 Transfer Listing Service Terms and Conditions, and the updated Closure Procedure. - The Board agreed to publish its opinion regarding the RIPE NCC Charging Scheme model for 2016 on the RIPE NCC Members Discuss mailing list in order to provide an opportunity for discussion prior to the GM in May 2015. - The Board resolved that members sending notice of termination in October, November or December can have their Standard Service Agreement (SSA) terminated before the end of the year and the annual contribution for the following year will not be due. RIPE NCC Management was asked to implement this decision. - The Board approved the updated RIPE Atlas Terms and Conditions for final publication. - The Board discussed the “Working for the Good of the Internet” initiative, including ideas to further develop RACI and encourage entries from the MENOG community. The Board agreed to support the CrypTech project with an EUR 50,000 donation in 2015. - The Executive Board reviewed the GM and agreed that all future GMs will be transcribed to improve transparency and participation. - The RIPE NCC Executive Board approved the Draft RIPE NCC Activity Plan and Budget 2015. You can find this here: https://www.ripe.net/internet-coordination/news/announcements/ripe-ncc-acti… You can give feedback by emailing the Executive Board directly at <exec-board(a)ripe.net>. RIPE NCC members can also discuss matters among the entire membership by emailing <members-discuss(a)ripe.net>. Kind regards Axel Pawlik Managing Director RIPE NCC

1 0

[news] New management interface for Resource Certification (RPKI)
by Alex Band 06 Jan '15

06 Jan '15

Dear colleagues, Today, we are proud to launch the new management interface for Resource Certification (RPKI): https://certification.ripe.net/ (LIR Portal log-in required) This release marks the third major overhaul of the system since its launch in 2011. All of the user experiences and feedback we received from you since the initial launch have helped shape this new interface. While the previous interface focused on helping new users get started with the system, the new interface incorporates functionality to help existing users solve problems using sensible defaults and best practices. We also managed to simplify the interface even further, reducing it from three pages to one in a fresh new look. You can watch a quick tour of the new interface here: http://youtu.be/gLwHp12wOGw I would like to stress that this release is not the conclusion of our work to improve the RPKI interface. We made a conscious decision to not implement every possible feature but to use this as a foundation to expand the functionality based on your needs and input. For example, a requested feature we would like to incorporate is the ability for users to keep their RIPE Database ROUTE objects synchronised with their ROAs, thereby providing a single location for easy routing management and monitoring. We are eager to hear your feedback on the new interface. User input is vital as we continue to simplify resource management and improve the experience for LIR Portal users. If you have comments or suggestions for improved features, please let me know by responding to this mail or by voicing your opinion on the Routing Working Group mailing list <routing-wg(a)ripe.net>. Kind regards, Alex Band Product Manager RIPE NCC

1 0