- ripe-list - mailman.ripe.net

NRO NC Election Result
by Ulka Athale 25 Jan '22

25 Jan '22

Dear colleagues, The election to fill one seat on the Number Resource Organization Number Council (NRO NC) / Address Supporting Organization Address Council (ASO AC) from the RIPE NCC service region took place during RIPE 83 (22-26 November 2021). Sander Steffann was elected for a three-year term starting in January 2022. Congratulations Sander! The original announcement made during the Closing Plenary of RIPE 83 can be found here: https://ripe83.ripe.net/archives/video/721/ The announcement posted to the NRO NC webpages can be found here: https://www.ripe.net/participate/internet-governance/internet-technical-com… The full list of NRO NC representatives is available at: https://www.nro.net/about/address-supporting-organization/the-nro-number-co… This announcement should have been sent shortly after the election results were announced. I apologise for this oversight and the delay in informing the list. Kind regards, Ulka Athale Senior Communications Officer RIPE NCC

1 0

RIPE NCC Open House: DNS4EU - 31 January, 13:00 UTC
by Chris Buckridge 25 Jan '22

25 Jan '22

Hi all, The European Commission’s recent launch of a tender process to establish a European public DNS resolver service (“DNS4EU”) has generated significant interest and attention. Reflecting that, the RIPE NCC will hold an ‘Open House’ online discussion next Monday, 31 January from 13:00-14:00 UTC (14:00-15:00 CET). We invite anyone with an interest in this issue to join for an opportunity to exchange insight and perspectives. RIPE NCC staff will provide a background presentation to kick off the discussion. You can find additional information and register for the session here: https://www.ripe.net/participate/meetings/open-house/ripe-ncc-open-house-dn… I look forward to seeing many of you there next Monday! Best regards, Chris Buckridge Advisor to the Managing Director, Global Strategic Engagement RIPE NCC

1 0

On RIPE Labs: The RIPE Chair Team Reports - Planning for 2022
by Mirjam Kuehne 24 Jan '22

24 Jan '22

Dear colleagues, In our first report of the year, as well as taking a look back at some of the highlights of 2021, we're also looking forward to new topics and challenges we as a community are likely to face in the year to come: https://labs.ripe.net/author/mirjam_kuhne/the-ripe-chair-team-reports-plann… Kind regards, Mirjam Kühne & Niall O'Reilly RIPE Chair Team

1 0

Re: [ripe-list] SBAS Operator Survey
by David Hausheer 24 Jan '22

24 Jan '22

Dear RIPE listeners, We'd like to bring to your attention that our Secure Backbone AS (SBAS) Operator Survey is still open and we would be very grateful for your response, which should not take more than 10 minutes of your time. Your answers will greatly help us to assess governance, feasibility and operator incentive aspects related to the deployment of our proposed SBAS architecture. The survey, together with a 3-minute video about SBAS, is available here: https://docs.google.com/forms/d/e/1FAIpQLSc4VCkqd7i88y0CbJ31B7tVXyxBlhEy_zs… Many thanks for your help! Best regards, David Hausheer On 16/12/2021 08:29, perrig(a)gmail.com wrote: > Dear RIPE, > > Knowing how challenging it is to apply new technologies to current > networks, in a collaboration between ETH, Princeton University, and > University of Virginia, we constructed a system that provides security > benefits for current Internet users while requiring minimal changes to > networks. Our design can be built on top of the existing Internet to > prevent routing attacks that can compromise availability and cause > detrimental impacts on critical infrastructure – even given a low adoption > rate. This provides benefits over other proposed approaches such as RPKI > that only protects a route’s origin first AS, or BGPsec that requires > widespread adoption and significant infrastructure upgrades. > > Our architecture, called Secure Backbone AS (SBAS), allows clients to > benefit from emerging secure routing deployments like SCION by tunneling > into a secure infrastructure. SBAS provides substantial routing security > improvements when retrofitted to the current Internet. It also provides > benefits even to non-participating networks and endpoints when > communicating with an SBAS-protected entity. > > Our ultimate aim is to develop and deploy SBAS beyond an experimental > scope. We have designed a survey to capture the impressions of the network > operator community on the feasibility and viability of our design. The > survey is anonymous and takes about 10 minutes to complete, including > watching a brief 3-minute introductory video. > > https://docs.google.com/forms/d/e/1FAIpQLSc4VCkqd7i88y0CbJ31B7tVXyxBlhEy_zs… > > We thank you for helping inform our further work on this project. We will > be happy to share the results with the community. > > With kind regards > Prateek Mittal, Adrian Perrig, Yixin Sun

1 0

Reminder: RIPE community session on proposed revised PDP - 26 January 2022
by Mirjam Kuehne 21 Jan '22

21 Jan '22

Dear colleagues, In case you missed the earlier announcement, here is the link and invitation for the meeting next week. You can find more details about the meeting in my mail from 12 January: https://www.ripe.net/ripe/mail/archives/ripe-list/2022-January/002410.html Kind regards, Mirjam Kühne ========= Topic: RIPE Workshop on revised PDP Time: Jan 26, 2022 16:00 - 17:30 Amsterdam time (UTC+1) Join Zoom Meeting https://ripe.zoom.us/j/98728370455?pwd=RXh5UStFRm9vaXFTMjVFcTJ4UERadz09 Meeting ID: 987 2837 0455 Passcode: 860568 Join by SIP 98728370455(a)zoomcrc.com Join by H.323 162.255.37.11 (US West) 162.255.36.11 (US East) 221.122.88.195 (China) 115.114.131.7 (India Mumbai) 115.114.115.7 (India Hyderabad) 213.19.144.110 (Amsterdam Netherlands) 213.244.140.110 (Germany) 103.122.166.55 (Australia Sydney) 103.122.167.55 (Australia Melbourne) 209.9.211.110 (Hong Kong SAR) 64.211.144.160 (Brazil) 69.174.57.160 (Canada Toronto) 65.39.152.160 (Canada Vancouver) 207.226.132.110 (Japan Tokyo) 149.137.24.110 (Japan Osaka) Meeting ID: 987 2837 0455 Passcode: 860568

1 0

New on RIPE Labs: RIPE NCC Information Security Controls Framework For Cloud Services
by Ivo Dijkhuis 18 Jan '22

18 Jan '22

Dear colleagues, Having shared the final version of our cloud strategy with you last October, we've now published a RIPE Labs article in which we present the RIPE NCC Cloud Security Controls Framework. This is the framework we'll be using to assess whether cloud providers meet the security requirements for our services. The details of how we came up with the framework and how it will be put into effect are available in the article: https://labs.ripe.net/author/ivodijkhuis/ripe-ncc-information-security-cont… If you have any questions or comments, we'd be happy to hear from you. Kind regards, Ivo Dijkhuis Senior Information Security Officer RIPE NCC

1 0

Preparation for RIPE community session on proposed revised PDP - 26 January 2022
by Mirjam Kuehne 12 Jan '22

12 Jan '22

Dear colleagues, As promised, here are some more details in preparation for the online session on the revised version of the PDP that we will hold on 26 January. You can find the zoom link at the end of this email. In April 2021 I sent two mails to this list with a number of concrete questions regarding suggested changes to the PDP. The first mail dealt with general changes to the document: https://www.ripe.net/ripe/mail/archives/ripe-list/2021-April/002203.html The second one focused specifically on the appeals process: https://www.ripe.net/ripe/mail/archives/ripe-list/2021-April/002204.html Please review the questions and reasoning behind the suggested changes laid out in these two emails as this will be the basis for our meeting. For reference, please also note the two documents that led to these suggested changes: - Review of the RIPE Appeals Procedure https://www.ripe.net/publications/docs/ripe-760 - Evolution of the RIPE Policy Development Process https://www.ripe.net/publications/docs/ripe-761 In my mail from 28 October I summarised the changes we made to the PDP based on the suggestions made in April: https://www.ripe.net/ripe/mail/archives/ripe-list/2021-October/002350.html You can find the new draft document at the link below. At the end of this web page, you will see how the new document differs from the current one: https://www.ripe.net/publications/docs/ripe-documents/other-documents/polic… Please let me know if you have any questions. Looking forward to a constructive session. Kind regards, Mirjam Kühne ============= Topic: RIPE Workshop on revised PDP Time: Jan 26, 2022 16:00 Amsterdam time (UTC+1) Join Zoom Meeting https://ripe.zoom.us/j/98728370455?pwd=RXh5UStFRm9vaXFTMjVFcTJ4UERadz09 Meeting ID: 987 2837 0455 Passcode: 860568 Join by SIP 98728370455(a)zoomcrc.com Join by H.323 162.255.37.11 (US West) 162.255.36.11 (US East) 221.122.88.195 (China) 115.114.131.7 (India Mumbai) 115.114.115.7 (India Hyderabad) 213.19.144.110 (Amsterdam Netherlands) 213.244.140.110 (Germany) 103.122.166.55 (Australia Sydney) 103.122.167.55 (Australia Melbourne) 209.9.211.110 (Hong Kong SAR) 64.211.144.160 (Brazil) 69.174.57.160 (Canada Toronto) 65.39.152.160 (Canada Vancouver) 207.226.132.110 (Japan Tokyo) 149.137.24.110 (Japan Osaka) Meeting ID: 987 2837 0455 Passcode: 860568

1 0

Confirmation of subscription
by Jason Larus Limited 12 Jan '22

12 Jan '22

jason.larus(a)gmail.com

1 0

Re: [ripe-list] [Community-Discuss] [arin-ppml] Update on Litigation Between AFRINIC and Cloud Innovation ltd
by Ronald F. Guilmette 31 Dec '21

31 Dec '21

In message <CANanHiw4sexT3NaogQahUedT4qg8x8N_i=bLYrVW01C2MKMSsw(a)mail.gmail.com> Ibeanusi Elvis <ibeanusielvis(a)gmail.com> wrote: >This "sockpuppet" ideology and terminology that has become an excessively >overused irrelevant term in this mailing list. What is wrong with sharing a >link of interest or a link that a member consider relevant to him/herself. >Freedom of expression is always promoted in this community as long as it >does not go out of line. Members of this community including the AFRINIC >organization itself always share updates and links; never have it been >considered an act of being a "Sockpuppet". Lets stop throwing words around >in this community mailing list and create unwanted confusion. Sockpuppetry is not an "ideology". It is a well-established fact of life on the modern Internet, just as "astroturfing" is in real life. If you don't know that then it is because either you are ignorant or else it is because you are pretending to be ignorant. The poster in question is using and was using a fradulent name together with an essentially anonymous gmail account. The name given in the From: header is bogus and is a reference to a non-existant fictitious person, as anyone who simply takes a moment to google the name can readily see. This is fundamentally different from Real People posting to these lists. Real People have histories, known connections, and readily identifiable employers. Sock puppets have none of these things. If you don't like people talking about sock puppets on these mailing lists then perhaps you should, in the first instance, try to get the sock puppets to stop posting garbage and unenlightening recycled company PR blurbs to these mailing lists. Most of us have real work to do, and if we really want to be bombarded by commercial advertisments being written and spread around by specific individual companies, at their request or prompting, and for their benefit, then there are other places where we can seek out that kind of stuff. Regards, rfg

2 1

(no subject)
by Mathanya Ramaboea 27 Dec '21

27 Dec '21

Mathanyawork(a)gmail.com

1 0