- ripe-list - mailman.ripe.net

RIPE 74: Day 1 Report and Day 2 Remote Participation
by Martina De Mas 09 May '17

09 May '17

Dear colleagues, The RIPE 74 Meeting got off to a great start yesterday with two plenary sessions and 520 checked in. The daily meeting report is available at: https://ripe74.ripe.net/programme/report/monday/ The second day has started and you can follow it live at: https://ripe74.ripe.net/live/main/ Kind regards, Martina de Mas Conference Coordinator RIPE NCC

1 0

RIPE 74 Programme Committee Nominations
by Benno Overeinder 08 May '17

08 May '17

Dear Friends and 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 Spring 2017 who will be elected by the RIPE community at RIPE 74 in Budapest. 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. 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. Nominations for the RIPE 74 PC elections can be sent in from today until Tuesday May 9th, 15:30 CEST. We will announce the PC elections at the RIPE meeting opening sessions, but interested parties can nominate themselves from now. We will close candidate nominations on Tuesday at 15:30 CEST, and publish the biographies on the RIPE Meeting web site. Candidates (or their stand-ins) can present themselves at the start of the Tuesday 16:00 CEST session. The RIPE PC online voting system will be open from Tuesday May 9th, 16:00 CEST until Thursday May 11th, 17:30 CEST, for the community members to cast their votes. The total voting numbers may be public. The official announcement of the elected RIPE PC members will be on Friday morning, the 12th May, at the start of the 11:00 CEST closing plenary session. Questions about the RIPE PC can be sent to pc(a)ripe.net. Regards, Brian, Leslie and Benno on behalf of the RIPE PC -- Benno J. Overeinder NLnet Labs http://www.nlnetlabs.nl/

2 1

New on RIPE Labs: 25 Years of the RIPE NCC – The First Hours
by Mirjam Kuehne 08 May '17

08 May '17

Dear colleagues, We're celebrating the 25th anniversary of the RIPE NCC this year. Please find a fun article on RIPE Labs in which Daniel Karrenberg remembers the very first hours of the organisation: https://labs.ripe.net/Members/dfk/25-years-of-the-ripe-ncc-the-first-hours Kind regards, Mirjam Kuhne RIPE NCC

1 0

RIPE Accountability Task Force: Updated Draft Scope and Presentation at RIPE 74
by Filiz Yilmaz 08 May '17

08 May '17

Dear colleagues, The RIPE Accountability Task Force has updated the draft scope based on community feedback (below). We are now seeking your approval on the updated version. In this latest vesion, we have changed the second bullet point from: "Document existing RIPE community structures or processes." to "Assemble a list of existing RIPE community structures or processes." This better reflects the stock-taking activity that we intend to perform. With this, we believe that we have addressed the community's concerns, and we would like to get your blessing by the end of RIPE 74. We would like to avoid wordsmithing this any further and are considering this "last call" for comments. Please share any comments or statements of support on this mailing list before Friday, 12 May. We will also be giving a brief update on the scope and work of the task force at RIPE 74 in Tuesday's Plenary at 9am. There will be plenty of time for comments from the floor, so please attend and give us your feedback. Kind regards RIPE Accountability Task Force Chairs Filiz Yilmaz & William Sylvester ==== *Updated Draft Scope* The RIPE Accountability Task Force agreed to: - Review existing RIPE community structures, documentation and processes to evaluate whether they are accountable and in alignment with RIPE values - Assemble a list of existing RIPE community structures or processes - Identify potential gaps where RIPE accountability could be improved or strengthened - Publish recommendations for the RIPE community - Identify areas where communications efforts or materials may be required The scope of the task force is limited to an examination of the RIPE community.

5 5

RIPE 74 Opens Today
by Martina De Mas 08 May '17

08 May '17

Dear colleagues, RIPE Chair Hans Petter Holen will open the RIPE 74 Meeting in Budapest today at 14:00 local time (UTC +2). If you cannot be at RIPE 74 in person, you can follow the meeting and participate remotely by viewing the live webcast and using the chat facilities here: https://ripe74.ripe.net/attend/about-remote-participation To stay up-to-date with all RIPE Meeting updates, follow us on Twitter: @ripemeeting, #ripe74 Kind regards, Martina Conference Coordinator RIPE NCC

1 0

Announcement: IANA Review Committee 3rd Meeting - Thursday 11 May 2017 at 12:00 PM UTC
by Nick Hyrka 03 May '17

03 May '17

This message is sent on behalf of the Number Resource Organization: Dear Colleagues, This is an invitation to participate as observers of the next IANA Review Committee (IANA RC) teleconference to be held on Thursday 11 May 2017 at 12:00 PM UTC. Webex information is posted below. More information about the IANA RC can be found at: https://www.nro.net/iana-numbering-services-review-committee/ Webex Details IANA RC 3rd Meeting Thursday, May 11, 2017 12:00 pm | UTC | 1 hr Meeting number (access code): 702 512 962 Meeting password: ianarc https://ripencc.webex.com/ripencc/j.php?MTID=m418ee1feded04d86eef9e2d04649d… Join by phone 0800-051-3810 Call-in toll-free number (UK) +44-203-478-5289 Call-in toll number (UK) Global call-in numbers https://ripencc.webex.com/ripencc/globalcallin.php?serviceType=MC&ED=534820… Toll-free calling restrictions https://www.webex.com/pdf/tollfree_restrictions.pdf Regards, German Valdez NRO

1 0

RIPE Policy Proposals - April Update
by Marco Schmidt 26 Apr '17

26 Apr '17

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: 2017-01, "Publish statistics on Intra-RIR Legacy updates" Proposals Accepted: 2016-05, "Synchronising the Initial and Subsequent IPv6 Allocation Policies" Proposals Awaiting Input: 2016-04, "IPv6 PI Sub-assignment Clarification" ====== Proposal Overview: PROPOSAL: 2017-01, "Publish statistics on Intra-RIR Legacy updates" OVERVIEW: The proposal aims to add the requirement that the RIPE NCC publish all changes to the holdership of legacy resources in the existing transfer statistics. STATUS: Discussion Phase WHERE TO COMMENT: Address Policy Working Group: address-policy-wg(a)ripe.net DEADLINE: 24 May 2017 FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2017-01 ====== The following proposal has been accepted: PROPOSAL: 2016-05, "Synchronising the Initial and Subsequent IPv6 Allocation Policies" OVERVIEW: The policy change matches the subsequent IPv6 allocation requirements with the initial allocation requirements. STATUS: Accepted & Implemented FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2016-05 ====== The following proposal is awaiting input before they can go any further in the PDP. PROPOSAL: 2016-04, "IPv6 PI Sub-assignment Clarification" OVERVIEW: The goal of this proposal is to define sub-assignments in IPv6 PI assignments as subnets of /64 and shorter. RIPE NCC IMPACT ANALYSIS: Explains feasibility and possible side effects. STATUS: Review Phase – Rewriting Proposal FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2016-04 ====== The RIPE NCC provides an overview of current RIPE Policy Proposals here: 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 10 May at 7:00 and 9:00 (UTC). The remote participation will be available at: https://ripe74.ripe.net/ We look forward to your involvement in the PDP. Kind regards, Marco Schmidt RIPE Policy Development Officer RIPE NCC Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

1 0

RIPE 74, Budapest, 8-12 May 2017
by Martina De Mas 26 Apr '17

26 Apr '17

Dear colleagues, RIPE 74 is just two weeks away. If you haven’t yet registered, follow this link to secure your place: https://ripe74.ripe.net/register/ ------------------------ Check out the Programme! ------------------------ Interactive meeting programme for the entire week can be found at: https://ripe74.ripe.net/programme/ Monday morning tutorials: https://ripe74.ripe.net/programme/meeting-plan/tutorials/ BoFs: https://ripe74.ripe.net/programme/meeting-plan/bof/ ------- Socials ------- RIPE Meetings are famed for their socials. Here’s what we have planned in Budapest: https://ripe74.ripe.net/programme/social-events/ ------------------------ Sunday RIPE NCC Training ------------------------ On Sunday, 7 May 2017, the RIPE NCC Training Department is organising a full-day Measurements and Tools Training Course. This course is free to attend and takes place at the Sofitel Budapest, which is a one-minute walk from the RIPE 74 meeting location. For more information and to register please visit: https://ripe74.ripe.net/on-site/parallel-events/mat-training/ ----- More information on RIPE 74 can be found at: https://ripe74.ripe.net/ Follow us on Twitter @ripemeeting, hashtag #RIPE74 I look forward to meeting you in Budapest! Best regards, Martina -- Martina de Mas Conference Coordinator RIPE Network Coordination Centre

1 0

RIPE 74 call for late submissions, LTs, and one tutorial and BoF
by Benno Overeinder 14 Apr '17

14 Apr '17

Dear colleagues, Brief version: The RIPE PC invites submissions for plenary, tutorial, BoF and Lightning Talks. Longer version: As distinct from previous RIPE meetings, the RIPE Programme Committee decided to keep two plenary slots open for so-called “late submission”. These plenary slots gives the community the opportunity to submit presentations that report on recent developments, issues, security incidents, etc., that are relevant to the RIPE audience. Independent from the realisation of late submissions, the PC has received a fair amount of high-quality submissions for the first deadline on March 12th. From these submissions, we have selected 14 presentations to complete the RIPE 74 plenary programme and no second CFP with a deadline in April was required. For the tutorials and BoFs we have one slot for each available: - Monday morning, 2 hour tutorial slot - evening, 1 hour BoF slot Also please consider to submit Lightning Talks for the Monday plenary. During the week of the RIPE meeting we will accept LTs for Tuesday and Friday. Please submit your plenary “late submission”, tutorial or BoF submission via the PC submission system, https://ripe74.ripe.net/submit-topic/submission-form/. The deadline for the submissions is *April 26th*. Kind regards, Benno Overeinder RIPE PC Chair https://ripe74.ripe.net/programme/ripe-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 74 will take place from 8-12 May 2017 in Budapest, Hungary. 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 74. See the full descriptions of the different presentation formats, https://ripe74.ripe.net/submit-topic/presentation-formats/. Proposals for plenary sessions, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than 26 April 2017. 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 - Data centre technologies - Network and DNS operations - Internet governance and regulatory practices - Network and routing security - Content delivery - Internet peering and mobile data exchange - Connected Things (aka. Internet of Things - IoT) 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 total for both presentation and any discussion The following general requirements apply: - Proposals must be submitted using the meeting submission system, https://ripe74.ripe.net/submit-topic/submission-form/. - Lightning talks should also be submitted using the meeting submission system (https://ripe74.ripe.net/submit-topic/submission-form/) and can be submitted any time up to and including the meeting week. Allocation of lightning talks will start a few days before the meeting, and will continue throughout the meeting. During the meeting, they may be announced on the day before the talk or even on the same day as the talk. - Lightning talks should also be submitted using the meeting submission system (https://ripe74.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

RIPE Accountability Task Force - Draft Scope
by Filiz Yilmaz 14 Apr '17

14 Apr '17

Dear colleagues, The RIPE Accountability Task Force was formed in October 2016 following a presentation <https://ripe73.ripe.net/archives/video/1248/> at RIPE 73. Since then task force has agreed on a draft scope (below) and published at: https://www.ripe.net/participate/ripe/tf/ripe-accountability-task-force We invite RIPE community members to send any feedback to this mailing list before we consider the scope final. We are currently undertaking a review of the community's procedures, documentation and structures in alignment with the draft scope and we will communicate our progress on this soon too. Please let us know what you think. Kind regards Filiz Yilmaz / William Sylvester RIPE Accountability Task Force Chairs ---- *Draft Scope* The RIPE Accountability Task Force agreed to: - Review existing RIPE community structures, documentation and processes to ensure they are accountable and in alignment with RIPE values - Document existing RIPE community structures or processes where needed - Identify potential gaps where RIPE accountability could be improved or strengthened - Publish recommendations for the RIPE community - Identify areas where communications efforts or materials may be required The scope of the task force is limited to an examination of the RIPE community. ----

4 4