- ripe-list - mailman.ripe.net

(no subject)
by Андрей Трубников 05 May '14

05 May '14

1 0

ARIN Reaches Final /8
by Andrew de la Haye 24 Apr '14

24 Apr '14

Dear colleagues, Yesterday, ARIN announced that they reached their final /8 of IPv4 address space and have moved to Phase Four of their IPv4 Countdown Plan. You can find more information on this here: https://www.arin.net/resources/request/countdown_phase4.html With LACNIC also reaching their final /8 earlier in March, four of the five RIRs have now reached this historic milestone. This highlights more than ever the need to move towards full IPv6 deployment. Many big players have already shown their commitment to deploying IPv6, and countless other organisations are also taking these necessary steps. It is encouraging to see that the amount of IPv6 traffic to Google, for example, has more than doubled over the previous year. When we look at the RIPE NCC's own statistics, more than 68% of our members now have an IPv6 allocation: https://labs.ripe.net/statistics/lirs-with-and-without-ipv6 And over 20% of all networks in our service region are currently announcing IPv6 prefixes: http://v6asns.ripe.net/v/6?s=_ALL;s=_RIR_RIPE_NCC The RIPE NCC is committed to IPv6 adoption and encourages all organisations to become IPv6 enabled. To find more information, advice from experts and where to get training, please see: www.IPv6actnow.org Kind regards Andrew de la Haye Chief Operations Officer RIPE NCC

1 0

Update on the IANA Transition Process
by Paul Rendek 17 Apr '14

17 Apr '14

Dear colleagues, As noted in earlier discussions, the National Telecommunications and Information Administration (NTIA), an agency of the U.S. Department of Commerce, has announced that it intends to transfer key Internet domain functions (the IANA functions) to the global multi-stakeholder community. An open process to develop a model for future IANA administration is now underway. The RIPE NCC has published a section on its website that provides background information on the IANA functions, the role of oversight of IANA and the RIPE NCC’s relationship to IANA. The pages also detail the process for development of the future IANA model, and the opportunities for the RIPE community and RIPE NCC membership to contribute: http://ripe.net/iana-transition The RIPE NCC would like to highlight several key points to help stimulate community discussion in this area: - The IANA function covers three separate areas: Internet resources, domain names and protocol assignments on behalf of the IETF. The primary concern for the RIPE NCC is ensuring the continued fair, efficient and stable management of Internet number resources in any future model or arrangement. - The RIPE NCC and the other RIRs actually have relatively few interactions with IANA. We receive allocations of Internet number resources according to global policies developed using the same bottom-up processes as in our regional communities. To date, the U.S. Government’s oversight of IANA has never been exercised to affect IANA operations or policy development relating to Internet number resources. - The RIPE community and the RIPE NCC work together using a well-established model of bottom-up, open and inclusive processes. These attributes, which underpin all RIPE NCC and RIPE community activities, are essential elements of a "multi-stakeholder" model, specified by the NTIA as a requirement for any proposal to move forward. - The RIRs have developed their own robust structures to allow for cooperation and coordination on a global level, most notably through the Number Resource Organization (NRO), which represents all five RIRs working cooperatively. The NRO Number Council, which is comprised of members from the five RIR communities (and which also plays the role of the ICANN Address Supporting Organization Address Council), currently provides oversight of the global policy development process as it pertains to Internet number resources. It is important that the RIPE NCC membership and the RIPE community's voices are heard in these discussions, as key stakeholders in how the global pool of Internet number resources is managed. Following discussion with the co-chairs of the RIPE Cooperation Working Group, we suggest that RIPE community discussion be focused in this working group, both on the mailing list and in RIPE Meeting sessions. This arrangement will allow anyone with an interest to participate or follow discussions, without the need to attend events in person. You can subscribe to the RIPE Cooperation Working Group mailing list at: https://www.ripe.net/ripe/mail/wg-lists/cooperation At RIPE 68 in Warsaw, there will be a discussion on the future of the IANA functions in the Cooperation Working Group session on 15 May (remote participation will be available): https://ripe68.ripe.net/programme/meeting-plan/ There will be opportunities to consider these issues in all RIPE-related venues, including ENOG, MENOG and other regional meetings. The RIPE NCC will also use its Roundtable Meetings to engage with governments and regulators on this topic. Finally, there are channels for global discussion, including the ICANN-hosted mailing list <ianatransition(a)icann.org>: https://mm.icann.org/mailman/listinfo/ianatransition The RIPE NCC will actively participate in the global development process that is being convened by ICANN. The RIPE NCC will be informed and directed by our community and membership on the best way forward with this transition. Kind regards, Paul Rendek Director of External Relations RIPE NCC

1 0

SEE 3 RIPE NCC Regional Meeting Report
by Serge Radovcic 16 Apr '14

16 Apr '14

Dear colleagues, The third South East Europe (SEE 3) RIPE NCC Regional Meeting took place from 14-15 April in Sofia, Bulgaria. The event had an excellent attendance of 229 people, including 135 from Bulgaria. It was also encouraging to see that many attendees from last year's SEE 2 Meeting in Macedonia returned to attend the SEE 3 Meeting. The community in south east Europe has proved to be extremely vibrant and eager to engage with the wider Internet industry. The excellent presentations and lively discussions at SEE 3 were further evidence of this. We would like to thank all who helped to make this such a successful event, particularly meeting co-hosts BIX.BG. RIPE NCC regional meetings are a fantastic way for the organisation to engage with our members and the community, and for those regional communities to let us know what we can do to help them. A full meeting report is available at: https://www.ripe.net/ripe/meetings/regional-meetings/see-3/meeting-report Best regards, Serge Radovcic Chief Communications Officer RIPE NCC

1 0

RIPE 68, 12-16 May 2014, Warsaw: Meeting Information
by RIPE Meeting 15 Apr '14

15 Apr '14

Dear colleagues, RIPE 68 takes place at the Sofitel Warsaw Victoria in Warsaw, Poland from 12-16 May 2014. We are pleased to announce that the RIPE 68 programme is now online! - RIPE 68 Plenary agenda: <https://ripe68.ripe.net/programme/meeting-plan/plenary/> - Two tutorials taking place on Monday morning: <https://ripe68.ripe.net/programme/meeting-plan/tutorials/> - Four BoFs planned during the meeting: <https://ripe68.ripe.net/programme/meeting-plan/bof/> If you haven't registered yet for RIPE 68, you can do so at: <https://ripe68.ripe.net/register> -------------------------- Discount Hotel Rooms -------------------------- Need a hotel in Warsaw? For a limited time, the RIPE 68 venue - Sofitel Warsaw Victoria - offers a discounted rate on the hotel rooms of EUR 127 per night Monday-Thursday and EUR 93 per night Friday-Sunday. The rate includes breakfast, WiFi, VAT and city tax (single occupancy). Deadline for booking is 21 April. You can find booking information and a selection of other hotel options near the meeting venue at: <https://ripe68.ripe.net/venue/hotels> To stay up-to-date, follow us on Twitter: @ripemeeting, #RIPE68 or join the Facebook RIPE Meetings page: <https://www.facebook.com/ripemeetings> See you in Warsaw in May! Best regards, Gergana Petrova Conference Coordinator RIPE NCC

1 0

RIPE 68 Plenary agenda
by Filiz Yilmaz 10 Apr '14

10 Apr '14

Dear colleagues, Please note that RIPE68 Plenary, BoF and Tutorial agendas are now published. https://ripe68.ripe.net/programme/meeting-plan/plenary/ https://ripe68.ripe.net/programme/meeting-plan/bof/ https://ripe68.ripe.net/programme/meeting-plan/tutorials/ See you in Warsaw! Kind regards Filiz Yilmaz Chair, RIPE PC

1 0

RIPE NCC Emergency Maintenance on Core Services
by Brian Riddle 08 Apr '14

08 Apr '14

Dear colleagues, Because of the announced security vulnerability in OpenSSL, the RIPE NCC will carry out emergency maintenance work on our core services between 14:00 and 16:00 (UTC). We apologise for any inconvenience this may cause. If you have any questions, please contact <ops(a)ripe.net>. Kind regards, Brian Riddle IT Manager RIPE NCC

1 0

Best Current Operational Practices TF proposed charter published
by Benno Overeinder 07 Apr '14

07 Apr '14

Hi, The RIPE BCOP Task Force proposed charter is now published on the RIPE TF webpage, see http://www.ripe.net/ripe/groups/tf/best-current-operational-practices-task-…. Comments on proposed charter are welcome on the bcop(a)ripe.net mailing list and the TF meeting in Warsaw. We intend to get the charter approved at the first TF meeting in Warsaw. Best regards, Jan Zorz & Benno Overeinder -- Benno J. Overeinder NLnet Labs http://www.nlnetlabs.nl/

1 0

The RIPE Community and the Evolution of the IANA Functions
by Axel Pawlik 20 Mar '14

20 Mar '14

Dear colleagues, On Friday 14 March, the United States Government announced that it intends to transition oversight of key Internet functions (including the Internet Assigned Numbers Authority, or IANA) to the global multi-stakeholder community. It has asked ICANN to facilitate, in consultation with the global multi-stakeholder community, the development of a proposal for the transition. Leaders of the I* Internet technical coordination organisations met several times and, in line with the Montevideo Statement on the Future of Internet Cooperation (October 2013), we agreed on some common principles for an evolution such as the one announced by the US Government. Regular participants in those meetings, including their affiliated organisations, are noted here: http://www.nro.net/news/statement-from-the-i-leaders-coordination-meeting As an outcome of these discussions, a common position was developed on the following points: - The roles of all Internet registry policy bodies stay unchanged. These bodies continue to hold policy authority for the protocol parameter, number, and name spaces, including responsibility to ensure the faithful registry implementation according to those policies. - The IETF, IAB, and RIRs are committed to the role of ICANN as the IANA protocol parameter and IP address registry operator. - ICANN reaffirms its commitment to implement all IANA registry functions in accordance with the respective policies. ICANN will also provide affirmations to all stakeholders (including governments) that all Internet registry policy bodies and ICANN itself will continue to use open and transparent processes. The full text, agreed upon by the I* leaders, is included at the end of this email. Separately, ICANN released a timeline that details its expectations of the multi-stakeholder consultation process. More information on these plans will undoubtedly come out of the upcoming ICANN Meeting in Singapore (23-27 March). The timeline document is available here: http://www.icann.org/en/about/agreements/iana/functions-transfer-process-14… While this timeline focuses on ICANN meetings and events, it is clear that this process will not take place only in ICANN venues. The five RIR communities are key stakeholders in this process, and it is vital that we discuss these issues both within our regional communities and globally to ensure that our voices are heard and our concerns recognised. The stable, accurate and professional management of the IANA functions, including management of the global IP address pool, is fundamental to the operation of the Internet. It is important that we not lose sight of this fact as management of the IANA evolves to more faithfully reflect the multi-stakeholder nature of the Internet community. In the RIPE community, these discussions will take place via the communication and discussion channels already in place, including the RIPE mailing list, the Cooperation Working Group and RIPE Meetings (including the upcoming RIPE 68 Meeting in Warsaw this May). The RIPE NCC will work, as ever, to facilitate these discussions and ensure that their output is effectively channeled into the global process. If you have any thoughts, comments or questions at this time, I encourage you to raise them on the RIPE mailing list <ripe-list(a)ripe.net> or the RIPE Cooperation Working Group mailing list <cooperation-wg(a)ripe.net>, and I look forward to further discussion at RIPE 68. Best regards, Axel Pawlik Managing Director RIPE NCC ******* Agreed text by the Leaders of I* organisations: In order to ensure global acceptance and affirmation of ICANN's role as administrator of the IANA functions, we are now pursuing the transition of USG's stewardship of the IANA functions from the USG to ICANN. The roles of all Internet registry policy bodies (such as the RIRs, IAB, IETF, ASO, ccNSO, ccTLD Registry Operators, and gNSO) stay unchanged. These bodies continue to hold policy authority for the protocol parameter, number, and name spaces, including responsibility to ensure the faithful registry implementation according to those policies. This transition from the USG has been envisaged since the early days of ICANN. It is now feasible due to the growing maturity of ICANN and other organisations in the Internet ecosystem. ICANN's structures and accountability mechanisms continue to evolve and advance guided by the Affirmation of Commitments (AoC) community reviews, including Accountability and Transparency Review Team (ATRT). In addition, ICANN will continue to embrace its aggressive roadmap to truly globalize its structures. In order to operationalize the transition from USG, ICANN will engage with the Internet community in a bottom-up public consultation process to ensure appropriate accountability mechanisms. In addition, ICANN will work with the names, numbers, and protocol communities to formalize relationships, commitments, and mutual responsibilities. When community stakeholders have input about the policies emanating from the names, numbers, and protocol communities, they would be directed to pursue their interests through the relevant Internet communities (such as the gNSO, ccNSO, ccTLD ROs, ASO, IAB, IETF, or the RIRs) and their mechanisms for consideration and potential redress. The IETF, IAB, and RIRs are committed to open and transparent processes. They also are committed to the role of ICANN as the IANA protocol parameter and IP address registry operator. The accountability mechanisms for ICANN's administration of these core internet functions will provide escalation routes that assure the names, numbers, and protocol communities that if IANA's performance is lacking, those communities can pursue defined processes for improving performance, including pre-agreed independent 3rd party arbitration processes. ICANN reaffirms its commitment to implement all IANA registry functions in accordance with the respective policies. ICANN will also provide affirmations to all stakeholders (including governments) from all Internet registry policy bodies and itself that all of us will use open and transparent processes. -- end --

1 0

Adoption Process for RIPE NCC Corporate Documents
by Axel Pawlik 17 Mar '14

17 Mar '14

Dear colleagues, Following requests from the RIPE community, the RIPE NCC has published the “Adoption Process for RIPE NCC Corporate Documents". This is available online at: http://www.ripe.net/lir-services/ncc/corporate-governance/adoption-process-… If you have any questions, please let us know. Kind regards, Axel Pawlik Managing Director RIPE NCC

1 0