- ripe-list - mailman.ripe.net

Call for Hosts for RIPE 79
by Martina De Mas 14 Mar '18

14 Mar '18

Dear colleagues, Are you interested in hosting the RIPE 79 Meeting on 21-25 October 2019? We are searching for dependable organisations within the RIPE NCC service region to help us host the RIPE 79 Meeting. The host helps with Internet connectivity, venue scouting, administrative and on-site support, and assists in finding local sponsors. In return, the host organisation enjoys excellent visibility among the RIPE community and the prestige of hosting a RIPE Meeting. Interested? Please find more information at: https://www.ripe.net/participate/meetings/ripe-meetings/call-for-host You can send your proposal by 15 April 2018 to: meeting(a)ripe.net. I look forward to hearing from you, Martina de Mas Conference Coordinator RIPE NCC

1 0

Call for Nominations: Rob Blokzijl Award
by Mirjam Kuehne 09 Mar '18

09 Mar '18

Dear colleagues, To celebrate the memory of Rob Blokzijl, Internet pioneer, founder and Chair of RIPE for 25 years, the Rob Blokzijl Foundation is pleased to invite nominations for the 2018 Rob Blokzijl Award. We will announce the recipient of the award during the RIPE 76 meeting in May 2018. The recipient will be a living person who has made substantial and sustained technical or operational contributions to the development of the Internet in the RIPE NCC service region. We specifically seek nominations of individuals who, in addition to their own contributions, have also supported and enabled others anywhere in the world. You can find more information on the nomination and selection procedure below and also on the following web page: http://rob-blokzijl-foundation.org/call-for-nominations.html Please help us spread the word by sending this call to anyone who may be interested. The 2018 Rob Blokzijl Award Committee Jaap Akkerhuis Eva Frölich Elise Gerich Daniel Karrenberg Niall O'Reilly ================== Nomination and Selection Procedure - Nominations are to be made by the proposer, who may be either the nominee in person or someone else. - Each nomination must include the following material: - The name and contact details of the nominee and those of the proposer (if different) - A statement of whether the nominee is aware that the nomination is being made - A statement, in as much detail as the proposer considers appropriate, setting out how the nominee meets the requirements for the award and a description of the proposer's relationship to the nominee; - A brief summary (no longer than 79 words) of the nominee's contributions, suitable for the award document - A professional biography or curriculum vitae of the nominee - For additional guidance, proposers can refer to the example nomination - Members of the Award Committee and the Foundation Board may not be nominated - Nominations must be submitted before 16 March 2018 23:59 UTC - Nominations should be sent to the following email address: <nominations(a)rob-blokzijl-foundation.org> - The Award Committee will report to the Foundation Board, indicating the selected awardee, as close to 26 March 2017 as possible

1 1

2nd call for presentations RIPE 76
by Benno Overeinder 08 Mar '18

08 Mar '18

Dear colleagues, Please note the approaching deadline of *11 March 2018* for RIPE 76 plenary programme submissions. You can find the CFP for RIPE 76 below or at https://ripe76.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, see the "Speakers" paragraph in CFP for more information. Kind regards, Benno Overeinder RIPE PC Chair https://ripe76.ripe.net/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 76 will take place from 14-18 May in Marseille, France. 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 76. See the full descriptions of the different presentation formats, https://ripe76.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 March 2018*. 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) Speakers Presenters, RIPE Working Group Chairs and the RIPE Programme Committee are required to cover their own costs to attend a RIPE Meeting (meeting ticket, travel and accommodation). We have various ticket options available depending on your needs. In extraordinary circumstances, the RIPE Chair can waive the meeting fee for presenters. These requests are dealt with on a case-by-case basis via pc(a)ripe.net. Also note that, on an individual basis, participants can apply for a RIPE Fellowship to develop their professional or academic career. For more information, please visit: https://www.ripe.net/participate/ripe/ripe-fellowship Submissions Presenters should be clear on whether they wish to submit a presentation for a plenary or working group (WG) session. At present, most working groups will solicit policy proposals, discussion points or other content directly via their mailing lists. If you’re not sure what kind of session you should be presenting at, please visit: https://ripe76.ripe.net/plenary-or-wg/ 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 (during evening sessions) - 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://ripe76.ripe.net/submit-topic/ - Lightning talks should also be submitted using the meeting submission system (https://ripe76.ripe.net/submit-topic/) 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. If you have any questions or requests concerning content submissions, please email pc(a)ripe.net. -- Benno J. Overeinder NLnet Labs https://www.nlnetlabs.nl/

1 0

Re: [ripe-list] RIPE NCC PGP-Key expired
by Andrew de la Haye 05 Mar '18

05 Mar '18

Hi Dominic and all, We are no longer PGP-signing our support emails, although we still accept PGP-authenticated updates to the RIPE Database. When we conducted our assessment, we weren't able to find a ticketing system that met our requirements and supported PGP. As the service was being used by a relatively small number of members, we decided that the benefits of the new ticketing system outweighed the PGP-signing service. It is also worth noting that the RIPE NCC public key was never meant for encrypted communication. It was only used for signing emails. However, we didn't notify members that we would not be PGP-signing our emails any more. This was an oversight on our part, and we would like to apologise for this. Kind regards, Andrew de la Haye Chief Operations Officer RIPE NCC On 01/03/2018 13:20, Dominic Schallert wrote: > Dear colleagues, > > we noticed that the PGP-Key for ncc(a)ripe.net <mailto:ncc@ripe.net> (Key > ID: C6839AEF) has expired > on the 2nd of February 2018. As of writing, no new public keys have been > published > over at https://www.ripe.net/manage-ips-and-asns/contact/ripe-ncc-pgp-keys > > Looking ahead to the rollout of the EU GDPR in May 2018, it might be > beneficial to > allow for PGP-encrypted communication between LIRs and RIPE NCC, besides > the existing PGP-based database authentication mechanism. > > Kind Regards > Dominic Schallert > > > *schallert.com e.U.* | Hauptstraße 35b, 6800 Feldkirch, Austria > > FN: 440372g | UID: ATU66209211 | Gerichtsstand: Feldkirch > > Tel.: +43 680 146 1947 | Fax: +43 134 242 642 616 > > www.schallert.com <http://www.schallert.com> | office(a)schallert.com > <mailto:office@schallert.com> > > > > > >

1 0

RIPE 76 Meeting - Upcoming Deadlines!
by Martina De Mas 05 Mar '18

05 Mar '18

Dear colleagues, RIPE 76 takes place at the Palais du Pharo in Marseille from 14-18 May 2018. If you haven’t yet registered, follow this link to secure your place: https://ripe76.ripe.net/register ------------ Discount Hotel Rooms ------------ The discounted rate on the selected hotels rooms will expire on 13 March, so make your booking soon! You can find booking information on the RIPE 76 hotel options here: https://ripe76.ripe.net/venue/accommodation ------------ Programme ------------ The draft meeting plan is available online: https://ripe76.ripe.net/programme/meeting-plan The RIPE Programme Committee is now seeking content proposals from the community for the plenary session presentations, panels, workshops and lightning talks at RIPE 76. *Please submit your presentation proposals by 11 March*: https://ripe76.ripe.net/submit-topic/cfp RIPE 76 socials provide great opportunities to network with other attendees. You can check out the socials we have organised at: https://ripe76.ripe.net/programme/social-events ------------ RIPE Fellowship ------------ The RIPE NCC will cover travel, accommodation, and full-week meeting ticket including the RIPE Dinner for selected candidates. The fellowship is open to anyone within the RIPE NCC service region - including RIPE NCC members. Apply before 6 April: https://ripe76.ripe.net/attend/ripe-fellowship ------------ New! On-site Childcare ------------ We are piloting on-site childcare at RIPE 76 to make it easier for parents to fully participate in the meeting. Space is limited, so please reserve your spot ASAP: https://ripe76.ripe.net/on-site/on-site-childcare/ ------------ More information on RIPE 76 can be found at: https://ripe76.ripe.net/ Follow us on Facebook and Twitter: @ripemeeting, #RIPE76 Best regards, Martina de Mas Conference Coordinator RIPE NCC

1 0

Re: [ripe-list] RIPE NCC PGP-Key expired
by Shane Kerr 02 Mar '18

02 Mar '18

Dominic, Dominic Schallert: > > we noticed that the PGP-Key for ncc(a)ripe.net <mailto:ncc@ripe.net> (Key > ID: C6839AEF) has expired > on the 2nd of February 2018. As of writing, no new public keys have been > published > over at https://www.ripe.net/manage-ips-and-asns/contact/ripe-ncc-pgp-keys > > Looking ahead to the rollout of the EU GDPR in May 2018, it might be > beneficial to > allow for PGP-encrypted communication between LIRs and RIPE NCC, besides > the existing PGP-based database authentication mechanism. Thanks for noticing this and bringing it up. One might say that since you are the first to notice and report this, almost a month after it expired, perhaps we should abandon PGP as a communication mechanism? Maybe we should ask the RIPE NCC to provide a more modern secure channel to communicate with them, such as Signal or some other open source encryption technology? Cheers, -- Shane

5 4

RIPE NCC PGP-Key expired
by Dominic Schallert 01 Mar '18

01 Mar '18

Dear colleagues, we noticed that the PGP-Key for ncc(a)ripe.net <mailto:ncc@ripe.net> (Key ID: C6839AEF) has expired on the 2nd of February 2018. As of writing, no new public keys have been published over at https://www.ripe.net/manage-ips-and-asns/contact/ripe-ncc-pgp-keys <https://www.ripe.net/manage-ips-and-asns/contact/ripe-ncc-pgp-keys> Looking ahead to the rollout of the EU GDPR in May 2018, it might be beneficial to allow for PGP-encrypted communication between LIRs and RIPE NCC, besides the existing PGP-based database authentication mechanism. Kind Regards Dominic Schallert schallert.com e.U. | Hauptstraße 35b, 6800 Feldkirch, Austria FN: 440372g | UID: ATU66209211 | Gerichtsstand: Feldkirch Tel.: +43 680 146 1947 | Fax: +43 134 242 642 616 www.schallert.com <http://www.schallert.com/> | office(a)schallert.com <mailto:office@schallert.com>

1 0

Register now for SEE 7 in Timișoara
by SEEurope 27 Feb '18

27 Feb '18

Dear colleagues, Join us for the seventh South East Europe (SEE 7)/RIPE NCC Regional Meeting in the historical Romanian city of Timișoara. SEE 7 will be held in Hotel Timișoara on 18 and 19 June 2018. The meeting is open to everyone and attendance is free of charge. Register for your place: http://www.ripe.net/see-7/register Top three reasons to join SEE 7: - Network with your peers and make new business contacts - Learn about best practices in your industry - Share your experience and ask advice from industry experts This meeting covers a wide range of topics, including: - IPv4 scarcity and IPv6 deployment - Commercial transactions of IPv4 addresses - Data centre technologies - Network, DNS and IXP operations - Internet governance and regulatory practices The SEE Programme Committee is now seeking content proposals from the community for the plenary session presentations, panels, workshops and lightning talks at SEE 7. Please submit your presentation proposals by 16 March: https://www.ripe.net/see-7/call-for-presentations Are you a talented Internet technology researcher? Are you working on interesting research? Apply for RACI before 4 March - it's open now! https://www.ripe.net/see-7/ripe-academic-cooperation-initiative-raci Complete information about the meeting can be found at: http://www.ripe.net/see-7 I look forward to seeing you in Timișoara! Best regards, Martina Conference Coordinator RIPE NCC

1 0

RIPE Fellowship at RIPE 76 - Apply Now
by Amanda Gowland 27 Feb '18

27 Feb '18

Dear colleagues, We are now accepting applications for the RIPE Fellowship at RIPE 76 in Marseille (14-18 May 2018). The RIPE Fellowship covers the cost of a meeting ticket, travel and accommodation for successful candidates in the RIPE NCC service region. *The application deadline is 6 April 2018 at 18:00 UTC* Apply now: www.ripe.net/fellowship To read more about the fellowship, see: https://labs.ripe.net/Members/agowland/embracing-the-next-generation-of-rip… Warm regards, Amanda Gowland On behalf of the RIPE Fellowship Selection Committee

1 0

Re: [ripe-list] Discussion on financial support for RIPE Chair
by Malcolm Hutty 21 Feb '18

21 Feb '18

Alexander Isavnin wrote: > > Support Option 2. > > Option 1 could move RIPE Community to uncomfortable lands of formalized organization, with unspecific for responsibilities Community > > Option 3 might cause conflicts of interests, making RIPE Chair dependent on a bad will of NCC's board or management. Before leaping to conclusions, it might be worth kicking around ideas for how the risks identified in Option 3 might be mitigated. I agree think the risk of loss of independence is a valid concern we should be wary about. I wouldn't agree with someone who was casually dismissive of this as an issue. But Option 3 doesn't *have* to be "the RIPE Chair is employed at will by, and under the direct instructions of, the NCC". With care and thought, I am confident we can do better than that. The main reason why the RIPE Community cannot employ its own Chair is that the Community does not exist as a legal person and so cannot form a contract, either with the Chair or the NCC. However, the Chair *will* be a legal person, and can form (and would) have a contract with the NCC. The terms of this contract could in principle be designed to protect his independence from the NCC, and accountability to the RIPE community. The Chair will himself have an interest defending those terms. For example, perhaps the contract could provide that it may not be terminated by the NCC unless and until some RIPE community process has removed the person as Chair [*]. That might still require us to be a bit more clear what the process in the RIPE community for removal of the Chair should be, but it moves the locus of work to be done back into the community. [*] There may be legal quibbles e.g. "you can't have a commitment to employ someone for an infinite period", but there can be workarounds: make it a fixed term contract of (say) fifty years, which could be terminated early but only under the following conditions...[by the Chair himself, by the RIPE community]. -- Malcolm Hutty | tel: +44 20 7645 3523 Head of Public Affairs | Read the LINX Public Affairs blog London Internet Exchange | http://publicaffairs.linx.net/ London Internet Exchange Ltd Monument Place, 24 Monument Street London EC3R 8AJ Company Registered in England No. 3137929 Trinity Court, Trinity Street, Peterborough PE1 1DA

3 2