- ripe-list - mailman.ripe.net

Introducing the RIPE NCC's New Look
by Serge Radovcic 02 Nov '15

02 Nov '15

Dear colleagues, Today the RIPE NCC is unveiling a fresh new look across its website and printed materials, at the heart of which is a new logo. As the RIPE NCC has evolved over time, it became apparent that our old logo, which had not changed much for 20 years, no longer represented everything that the RIPE NCC is and all that we do. During this time, our visual identity was diluted and became scattered as we developed new services, tools and departments that each had their own look and feel. Finally, the old logo was difficult to work with and use across various printed and online media. For these reasons, we decided it was time to update our look with a new design that is modern, easy to work with, and represents our core values, the community we represent, and the services we offer. The new logo was rolled out across the www.ripe.net website earlier this morning and we invite you to take a look. The three hexagons reflect our function as a registry, the services we offer and our coordination role, with the community at the intersection. Also reflected are our core values of transparency, engagement and inclusiveness. If you’re interested in learning more about the background, design process and everything the logo represents, you can read about it in this RIPE Labs article: https://labs.ripe.net/Members/miguel_bastos/the-ripe-nccs-new-look The logos for all of our services and departments, from the RIPE Database to RIPE Atlas to Training Services, are now a variation of the main logo in order to strengthen our visual identity and make it clear that all of these offerings are provided by one organisation. We hope you’ll be just as excited about our new look as we are. Kind regards, Serge Radovcic Chief Communications Officer RIPE NCC

1 0

[news] RIPE Policy Proposals - October Update
by Marco Schmidt 29 Oct '15

29 Oct '15

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: 2015-05, “Revision of Last /8 Allocation Criteria” Proposals Accepted: 2015-03, “Assessment Criteria for IPv6 Initial Allocation Size” Proposals Awaiting Input: 2014-03, “Remove Multihoming Requirement for AS Number Assignments” 2015-04, “RIPE Resource Transfer Policies” Proposal Overviews: NEW 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 WHERE TO COMMENT: Address Policy Working Group: address-policy-wg(a)ripe.net DEADLINE: 18 November 2015 FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2015-05 ===== The following proposal has been accepted since the last update. PROPOSAL: 2015-03, “Assessment Criteria for IPv6 Initial Allocation Size” OVERVIEW: Introduces new criteria for the evaluation of large IPv6 allocation requests. These new criteria are hierarchical and geographical structure and segmentation for security and planned longevity. The current requirements, number of users and extent of infrastructure, are retained. STATUS: Accepted IMPLEMENTATION: Implemented on 7 October 2015 FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2015-03 ===== The following proposals are awaiting input before they can go any further in the PDP. PROPOSAL: 2014-03, “Remove Multihoming Requirement for AS Number Assignments” OVERVIEW: Aims to ease the requirements when requesting an Autonomous System (AS) Number. To this end, the following actions are proposed: - Remove the need for evaluation - Limit the number of AS Numbers per organisation to 1,000 - Require that 16-bit AS Numbers are multihomed after nine months RIPE NCC IMPACT ANALYSIS: Includes the point that it will be the End User that decides if the need for an AS Number is technically reasonable. STATUS: Review Phase - awaiting new proposal version WHERE TO COMMENT: Address Policy Working Group: address-policy-wg(a)ripe.net FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2014-03 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. STATUS: Discussion Phase - awaiting impact analysis* FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2015-04 *The goal of the impact analysis is to provide supporting information to facilitate discussions about the proposal and to outline the proposal’s possible impact if it were to be accepted. ===== 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 18 November at 7:00 and 9:00 (UTC). The remote participation will be available at: https://ripe71.ripe.net/ We look forward to your involvement in the PDP. Kind regards, Marco Schmidt RIPE Policy Development Officer RIPE NCC

1 0

RIPE 71 Agenda Online
by Benno Overeinder 21 Oct '15

21 Oct '15

Dear colleagues, The agenda for RIPE 71 is online, see https://ripe71.ripe.net/programme/meeting-plan/plenary/ Hope to see you in Bucharest, November 16-20 2015. Benno Overeinder RIPE Programme Committee -- Benno J. Overeinder NLnet Labs http://www.nlnetlabs.nl/

1 0

RIPE Programme Committee elections at RIPE 71
by Benno Overeinder 19 Oct '15

19 Oct '15

Dear Colleagues, The RIPE Programme Committee is responsible for recruiting and selecting presentations for the RIPE Meeting Plenary sessions. As the term of two RIPE PC members end, we are looking for new members in 2015 who will be elected by the RIPE community at RIPE 71 in Bucharest. The Charter of the RIPE Programme Committee (https://www.ripe.net/ripe/docs/ripe-pc-charter) provides more information about the composition and roles of the RIPE PC. There are currently two seats up for election to the RIPE PC. Please send nominations, with a biography, statement of interest and photograph, to pc(a)ripe.net. With the RIPE 71 PC elections, nominations can be sent in from today on until Tuesday November 17th, 15:30. We announce the PC elections at the RIPE meeting opening sessions, but interested parties can nominate themselves already. We will close candidate nominations on Tuesday 15:30, and publish the biographies on the RIPE Meeting web site. Candidates (or stand-ins for candidates) can present themselves at the start of the Tuesday 16:00 session. The RIPE PC online voting system will be open from Tuesday November 17th, 16:00 until Thursday November 19th, 17:30, for the community members to cast their votes. The official announcement of the elected RIPE PC members will be on Friday morning at the start of the 11:00 closing plenary session. Questions about the RIPE PC can be sent to pc(a)ripe.net. Kind regards, Benno Overeinder Chair, RIPE PC -- Benno J. Overeinder NLnet Labs http://www.nlnetlabs.nl/

1 0

NRO NC Nominations Deadline
by Axel Pawlik 16 Oct '15

16 Oct '15

Dear colleagues, Today is the deadline for all nominations to the Number Resource Organisation (NRO) Number Council (NC). Please send your nominations to <nominations at ripe.net> by 23:59 UTC today, 16 October 2015. All confirmed nominations will be listed on the RIPE NCC website by 19 October 2015. The election to the NRO NC seat will take place during the Plenary at the RIPE 71 Meeting to be held in Bucharest from 16-20 November 2015. All members of the Internet community who are present at that Plenary may vote in the election. All nominees may submit a written statement in support of their nomination for publication on the RIPE NCC website. Other individuals may express support for nominated individuals by sending an email to <nominations at ripe.net>. Expressions of support will also be published on the RIPE NCC website. To find out more about the NRO NC and the election process, please see: https://www.ripe.net/participate/internet-governance/internet-technical-com… Regards, Axel Pawlik Managing Director RIPE NCC

1 0

Final Reminder: Call for Nominations to the NRO NC
by Axel Pawlik 08 Oct '15

08 Oct '15

Dear colleagues, This is a final reminder of the call for nominations from the RIPE NCC service region to fill one vacant seat on the Number Resource Organization (NRO) Number Council (NC). The three-year term of Dmitry Kohmanyuk ends on 31 December 2015. The election to the NRO NC seat will take place during the Plenary at the RIPE 71 Meeting to be held in Bucharest from 16-20 November 2015. All members of the Internet community who are present at that Plenary may vote in the election. The deadline for nominations is 16 October 2015. Any individual residing within the RIPE NCC service region is eligible for nomination, except Regional Internet Registry (RIR) staff members. Self-nominations are permitted. Please send your nominations to <nominations at ripe.net> by 23:59 UTC on 16 October 2015. All confirmed nominations will be listed on the RIPE NCC website by 19 October 2015. All nominees may submit a written statement in support of their nomination for publication on the RIPE NCC website. Other individuals may express support for nominated individuals by sending an email to <nominations at ripe.net>. Expressions of support will also be published on the RIPE NCC website. To find out more about the NRO NC and the election process, please see: https://www.ripe.net/participate/internet-governance/internet-technical-com… Regards, Axel Pawlik Managing Director RIPE NCC

1 0

Iran and K-root - The Rest of the Story
by Vesna Manojlovic 02 Oct '15

02 Oct '15

Dear colleagues, Dyn Research published an article on K-root recently. Here we would like to augment the picture with data from RIPE Atlas in order to provide a more complete picture of the effect of the K-root node in Iran. Please find the results on RIPE Labs: https://labs.ripe.net/Members/emileaben/iran-and-k-root-the-rest-of-the-sto… Kind regards, Vesna

2 1

Join RIPE Atlas Hackathon - 14-15 November - Bucharest
by Vesna Manojlovic 29 Sep '15

29 Sep '15

Calling all software developers, designers and network operators! The next RIPE Atlas hackathon takes place 14-15 November in Bucharest, right before RIPE 71. We're looking for creative thinkers to help us find new ways to use RIPE Atlas data to monitor networks and troubleshoot issues as well as ways to improve the existing toolset. Is this you? Then we want to hear from you! ----------------------- How to Apply ----------------------- The application form is online at: https://atlas.ripe.net/hackathon/tools-2015/#!application-form *The deadline to apply is Tuesday, 6 October* Successful applicants will: - Work alongside RIPE Atlas engineers - Get to know others in your field - Contribute to the shared code - Exchange knowledge and experience All source code developed during the hackathon will be publicly licensed and available on GitHub, and will be free for the entire community to use. ---------------------- Hackathon details --------------------- Date: 14-15 November 2015 Time: Saturday 09:00-19:00, Sunday 09:00-21:00 (including party) Location: JW Marriott Bucharest Grand Hotel, Bucharest, Romania Applicants will hear back from the jury on 12 October so that travel arrangements can be made on time. Find out more on RIPE Labs: https://labs.ripe.net/Members/becha/join-the-ripe-atlas-tools-hackathon -------------------- Call for Sponsors ------------------- We are still looking for sponsors! Is your organisation interested in supporting our efforts? Please email me promptly and directly – thank you! I look forward to seeing you there! Regards, Vesna

1 0

Last Call for presentations and Draft programme for RIPE 71
by Benno Overeinder 26 Sep '15

26 Sep '15

Colleagues, A list of currently accepted RIPE 71 presentations is now published at: https://ripe71.ripe.net/programme/ There are still few slots remaining for a final RIPE 71 programme and RIPE Programme Committee will accept new proposals until 11 October 2015. This is our last call for you to submit your proposals. You can find the CFP for RIPE 71 below, or at https://ripe71.ripe.net/submit-topic/cfp/, for your proposals for plenary session presentations, tutorials, workshops, BoFs (Birds of a Feather sessions) and lightning talks. Please also note that speakers do not receive any extra reduction or funding towards the meeting fee at the RIPE Meetings. Kind regards, Benno Overeinder RIPE PC Chair https://www.ripe.net/participate/meetings/ripe-meetings/pc ---------------------------------------- Call for Presentations A RIPE Meeting is an open event where Internet Service Providers, network operators and other interested parties get together. Although the meeting is mostly technical, it is also a chance for people to meet and network with others in their field. RIPE 71 will take place from 16-20 November 2015 in Bucharest, Romania. The RIPE Programme Committee (PC) is now seeking content proposals from the RIPE community for the plenary sessions, BoFs (Birds of a Feather sessions), panels, workshops, tutorials and lightning talks at RIPE 71. See the full descriptions of the different presentation formats, https://ripe71.ripe.net/submit-topic/presentation-formats/. Proposals for plenary sessions, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than 11 October 2015. Proposals submitted after this date will be considered depending on the remaining available space in the programme. The PC is looking for presentations covering topics of network engineering and operations, including but not limited to: - IPv6 deployment - Managing IPv4 scarcity in operations - Commercial transactions of IPv4 addresses - Data centre technologies - Network and DNS operations - Internet governance and regulatory practices - Network and routing security - Content delivery - Internet peering and mobile data exchange Submissions RIPE Meeting attendees are quite sensitive to keeping presentations non-commercial, and product marketing talks are strongly discouraged. Repeated audience feedback shows that the most successful talks focus on operational experience, research results, or case studies. For example, presenters wishing to describe a commercial solution should focus on the underlying technology and not attempt a product demonstration. Presenters should indicate how much time they will require. In general, the time allocated for the different presentation formats is as follows: - Plenary presentations: 20-25 minutes presentation with 5-10 minutes discussion - Tutorials: up to two hours (Monday morning) - Workshops: one hour (during evening sessions) to two hours (Monday morning) - BoFs: approximately one hour - Lightning talks: 10 minutes The following general requirements apply: - Proposals must be submitted using the meeting submission system, https://ripe71.ripe.net/submit-topic/submission-form/. - Lightning talks should also be submitted using the meeting submission system (https://ripe71.ripe.net/submit-topic/submission-form/) and can be submitted any time up to and including the meeting week. The allocation of lightning talks will be announced on short notice---in some cases on the same day but often one day prior to the time slot allocated. - Presenters who propose a panel or BoF are encouraged to include speakers from several (perhaps even competing) companies and/or a neutral facilitator. - All presentation proposals will only be considered by the PC if they contain at least draft presentation slides (slides may be updated later on). For panels, proposals must contain a clear description, as well as the names of invited panellists, presenters and moderators. - Due to potential technical issues, presenters/panellists should be physically present at the RIPE Meeting. If you have any questions or requests concerning content submissions, please email pc [at] ripe [dot] net. -- Benno J. Overeinder NLnet Labs http://www.nlnetlabs.nl/

1 0

IANA Review Committee Selection Process - RIPE Community Support
by Hans Petter Holen 24 Sep '15

24 Sep '15

Dear RIPE community, As you may be aware, the proposal for IANA stewardship developed by the CRISP Team (and now incorporated into the IANA Stewardship Transition Coordination Group’s proposal) proposes establishing a community-based Review Committee to assist the RIRs in their periodic review of the IANA numbering services Service Level Agreement. In recent months, the NRO Executive Council circulated a draft charter for this Review Committee, noting that the Review Committee “will comprise 15 members, constituted by: (a) two community appointees from each RIR region (who must not be RIR staff); and (b) one RIR staff from the region (who will be a non-voting member).” The charter also notes that “Each RIR shall appoint their Review committee members by a method of its own choosing.” https://www.nro.net/wp-content/uploads/Review-Committee-Charter-draft-Publi… The RIR Executive Council have indicated that they would like to establish this Review Committee in the coming months (ahead of the IANA stewardship transition), so it is important that the RIPE community come to consensus on how we will select our Review Committee members, and who those members will be. I would like to suggest a solution for your consideration and discussion: we currently have three community representatives on the NRO Number Council, two of which are elected by the community (the third is appointed by the RIPE NCC Executive Board). Acknowledging that the work of the Review Committee will likely be quite limited, I suggest that we appoint the two community-elected NRO Number Council representatives as our representatives to the Review Committee. The third, non-voting member of the Review Committee, who will be a RIPE NCC staff member, would then be appointed by the RIPE NCC Executive Board. I believe that this is a straight forward and efficient proposal that would avoid an extra election process. It is based on our long-standing NRO Number Council process and employing the knowledge and talents of individuals who clearly have the trust of the RIPE community. It is important, however, that the community agree on a method for selecting Review Committee members, so if you support this method I would appreciate that you do so on the RIPE list (ripe-list(a)ripe.net) by Monday, 28 September. If this proposal is not acceptable we will conduct a separate IANA Review Committee selection process that would need to be planned prior to the RIPE 71 in November. I look forward to hearing your thoughts. Kind Regards, -- Hans Petter Holen, RIPE Chair email: hph(a)oslo.net | http://hph.oslo.net

8 9