- ripe-list - mailman.ripe.net

The Ripe Chair
by Hans Petter Holen 17 Oct '18

17 Oct '18

I would like to draw your attention to the ongoing discussion of the RIPE Chair document. The last revision was just to the ripe-chair-discuss list, and you can review the latest version at: https://www.ripe.net/ripe/mail/archives/ripe-chair-discuss/2018-October/000… If you want to paarticipate in the discussion, please join the conversation on the list. https://www.ripe.net/mailman/listinfo/ripe-chair-discuss/ or in the Friday Morning session at the RIPE77 meeting. https://ripe77.ripe.net/programme/meeting-plan/plenary/#fri1 Hans Petter Holen RIPE Chair -- -- Hans Petter Holen Mobile +47 45 06 60 54 | hph(a)oslo.net | http://hph.oslo.net

1 0

RIPE Accountability Task Force Report draft comments
by steve＠nashfamily.me.uk 16 Oct '18

16 Oct '18

1 0

RIPE 77 Highlights - Day 1
by Martina De Mas 16 Oct '18

16 Oct '18

Dear colleagues, RIPE 77 started in Amsterdam yesterday with 815 attendees registered and 635 checked in by the day's end. The highlights of the day are online: https://ripe77.ripe.net/programme/report/monday/ Tuesday's sessions have already begun with a full day of plenary sessions lined up: - VXLAN Security or Injection - EVPN to the Host - Deploying a Disaggregated Network Model using EVPN Technology - BGP Scanner - BGP Communities: Even more Worms in the Routing Can - Routing Attacks in Bitcoin - Why It is Important to Remember Jon Postel - The Human Factors of Security Misconfigurations - Let's Fix the Weakest Link - Innovation and Human Rights in the Internet Architecture – Is Self-Regulation Delivering on its Promise? - RIPE Accountability Task Force Report - Machine Learning with Networking Data - Technical Debt: an Anycast Story Lightning Talks - Results of the Quantum Internet Hackathon - 8 Ways Network Engineers use Snabb - The Sunset of VXLAN Women in Tech Lunch - Starts at 12.30 in the La Camelia restaurant on the ground floor BoF - RIPE Navel Gazing: Who Are We? Who Do We Want To Be? If you can't be here in person, you can participate remotely: https://ripe76.ripe.net/live/main/ And follow #RIPE77 and @RIPEMeeting on Twitter for the latest updates. Kind regards, Martina de Mas Event Organiser RIPE NCC

1 0

RIPE 77 Opens Today
by Martina De Mas 15 Oct '18

15 Oct '18

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

1 0

weird T&Cs for RIPE meetings
by Jim Reid 11 Oct '18

11 Oct '18

Since there doesn’t appear to be a mailing list for RIPE77 attendees, this seems the most suitable place to raise the following. The lovely and efficient NCC meeting staff have sent me (and presumably everyone else) email about practical matters for RIPE77. It contains the following: "You are required to wear your badge during the meeting at ALL times for security purposes.” EH? What “security purposes”? I doubt this badge can protect me from terrorist attack or something dodgy from a nearby frikandel automat. Why are we required to wear badges at all times? When was this rule introduced and who took the decision? Is the next step to have badge goons policing who is allowed to get a coffee or go into the sessions? If a meeting hotel has some silly rule about wearing badges at all times, I would hope we could just say it’s the hotel that’s imposing this nonsense, not RIPE.

8 9

Re: [ripe-list] weird T&Cs for RIPE meetings
by Randy Bush 11 Oct '18

11 Oct '18

>> i try to remember to wear my badge, and high so folk can easily >> pretend they remember my name. > We will do badge checks at the WG microphones! microphones wear badges?

1 0

RIPE 77 Programme Committee Nominations
by Brian Nisbet 05 Oct '18

05 Oct '18

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 Autumn 2018 who will be elected by the RIPE community at RIPE 77 in Amsterdam. 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 77 PC elections can be sent in from today until Tuesday October 16th, 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 (UTC+2), 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 October 16th, 16:00 CEST until Thursday October 18th, 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 19th October, 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, Leslie, Brian and Benno on behalf of the RIPE PC Brian Nisbet Network Operations Manager HEAnet CLG, Ireland's National Education and Research Network 1st Floor, 5 George's Dock, IFSC, Dublin D01 X8N7, Ireland +35316609040 brian.nisbet(a)heanet.ie www.heanet.ie Registered in Ireland, No. 275301. CRA No. 20036270

1 0

Input by the NRO Executive Council on the Public Consultation to Determine the Future Structure of the ASO
by Antony Gollan 27 Sep '18

27 Sep '18

This message is sent on behalf of the Number Resource Organization (NRO) Input by the NRO Executive Council on the Public Consultation to Determine the Future Structure of the ASO Proposed Next Steps In January 2018, the NRO Executive Council responded to the 18 resulting recommendations that were issued following the second independent review of the Address Supporting Organization (ASO) carried out in 2017 by ITEMS International. The last of these Recommendations was that a public consultation be held in each of the five RIR communities to determine the future structure of the ICANN Address Supporting Organization (ASO). The recommended public consultations have been initiated in each RIR community over the past six months, including discussions on mailing lists and at meetings in each of the five regions. The NRO EC have considered results of this process to date, and have distilled the following points as a proposed way forward. 1) While not specifically asked as part of our consultation, there was prevailing view across the communities that the number community’s relationship with ICANN (that which is referred as the ASO relationship) should continue. A significant number of community members suggested that the relationship must be significantly simplified and its focus limited to number community matters. 2) The ASO Review recognised that the number community relationship with ICANN is unlike that of other Supporting Organizations. The number community’s engagement with ICANN serves primarily to facilitate coordination of global Internet number resource policies. It follows that number community representatives be careful in appraising current and future proposed ICANN-related work items, and be prepared to decline those that lie outside this scope. 3) It is clear that the existence of two separate identities (those of the NRO and the ASO) leads to complexity and confusion in the ICANN relationship. The NRO EC will work with the ICANN organisation to determine the viability of consolidating the number community’s participation in ICANN under either the “Number Resource Organization” or the “Address Supporting Organisation”. 4) The number community finds value in the ICANN relationship and in ICANN’s defined role as described above. We support ICANN in continuing to undertake this role, and will support continuing evolution of our relationship, including further changes as needed, as time goes on. The NRO EC provides this statement to the RIR communities in each region as a possible common way forward to aid in their consideration of the future structure of the ASO. Regards Antony Gollan Senior Communications Officer RIPE NCC

1 0

2018-04 Proposal Accepted and Implemented (PDP Clarification)
by Marco Schmidt 26 Sep '18

26 Sep '18

Dear colleagues, Consensus has been reached on 2018-04, "PDP Clarification". This proposal clarified the options available to the Working Group chairs at the end of the Review Phase of the RIPE Policy Development Process (PDP). You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2018-04 The new RIPE Document is called ripe-710 and is available at: https://www.ripe.net/publications/docs/ripe-710 This proposal is implemented with immediate effect. Thank you to everyone who provided input. Kind regards, Marco Schmidt Policy Officer RIPE NCC Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

1 0

2018-04 Review Phase (PDP Clarification)
by Marco Schmidt 24 Sep '18

24 Sep '18

Dear colleagues, Proposal 2018-04, "PDP Clarification" is now in the Review Phase. This proposal aims to clarify the options available to the Working Group chairs at the end of the Review Phase of the RIPE Policy Development Process (PDP). The RIPE NCC has prepared an impact analysis on this latest proposal version to support the community’s discussion. You can find the full proposal and impact analysis at: https://www.ripe.net/participate/policies/proposals/2018-04 And the draft documents at: https://www.ripe.net/participate/policies/proposals/2018-04/draft As per the RIPE Policy Development Process (PDP), the purpose of this four week Review Phase is to continue discussing the proposal, taking the impact analysis into consideration, and to review the full draft RIPE Policy Document. At the end of the Review Phase, the RIPE Chair will determine whether the proposal has reached rough consensus. It is therefore important to provide your opinion, even if it is simply a restatement of your input from the previous phase. We encourage you to read the proposal, impact analysis and draft document and send any comments to <ripe-list(a)ripe.net> before 17 July 2018. Kind regards, Marco Schmidt Policy Officer RIPE NCC Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

11 11